[SuSE Linux] initd(?) lockups with 5.3, 6.0, and 6.1
Have been having many problems with our SuSE boxen that are not all identical, but i believe them to still be related. This has been quite a problem, because my deployment of the linux systems was based mainly on the stability of linux, and all of these boxes have proven to be unstable. Problems appear as one of three types: Problem 1: initd "crashed", initd running at 99 initd and the bash shells running on the VCs died, could not kill initd with kill-9, could not change the init level, could not shutdown. Only processes showing on 'ps aux' were the initd, the bashs, and the kernel stuff. Only thing i've found to do is a hardware reset. Problem 2: when tried to reboot, it would say that it was going into runlevel 6, but then nothing would happen. could not manually change runlevels. no change with a 'kill -HUP'. only way out is a hardware reset. Problem 3: box stopped responding to telnet requests. would not respond to ftp, http, telnet, smtp. Everything appeared to be fine from the console. on the console, could not 'telnet localhost'. connection would be established, but would not log in syslog and would not present login. when this has happened on machines that are masq gateways , the masq seems to work without inturruption. Followed by Problem 2. Problem 4: box would be trucking along, with no seeming problem. Then type 'ps aux' and get 300-400 zombies listed. each program run would zombie on exit. could not kill-9 them. Followed by Problem 2. BOX 1: description: IBM PC Server 325, Dual-P2-300's, 64 meg RAM, 2 10/100 NIC ultra scsi, SuSE 6.0, upgraded from 5.3, Kernel 2.2.3, all SuSE 6.0 updates, all the package upgrades needed for 2.2.X problems: was running a remote X session and was hit with Problem #1 while on SuSE5.3, so upgraded to 6.0 and had the same thing happen. has had Problem #3 and #4 at least once, and always has Problem #2 if its been up a coupla days. BOX 2: description: Gateway G-450, P2-450, 128 meg RAM, 10/100 tulip card, ide, SuSE6.1, upgraded from 6.0, Kernel 2.2.9 problems: did fresh install of 6.0 to see if a fresh install would fix Problem #1. Had Problem #1, so i upgraded to 6.1 and again had Probelm #1. have also had Problem #2, #3, and #4 on this box. Problem #4 only happened after the 6.1 upgrade though. BOX 3: description: generic P2-333, 128 meg RAM, 10/100 tulip card, ide drive, SuSE 6.1 upgraded from 5.3 to 6.0, kernel 2.2.5 problems: Problem #2 is common and has occured on all three versions Problem #3 has occured with 6.0 and 6.1, and #4 has occured twice with 6.1 BOX 4: description: generic K62-350, 128 meg RAM, 10/100 tulip card, ide drive stock SuSE 6.0 problems: Problem #3 once. BOX 5: description: generic K62-350, 128 meg RAM, 10/100 tulip card, ide drive very minimal stock SuSE 6.0 install, acts as a masq gateway, http and informix server. generally runs at 0.02 load. problems: Problem #3 frequent (once a week or so). always followed by Problem #2. One weekend had Problem #3 and it cleared itself up after about 24 hours, still had Problem #2 when i went to reboot it the monday after. BOX 6: description: generic P75, 16 meg RAM, ne2000 card, ide drive, very minimal stock SuSE 6.0 install, remote webserver, very lightly hit. problems: Problem #3 has happened at least twice, both times it cleared itself up after 24 or so hours. have not tried a manual reboot. BOX 7: description: generic 486-25, 16 meg RAM, ne2000 card, ide drive, very minimal stock SuSE6.0 install, print server. problems: has Problem #2 everytime we've tried to reboot it. Me and one other person care for the linux boxen, and we have about 8 years linux experience between us, but we're both at a loss. Rocky, rocky@rbxinc.com kether@smluc.org -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
Hi, On Wed, Jun 02, kether@smluc.org wrote:
Have been having many problems with our SuSE boxen that are not all identical, but i believe them to still be related.
[severe problems even with init]
description: IBM PC Server 325, Dual-P2-300's, 64 meg RAM, 2 10/100 NIC ultra scsi, SuSE 6.0, upgraded from 5.3, Kernel 2.2.3, all SuSE 6.0
For some boxes you only write "SuSE 6.0", but don't mention the kernel version. I assume you use some 2.2.x kernel on all of them. Right? Could you please downgrade one of the machines to kernel 2.0.36 and see if the problem persists? I'm quite sure the problem is kernel related, but I cannot confirm this sort of problem here. We have lots of machines running 2.2.7 and 2.2.5. Our servers running 2.0.36 almost all have uptimes of more than 100 days. [...]
Rocky, -o) Hubert Mantel Goodbye, dots... /\\ _\_v
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
unless i specifically said i upgraded the kernel, i didnt. the remote web server, the print server, and the masq gateway are all minimal 6.0 installs, with the stock kernels. was kinda my point, that i'd been getting similar problems accross different hardwares and different kernels...:) Rocky. On Thu, 3 Jun 1999, Hubert Mantel wrote:
Hi,
On Wed, Jun 02, kether@smluc.org wrote:
Have been having many problems with our SuSE boxen that are not all identical, but i believe them to still be related.
[severe problems even with init]
description: IBM PC Server 325, Dual-P2-300's, 64 meg RAM, 2 10/100 NIC ultra scsi, SuSE 6.0, upgraded from 5.3, Kernel 2.2.3, all SuSE 6.0
For some boxes you only write "SuSE 6.0", but don't mention the kernel version. I assume you use some 2.2.x kernel on all of them. Right?
Could you please downgrade one of the machines to kernel 2.0.36 and see if the problem persists? I'm quite sure the problem is kernel related, but I cannot confirm this sort of problem here. We have lots of machines running 2.2.7 and 2.2.5.
Our servers running 2.0.36 almost all have uptimes of more than 100 days.
[...]
Rocky, -o) Hubert Mantel Goodbye, dots... /\\ _\_v -- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
-- To get out of this list, please send email to majordomo@suse.com with this text in its body: unsubscribe suse-linux-e Check out the SuSE-FAQ at <A HREF="http://www.suse.com/Support/Doku/FAQ/"><A HREF="http://www.suse.com/Support/Doku/FAQ/</A">http://www.suse.com/Support/Doku/FAQ/</A</A>> and the archive at <A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html"><A HREF="http://www.suse.com/Mailinglists/suse-linux-e/index.html</A">http://www.suse.com/Mailinglists/suse-linux-e/index.html</A</A>>
participants (2)
-
kether@smluc.org
-
mantel@suse.de