Cannot reboot Debian Etch - 1 Core at 100% Post: 302360123

Sponsored Content

Operating Systems Linux Debian Cannot reboot Debian Etch - 1 Core at 100% Post 302360123 by jelloir on Thursday 8th of October 2009 07:19:14 AM

10-08-2009

Registered User

Cannot reboot Debian Etch - 1 Core at 100%

I have a weird problem.

I cannot reboot my Debian Etch Server and one core shows as using 100% CPU but nothing appears to be using it????

I have tried kill -9 and killall via htop on the nbd mount and poweroff and shutdown commands but gett nothing.

I also killed a number of other processes but no joy.

Anyone have any ideas? I just want to reboot it..... never had this happen before on Debian.

jelloir

View Public Profile for jelloir

Find all posts by jelloir

3 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Install App in Debian Etch 4.0

I am trying to install a couple applications that I downloaded on my Debian Etch 4.0 OS but I don't know how. 1) I tried using sudo apt-get install...but it always tells me I'm not in the sudoers file 2) I tried using root terminal, but I cant seem to navigate anywhere and I don't know where...

2. Solaris

server reboot itself but no core dump

I wonder if anyone here came accross the same situation like me. One of server in my company reboot itself serveral days ago. I have checked /var/adm/messages... there is nothing there but a few messages mention explorer file has been generated by sysadmin. There is no core dump file either....

3. Debian

Debian Etch - install us-keyboard driver

Hi, i'm using a debian-4.0r1 on an old subnet machine. I have to extend it with an other keyboard . What i have is a DVD of etch 4.0r7. How can i install and load the keyboard-driver for the us-keyboard? Can anybody please give me a hint how to do that? Thanks in advance

LEARN ABOUT MINIX

reboot

REBOOT(8)						      System Manager's Manual							 REBOOT(8)

NAME

       reboot - reboot the system immediately

SYNOPSIS

       reboot [-f]

DESCRIPTION

       Reboot  can  be	used  to  reboot  the  system  after  installing a new kernel.	It does not inform the users, but does log it's actions in
       /usr/adm/wtmp and /usr/adm/authlog.  The system is then rebooted with the reboot(2) systemcall.

       If the -f flag is not given then all processes are sent terminate signals to give them a chance to die peacefully before the reboot() call.

       If the wtmp file exists, reboot logs itself as if it were a shutdown.  This is done to prevent last(1) from talking  about  system-crashes.
       Reboot is registered as is in the authlog file.

       Reboot can only be executed by the super-user.  Any other caller will be refused, either by reboot(8) or by reboot(2).

SEE ALSO

       reboot(2), shutdown(8), halt(8), boot(8).

BUGS

       The  error message's given by reboot are not always useful.  There are several routines that can fail, but which are not fatal for the pro-
       gram.

AUTHOR

       Edvard Tuinder (v892231@si.hhs.NL)

																	 REBOOT(8)