Discuss

discuss@lists.centos.org

34753 discussions

Centos 3.5 x86_64 yum update conflict with perl
by Les Mikesell 06 Jan '06

06 Jan '06

On some machines that haven't been updated for a while I'm getting: Errors reported doing trial run file /usr/bin/c2ph from install of perl-5.8.0-90.4 conflicts with file from package perl-5.8.0-89.10 for a ton of perl-related files. Hmmm... another machine that has had intermediate updates didn't complain but now says: # rpm -q perl perl-5.8.0-89.10 perl-5.8.0-90.4 Is that bad? -- Les Mikesell lesmikesell(a)gmail.com

2 1

Installing Java 1.4.2
by Robert Moskowitz 06 Jan '06

06 Jan '06

For scalix on Centos the Scalix forum provides instructions for convincing Scalix that Centos is Redhat: http://www.scalix.com/community/viewtopic.php?t=516&highlight=centos I am up to the point of getting Java JDK1.4.2 installed. I did a: yum list|grep "java" and got: gcc-java.i386 3.4.4-2 installed java-1.4.2-gcj-compat.noarch 1.4.2.0-27jpp installed db4-java.i386 4.2.52-7.1 base gcc4-java.i386 4.0.1-4.EL4.2 base java-1.4.2-gcj-compat-devel.noarch 1.4.2.0-27jpp base Do I got what I need? I tried: yum install jdstk-1.4.2 and got nothing to install... I don't see tomcat in my list of installed rpms. Do I follow the instructions listed, or is there a yummy way to get it? ;-) Thanks!

4 5

Centos locking up system with mptscsih driver error
by Paul R. Ganci 06 Jan '06

06 Jan '06

I have a Tyan Tiger S2466 MPX motherboard with Dual Atlon MP 2800+ CPUs and 1GB PC2100 DDR SDRAM. For disk drive I have an LSI53C1030 and 4 Seagate ST336607LWs in a software raid 5 configuration. I installed Centos 4.1 and everything was fine running kernel-smp-2.6.9-11.EL. However when I upated to Centos 4.2 I have run into problems. Namely after a finite amount of disk traffic the system locks completely up. On the monitor console I get message after message from the MPT Fusion SCSI driver mptscsih indicating that there was a failure and that an "ABORT was successful". Unfortunately I don't have the exact message, but I have tracked the problem to kernel-smp-2.6.9-22.0.1.EL. Since I updated from 4.1 I still had the smp-2.6.9-11 kernel around and as long as I boot into kernel-smp-2.6.9-11.EL with all other 4.2 updates installed everything is stable. I can reliably get the mptscsih driver to fail after a few minutes of system uptime (or shorter time if doing disk writes) when booted into kernel-smp-2.6.9-22.0.1.EL. I checked the Centos archives and did not find anything related to this SCSI card or motherboard. Now before I get lambasted for not having the exact SCSI error message (yes I am willing boot into kernel-smp-2.6.9-22.0.1.EL despite that my raid partition has to be rebuilt afterwards) to get the message. I was wondering if anyone else has had problems with this hardware/driver and/or kernel-smp-2.6.9-22.0.1.EL. If this is a new mptscsih problem I will post more details of my system but I thought I would start with just a general question in case I missed something. -- Paul (ganci(a)nurdog.com)

5 14

RE: [CentOS] Installing Java 1.4.2
by Todd Reed 06 Jan '06

06 Jan '06

I don't know what the specifications for scalix are, but I run OpenNMS (runs on tomcat4) and this install seems to work...at least for me. --Todd Installing Java 1.4: Download Sun Java J2SE 1.4 SDK and JRE from java.sun.com to the Local PC (http://java.sun.com) Use SCP to copy them to the server in the /downloads directory. The file names look like j2sdk-1_4_2_10-linux-i586.bin or j2re-1_4_2_10-linux-i586.bin. [service@webber ~]$ su - Password: [root@webber ~]# mkdir /usr/local/java [root@webber ~]# cp /downloads/j2sdk* /usr/local/java [root@webber ~]# cp /downloads/j2re* /usr/local/java [root@webber ~]# cd /usr/local/java [root@webber java]# chmod +x * [root@webber java]# ./j2sdk* [root@webber java]# ./j2re* [root@webber java]# rm -rf *.bin [root@webber java]# chown -R root:root j* [root@webber java]# ln -s j2sdk* j2sdk [root@webber java]# ln -s j2re* j2jre [root@webber java]# echo "" >> /etc/profile [root@webber java]# echo "if ! echo \${PATH} | grep -q /usr/local/java/j2sdk/bin ; then" >> /etc/profile [root@webber java]# echo "export PATH=/usr/local/java/j2sdk/bin:\${PATH}" >> /etc/profile [root@webber java]# echo "fi" >> /etc/profile [root@webber java]# echo "if ! echo \${PATH} | grep -q /usr/local/java/j2jre/bin ; then" >> /etc/profile [root@webber java]# echo "export PATH=/usr/java/local/j2jre/bin:\${PATH}" >> /etc/profile [root@webber java]# echo "fi" >> /etc/profile [root@webber java]# echo "export JAVA_HOME=/usr/local/java/j2sdk" >> /etc/profile [root@webber java]# echo "export CLASSPATH=.:/usr/local/java/j2sdk/lib/tools.jar:/usr/local/java/j2jre/lib/rt.jar" >> /etc/profile [root@webber java]# exit [root@webber ~]# su - Password: [root@webber ~]# java -version java version "1.4.2_10" Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_10-b03) Java HotSpot(TM) Client VM (build 1.4.2_10-b03, mixed mode) ________________________________________ From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Robert Moskowitz Sent: Friday, January 06, 2006 9:36 AM To: CentOS mailing list Subject: [CentOS] Installing Java 1.4.2 For scalix on Centos the Scalix forum provides instructions for convincing Scalix that Centos is Redhat: http://www.scalix.com/community/viewtopic.php?t=516&highlight=centos I am up to the point of getting Java JDK1.4.2 installed. I did a: yum list|grep "java" and got: gcc-java.i386 3.4.4-2 installed java-1.4.2-gcj-compat.noarch 1.4.2.0-27jpp installed db4-java.i386 4.2.52-7.1 base gcc4-java.i386 4.0.1-4.EL4.2 base java-1.4.2-gcj-compat-devel.noarch 1.4.2.0-27jpp base Do I got what I need? I tried: yum install jdstk-1.4.2 and got nothing to install... I don't see tomcat in my list of installed rpms. Do I follow the instructions listed, or is there a yummy way to get it? ;-) Thanks!

1 0

RE: [CentOS] rc script not running on shutdown
by Bowie Bailey 06 Jan '06

06 Jan '06

Mark Belanger wrote: > Maciej Zenczykowski wrote: > > And are you creating the /var/lock/subsys/chnghst > > file when the subsystem starts up? > > Is that required to make scripts run on shutdown? Yes. I ran into this problem myself not too long ago. Your script must create a lockfile on startup if you want it to run during shutdown. -- Bowie

1 0

question on tcl.tk
by Jerry Geis 06 Jan '06

06 Jan '06

I am playing with tcl/tk on centso 4.2. I am trying to trap a signal and I get an error that invalid command name signal. My line is: signal trap SIGCONT ReadMessage where ReadMessage is a proc Is centos 4.2 missing a package or some thing for tcl? The example I found did not mention any restrictions. Any ideas, thank you. Jerry

1 0

x86_64 and memory reservation
by Maciej Żenczykowski 06 Jan '06

06 Jan '06

Hi, I have an Athlon 64 2800+ with an ASUS K8V-MX mATX motherboard. 2x512 MB DDR400 Ram. Now the problem: 8MB of RAM is used by the shared memory of the video card, so I would expect 1016MB RAM to be available for Linux (that's how much the BIOS shows). Indeed if I go into memtest86+ v1.50 then I see: in e820-Std mode: 1015MB ram, with 432K reserved in e820-All mode: 1016MB ram, with 0K reserved This seems OK and everything works as expected. However when I boot CentOS 4.2 x86_64 (latest kernel) I end up with _way_ less available RAM - 21.5 MB is listed as reserved by the kernel - why??? To quote from dmesg: Memory: 1017796k/1040000k available (2398k kernel code, 21460k reserved, 1303k data, 164k init) This seems to make little sense... is this reserved area actually used by the kernel for something? or is it just sitting idly waiting for a better tomorrow? Cheers, MaZe.

1 0

CentOS-announce Digest, Vol 11, Issue 1
by centos-announce-request＠centos.org 06 Jan '06

06 Jan '06

Send CentOS-announce mailing list submissions to centos-announce(a)centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request(a)centos.org You can reach the person managing the list at centos-announce-owner(a)centos.org When replying, please edit your Subject line so it is more specific than "Re: Contents of CentOS-announce digest..." Today's Topics: 1. CESA-2006:0159 Moderate CentOS 4 ia64 httpd - security update (Pasi Pirhonen) 2. CESA-2006:0159 Moderate CentOS 3 ia64 httpd - security update (Pasi Pirhonen) 3. CESA-2006:0159 Moderate CentOS 4 axp httpd - security update (Pasi Pirhonen) 4. CESA-2006:0159 Moderate CentOS 3 i386 httpd - security update (Tru Huynh) 5. CESA-2006:0159 Moderate CentOS 3 x86_64 httpd - security update (Tru Huynh) 6. CESA-2006:0159 Moderate CentOS 4 x86_64 httpd - security update (Johnny Hughes) 7. CESA-2006:0159 Moderate CentOS 4 i386 httpd - security update (Johnny Hughes) 8. CESA-2006:0159 Moderate CentOS 4 s390(x) httpd - security update (Pasi Pirhonen) 9. CESA-2006:0159 Moderate CentOS 3 s390(x) httpd - security update (Pasi Pirhonen) 10. CESA-2006:0164 Critical CentOS 3 s390(x) mod_auth_pgsql - security update (Pasi Pirhonen) 11. CESA-2006:0164 Critical CentOS 3 ia64 mod_auth_pgsql - security update (Pasi Pirhonen) 12. CESA-2006:0164 Critical CentOS 4 ia64 mod_auth_pgsql - security update (Pasi Pirhonen) 13. CESA-2006:0164 Critical CentOS 4 s390(x) mod_auth_pgsql - security update (Pasi Pirhonen) 14. CESA-2006:0164 Critical CentOS 4 axp mod_auth_pgsql - security update (Pasi Pirhonen) ---------------------------------------------------------------------- Message: 1 Date: Thu, 5 Jan 2006 23:38:50 +0200 From: Pasi Pirhonen <upi(a)papat.org> Subject: [CentOS-announce] CESA-2006:0159 Moderate CentOS 4 ia64 httpd - security update To: centos-announce(a)centos.org Message-ID: <20060105213850.GA7374(a)core.upi.iki.fi> Content-Type: text/plain; charset="us-ascii" CentOS Errata and Security Advisory 2006:0159 https://rhn.redhat.com/errata/RHSA-2006-0159.html The following updated files have been uploaded and are currently syncing to the mirrors: files: updates/ia64/RPMS/httpd-2.0.52-22.ent.centos4.ia64.rpm updates/ia64/RPMS/httpd-devel-2.0.52-22.ent.centos4.ia64.rpm updates/ia64/RPMS/httpd-manual-2.0.52-22.ent.centos4.ia64.rpm updates/ia64/RPMS/httpd-suexec-2.0.52-22.ent.centos4.ia64.rpm updates/ia64/RPMS/mod_ssl-2.0.52-22.ent.centos4.ia64.rpm -- Pasi Pirhonen - upi(a)iki.fi - http://iki.fi/upi/

1 0

RE: Linux HA may not be the best choice in your situation. [CentOS]High Availability using 2 sites
by Todd Reed 06 Jan '06

06 Jan '06

Ok...I see some of your points, but if SITE_A talked to SITE_B via the internet and they use a 1:1NAT, if the internet goes down at SITE_A, it breaks the 1:1 NAT. Servers down are different than the Internet connection being down. I never said RRD should be used for failover. I said it could be in combination with my idea. I guess it would help to know if the web services are serving only the company, or are they serving the public/Internet? --Todd -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Bryan J. Smith Sent: Thursday, January 05, 2006 2:55 PM To: CentOS mailing list Subject: RE: Linux HA may not be the best choice in your situation. [CentOS]High Availability using 2 sites Todd Reed <treed(a)astate.edu> wrote: > As for Brian's Message: > 1) You are right, to a point. To what point? Round-robin DNS is not, and never will be, failover. And even some logic we've discussed here is rather subjective and arbitrary, even for one, specific app -- working on a corporate network (before considering across the Internet). > I'm not saying that my idea was a replacement for BGP. I even > state that by saying "This is no substitution for BGP". Again, I wish I would have _never_ said BGP. I mean an AS. > 2) You are correct in saying that you need to change in how > the world sees you (whether that be in the application or > layer3 routing). That can be done at the application layer or > at layer 3. But, if you are a small company that has only 1 > internet link at your primary site and 1 internet connection at > your remote site and you rely on the internet for > communications between the sites, then you technically do > not qualify for an AS number. That makes BGP useless. > That makes your solution be somewhere in the upper layer of > the OSI model. That's why I gave a _second_ recommendation. If you can guarantee your borders will _at_least_ be up, even if the servers behind it are down, you can implement 1-to-1 NAT at the border. I.e., if site A's servers are down, site A's border can use 1-to-1 NAT to target site B's servers. Please recognize I'm giving not just the "high end" solution, but I'm also giving a "feasible" solution for SMBs too. ;-> [ SIDE NOTE: I was _not_ the person who brough up Google either. But when someone did, I (as well as at least 1 other) showed that I wasn't off-the-mark on how Google does it either. ;-] > 3) My idea was more on the lines of internet failure at the > primary site and using RRDNS on top of that. If the secondary > DNS server kicked in and pulled it's configs from the hidden > master, then the hidden record wouldn't be configured for RRDNS > because it is only used when the primary site fails. The problem is _still_ propogation. That's why, in the absence of your own AS, you need the failed site to redirect all traffic under the guise of 1-to-1 NAT to the site that is up. It's very simple to do, and they even have affordable devices to do so with Linux+ASICs (i.e., faster than a host-based Linux solution). > 4) My idea was also an application layer solution. > Last time I checked, BGP was in Layer 3. Forget I even mentioned ASNs for a moment. I _also_ mentioned using 1-to-1 NAT between sites, and it works _well_ too. It not only _avoids_ the propogation issue, but better yet, it work work _while_ propogation is still occuring. > 5) Yes, there are some delays when using DNS. Likewise > there are delays with BGP. Certainly BGP delays are a lot > quicker. No argument there. Sigh, you're not getting my point at all on layer-3. You've totally missed it. It's not comparable to application-level. It's absolute. > But again, my idea is looking at it from an application layer > POV. _Eventually_ you'd have to change the application-layer as well, _if_ the site was down awhile. But in the meantime, you _need_ to do layer-3 redirection for the immediate failover. 1-to-1 NAT does this. It's very simple. It just works. -- Bryan J. Smith Professional, Technical Annoyance b.j.smith(a)ieee.org http://thebs413.blogspot.com ---------------------------------------------------- *** Speed doesn't kill, difference in speed does *** _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

4 7

RE: Linux HA may not be the best choice in yoursituation. [CentOS]High Availability using 2 sites
by Todd Reed 06 Jan '06

06 Jan '06

In a nutshell and very first of all, you need at least 2 internet connections. Those ISP must be willing to setup BGP peering between your routers and theirs. Once that agreement has been made, you need to get their AS Numbers and submit the ASN request located on ARIN's website (http://www.arin.net) After some paperwork and money exchanges, ARIN assigns you an AS number. At that point, you can configure the BGP peering. There's more details to it, but that's what I went through in a nutshell. ARIN has a pretty good flowchart of their process located at http://www.arin.net/education/asn_process/index.html --Todd -----Original Message----- From: centos-bounces(a)centos.org [mailto:centos-bounces@centos.org] On Behalf Of Tim Edwards Sent: Thursday, January 05, 2006 6:33 PM To: CentOS mailing list Subject: Re: Linux HA may not be the best choice in yoursituation. [CentOS]High Availability using 2 sites Bryan J. Smith wrote: > Exactly! That's why I keep both agreeing _and_ dismissing > many suggestions, because most are only feasible _if_ they > are for a corporate intranet. Most are too arbitrary for the > Internet. > > I believe the original poster was talking about the Internet, > but I could be wrong. Yes I am talking about the Internet, not an Intranet. Thanks for all your replies, especially Brian, they've helped me see more clearly what the options are. I'd already given up on Round Robin or any other kind of DNS 'solution' before I posted, after reading this: http://homepages.tesco.net./~J.deBoynePollard/FGA/dns-round-robin-is-use less.html I don't think the difficulties and expense of getting an AS number and setting up BGP to work with our ISP will be worth it, but I'm not sure - what steps exactly are involved in doing that? -- Tim Edwards _______________________________________________ CentOS mailing list CentOS(a)centos.org http://lists.centos.org/mailman/listinfo/centos

2 1

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

Discuss