Hi all, I have a problem with a CentOS 4 and now updated to 4.1 server, every so often the other servers try to contact it and this not there a retry and it is, like it goes to sleep, I have no problem with the fedora1, RH9 and slackware machines they just never do this. its most annoying.. they all use IP's not names. all access lists are identical, all hosts files are identical, all exports and fstabs are same format.
in fact one of the machines on another network altogether reponds instantly. if I reboot *shudder* the CentOS box it fixes it, temporarily, but thats a joke, the hardware is fine, it used to run slackware smoothly, I hope I dont have to go back to it :)
TIA
On Fri, 2005-07-01 at 16:59 +1000, Res wrote:
Hi all, I have a problem with a CentOS 4 and now updated to 4.1 server, every so often the other servers try to contact it and this not there a retry and it is, like it goes to sleep, I have no problem with the fedora1, RH9 and slackware machines they just never do this. its most annoying.. they all use IP's not names. all access lists are identical, all hosts files are identical, all exports and fstabs are same format.
in fact one of the machines on another network altogether reponds instantly. if I reboot *shudder* the CentOS box it fixes it, temporarily, but thats a joke, the hardware is fine, it used to run slackware smoothly, I hope I dont have to go back to it :)
TIA
I haven't seen this issue ... but it might actually be sleeping.
CentOS-4 uses a 2.6.9-x kernel that is much better at doing what your BIOS says for power saving mode than 2.4 kernels were. I would first check the sleep settings in the BIOS of the problem machine.
If that doesn't work, you try turning off the apmd and acpid services.
Also, to really search for fixes ... the exact hardware that is having problems might help.
On Fri, 1 Jul 2005, Johnny Hughes wrote:
On Fri, 2005-07-01 at 16:59 +1000, Res wrote:
I have a problem with a CentOS 4 and now updated to 4.1 server, every so often the other servers try to contact it and this not there a retry and it is, like it goes to sleep, I have no problem with the fedora1, RH9 and slackware machines they just never do this.
I haven't seen this issue ... but it might actually be sleeping.
CentOS-4 uses a 2.6.9-x kernel that is much better at doing what your BIOS says for power saving mode than 2.4 kernels were. I would first check the sleep settings in the BIOS of the problem machine.
If that doesn't work, you try turning off the apmd and acpid services.
that unfortunately means teh system wont do a real poweroff if the UPS instructs it to.
dropped down to 2.4.31 kernel and the problem seems to have gone away so I think your right, its the 2.6.x kernel doing what it should, regrettably we dont want it to :)
On Sat, 2005-07-02 at 22:08, Res wrote:
CentOS-4 uses a 2.6.9-x kernel that is much better at doing what your BIOS says for power saving mode than 2.4 kernels were. I would first check the sleep settings in the BIOS of the problem machine.
If that doesn't work, you try turning off the apmd and acpid services.
that unfortunately means teh system wont do a real poweroff if the UPS instructs it to.
dropped down to 2.4.31 kernel and the problem seems to have gone away so I think your right, its the 2.6.x kernel doing what it should, regrettably we dont want it to :)
What about changing the power-saving options in bios to do what you want?
On Sat, 2 Jul 2005, Les Mikesell wrote:
On Sat, 2005-07-02 at 22:08, Res wrote:
CentOS-4 uses a 2.6.9-x kernel that is much better at doing what your BIOS says for power saving mode than 2.4 kernels were. I would first check the sleep settings in the BIOS of the problem machine.
If that doesn't work, you try turning off the apmd and acpid services.
that unfortunately means teh system wont do a real poweroff if the UPS instructs it to.
dropped down to 2.4.31 kernel and the problem seems to have gone away so I think your right, its the 2.6.x kernel doing what it should, regrettably we dont want it to :)
What about changing the power-saving options in bios to do what you want?
I'm sure they were all set to disable, one of the first things we normally do :)
On Sun, 2005-07-03 at 15:42 +1000, Res wrote:
On Sat, 2 Jul 2005, Les Mikesell wrote:
On Sat, 2005-07-02 at 22:08, Res wrote:
CentOS-4 uses a 2.6.9-x kernel that is much better at doing what your BIOS says for power saving mode than 2.4 kernels were. I would first check the sleep settings in the BIOS of the problem machine.
If that doesn't work, you try turning off the apmd and acpid services.
that unfortunately means teh system wont do a real poweroff if the UPS instructs it to.
dropped down to 2.4.31 kernel and the problem seems to have gone away so I think your right, its the 2.6.x kernel doing what it should, regrettably we dont want it to :)
What about changing the power-saving options in bios to do what you want?
I'm sure they were all set to disable, one of the first things we normally do :)
There is an option you can put on the end of the kernel line in /boot/grub/grub.conf that turns off some acpi features and it might work:
acpi=ht
On Sun, 2005-07-03 at 13:08 +1000, Res wrote:
On Fri, 1 Jul 2005, Johnny Hughes wrote:
On Fri, 2005-07-01 at 16:59 +1000, Res wrote:
I have a problem with a CentOS 4 and now updated to 4.1 server, every so often the other servers try to contact it and this not there a retry and it is, like it goes to sleep, I have no problem with the fedora1, RH9 and slackware machines they just never do this.
The last time I had this problem I found that there were two machines on the network with the same ip address.
-
Edward J. Weinberg -
Johnny Hughes -
Les Mikesell -
Res