Natty won't shutdown for me - the start up/shutting down graphic comes up and the 'light' go down from 5 to 3 then it just hangs there.
Is there a shutdown log? I've looked in /var/log/messages but there's nothing relevant there.
Further to this LQ thread which Tinkster solved by suggesting the last command (thanks Tinkster) I have been exploring last -x reboot and have found that the reported duration is incorrect for the last reboot and shutdown when a old wtmp file is used. Not having a record for the following shutdown, last assumes that the system has been up until the current time and similarly for the shutdown.
The output comes in time order, latest first, each line showing the time of the reboot and the uptime from then to shutdown. Using last -x reboot shutdown to show the shutdown time, here's an illustration
Code:
shutdown system down 2.6.29.6-smp Sun Mar 7 15:35 - 03:02 (11:27)
reboot system boot 2.6.29.6-smp Sun Mar 7 09:35 (05:59)
09:35 until 15:35 is 05:59.
When the uptime exceeds 24 hours it is shown as (<days>+<hours:minutes) like this
Code:
shutdown system down 2.6.29.6-smp Sun Feb 21 12:39 - 13:20 (00:40)
reboot system boot 2.6.29.6-smp Sat Feb 20 09:39 (1+02:59)
09:39 until 12:39 the next day is 1 day 02:59.
The time in parentheses at the end of the shutdown lines is normally the time until the next shutdown.
So far so good. The incorrect output is for the last reboot and shutdown of an old wtmp file. Here's the output of last /var/log/wtmp -x reboot shutdown; last -f /var/log/wtmp.1 -x reboot shutdown
Code:
[snip]
reboot system boot 2.6.29.6-smp Fri Mar 12 07:42 (01:54)
shutdown system down 2.6.29.6-smp Fri Mar 12 01:31 - 09:37 (08:05)
wtmp begins Thu Mar 11 08:25:26 2010
[snip]
reboot system boot 2.6.29.6-smp Wed Mar 10 14:12 (15+01:42)
shutdown system down 2.6.29.6-smp Wed Mar 10 12:41 - 15:54 (15+03:13)
[snip]
The boot started at "Wed Mar 10 14:12" which had an actual uptime of 1 day 11:20 is reported as 15 days 03:13 which is the time from then until the last -f /var/log/wtmp.1 -x reboot shutdown command was issued. The time from shutdown to shutdown is similarly affected.
I'm trying to reboot the server (shutdown -r now).But it seems like nothing happened.
When I try "shutdown -c", the system prompts "shutdown: cannot find pid of running shutdown."
I am running natty (64bin) and recently it has stopped responding to either the shutdown or reboot command from the panel menu. When you select shutdown, and then hit yest to confirm, nothing happens. I looked at the logs and nothing seems to be generating any errors either. Not even sure how to trouble shoot this issue.
View 1 Replies View RelatedI have installed ubuntu 11.04 on my HCL Me Laptop. The OS is not getting halted when I use the shut down or the restart menu from the GUI. It is not shutting down when used the commands 'sudo shut down now' or 'sudo poweroff now' or 'sudo halt now' or 'sudo init 0' also. Except when used the 'shut down' command, the command line hangs at:
init: plymouth-upstart-bridge main process (1981) terminated with status 1
checking for running unattended upgrades.
When used the 'shut down' command, the violet screen where the word ' ubuntu ' is written appears and hangs. I have updated my OS yesterday, but it is not fixing the problem. All the time I am using power button to have a forced shutdown. I loved the natty nerwhal.
I just did an install of Natty into a separate partition and incurred several problems. I have a Dell-DXP061 with 4 GB of memory and an Nvidia GForce 7300LE and a Dell 27in. monitor at a resolution of 1920x1200.
Initially it booted in to Ubuntu Classic as expected due to needing a proprietary video driver. So the first thing I did was to install the recommended Nvidia driver and attempted to reboot. It would not start either Unity or Classic. So I did a re-installation and then selected the experimental open 3D driver and was then able to bring up the system in both Unity and Ubuntu Classic. I installed a number of programs including cairo-dock, which I really like, emacs23, and gnucash. I have used gnucash for years and consider it a necessity. However, the Natty version will not display correctly the "gnucash-data" file I created with version 2.2.9 that I have been running on 10.10. This is almost a show stopper for me.
When I try to do a restart, the screen goes black, "Ubuntu" appears with the little dots, three of the dots change color and the system hangs. The system only stops when I hold the power button to effect a complete power outage. Interestingly the LiveCD did not seem to have a problem with restart.
I can see how a causal user might like the Unity interface, but I don't think that I am interested. I guess I will stick to gnome for a while, at least until Gnome3 and then I am not sure where I will go.
I have recently upgraded to the 10.04 Alpha and have been unable to reboot or shutdown. I know it's just an alpha and therefore problems are bound to exist, so I tried reinstalling from a live cd of Alpha 3. But I am still unable to reboot or shutdown.To clarify what happens, I click on shutdown or reboot, the pop-up appears, I click on the shutdown/reboot button and it seems to complete it. It says that processes have been killed and something has exited with 255. But my computer is still on. I am guessing that Ubuntu is shutting down, it's just not actually shutting my computer down or restarting it.
View 5 Replies View RelatedI have a remote server (Xubuntu 10.04) which suffered an electricity brownout yesterday. The server itself is backed with an ups, but it is connected to a external firewire disk, which is not, and this disk malfunctioned as a result of the brownout.
The problem: Now, any process trying to access the external disk freezes and ends up in eternal D state in the process list, including ls and umount. Even trying to ls a directory which contains a symbolic link to a file in that drive just causes ls to freeze. These processes cannot be killed even with SIGKILL, so I proceeded to reboot but...
None of the reboot commands work. Instead they just get added to the ever increasing list of D state processes. I tried (sudo) shutdown -r now, reboot -f now and finally plain shutdown -h now. Is there anything else to try other than ask somebody to actually go to the server and pull the plug (which is not at all trivial)? Some way to tell kernel not to worry about messing stuff up, and just reboot?
we've just bought 30 newest nettops ACER Aspire R3700 with ION 2. I've tried ubuntu, kubuntu, xubuntu. Everything works as expected, but... the first one freezes when trying to reboot, shutdown or enter sleep mode. Checked on several hardware units. The desktop just freezes and nothing happens (ubuntu 10.10, both x32 and amd64). Also no one installs the wi-fi drivers, only ethernet
View 4 Replies View RelatedFrom a 11.04 Ubuntu, I installed the meta-package xfce4 (*). Now, in the xfce4 session, "suspend" and "logout" (from the xfce4-panel button) works, but "shutdowmn" and "reboot" not, they only lead to GDM. (the shutdowm option there works.)
I tried to solve that by installing the meta-package "xubuntu-desktop" (maybe there are some necessary settings included?), and in fact, the login-screen changed (it's still GDM, I suppose) and there is now a "xubuntu" session, but in that, the probem is just the same: shutdown only leads to the login screen.
In Gnome Classic or Unity, shutdowmn works as it shoulds, so it's not a general problem with my computer.
In Detail, in forst tried to install xfce4 with ubuntu-software-center, but although it seemed to succeed, there was no xfce session. In Synaptic, installing the xfce3 metapackage worked. In fact, software-center seemed to have overlooked some dependencies...
I recently migrated from Hardy 8.04 LTS (32) to Karmic 9.10 (32) so that the restricted ATI drivers and CCC would work correctly - that part is basically fine.
The problem for the past couple of weeks has been Karmic randomly shutting down, and rebooting the system after 1 or 2 hours up-time.
Why would this be happening, it was fine for the first few weeks after installing Karmic.
My system currently consists of the following;
Gigabyte MA790FX-DS5 mainboard - Jan '08
AMD 3.0Ghz Phenom II X4 945 CPU - Oct '09
4GB DDR2 Kingston HyperX RAM (1066 MHz) - Jul '09
Sapphire ATI HD5770 1GB GDDR5 video - Dec '09
Cooler Master Extreme Power Plus 640 watt power supply - Nov '09
Cooler Master Centurion 5 CAC-T05 case - Jan '08
1 pata 500 GB, 3 sata 500 GB & 1 sata 640 GB drives
2 DVD burners (Pioneer and LG)
2 x 19" (4:3) Samsung SyncMaster 943N LCD monitors
I used to have lmsensors working with the Athlon 2.8GHz dual core in Hardy, but they wouldn't work with the new Phenom 3.0 GHz 945 CPU in Hardy (and they still won't work in Karmic).
Th upshot is that I don't have cpu, system, or graphics temps; nor do I have any fan speeds, so I don't know what temps or fan speeds my system is running without rebooting into BIOS (which isn't much good as I really need to know what's happening when I'm using the OS itself).
Does anyone know what could be causing this random shut-down/reboot problem?
i searched the forum about this subject, i found many post but nothing useful. i also wonder why a normal user is not prompted to authenticate as root to perform these tasks. i thought the file /etc/sudoers but i don't think this is the point. i tried the group "shutdown" but does not exist. i read that this is expected in ubuntu server so it should exist even in the desktop version, i guess.
View 3 Replies View Relatedubuntu with windows xp on my laptop. My problem is everytime I out of ubuntu, the vga driver seems to disappear. I can't start x server, and when go into windows xp, the screen is on very low resolution state. After go into win xp and reboot, I can boot either ubuntu or winxp normally, everything is okey again. In summary:- When go into XP and reboot, I can boot ubuntu and XP normally.- When go into ubuntu and reboot, I can only boot with very low resolution in XP and can not start x server if boot ubuntu
View 3 Replies View RelatedI recently updated my 10.04 (se remix,I guess it's only preinstalled language support and some other thinks like link to ubuntu se homepage; http://ubuntu.se/content.php/322-Ubu...it-uppdatering!) to 10.10.
I now I'm stuck with a quite annoying (but not sever) error. When I shut down the computer doesn't turn of it just restart?!
I know I had some similar issue with my old EEEPC but that was a GRUB 1 error and now I'm running the latest GRUB so ...
I have an mysql innodb ~ 20gigs. Normally shutting down mysql (service mysql stop) takes a few seconds. When I reboot Ubuntu with the reboot or shutdown command it just reboots it super fast without mysql logging (/usr/sbin/mysqld: Shutdown complete) Also during this shutdown the following is failed: umount2: device or resource busy /data: device is busy.
mysql is setup to read from /data . Why is ubuntu not waiting for mysql to properly shutdown before unmounting the filesystem and rebooting?
I remember that in previous Ubuntu releases, it was possible to restart/shutdown at the logon screen via the keyboard. I think it was via the F10 key. Can this function be brought back?
View 1 Replies View RelatedI am facing the issue that the PC not capable to shutdown or reboot; In order to debug that, htop tells me the running processes but all seems normal, I killed few but still cold reset is needed.There is certainly a problem somewhere. the best would be to know which process are weirdly hanging. It could make this testing debian bit better to know which package has these issues.
View 1 Replies View RelatedI want to disable Reboot and Shutdown options from the drop down menu in Ubuntu 9.10. I tried this:[URL] I also tried to modify the gdm.conf file, but the changes I made, made no difference.
View 2 Replies View RelatedTwo or three times on a daily basis it just freezes and I do not know why. For example, I am doing some minor coding, surfing the web and just some regular stuff and suddenly, out of nowhere, it just freezes. I cannot force reboot, cannot shutdown, cannot run, cannot enter terminal, nothing. Totally helpless. Only physical reboot do the work. Never had this issue before.
View 9 Replies View RelatedRecently I installed Fedora 12 64bit in my HP Compaq 6720s. Among many other problems that I had and I solved with your help, I have the following problem:When I restart or shut-down Fedora 12 it crushes and hangs and only thing that I can do is to stop and restart my laptop by means of ON/OFF button.My question is:Is there any way to see this error (maybe some log file or something) so I can send this message or log file here in this forum and get some help?
View 1 Replies View RelatedI hoping someone can point me in a direction. I installed F13 KDE from the live cd and now when I Shutdown or Reboot, it takes 2 minutes and 8 seconds for the machine to power off. Yes, I timed it.Happens everytime like that. Even when booting from both "mainstream" live cd and the KDE spin live cd. When I hit the Shutdown or Reboot, it goes through the daemons/services shutdown the flashes up the Halting System or Please wait while the system reboots messages (respectivley), turns off the LCD and then just... sits with the power light on and hard drive activity light on. I should mention this is on a Toshiba Laptop about 2 years old now. Intel Chipsets. (Satellite Pro S300M-S2142 if anyone is really curious). The hard drive light stays on for about 1:03 minutes and then it turns off, at 2:08 minutes - the Power light finally turns off and the thing finally shuts down or reboots. If this sounds familiar, it's because it is and I've posted about it with F12 and it's still there with F13. Running kernel-2.6.33.3-85.fc13.x86_64
View 1 Replies View RelatedAfter a couple of days, some commands related to the disk (df) or files (ls) or killing process (kill -9) doesn't respond. Even I can't reboot or shutdown my server. After an hard reboot, some files are not here anymore or the log files are not filled anymore until I restart.My disk are behind the RAID controller i6 and are configure in RAID 1. The disks are two HP SCSI 72,8GB 10k RPM.Maybe I am totally wrong to check the disk access side, so I am open to other explanation.I can also add that my CPU is running under 1% et my RAM under 10%.
View 14 Replies View RelatedI don't follow why the Suspend option is there and the Reboot and Shutdown is not. Can anyone guide me to the code needed to add the selections. I know I can use a Terminal to shutdown or reboot but a simpler solution would be nice. I expect there are methods to fix most of what I don't like about Gnome 3 but I haven't found them yet. Is there a central place for the solutions needed to deminimalize Gnome 3? I really prefer one click control.
View 4 Replies View RelatedI want to change the reboot of ctrl+alt+del for shutdown, how i can do this in Fedora 15 ?
View 1 Replies View RelatedA couple of little niggles seen with KDE4.6. On 32bit install, (openSUSE11.3 was clean install)
-- reboot and shut down do nothing but hibernate and sleep are ok, can only powerdown with su privileges,
-- order of applications in plasma bar change after reboot.
On 64bit install, (openSUSE11.3 was update of openSUSE11.2)
-- slow poweroff overcome with new user profile, (no longer a problem with latest update)
-- inconsistent mouse curser theme, over desktop theme is Oxygen White, over application windows its DMZ
(resolved mouse cursor theme issue on 64bit install.
-- /etc/sysconfig, parameter X_MOUSE_CURSOR="DMZ"
-- and
-- /usr/share/icons/default was a link to DMZ
-- /usr/share/icons/default.kde4 was a link to oxygen
-- changed so that both were linked to DMZ
-- mouse cursor now consistent within windows and across desktop.
On one of my computers that I upgraded from 11.3 to 11.4 with a SSD HDD, it no longer umounts any disks on reboot or shutdown, there are no errors shown, it goes from sending TERM and KILL to rebooting.here is my fstab:
Code:
/dev/disk/by-id/ata-OCZ_SOLID_SSD_MK0109030A6100011-part1 /boot ext4 acl,user_xattr,noatime 1 2
[code]...
I've added entries to my Openbox menu labeled Reboot and Shutdown. Problem is, reboot and shutdown h only work as root, and I never login as root. I've tried su-to-root -c reboot, but the menu entries remain unresponsive. I do not have sudo installed because I feel it is a security issue. However, I found that sudo reboot works with the menu entry, but only if my account is set to use sudo without a password in /etc/sudoers. I use tint2 as my panel, but have had no luck with finding a shutdown/reboot button.
View 4 Replies View Relatedi have a server which was halt on last Thursday(may be halt by some one). using Oracle Enterprise Linux 5.3.
View 2 Replies View RelatedI want to do a shutdown -rF 3:00 to reboot my RHEL server at 3am tomorrow and force an e2fsck on each volume. But I want the e2fsck to run with the -y switch so it automatically answers yes so it will fix any problems it find automatically.
I can't find anywhere where it says if it will do this or not. does anyone know or have proof? Or is there a better way to do what I'm trying to accomplish?
Basically my problem can be neatly summed up as the problem described at both here and here. I can only presume it's a rather uncommon problem to do with a particular hardware setup since I can't find any widespread bug reports of it, but it is (on my system at least) highly replicable. I can reboot my system from Natty and it either one of two scenarios. It can reboot the system (as first asked) then reboot again in the middle of POST and splurge an error about interrupting POST at me (and keep giving me this error every reboot till I go into the bios and resave some settings).
Alternatively, it can get all the way into grub, where I can dual boot into Windows, windows will get some arbritary point in (usually the login screen give or take 10 seconds) and then reboot at random. It's not even a windows crash since I've disabled auto-reboot.I'm not sure what's causing it but I can only presume it's something at the kernel level, since I'm not sure anything else would have the kind of power needed to interfere with the system at an 'outside the OS' level. As such I wouldn't have any idea how to go about fixing it, but I can hope that someone here may be able to point me in the direction of potential settings I can change (probably BIOS I guess) that might aleviate the issue till a fix is found.