Thanks Carl, On Thursday 15 June 2006 20:36, Carl Hartung wrote:
Hi Peter,
On Thursday 15 June 2006 07:49, Peter Sutter wrote:
I am getting an un-clean shutdown with subsequent hang on on a SuSE V9.2 system.
<snip>
How long has this system been in service with the present configuration? Is the fault "out of the blue" or could you have done something beforehand to trigger it? e.g. software updates/additions, edit config files, etc.?
Well, the system just got a new motherboard and processor, the processor is now 64 bit capable. I run a 'system repair' just to make sure, and it installed some 64-bit software but was otherwise clean. It can't be hardware, because the rescue system and a test system I have on a usb portable drive shut down/restart completely and correctly, only when booting into the root partition does it hang, so it must be configuration related.
The system now hangs, and I have to press the reset button or power cycle. To me, this means a 130 km round trip to reset an un-attended system.
Then you'll probably want to fix the system in situ, not remotely, or else bring it back for repair, right? Is this a server? What hardware?
I am convinced that it is not hardware related. It got upgraded to a 3 Ghz Intel Pentium IV, before 1GHz Pentium IV. It is a kind of a server, running rsync, mysql, apache, php, and exports one nfs share and runs some special application software. The application software does not have any daemons. Original install was as standard workstation with kde, although nobody really logs now on to it interactively.
Anything interesting in the logs?
No, except one funny error at startup /etc/sysconfig/cron: line 48: syntax error near unexpected token `(' /etc/sysconfig/cron: line 48: `## "Set this to "yes" to entirely remove (rm -rf) all files and subdirectories' which is a comment line, but nothing for shutdown. The system says it is rebooting/powering off, but just doesn't do it, most likely because of the error. The root partition is always 'dirty' on startup. shutting down from runlevel s after dismounting all disks manually, still produces the error. Something must still be using /proc, but how do I find out what.
Carl
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com