Discuss

discuss@lists.centos.org

34758 discussions

RE: [CentOS] Hard drive errors
by Bowie Bailey 22 Sep '06

22 Sep '06

Bowie Bailey wrote: > Karanbir Singh wrote: > > Jordi Espasa Clofent wrote: > > > > > > The ideal should be to use the SmartTools utilities, but, if I'm > > > right, there're problems with SATA support. > > > > smartctl on CentOS >= 4.3, supports SATA just fine. > > Sounds good. I'll give it a try. I tried smartctl and it ran fine, but found no errors (on the short test). FYI - I had to specify the ata device type to make it work. smartctl -d ata -t short /dev/sda I was also able to get the smartd service running by adding '-d ata' to both lines in the /etc/smartd.conf file. Everything seems to be running normally now. Smartd is configured to send me email on problems now, so I'll keep an eye on it and see what happens. -- Bowie

3 2

Firewire question (Centos 4.4)
by Akemi Yagi 22 Sep '06

22 Sep '06

Johnny Hughes wrote: > > Firewire is not turned on in the standard RHEL kernel. It is on in the > CentOSPlus kernel. Since firewire is a must have for the system I am setting up, I recompiled the kernel with the firewire support turned on and installed it. Then later, I decided to try the CentOSplus kernel. The system booted just fine but I noticed something odd. In /boot, System.map and vmlinuz are still pointing to the custom kernel, not the centosplus kernel. Should I manually correct the symlinks? Akemi

1 0

RE: [CentOS] postfix problem since update: mail loops back to myself
by Alex Palenschat 22 Sep '06

22 Sep '06

> David Hrbáč wrote: > > OK, so let's sum it up. > > > > Let's have domain1.tld and domain2.tld. > > > > domain1.tld has: > > 20 server.domain2.tld > > 10 server.domain1.tld > > > > domain2.tld has: > > 20 server.domain1.tld > > 10 server.domain2.tld > > > > on server.domain1.tld we need to have: > > domain1.tld within virtual domains or local domain > domain2.tld within > > transport > > > > on server.domain2.tld we need to have: > > domain2.tld within virtual domains or local domain > domain1.tld within > > transport > > > > that's correct. > _______________________________________________ I am a bit noobish with postfix and think you would be better served by posting to the postfix-users mailing list, but have you ruled out name resolution as the culprit? Is it possible that bind has also been updated at the same time. Where does your resolver on the mail server think the backup domain is? Also, did your /etc/hosts file change in the upgrade or subsequent to that? Just a guess, alex

1 0

Tyan K8HM and lm_sensors
by Bowie Bailey 22 Sep '06

22 Sep '06

I have a Tyan Thunder K8HM (S3892) motherboard and I am trying to get lm_sensors to work with it. The problem is that I am getting conflicting information. The source for lm_sensors says not to compile the modules for the 2.6 kernel. The information from Tyan says that I need to compile the modules if my kernel is less than 2.6.12. Has anyone here configured lm_sensors for this motherboard? Any suggestions on whether it is safe to install the lm_sensors i2c-piix4 module in the 2.6.9 kernel? CentOS-4.4-x86_64 lm_sensors 2.10.0 -- Bowie

1 0

Problem deleting an active route
by Dale 22 Sep '06

22 Sep '06

Hi all, Some how I have an extra active route setup in my CentOS 4.4 system (that unfortunately at a data center a ways away from me). I have tried using /sbin/route del -net xxx.xxx.xxx.xxx but get an error. I also have Webmin installed and I can delete the route from there, but on applying the network config, the route comes back. I have no idea where it is coming from. It is preventing me from getting out of the box to any other services. Any suggestions greatfully accepted! Thanks Dale

6 11

cmd line import of certificates
by Phil Savoie 22 Sep '06

22 Sep '06

Hi All, Would anyone know of a way to import certificates into netscape/mozilla on the command line? Thanks in advance, Phil

1 0

RE: [CentOS] Problem deleting an active route
by Alex Palenschat 22 Sep '06

22 Sep '06

> The big difference between mine and yours is that the > 169.254.0.0 route > is showing up on eth0 - which is the only port connected. I > can get into > the box, but the box can not get out to anyplace. I could be > looking in > the wrong place for the solution, I figured that this looks wrong to > have this apparent self-assigned IP on my only active ethernet port. What do you mean the box cannot get out to anyplace? What apps etc. Are you certain it is not a firewall or DNS issue? What are you trying and are there any errors? Simple stuff but sometimes overlooked. alex

1 0

rgmanager Hanging at shutdown
by Sherwyn Greene 22 Sep '06

22 Sep '06

HI All I'm working on a test cluster system with two computer system, both are almost the same spec... the problem i'm having is the service I create in the services are not shown in the cluster manager tab on the cluster configuration, and when I go to reboot the systems the rgmanager service hangs and I need to push the reset button on the system to reboot. How can i fix this prob??? Thanks Sherwyn Greene Planner / I.T. Technician Project Controls Dept. Kentz-OJ's E&I Services J.V. +1 (868) 648-0876

1 0

RE: [CentOS] Hard drive errors
by Bowie Bailey 22 Sep '06

22 Sep '06

Karanbir Singh wrote: > Jordi Espasa Clofent wrote: > > > > The ideal should be to use the SmartTools utilities, but, if I'm > > right, there're problems with SATA support. > > smartctl on CentOS >= 4.3, supports SATA just fine. Sounds good. I'll give it a try. > > At least, you can boot with liveCD-util (like UltimateBootCD, for > > example) and check the HD integrity. > > why not use the CentOS-4 LiveCD ? I downloaded the CentOS-4 LiveCD last night. The system is running from the hard drives at the moment, but if it dies again, I'll try the LiveCD. -- Bowie

1 0

RE: [CentOS] Re: Hard drive errors
by Bowie Bailey 22 Sep '06

22 Sep '06

Peter Farrow wrote: > This can be caused by overheating. If the drives are mounted close > together as some chassis configurations permit, then it make sense > they may both exhibit the same problem, but not necessarily > simultaneously. > > Are this log entries adjacent to each other? The drives have an open slot between them and a 120mm fan right in front of them, so I don't think overheating is an issue. At one point, I shut the machine down and let it sit for an hour or so. The errors started back up immediately during the boot process when I turned it back on. The log entries are adjacent...usually with the exact same timestamp. There are no other errors mixed in with them. I was able to get the system to boot yesterday. It triggered a raid rebuild which finished last night. The last batch of errors happened at 4am and the system appears to be running normally now. Here's a snip from the logs showing the errors and the rebuild: (I've cut out a few columns to shorten the lines) ---------------------------------- 22:36:21 kernel: ata3: command 0x25 timeout, stat 0x50 host_stat 0x24 22:36:21 kernel: ata3: status=0x50 { DriveReady SeekComplete } 22:36:21 kernel: Current sda: sense key No Sense 22:36:21 kernel: ata4: command 0x35 timeout, stat 0x50 host_stat 0x24 22:36:21 kernel: ata4: status=0x50 { DriveReady SeekComplete } 22:36:21 kernel: Current sdb: sense key No Sense 22:37:09 kernel: ata3: command 0x25 timeout, stat 0x50 host_stat 0x24 22:37:09 kernel: ata3: status=0x50 { DriveReady SeekComplete } 22:37:09 kernel: Current sda: sense key No Sense 22:38:03 kernel: md: md1: sync done. 22:38:03 kernel: RAID1 conf printout: 22:38:03 kernel: --- wd:2 rd:2 22:38:03 kernel: disk 0, wo:0, o:1, dev:sda2 22:38:03 kernel: disk 1, wo:0, o:1, dev:sdb2 23:25:39 kernel: ata3: command 0xca timeout, stat 0x50 host_stat 0x24 23:25:39 kernel: ata3: status=0x50 { DriveReady SeekComplete } 23:25:39 kernel: Info fld=0x662270, Current sda: sense key No Sense 23:25:39 kernel: ata4: command 0xca timeout, stat 0x50 host_stat 0x24 23:25:39 kernel: ata4: status=0x50 { DriveReady SeekComplete } 23:25:39 kernel: Info fld=0x662270, Current sdb: sense key No Sense ---------------------------------- These errors are showing ata3 and ata4 because I switched the drives to different SATA connections on the MB. These are the same drives that I showed previously with errors on ata1 and ata2. -- Bowie

1 0

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