Discuss

discuss@lists.centos.org

34758 discussions

I/O statistics per PID
by Sergio Belkin 26 May '08

26 May '08

Hi, I've found a great tool called pidstat which is able to report I/O disks statistic. But, it's only for kernels 2.6.20 and later only, is there any tool for Centos xen kernel? Thanks in advance! -- -- Open Kairos http://www.openkairos.com Watch More TV http://sebelk.blogspot.com Sergio Belkin -

2 1

1333/8GB Intel motherboard for C5.1
by Drew Weaver 26 May '08

26 May '08

Hi there, has anyone run into any Desktop/Workstation Intel brand motherboards that work with CentOS 5.1 (4.6/3.9 out of box compatibility is a very large plus) and work with the 1333MHZ cpus such as the 8400/9450 and accept 8GB of RAM? The closest we've found so far is the DG31PR which is alright but it has the limitation of 4GB of RAM and an unsupported Realtek NIC. The DQ35JO is also ok, but requires quite a bit of 'jostling' to get to work such as pci=nommconf and other tweaks, we need something that will work out of box, anyone found anything recently? Thanks in advance if anyone has any hints. -Drew

10 15

how to debug ssh slow connection issues.
by Jason Pyeron 26 May '08

26 May '08

I do not have any ideas on this. Where should I start. [root(a)192.168.1.80 security]# date && time ssh -v 192.168.1.21 date Fri May 23 11:43:53 EDT 2008 OpenSSH_3.9p1, OpenSSL 0.9.7a Feb 19 2003 debug1: Reading configuration data /root/.ssh/config debug1: Applying options for 192.168.1.21 debug1: Reading configuration data /etc/ssh/ssh_config debug1: Applying options for * debug1: Connecting to 192.168.1.21 [192.168.1.21] port 22. debug1: Connection established. debug1: permanently_set_uid: 0/0 debug1: identity file /root/.ssh/identity type -1 debug1: identity file /root/.ssh/id_rsa type -1 debug1: identity file /root/.ssh/id_dsa type 2 debug1: Remote protocol version 1.99, remote software version OpenSSH_4.6 debug1: match: OpenSSH_4.6 pat OpenSSH* debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_3.9p1 debug1: SSH2_MSG_KEXINIT sent debug1: SSH2_MSG_KEXINIT received debug1: kex: server->client aes128-cbc hmac-md5 none debug1: kex: client->server aes128-cbc hmac-md5 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(1024<1024<8192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP debug1: SSH2_MSG_KEX_DH_GEX_INIT sent debug1: expecting SSH2_MSG_KEX_DH_GEX_REPLY debug1: Host '192.168.1.21' is known and matches the RSA host key. debug1: Found key in /root/.ssh/known_hosts:4 debug1: ssh_rsa_verify: signature correct debug1: SSH2_MSG_NEWKEYS sent debug1: expecting SSH2_MSG_NEWKEYS debug1: SSH2_MSG_NEWKEYS received debug1: SSH2_MSG_SERVICE_REQUEST sent debug1: SSH2_MSG_SERVICE_ACCEPT received Paused 9 seconds. debug1: Authentications that can continue: publickey,password debug1: Next authentication method: publickey debug1: Trying private key: /root/.ssh/identity debug1: Trying private key: /root/.ssh/id_rsa debug1: Offering public key: /root/.ssh/id_dsa debug1: Server accepts key: pkalg ssh-dss blen 433 debug1: read PEM private key done: type DSA Paused 9 seconds. debug1: Authentication succeeded (publickey). debug1: channel 0: new [client-session] debug1: Entering interactive session. Paused 16 seconds. debug1: Sending command: echo debug1: client_input_channel_req: channel 0 rtype exit-status reply 0 debug1: channel 0: free: client-session, nchannels 1 debug1: Transferred: stdin 0, stdout 0, stderr 0 bytes in 13.5 seconds debug1: Bytes per second: stdin 0.0, stdout 0.0, stderr 0.0 debug1: Exit status 0 real 0m34.027s user 0m0.014s sys 0m0.083s Fri May 23 11:51:32 EDT 2008 [root@statics31 security]# And the log from 192.168.1.21 (different run so the dates won't match): ==> /var/log/secure <== May 23 12:01:56 192.168.1.21 pam_stack[23836]: called for "PAM_ACCOUNT" May 23 12:01:56 192.168.1.21 pam_stack[23836]: called from "sshd" May 23 12:01:56 192.168.1.21 pam_stack[23836]: initializing May 23 12:01:56 192.168.1.21 pam_stack[23836]: creating child stack `system-auth' May 23 12:01:56 192.168.1.21 pam_stack[23836]: creating environment May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_CONV to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_RHOST to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_RUSER to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_SERVICE to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_TTY to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_USER to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing data to child May 23 12:01:56 192.168.1.21 pam_stack[23836]: calling substack May 23 12:01:56 192.168.1.21 pam_stack[23836]: substack returned 0 (Success) May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_CONV to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_RHOST to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_SERVICE to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_TTY to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing PAM_USER to parent May 23 12:01:56 192.168.1.21 pam_stack[23836]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing data back May 23 12:01:56 192.168.1.21 pam_stack[23836]: passing former back May 23 12:01:56 192.168.1.21 pam_stack[23836]: returning 0 (Success) May 23 12:01:56 192.168.1.21 pam_stack[23844]: called for "PAM_OPEN_SESSION" May 23 12:01:56 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:01:56 192.168.1.21 pam_stack[23844]: initializing May 23 12:01:56 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:01:56 192.168.1.21 pam_stack[23844]: calling substack May 23 12:01:56 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:01:56 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing data back May 23 12:01:56 192.168.1.21 pam_stack[23844]: passing former back May 23 12:01:56 192.168.1.21 pam_stack[23844]: returning 0 (Success) ==> /var/log/messages <== May 23 12:01:56 192.168.1.21 sshd[23836]: Accepted publickey for root from 192.168.1.80 port 39910 ssh2 May 23 12:01:56 192.168.1.21 sshd(pam_unix)[23844]: session opened for user root by (uid=0) ==> /var/log/secure <== May 23 12:02:01 192.168.1.21 pam_stack[23844]: called for "PAM_SETCRED" May 23 12:02:01 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:02:01 192.168.1.21 pam_stack[23844]: initializing May 23 12:02:01 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:02:01 192.168.1.21 pam_stack[23844]: calling substack May 23 12:02:01 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:02:01 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing data back May 23 12:02:01 192.168.1.21 pam_stack[23844]: passing former back May 23 12:02:01 192.168.1.21 pam_stack[23844]: returning 0 (Success) ==> /var/log/messages <== May 23 12:02:16 192.168.1.21 sshd[23844]: error: channel 0: chan_read_failed for istate 3 ==> /var/log/secure <== May 23 12:02:16 192.168.1.21 pam_stack[23844]: called for "PAM_SETCRED" May 23 12:02:16 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:02:16 192.168.1.21 pam_stack[23844]: initializing May 23 12:02:16 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:02:16 192.168.1.21 pam_stack[23844]: calling substack May 23 12:02:16 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:02:16 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing data back May 23 12:02:16 192.168.1.21 pam_stack[23844]: passing former back May 23 12:02:16 192.168.1.21 pam_stack[23844]: returning 0 (Success) May 23 12:02:21 192.168.1.21 pam_stack[23844]: called for "PAM_CLOSE_SESSION" May 23 12:02:21 192.168.1.21 pam_stack[23844]: called from "sshd" May 23 12:02:21 192.168.1.21 pam_stack[23844]: initializing May 23 12:02:21 192.168.1.21 pam_stack[23844]: found previously-used child stack `system-auth' May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_CONV to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to child: source not set May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_TTY to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_USER to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to child: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing data to child May 23 12:02:21 192.168.1.21 pam_stack[23844]: calling substack May 23 12:02:21 192.168.1.21 pam_stack[23844]: substack returned 0 (Success) May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_AUTHTOK to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_CONV to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_FAIL_DELAY to parent: source not set May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_OLDAUTHTOK to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_RHOST to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_RUSER to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_SERVICE to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_TTY to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing PAM_USER to parent May 23 12:02:21 192.168.1.21 pam_stack[23844]: NOT passing PAM_USER_PROMPT to parent: source is NULL May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing data back May 23 12:02:21 192.168.1.21 pam_stack[23844]: passing former back May 23 12:02:21 192.168.1.21 pam_stack[23844]: returning 0 (Success) ==> /var/log/messages <== May 23 12:02:16 192.168.1.21 last message repeated 2 times May 23 12:02:21 192.168.1.21 sshd(pam_unix)[23844]: session closed for user root -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- - - - Jason Pyeron PD Inc. http://www.pdinc.us - - Principal Consultant 10 West 24th Street #100 - - +1 (443) 269-1555 x333 Baltimore, Maryland 21218 - - - -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- This message is for the designated recipient only and may contain privileged, proprietary, or otherwise private information. If you have received it in error, purge the message from your system and notify the sender immediately. Any other use of the email by you is prohibited.

4 14

cups causing segfault
by Gregory P. Ennis 26 May '08

26 May '08

Everyone, I have a new installation of Centos 5.1 that I am using on a gateway server that also has dhcp, named servers. I also have cups set up to function as a print server, and sendmail is being used as a relay to our mail server. yum-cron appears to be updating everything daily as desired. This Centos 5.1 gateway was created to replace a Fedora Core 5 system with the same functions. When I set up cups I copied the FC5 subdirectory into the Centos 5.1 system. Everything appears to work as expected. For some reason I am having sendmail crator without giving me a notice in the logs as far as I can determine. However, when I looked at the messages logs I found it filled with many entries in the form of : kernel: ipp[24519]: segfault at 0000000000000000 rip 00002aaaabf2abc0 rsp 00007fff25495348 error 4 I've done a google search and there appeared to be a problem with doubled printer entries in the printer.conf causing the log entry, but after checking my printer.conf file everything appears to be ok. This file also worked on FC5 without a problem. I am not sure if the cups problem is related to the sendmail problem. Any ideas? Greg Ennis

2 6

RE: [CentOS] Hourly restart
by Gregg McClintic 25 May '08

25 May '08

To be honest I have no idea what is needed by the kernel for the bios to beable to check that the os is responding correctly. I enabled it on a test server and had the same issue on a default 4.6 cent install. I could have the name in the bios (the service ) incorrect ie, watch guard,watch dog , watch "something" I know it is psent on serval types of motherboad manufactures. Take a look should be easy to find

2 1

Opinions about SSH and DNS
by Clint Dilks 25 May '08

25 May '08

Hi People, As part of securing SSH we currently have UseDNS set to yes. But we are finding that a number of ISP's are deliberately refusing to configure matching forward and reverse DNS records. So I am wondering how many of you are still using this option?

2 1

saslauthd for sendmail SMTP relay
by Bernd Bartmann 25 May '08

25 May '08

Hi, I'm running a Centos 5.1 server that uses saslauthd to allow sendmail SMTP relaying for some clients. saslauthd is configured to use method "shadow" to lookup the username / password directly from /etc/shadow. This setup has been working for several month now, but is broken since last Monday. I haven't changed anything neither on the server nor on the clients. Now whenever a client tries to relay email I see this messages in the logs: /var/log/maillog: AUTH failure (LOGIN): authentication failure (-13) SASL(-13): authentication failure: checkpass failed /var/log/messages: saslauthd[3665]: do_auth : auth failure: [user=username] [service=smtp] [realm=] [mech=shadow] [reason=Unknown] Does someone have an idea how to debug this further, esp. how to find the real reason as the message [reason=Unknown] is not very helpful at all. Thanks in advance, Bernd.

2 5

RE: [CentOS] Hourly restart
by Gregg McClintic 25 May '08

25 May '08

Anything in the bios called watchdog turned on?

2 1

Hourly restart
by Linux 25 May '08

25 May '08

Hi, Without any update, hardware/software modification, etc... one of my systems "Hourly restart" problem started again. Currently, I counted 5 restarts at 59th minute. No log entry, no console error, nothing really interesting. If I do not see camera records with my own eyes, I'll suspect about someone from D.C. hardreseting the box. Now, I guess /var failed mounting and ssh not available. Maybe next hour restart does a magic... Last time, a kernel update solved hourly restart problem. Before loosing access, I checked and saw a new kernel with -21 ending number (x86_64, forgot to mention) and waiting for XFS module to be ready (Well, I wish I had left it ext3) After that, perhaps update will solve the problem again, but why? Last time I stopped all crons, unneeded services, remote access, etc.. Put a man in front of the monitor and made him monitor everything. Only thing he saw was a welcoming BIOS without any sign at the 60th minute. Replaced power cords, power supply, some disks, RAM modules, etc... Currently I have the last recovered remote logs of temperature and voltage sensors of the system, all seems fine, nothing suspicious. I am out of ideas. I have many gentoo boxes on the almost same hardware and a few centos boxes. Only this one failes continuously... I'd like to hear advice and suggestions about how to debug / repair this situation. Thanks. P.S.: Complete hardware replacement plan is currently in action, new hardware will be ready soon but I'm not so sure about hardware failure. Why did it stopped last time after a simple kernel update?

1 0

How is this possible?
by MHR 25 May '08

25 May '08

As an experiment, I am attempting to build a more recent version of GNOME than 2.16.0 on CentOS 5.1. I've tried both garnome and jhbuild, and neither one works quite right. Jhbuild blows out looking for a dbus-glib-1 revision >= 0/74 (the release rev is 0.70), so I downloaded that and tried to build it. This results in the following error: gcc -g -O2 -Wall -Wchar-subscripts -Wmissing-declarations -Wmissing-prototypes -Wnested-externs -Wpointer-arith -Wcast-align -Wfloat-equal -Wsign-compare -o .libs/dbus-binding-tool dbus-binding-tool-glib.o dbus-glib-tool.o ./.libs/libdbus-gtool.a -L/lib64 ./.libs/libdbus-glib-1.so -ldbus-1 -lgobject-2.0 -lglib-2.0 /usr/lib/libexpat.so -lnsl /usr/lib/libexpat.so: could not read symbols: File in wrong format collect2: ld returned 1 exit status make[4]: *** [dbus-binding-tool] Error 1 make[4]: Leaving directory `/home/mhr/Download/dbus-glib-0.74/dbus' make[3]: *** [all-recursive] Error 1 make[3]: Leaving directory `/home/mhr/Download/dbus-glib-0.74/dbus' make[2]: *** [all] Error 2 make[2]: Leaving directory `/home/mhr/Download/dbus-glib-0.74/dbus' make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory `/home/mhr/Download/dbus-glib-0.74' make: *** [all] Error 2 When I try to use garnome, it eventually runs into exactly the same error. I've checked /usr/lib/libexpat.so, and this is what I get: $ ls -l /usr/lib/libexpat.so lrwxrwxrwx 1 root root 27 Jan 8 13:11 /usr/lib/libexpat.so -> ../../lib/libexpat.so.0.5.0 $ ls -l /lib/libexpat.so.0.5.0 -rwxr-xr-x 1 root root 133056 Jan 6 2007 /lib/libexpat.so.0.5.0 $ file /lib/libexpat.so.0.5.0 /lib/libexpat.so.0.5.0: ELF 32-bit LSB shared object, Intel 80386, version 1 (SYSV), stripped When I look at this library with nm, lld and objdump, they all seem to be able to read it just fine. There is also the 64 bit version that lives in /ib64 and has a .ink from /usr/lib64, and that also reads fine. What did I miss here? Thanks. mhr

4 6

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