When I shut down the computer, it does not remain shut down. This is different from "restarting" the computer because when I "shutdown" the computer powers down, the fan and disks stop spinning for a second, and then everything starts again. When I "restart" the fan and disks remain spinning throughout the restart process.Further, the computer is dual booting with Windows XP Pro. If I shut down from Windows, the system remains shut down.
System Information:
Ubuntu 10.04 Lucid Lynx
kernel: 2.6.32-26-generic
i just wanted to check if its something silly ive overseen and if anyone else is having this problem...im running Ubuntu 10.04.2 LTS with latest version of squid 2.7.STABLE7-1ubuntu12.2. now when i shutdown or reboot the system, it says something along this lines of umount: /var is busy (check using lsof...). this is followed by text in red: [fail].when the system starts up again, i can see /var journal is recovering, so the /var partition was not cleanly unmounted during shutdown. obviously, there is a risk of filesystem corruption here. FYI, i have /var and other important mountpoints as separate partitions (LVM; ext4).
to confirm my suspicions of squid still running during shutdown, i checked /var/log/squid/cache.log and there is no indication that it received the signal to terminate. if i manually run "stop squid", then cache.log would show that squid has stopped successfully (or words to that effect).to confirm that /var is locked by squid during shutdown, ive added a script to run "lsof | grep var" before filesystems are unmounted. and voila! it indicates that various files used by squid in /var such as swap.state are still open. hence, the next system startup would result in /var recovering journal again.finally, i tried running "stop squid" before issuing the shutdown command and it successfully unmounts /var and i do not get /var recovering journal on the next system startup.
I have opensuse 11.4 (Gnome + KDE) installed. The problem is with Gnome. When in KDE, everything works fine. But in gnome, when I shutdown/restart, it merely logs off the session. Then I have to shutdown it from the menu in the login screen.
I've made a Live CD of version 10.04 on a machine running 10.04 (amd64). The disk boots fine on a 2nd machine but does not boot on the machine that created it. The CD/DVD is new and works for other things so I don't think it is this. The Live CD gets to the ISOLINUX screen but instead of "Loading" the screen goes blank and the system shuts down. I've tried everything I can think of (the disk works fine on another machine).
I have an old geforce 6200 AGP card and I upgraded from 9.10 to 10.04 Lucid, now my video driver won't stay loaded.It says it is loaded in the hardware drivers, but no advanced graphics work, until I go into System/appearance and click extra visual effects. Then it looks for drivers and asks to keep these, I say yes and can activate Compiz effects and all is well. Until I reboot and have to start over
my 9.04 64 bit ubuntu machine is having some major stuttering issue, as in it can't stay on track and doesn't respond to keys at certain times, the normal flashing text bar is flashing very quickly and very eradically as well. I reinstalled ubuntu keeping my /home on a separate partition, and then upgraded to 9.10 thinking that'd fix it, it didn't.at this point i don't know what's happening, My windows partition is fine.
I could easily go to ms system monitor display by clicking on background of desktop and finding it through there to change settings related to desktop. I want to be able to watch a movie without the desktop screen saver thing going off. where can extend it to longer than 2-3 minutes on linux mint?
when I open this it opens up greyed out for a split second then closes.I started it in a console ,it did the same but the following was left in the terminal
Is there something that blocks cron from running a shutdown command? I'm doing a daily bounce to break an attack (I have thread about that in security forum), but I always end up doing it manually. The cron log shows it being fired off at the right time...but the server never bounces. I thought maybe I just missed it, but there is nothing in messages that shows the server restarting (unlike when i do it manually, you see the start-up logging).
I'm in 9.10, I had KDE 4.3 now with SC 4.4, and it doesn't reboot or shut down from any graphical way I can access. Power management works otherwise, and I can shut down from the command line.
I have a server Hp proliant DL160 G6 with CentOS 5.4 . When I do shutdown -h now it doesn't poweroff.
I try differents options for acpi in menu.lst file. acpi=force, acpi=noacpi,acpi=off,acpi=ht but there's the same problem.
This the stdout when I do shutdown: Halting system... md: stopping all md devices. Completed flushing cache on controller 0 ACPI: PCI interrupt for device 0000:05:00.1 disabled xenbr0: port 2(peth0) entering disabled state ACPI: PCI interrupt for device 0000:05:00.1 disabled Power down. acpi_power_off called
I show you any specific information about my server:
I'm getting some trouble with Wake on Lan. The main question is: when I shutdown a PC through Windows, the WOL works well, but it doesn't happen when I shutdwon the same PC through Linux. It happens in all of my PCs here in the company.
I shutdown around 4 - 5 hours ago which would be around 14:00 to 15:00 time range. But as you can see there's no entry for it. Why? and how can i find when i last shutdown?
Code: last lyle pts/1 :0.0 Tue Jul 6 19:18 still logged in lyle :0 Tue Jul 6 19:15 still logged in lyle tty7 :0 Tue Jul 6 19:15 still logged in
When I bring down a certain machine with some nfs mounts using init 0, it hangs forever while trying to bring down the mounts, but if I bring it down using halt -p (which I've read just calls shutdown if I'm in init 3), it comes down in a timely manner. I've also read that shutdown still calls all the rc.d kill scripts just like init 0, so what is actually the difference between them? Is it this:
Quote:
All processes are first notified that the system is going down by the signal SIGTERM?Does init not do that? I'm not trying to directly troubleshoot why NFS makes me hang with init 0 at this point, just wondering why shutdown works whereas init 0 doesn't.
I know the problem has been partly solved in this old thread [URL] .....
Now we have Jessie as stable, yet LXDE doesn't shutdown properly:
On the same computers, Wheezy LXDE shut down very fast
I installed Jessie from the netinstall image.
On a 2007 computer, it's like the old days with a Pentium II running some version of Puppy Linux or Slitaz. The system shuts down after a while but the computer remains on.
On a 2013 laptop, I added the line init=/bin/systemd in the Grub default file as advised on the old thread above. The laptop shuts down after a while, the system first, then the hard disk goes to sleep, then all the leds are off.
If I run the magic command, the computer shutdowns in a breeze, perhaps even quicker than good old Wheezy:
Code: Select all# systemctl poweroff
Now, is this still a systemd bug? Doesn't look like it since the systemctl command works. Is it an LXDE bug? Looks like it in a way - if the LXDE shutdown button enabled the systemctl poweroff command, I suppose the button would work?
Is there a way to make the LXDE shutdown button run the systemctl poweroff command?
I'm glad Wheezy is still with us because I wouldn't install Jessie for newbies — they'd think shutdown (through clicking on a button) is even worse than in Windows.
i have installed ubuntu ultimate edition 10.04 in my toshiba c650 recently,however it is taking too long before it startup. 2 when i log off the cursor still remain untill all power have been discharged. what could be the problem
i have centos 5 system and when i select shut down from the the top taskbar there appears a small rectangle that has an option of shutdown, restart and 60 sec timer but in our case neither the timer is ticking and when we select to shut down the system, the button color for shutdown shows we have pressed it and then the system doesn't goes into shut down immidiately, and the little rectangle window stays there, you can continue to work on the desktop and then it shuts down after 30 seconds
From couple of mins my system shutdowned without my permission I thought I'm infected or something because I installed aMSN so I thought it's because of it, but I checked my syslog and found this:
May 5 00:01:30 spuny-laptop kernel: [ 2441.497050] CE: hpet increasing min_delta_ns to 15000 nsec May 5 00:17:01 spuny-laptop CRON[1912]: (root) CMD ( cd / && run-parts --report /etc/cron.hourly) May 5 00:37:32 spuny-laptop pppd[1560]: Protocol-Reject for unsupported protocol 0xac05 May 5 00:38:15 spuny-laptop pulseaudio[1426]: ratelimit.c: 2 events suppressed May 5 00:48:06 spuny-laptop kernel: [ 5237.586974] hda-intel: IRQ timing workaround is activated for card #0. Suggest a bigger bdl_pos_adj. May 5 00:50:22 spuny-laptop kernel: [ 5373.683347] Critical temperature reached (100 C), shutting down. May 5 00:50:22 spuny-laptop kernel: Kernel logging (proc) stopped.
Temperature reached is that what cause system halt? Also when I press ctrl+alt+Fn I see blank screen why is that?
I am using Ubuntu 10.04. From last 3-4 days, after updating, I am not able to shutdown the system. I try to use command, but behavior is same Whenever I try to shutdown the system, it exits from desktop environment and a white screen displays on screen. And nothing happened. One time I did wait for 1/2 hr, but system dont seems to power down.
It appears I've got some strange driver problem.. When I shut down this computer, the NIC apparently doesn't go off. The LEDs next to the ethernet socket keep blinking, so does the LED on my ethernet switch.
I don't have this problem when using XP, only Karmic. That leads me to think that there's something wrong with the network driver. My NIC is on-board, the ASUS M3A32-MVP. According to System Info this is the Marvell 88E8056 PCI-E. It seems like ASUS doesn't have the drivers on their website (anymore), because their website search returns empty handed. Also the motherboard product page doesn't appear to know it.
Anyone have any tips / ideas? I'm just unplugging the machine before turning it off now... as it appears to be disturbing the rest of my network
My Ubuntu file server sits under a desk and shares files with the network without a hitch, and in a perfect world I wouldn't ever need to shut it down (I reached 6 months uptime once). However, since it occasionally needs service, or additions and needs to be moved, I need to shut down.
The trouble is, the power management system is borked, so whenever I issue "sudo powerff now", the system halts, but the PSU stays on. I usually wait a few minutes after and flip the PSU switch, but I'm never sure if the system is already down.
Is there a way to reorder the way services shut down so that I put SSH last, and therefore know when the system is down when my session is disconnected? Is defaults.rc or whatever responsible for that?
Just installed Ubuntu 9.04 last night. All seems perfect except on shutddown. It seems to go through all shutdown processes but right about the time you expect the computer to turn off a message says: "system halted [4027.514883]" Have Googled it but no matches. If I just push the on/off button at that point it shuts off immediately
I tried the above command on my pc. It broadcasts the message passed , but I noticed one thing that during this time( 2min) normal users are not allowed to login onto the terminal.
am starting to get this figured out. finally got the wifi working on a HP touchsmart tx2 laptop and once i give ubuntu a total system shutdown command this system restarts, is this normal or do i need to fix something?
I 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 currently run kernel 2.6.34.7-66.fc13.i686 (sort of). When I select from the Gnome menu System -> Shutdown and select Shutdown from the dialog, my system only logs out, presenting me with the greeting screen. While this is a minor problem and I rarely shutdown my machine, it is mildly disconcerting.I have dropped back to 2.6.34.7-63.fc13.i686 and that shutdowns properly using this method. (Also, 2.6.34.7-61.fc13.i686 works properly). I can imagine that it might close some security issue in which an unauthorized user is able to halt the entire machine. Especially if this is something that will continue in future releases of the kernel.
after installing linux mint 7, I have been getting one beep on shutdown, a google search on this came back as a ram problem...but then i ran across a bunch of posts on ubuntu forums about one beep on shutdown, with an older version of ubuntu, grep does return some paramter errors, but in the mint bug report page those are listed as : benign ignore. it doen't bother me in the least, as long as it isn't a warning of impending hardware failure.
