Shutdown Problem
Debian 6.0.6 (64 bit)/KDE 4.4.5 For some reason when I shutdown the system, either as a user or as root, the process hangs on: Currently running process (pstree): The only recourse I seem to have is to hit the reset button. Reinstalling psmisc did not solve the problem. Assistance in solving this problem will be appreciated. Thanks in advance. -- Stephen P. Molnar, Ph.D. Life is a fuzzy set Foundation for Chemistry Stochastic and multivariate www.FoundationForChemistry.com (614)312-7528 (c) Skype: smolnar1 -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/5072e2b9.6000...@sbcglobal.net
Re: Shutdown Problem
On Mon 08 Oct 2012 at 10:27:05 -0400, Stephen P. Molnar wrote: Debian 6.0.6 (64 bit)/KDE 4.4.5 For some reason when I shutdown the system, either as a user or as root, the process hangs on: Currently running process (pstree): The only recourse I seem to have is to hit the reset button. Reinstalling psmisc did not solve the problem. Everything you see on the screen when the hang occurs can only be of help. pstree itself is probably not the problem. -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20121008204020.GG30872@desktop
shutdown problem in combination with autofs/NFS
Hello, occassionally our Debian 6 boxes don't shutdown. The shutdown process hangs forever with the last messages: Turning off quotas:...Checking for running unattended-upgrades: I assume, I found the reason for this issue, but no solution. Our linux computers mount some directories via NFS. The directories /home and /sw are managed by the automounter. /usr/local is a symlink to /sw/local.debian-6 which is mounted from the NFS server. While shutting down, sometimes the automounter finishes to early. Afterwards all scripts in /etc/init.d which look for binaries in /usr/local/bin hang. Until Debian 5 this wasn't an issue, because the automounter finishes at a well defined time relatively to other services. But with the new dependency based init system, this time seems to vary and sometimes the automounter finishes to early. If this situation occurs, all local terminals are dead and can be used for debugging. But from an open ssh session I can restart autofs and then the shutdown goes further. First I tried to remove /usr/local/bin from the PATH variable in /etc/profiles. But this doesn't not help, because a lot of init scripts define theire own PATH variable: # grep -l PATH.*/usr/local/bin /etc/init.d/* /etc/init.d/alsa-utils /etc/init.d/apache2 /etc/init.d/binfmt-support /etc/init.d/cpufrequtils /etc/init.d/cups /etc/init.d/hal /etc/init.d/ipmievd /etc/init.d/libvirt-bin /etc/init.d/networking /etc/init.d/quota /etc/init.d/quotarpc /etc/init.d/saned /etc/init.d/schroot /etc/init.d/sysstat /etc/init.d/unattended-upgrades Next we tried to adjust the dependencies in /etc/init.d/autofs. But we didn't found a working solution. Is there a simple solution or workaround for this? I didn't filed a bug until now, because of the nonstandard configuration with /usr/local via NFS/autofs. Or should I do this? Ingo Rogalsky -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4e42640e.70...@web.de
Re: Shutdown problem -- cron job related?
At certain times, seems Friday noontime, I am unable to shutdown the
system. Instead of the usual scripts to killing all processes, unmounting
everything and will now halt, goodby, I get:
process running pstree (or something like that)
shutdown aborted
At this point, the system (or at least any console or UI) is dead.
What it this?
Just see which process is running pstree.
ps -eaf | grep pstree
You could find the parent pid of pstree (second column).
Look at the parent of pstree, and the process started this one.
If you go back that way, finally you will reach init, but before that you
could find which system process started these processes.
I'll have to try it when I know the thing is running.
As I recall, pstree is not part of basic installation.
It was put to do some scripting, regarding found, in
perl/python?
My first bet would be to remove offensive cron line and
shutdown normally. Than to do filesystem checks. Next,
to set cron to use pstree as a regular user. I think that
shutdown was done in some parts, aka closed network. What
has to wait, hangs the system.
Otherwise, there is a chance that some housekeeping pro-
cesses are started at noon every day. You could always
look at /etc directory and find them. Some unices have
it in /etc/periodic/daily. It starts with #!/bin/sh.
Another clue may be in /var/log, as a result of newsyslog.conf.
I have no /etc/periodic and no logs for pstree
I manually ran it (x11 variant) and this is what I got:
init-+-Xprt
|-akonadi_control-+-akonadi_ical_re
| |-8*[akonadi_kabc_re]
| |-4*[akonadi_kcal_re]
| |-42*[akonadi_maildir]
| |-akonadi_maildis
| |-akonadi_nepomuk---{akonadi_nepomu}
| |-akonadi_vcard_r
| |-akonadiserver-+-mysqld---74*[{mysqld}]
| | `-66*[{akonadiserver}]
| `-4*[{akonadi_contro}]
|-apmd
|-atd
|-avahi-daemon---avahi-daemon
|-boinc
|-clamd---2*[{clamd}]
|-console-kit-dae---63*[{console-kit-da}]
|-cron
|-cupsd
|-das_watchdog---{das_watchdog}
|-3*[dbus-daemon]
|-2*[dbus-launch]
|-ddclient
|-dirmngr
|-dovecot-+-2*[dovecot-auth]
| |-imap
| |-3*[imap-login]
| `-3*[pop3-login]
|-exim4
|-fail2ban-server---6*[{fail2ban-serve}]
|-fetchmail
|-2*[getty]
|-gpm
|-hald-+-hald-runner-+-hald-addon-inpu
| | `-hald-addon-stor
| `-{hald}
|-in.tftpd
|-inetd
|-jackdbus
|-kaccess
|-kded4---{kded4}
|-kdeinit4-+-kio_file
| |-kio_http_cache_
| |-kio_imap4
| |-klauncher
| |-ksmserver-+-kwin
| | `-{ksmserver}
| |-python---python---python
| `-qjackctl---{qjackctl}
|-kdm-+-Xorg
| `-kdm---startkde-+-kwrapper4
| `-2*[ssh-agent]
|-kget
|-kglobalaccel
|-klipper
|-klogd
|-kmail---{kmail}
|-kmix
|-knemo
|-knotify4
|-korgac---{korgac}
|-krunner---{krunner}
|-kxkb---{kxkb}
|-nepomukserver
|-plasma-desktop-+-ksysguardd
|`-7*[{plasma-desktop}]
|-portmap
|-postmaster-+-postmaster
|`-postmaster---postmaster
|-preload
|-proftpd
|-rpc.mountd
|-rpc.statd
|-smartd
|-spamd---2*[spamd]
|-sshd
|-svscanboot-+-readproctitle
|`-svscan
|-syslogd
|-tinyproxy---11*[tinyproxy]
|-udevd---2*[udevd]
|-xfs
|-xfstt
`-yakuake-+-bash---pstree.x11
`-{yakuake}
Press return to close
Which would basically reflect what init ran and what kde4 is doing when I did
it. Why would this be stuck at the end?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/201005091612.7.d_ba...@012.net.il
Re: Shutdown problem -- cron job related?
On Sun, May 9, 2010 at 18:42, David Baron d_ba...@012.net.il wrote:
At certain times, seems Friday noontime, I am unable to shutdown the
system. Instead of the usual scripts to killing all processes,
unmounting
everything and will now halt, goodby, I get:
process running pstree (or something like that)
shutdown aborted
At this point, the system (or at least any console or UI) is dead.
What it this?
Just see which process is running pstree.
ps -eaf | grep pstree
You could find the parent pid of pstree (second column).
Look at the parent of pstree, and the process started this one.
If you go back that way, finally you will reach init, but before that you
could find which system process started these processes.
I'll have to try it when I know the thing is running.
As I recall, pstree is not part of basic installation.
It was put to do some scripting, regarding found, in
perl/python?
My first bet would be to remove offensive cron line and
shutdown normally. Than to do filesystem checks. Next,
to set cron to use pstree as a regular user. I think that
shutdown was done in some parts, aka closed network. What
has to wait, hangs the system.
Otherwise, there is a chance that some housekeeping pro-
cesses are started at noon every day. You could always
look at /etc directory and find them. Some unices have
it in /etc/periodic/daily. It starts with #!/bin/sh.
Another clue may be in /var/log, as a result of newsyslog.conf.
I have no /etc/periodic and no logs for pstree
I manually ran it (x11 variant) and this is what I got:
init-+-Xprt
|-akonadi_control-+-akonadi_ical_re
| |-8*[akonadi_kabc_re]
| |-4*[akonadi_kcal_re]
| |-42*[akonadi_maildir]
| |-akonadi_maildis
| |-akonadi_nepomuk---{akonadi_nepomu}
| |-akonadi_vcard_r
| |-akonadiserver-+-mysqld---74*[{mysqld}]
| | `-66*[{akonadiserver}]
| `-4*[{akonadi_contro}]
|-apmd
|-atd
|-avahi-daemon---avahi-daemon
|-boinc
|-clamd---2*[{clamd}]
|-console-kit-dae---63*[{console-kit-da}]
|-cron
|-cupsd
|-das_watchdog---{das_watchdog}
|-3*[dbus-daemon]
|-2*[dbus-launch]
|-ddclient
|-dirmngr
|-dovecot-+-2*[dovecot-auth]
| |-imap
| |-3*[imap-login]
| `-3*[pop3-login]
|-exim4
|-fail2ban-server---6*[{fail2ban-serve}]
|-fetchmail
|-2*[getty]
|-gpm
|-hald-+-hald-runner-+-hald-addon-inpu
| | `-hald-addon-stor
| `-{hald}
|-in.tftpd
|-inetd
|-jackdbus
|-kaccess
|-kded4---{kded4}
|-kdeinit4-+-kio_file
| |-kio_http_cache_
| |-kio_imap4
| |-klauncher
| |-ksmserver-+-kwin
| | `-{ksmserver}
| |-python---python---python
| `-qjackctl---{qjackctl}
|-kdm-+-Xorg
| `-kdm---startkde-+-kwrapper4
| `-2*[ssh-agent]
|-kget
|-kglobalaccel
|-klipper
|-klogd
|-kmail---{kmail}
|-kmix
|-knemo
|-knotify4
|-korgac---{korgac}
|-krunner---{krunner}
|-kxkb---{kxkb}
|-nepomukserver
|-plasma-desktop-+-ksysguardd
|`-7*[{plasma-desktop}]
|-portmap
|-postmaster-+-postmaster
|`-postmaster---postmaster
|-preload
|-proftpd
|-rpc.mountd
|-rpc.statd
|-smartd
|-spamd---2*[spamd]
|-sshd
|-svscanboot-+-readproctitle
|`-svscan
|-syslogd
|-tinyproxy---11*[tinyproxy]
|-udevd---2*[udevd]
|-xfs
|-xfstt
`-yakuake-+-bash---pstree.x11
`-{yakuake}
Press return to close
Which would basically reflect what init ran and what kde4 is doing when I
did
it. Why would this be stuck at the end?
--
To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact
listmas...@lists.debian.org
Archive: http://lists.debian.org/201005091612.7.d_ba...@012.net.il
pstree is used to list a tree of processes and it should not take much time.
I think your problem is arising from the originator of pstree. Have you
tried using top to see any other process is taking cpu/memory? Also take
a look
at all cron related directories and files, all files in /etc/cron.dailly,
/etc/crontab
Shutdown problem -- cron job related?
At certain times, seems Friday noontime, I am unable to shutdown the system. Instead of the usual scripts to killing all processes, unmounting everything and will now halt, goodby, I get: process running pstree (or something like that) shutdown aborted At this point, the system (or at least any console or UI) is dead. What it this? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005082252.52352.d_ba...@012.net.il
Re: Shutdown problem -- cron job related?
On Sun, May 9, 2010 at 01:22, David Baron d_ba...@012.net.il wrote: At certain times, seems Friday noontime, I am unable to shutdown the system. Instead of the usual scripts to killing all processes, unmounting everything and will now halt, goodby, I get: process running pstree (or something like that) shutdown aborted At this point, the system (or at least any console or UI) is dead. What it this? -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201005082252.52352.d_ba...@012.net.il Just see which process is running pstree. ps -eaf | grep pstree You could find the parent pid of pstree (second column). Look at the parent of pstree, and the process started this one. If you go back that way, finally you will reach init, but before that you could find which system process started these processes.
Re: Shutdown problem -- cron job related
At certain times, seems Friday noontime, I am unable to shutdown the system. Instead of the usual scripts to killing all processes, unmounting everything and will now halt, goodby, I get: process running pstree (or something like that) shutdown aborted At this point, the system (or at least any console or UI) is dead. As I recall, pstree is not part of basic installation. It was put to do some scripting, regarding found, in perl/python? My first bet would be to remove offensive cron line and shutdown normally. Than to do filesystem checks. Next, to set cron to use pstree as a regular user. I think that shutdown was done in some parts, aka closed network. What has to wait, hangs the system. Otherwise, there is a chance that some housekeeping pro- cesses are started at noon every day. You could always look at /etc directory and find them. Some unices have it in /etc/periodic/daily. It starts with #!/bin/sh. Another clue may be in /var/log, as a result of newsyslog.conf. Best regards Zoran -- To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100509044319.ga1...@faust.net
Re: lvm + dm-crypt = shutdown problem (mount: / is busy)
On Wed, Mar 05, 2008 at 11:17:56AM +0200, Giorgos D. Pallas wrote: And why doesn't it first unmount root fs and then disable the LV? I guess the answer to this is that root fs is not unmounted but rather remounted read-only, so it would fail again... Is that it? (I am relatively new to linux and I want to make sure I understand this correctly...) Yes, one cannot unmount the current /, as it's always busy. Re-mounting it read-only is the usual way, but you can't completely shut down LVM with it. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: lvm + dm-crypt = shutdown problem (mount: / is busy)
Maximilian Gass wrote: On Wed, Feb 27, 2008 at 03:17:41PM +0200, Giorgos D. Pallas wrote: I am running debian testing, and I am experiencing lately this (hopefully) non-destructive problem: This problem is non-destructive and normal. Now, this 'Can't deactivate volume group', always happened, and I guess it is because the root filesystem is still used after LVM shuts down. If someone knows why this happens, plz tell me! Yes, the LV with / on it can't be disabled, so it fails. And why doesn't it first unmount root fs and then disable the LV? I guess the answer to this is that root fs is not unmounted but rather remounted read-only, so it would fail again... Is that it? (I am relatively new to linux and I want to make sure I understand this correctly...) Cheers, Giorgos smime.p7s Description: S/MIME Cryptographic Signature
Re: lvm + dm-crypt = shutdown problem (mount: / is busy)
On Wed, Mar 05, 2008 at 11:17:56AM +0200, Giorgos D. Pallas wrote: Maximilian Gass wrote: On Wed, Feb 27, 2008 at 03:17:41PM +0200, Giorgos D. Pallas wrote: I am running debian testing, and I am experiencing lately this (hopefully) non-destructive problem: This problem is non-destructive and normal. Now, this 'Can't deactivate volume group', always happened, and I guess it is because the root filesystem is still used after LVM shuts down. If someone knows why this happens, plz tell me! Yes, the LV with / on it can't be disabled, so it fails. And why doesn't it first unmount root fs and then disable the LV? I guess the answer to this is that root fs is not unmounted but rather remounted read-only, so it would fail again... Is that it? (I am relatively new to linux and I want to make sure I understand this correctly...) maybe because you need to call a program on / in order to deactivate the LVM, but without / you can't call that program... A signature.asc Description: Digital signature
Re: lvm + dm-crypt = shutdown problem (mount: / is busy)
On Wed, Feb 27, 2008 at 03:17:41PM +0200, Giorgos D. Pallas wrote: I am running debian testing, and I am experiencing lately this (hopefully) non-destructive problem: This problem is non-destructive and normal. Now, this 'Can't deactivate volume group', always happened, and I guess it is because the root filesystem is still used after LVM shuts down. If someone knows why this happens, plz tell me! Yes, the LV with / on it can't be disabled, so it fails. pgpEvk2NahlAR.pgp Description: PGP signature
lvm + dm-crypt = shutdown problem (mount: / is busy)
Hello everybody! I am running debian testing, and I am experiencing lately this (hopefully) non-destructive problem: During shutdown I get: -- Αsking all remaining processes to terminate... done Killing all remaining processes... failed ... Deactivating swap... done Unmounting local filesystems... done Shuting down LVM volume groups Can't deactivate volume group evg with 1 open logical volume failed! Stoping early crypto disks... done mount: / is busy Will now halt -- Now, this 'Can't deactivate volume group', always happened, and I guess it is because the root filesystem is still used after LVM shuts down. If someone knows why this happens, plz tell me! The problem that appeared some days ago (maybe after an upgrade of some testing packets), is that killing all remaining processes fails and also this mount: / is busy appears just before computer halt. How can I see which processes causes the problem and cannot be properly killed? Info: LVM is set on dm-crypt. As I see, the order in which the /etc/init.d scripts are called during shutdown is: ... lrwxrwxrwx 1 root root 22 2008-01-16 20:29 S31umountnfs.sh - ../init.d/umountnfs.sh lrwxrwxrwx 1 root root 20 2008-01-16 20:29 S35networking - ../init.d/networking lrwxrwxrwx 1 root root 18 2008-01-16 20:29 S36ifupdown - ../init.d/ifupdown lrwxrwxrwx 1 root root 18 2008-01-16 20:29 S40umountfs - ../init.d/umountfs lrwxrwxrwx 1 root root 20 2008-01-16 20:29 S48cryptdisks - ../init.d/cryptdisks lrwxrwxrwx 1 root root 14 2008-01-16 20:29 S50lvm2 - ../init.d/lvm2 lrwxrwxrwx 1 root root 26 2008-01-16 20:29 S59cryptdisks-early - ../init.d/cryptdisks-early lrwxrwxrwx 1 root root 20 2008-01-16 20:29 S60umountroot - ../init.d/umountroot lrwxrwxrwx 1 root root 14 2008-01-16 20:29 S90halt - ../init.d/halt Isn't this wrong, that first LVM tries to shut, and then root fs tries to unmount? I guess first should root fs be unmounted, then LVM, and last dm-crypt... Am I wrong? If anybody can enlighten me on these matters, I would appreciate it much! Giorgos Pallas -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: shutdown problem : acpi_power_off freeze
On Thu, Nov 08, 2007 at 11:32:45PM +0100, Bruno Costacurta wrote: I'm using 2.6.18-5-686 Do you reckon I should upgrade ? If you are running stable you could try a newer kernel from backports.org Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
Re: shutdown problem : acpi_power_off freeze
On Friday 09 November 2007 09:36, Andrei Popescu wrote: On Thu, Nov 08, 2007 at 11:32:45PM +0100, Bruno Costacurta wrote: I'm using 2.6.18-5-686 Do you reckon I should upgrade ? If you are running stable you could try a newer kernel from backports.org Regards, Andrei Indeed it works fine as I installed kernel 2.6.22 (from backports.org as I'm running stable) Thanks to all for your attention. Bye, Bruno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: shutdown problem : acpi_power_off freeze
On Wednesday 07 November 2007 19:54, Giorgos Pallas wrote: Andrei Popescu wrote: On Sun, Nov 04, 2007 at 12:28:09PM +0100, Bruno Costacurta wrote: Hello to all, when I shutdown my computer it doesn't turn off but freeze with the message 'acpi_power_off called'. However the shutdown was working before I re-config my ALSA sounds (via alsaconf) and indeed I have a vague remember reading something in the past like acpi has / have some problems with alsa which might block a complete shutdown like in my case. In order to pinpoint the problem you could remove the alsa modules first. Regards, Andrei Strange. I had exactly the same problem and I found out it was the intel sound modules... So I wrote a simple /etc/init.d/ script which unloaded them just before the shutdown. The strange thing is that after a pretty recent kernel upgrade, I found that that was fixed, so I deleted my custom script. Are you using an old kernel? (I am now using the 2.6.22-2-686). Giorgos I'm using 2.6.18-5-686 Do you reckon I should upgrade ? Bye, Bruno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: shutdown problem : acpi_power_off freeze
Andrei Popescu wrote: On Sun, Nov 04, 2007 at 12:28:09PM +0100, Bruno Costacurta wrote: Hello to all, when I shutdown my computer it doesn't turn off but freeze with the message 'acpi_power_off called'. However the shutdown was working before I re-config my ALSA sounds (via alsaconf) and indeed I have a vague remember reading something in the past like acpi has / have some problems with alsa which might block a complete shutdown like in my case. In order to pinpoint the problem you could remove the alsa modules first. Regards, Andrei Strange. I had exactly the same problem and I found out it was the intel sound modules... So I wrote a simple /etc/init.d/ script which unloaded them just before the shutdown. The strange thing is that after a pretty recent kernel upgrade, I found that that was fixed, so I deleted my custom script. Are you using an old kernel? (I am now using the 2.6.22-2-686). Giorgos -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: shutdown problem : acpi_power_off freeze
On Sun, Nov 04, 2007 at 12:28:09PM +0100, Bruno Costacurta wrote: Hello to all, when I shutdown my computer it doesn't turn off but freeze with the message 'acpi_power_off called'. However the shutdown was working before I re-config my ALSA sounds (via alsaconf) and indeed I have a vague remember reading something in the past like acpi has / have some problems with alsa which might block a complete shutdown like in my case. In order to pinpoint the problem you could remove the alsa modules first. Regards, Andrei -- If you can't explain it simply, you don't understand it well enough. (Albert Einstein) signature.asc Description: Digital signature
shutdown problem : acpi_power_off freeze
Hello to all, when I shutdown my computer it doesn't turn off but freeze with the message 'acpi_power_off called'. However the shutdown was working before I re-config my ALSA sounds (via alsaconf) and indeed I have a vague remember reading something in the past like acpi has / have some problems with alsa which might block a complete shutdown like in my case. acpid seems correctly start : ps -ef | grep -i acpi root15 9 0 11:57 ?00:00:00 [kacpid] root 2890 1 0 11:57 ? 00:00:00 /usr/sbin/acpid -c /etc/acpi/events -s /var/run/acpid.socket 105 2911 2903 0 11:57 ?00:00:00 hald-addon-acpi: listening on acpid socket /var/run/acpid.socket bruno 3642 3495 0 12:01 pts/100:00:00 grep -i acpi Thanks for reading and/or any help Bye, Bruno -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
re: shutdown problem
Apparently debian tries to use acpi by default and I suspect your bios may be too old. You might try acpi=force lapic as two boot parameters on the kernel lines in menu.lst. After that's done try aptitude dist-upgrade as root and when that's finished try shutdown -h now and power off the system if necessary and wait a minute then power back up and after logging in as root do shutdown -h now and see if anything improves. I have a Dell over here with circa 1999 cmos and acpi won't run without acpi=force here. A consequence I found with not having acpi running is that cd burning doesn't work. I'm using the speakup version of debian but at kernel level 2.6.18. When I have this system shutdown, it actually works and the system turns off. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
acpi - apm - shutdown Problem
Problem: shutdown -h 0 schaltet den Computer nicht ganz aus ... bildschirm wird zwar schwarz . aber rechner läuft weiter ... hmmm... muss ihn dann abwürgen:( Hast Du acpi aktiviert? Ich würde mal den acpid installieren und dann auch alles mögliche was ACPI angeht im Kernel aktivieren. Auf keinen Fall apm und acpi gleichzeitig aktivieren. auf meiner Kiste (Acer Travelmate 800 Pentium M 1.4GH - Debian 'SID' 2.4.24) ist acpid nicht installiert - apm ist aber drauf und scheint aktiv zu sein. kann ich nun mit apt-get das paket acpid trotzdem installieren? Oder muss ich zuerst apm deinstallieren? Oder erst einen Kernel bauen, der acpi unterstützt? Welche Version ? habe mal die Sourcen für 2.4.25 runtergeladen viele Fragen ;) danke für eure Hilfe matthias -- Haeufig gestellte Fragen und Antworten (FAQ): http://www.de.debian.org/debian-user-german-FAQ/ Zum AUSTRAGEN schicken Sie eine Mail an [EMAIL PROTECTED] mit dem Subject unsubscribe. Probleme? Mail an [EMAIL PROTECTED] (engl)
Re: shutdown problem
Hi Jack: I had the same problem. I found not to use a location in /etc/shutdown.allow but only the user's name. hth Dean Jack wrote: hi all: it used to work well. I followed someone's suggestion and changed Ctrl-Alt-Del to shutdown the machine. Now I got this error: shutdown: no authorized users logged in which is not true. What could be wrong? thanks! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: shutdown problem
Many thanks to people who replied. Yes, removing /etc/shutdown.allow helps. I put a username in that file, the user I log in for everyday's working. dont know why it caused the problem. I also found a symptom as well: `who` did not return anything. I think I am going to use sudo to shutdown, which I found easy to configure too. happy holidays! On Wed, Dec 27, 2000 at 07:47:56AM -0600, Dean wrote: Hi Jack: I had the same problem. I found not to use a location in /etc/shutdown.allow but only the user's name. hth Dean Jack wrote: hi all: it used to work well. I followed someone's suggestion and changed Ctrl-Alt-Del to shutdown the machine. Now I got this error: shutdown: no authorized users logged in which is not true. What could be wrong? thanks!
shutdown problem
hi all: it used to work well. I followed someone's suggestion and changed Ctrl-Alt-Del to shutdown the machine. Now I got this error: shutdown: no authorized users logged in which is not true. What could be wrong? thanks!
Re: shutdown problem
On Tue, Dec 26, 2000 at 10:36:54PM -0500, Jack wrote: hi all: it used to work well. I followed someone's suggestion and changed Ctrl-Alt-Del to shutdown the machine. Now I got this error: shutdown: no authorized users logged in which is not true. What could be wrong? What does the line in inittab look like? kent -- In order to make an apple pie from scratch, you must first create the universe. - Carl Sagan
Re: shutdown problem
ca:12345:ctrlaltdel:/sbin/shutdown -t1 -a -r now On 20001226.2310, ktb said ... On Tue, Dec 26, 2000 at 10:36:54PM -0500, Jack wrote: hi all: it used to work well. I followed someone's suggestion and changed Ctrl-Alt-Del to shutdown the machine. Now I got this error: shutdown: no authorized users logged in which is not true. What could be wrong? What does the line in inittab look like? kent -- In order to make an apple pie from scratch, you must first create the universe. - Carl Sagan -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- Yay verily and was much work done, and several projects signed off. And there was much rejoicing. And QA came unto thy programming team and talked about having a post project dissection of 'what we could do better'. A great shadow fell across the land and the hackers fled into the darkest corners of the offices. -- Alan Cox
Re: shutdown problem
On Tue, Dec 26, 2000 at 10:36:54PM -0500, Jack wrote: hi all: it used to work well. I followed someone's suggestion and changed Ctrl-Alt-Del to shutdown the machine. Now I got this error: shutdown: no authorized users logged in which is not true. What could be wrong? rm -f /etc/shutdown.allow -- Ethan Benson http://www.alaska.net/~erbenson/ pgpAyIfxt8eiP.pgp Description: PGP signature
shutdown problem
Hello, I notice a strange behaviour when I want to shutdown my PC. When I do shutdown -h now it shuts down linux as it should. But when I then turn of the Power my PC restart after one or two seconds. I have the same behaviour with WinNT (i have a dual boot system) but i did not care about that to much. Now, suddenly it seems to occur with linux also?? Anybody any ideas ?? Greetings Stefan Goeman. -- * SIEMENS ATEA NV * * * * ICN D NC A: * *Ir. Stefan Goeman * *Tel: +32 14 253020* *e-mail: [EMAIL PROTECTED] * * * * P.S.: Linux is great!! *
Re: shutdown problem
On Tue, Oct 03, 2000 at 04:53:23PM +, stefan goeman wrote: Hello, I notice a strange behaviour when I want to shutdown my PC. When I do shutdown -h now it shuts down linux as it should. But when I then turn of the Power my PC restart after one or two seconds. I have the same behaviour with WinNT (i have a dual boot system) but i did not care about that to much. Now, suddenly it seems to occur with linux also?? Anybody any ideas ?? Greetings Stefan Goeman. -- * SIEMENS ATEA NV * * * * ICN D NC A: * *Ir. Stefan Goeman * *Tel: +32 14 253020* *e-mail: [EMAIL PROTECTED] * * * * P.S.: Linux is great!! * -- Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] /dev/null It's ACPI BIOS. Many new BIOS have a setting which make the power switch behave as standby/power switch. This changes the power off behaviour. Try pushing the power switch and holding for 4-5 seconds before releasing. It should stay off. Also, look through your BIOS setup menu's to find the power switch setting. scott worley [EMAIL PROTECTED]
Re: Shutdown problem (fwd)
I tried /sbin/halt and /sbin/poweroff in /etc/inittab The actual line in /etc/inittab at present is ca:12345:ctrlaltdel:/sbin/halt Suresh What is the shutdown command syntax that you are using? John Foster [EMAIL PROTECTED] ICQ# 19460173
Re: Shutdown problem (fwd)
On Fri, 11 Feb 2000, Suresh said, I tried /sbin/halt and /sbin/poweroff in /etc/inittab The actual line in /etc/inittab at present is ca:12345:ctrlaltdel:/sbin/halt Use shutdown -h now see man shutdown -ptw
Shutdown problem (fwd)
Hi I have installed debian 2.0 in a IBM netfinity 3000 machine. My problem is when the machine is halted, sometimes it hangs after the message Shutting down cron Any ideas of what to do? Pl send a cc of the reply to [EMAIL PROTECTED] Suresh - Suresh Kumar.R Email: [EMAIL PROTECTED] Dept of Electronics Communication College of Engineering, Trivandrum - 695 016 INDIA
Re: Shutdown problem (fwd)
Suresh Kumar.R wrote: Hi I have installed debian 2.0 in a IBM netfinity 3000 machine. My problem is when the machine is halted, sometimes it hangs after the message Shutting down cron Any ideas of what to do? -- What is the shutdown command syntax that you are using? -- AdVance-Computing Systems We sell fine quality servers and workstations. We specialize in multiprocessor units. We install Debian Linux at no extra charge! John Foster [EMAIL PROTECTED] ICQ# 19460173
startup/shutdown problem
During shutdown process, I SOMETIME obtain the following error message : (A) can't umount /dev/hda3, '/' is busy. When I boot Linux again I obtain : (B) /dev/hda3 has reached maximum mount count, check forced... and It seems Linux is scanning my /dev/hda3 partition. At the end : (C) 12345 blocks not contiguous (4.3 %) (NOTE: 12345 is not the real number, because it change every time) After those strange messages, Linux continue the booting process, normally and all on my System SEEMS ok. I sometime obtain the messages (b)(C) without having the error message (a) previuosly. What's wrong ? Does Linux need 'defrag' as DOS/WINDOWS ?? I have got Debian 2.1 on a Pentium 120 Intel, /dev/hda3 is my primary Linux partition on a Conner Peripherals Hard disk with 1.2 GByte. I have got another Linux partition (/dev/hdb2) on a different hard disk (Fujitsu with 4.3 GByte), and I SOMETIME obtain on it the same error messages (A)(B)(C). I have got the kernel 2.2.13 compiled by myself, and I took care of all configuration parameters, but I still have got the problem. During the boot process, I ALWAYS obtain the following message too: (D) SIOCADDRT: invalid argument Have you got any idea about those strange behaviours ? Thank you to all.
Re: startup/shutdown problem
On Thu, 27 Jan 2000 [EMAIL PROTECTED] wrote: During shutdown process, I SOMETIME obtain the following error message : (A) can't umount /dev/hda3, '/' is busy. I'm not sure what would cause this, but it can happen if the init scripts try to close down the root partition before all the processes have died. If you have a process that won't die, this can happen. But it doesn't really hurt anything, since the files are in a pretty clean state anyway. (B) /dev/hda3 has reached maximum mount count, check forced... This just means exactly what it says. Every so often, a filesystem gets checked, whether it needs it or not. (C) 12345 blocks not contiguous (4.3 %) Tells you how many of your files are not contiguous on the disk. 4.3% is a very good percentage. Does Linux need 'defrag' as DOS/WINDOWS ?? A defrag exists for Linux but you don't need to use it. The Linux kernel keeps the filesystems pretty defragmented as it is. If you split /usr and /home off on separate partitions, it stays even more defragmented. During the boot process, I ALWAYS obtain the following message too: (D) SIOCADDRT: invalid argument This usually means that a device, probably a network card, had a problem with the configuration. If everything seems to be working correctly, ignore it.
debian 2.0 shutdown problem
Hi, I installed debian 2.0 successfully. But when I tried to shutdown, the machine apparently hangs with the following line. Stopping periodic command scheduler: cron. It has happened to me with another debian installation also. On some installations, it has gone without any problems. Any ideas? Suresh - Suresh Kumar.R Email: [EMAIL PROTECTED] Dept of Electronics Communication College of Engineering, Trivandrum - 695 016 INDIA
Shutdown problem
I have a quick question that I'm embarassed to ask. How do you properly shutdown? A few days ago I could shutdown completely with no problem. After installed PPP, XWindows, and a few other odds and ends, shutdown doesn't complete shutting down. It stops at Enter root password for maintenance or Control-D for restart, or something like that. Sometimes I can get it to tell me that there are no more processes left to kill on this run level. I know I must be doing something wrong. Can someone please help me? -- TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word unsubscribe to [EMAIL PROTECTED] . Trouble? e-mail to [EMAIL PROTECTED] .
