Server :: Shutdown The Nodes From The Master Terminal Using "shutdown -h Now" Get Shutdown?
Dec 10, 2010
I have installed a cluster computer with 10 nodes . The manufacturer is HP . All nodes and the master node have redhat enterprise linux installed in them . When I shutdown the nodes from the master terminal using "shutdown -h now" they get shutdown . But they dont get completely turned off . This issue bothers me when the power supply is given , all nodes boot up simultaneously generating a huge heat .
Thing to note : When we shutdown our PC they get completely turned off . When the power supply is given , a press on the Power On button is required to boot the system. But , why does it not happpen in the case of cluster? Is there any other way of completely turning off the nodes from the master terminal ?
I have a cluster script (CentOS 5.4) and I need a UPS for a shutdown. It should look like this ... The first node must wait until the second node has completed several actions and has been completely shut down. So I need a script with a shutdown wait until the other node is ... I was thinking of a test using ping. Alternatively, I would also have an IPMI interface. However, the "pause" may last a maximum of 10 minutes ... Then the wait must be ended.
Recently I installed vncserver (tigervnc) on my desktop. Ever since my computer refuses to shutdown normally. At shutdown the following message pops up: Quote: System policy prevents stopping the system when other users are logged in Then I have to enter the root password to shutdown. If I stop vncserver before, the computer shuts down normally.
when my pc boots and shuts down my monitor goes into 'input out of range' mode for a bit between the gui and the text only phases of boot/shutdown.is there a way to fix this? or where to start troubleshooting?also, when it shuts down it hangs after coming back to the text only part
I cannot locate shutdown log for Linux shutdown to check various activities carried out during shutdown. I can view Startup Log which is availble on console>Applications>System Tools>System Logs.
I have included Shutdown/Startup in dbora, so that Oracle 10gR2 Shutdown/Startup will be automated during OS Shutdown/Startup.
I want to check Shutdown log because Oracle Shutdown was not running, as from $ORACLE_HOME/shutdown.log contains no entries, where as startup log contains latest startup details.
That means here 2 issues are there. One, I want to locate OS Shutdown Log and the other being Why Oracle Shutdown not getting executed.
I cant shutdown without running sudo shutdown. When I try to use the default gnome shut down it takes me back to the logon screen. Fresh install today and I've had the same problem on other installs.
Ubuntu will randomly pop up the shutdown menu and then shutdown.It seems to happen when im in firefox and typing and it has been difficult to replicate. I dont think it is a temp issue since watch sensors shows temmp of 40-50C. Someimtes it happens every minute someimtes i can go 10min without it happening.
Dell Inspiron 1525 ubuntu 10.04 (only os on system)
looking for a command that shutdown/reboot my ubuntu just same as process that happened when I press shutdown buttonIn fact I need to close all programs that are running and then PC shutdown (that happened when I press shutdown button).
I'm new to Ubuntu and have spent several days trying to make a few simple alterations to my Myth 9.10 installation. My biggest task was to get the MCE "power" and "start" buttons working, which they now are - sort of.
The problem is with the shutdown command that the power button activates seems to be different to the shutdown command from the taskbar shutdown menu i.e. when I switch off the computer with the remote it restarts with the "recovery" menu as it wasn't shutdown properly. Same thing happens with the shutdown command from a terminal window. Shutting off from the desktop menu is fine.
I did a live upgrade from 11.3 KDE and observe a following issue.When I press the shutdown button on the laptop it initiates the shutdown and shuts down fine but after a significant delay of time (something like 30 seconds). When I click the shutdown button in KDE it initiates the shutdown instantly. This was not the case in 11.3 where the shutdown worked the same regardless of the method that triggered it
When I try shutting down Ubuntu (10.04) via the terminal (sudo shutdown now) it locks on the splash screen. I doesn't doe that when I shutdown with the button.
Naturally i don't want to harm my system but I would like I shutdown via the terminal. I understand there are shutdown poweroff and halt commands. Which is the safe one (like as if I just did it using the GUI) at the moment I am just using shutdown now and that seems to work fine, I just want to check that it's not harming my system and that this command does everything it needs to ie closes all programs and shuts everything down in a safe way.
I have a habit of watching videos when I go to sleep. So I decided to start using, for example, the following when I laid down:
sudo shutdown -h -P 60
Of course this shuts down the computer in an hour. I was wondering if there was a way I could get the computer to beep a few times for the last 10 Minutes and then a few more times for the last 5 minutes?
I was playing with the Gnome-shell and my gui crashed. I was stuck in full-screen Terminal (i.e., Ctrl Alt F2) but I could not figure out how to shutdown/restart the computer.Anybody know if there's a command for this that works from within Terminal?
I use Rapidshare a lot to download files and wanted a simple terminal command or program that would shutdown my monitor so I don't have to manually do it.
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.
My home desktop computer upgraded to Ubuntu Lucid Lynx 10.04 without any problems. However, after all was said and done, the boot up and shut down screens look like crap. They are all in terminal text, and without any graphics. I have attached pictures of what they look like. This can't be right. Is there a way I can set the system to use the proper graphics when booting up and shutting down? I like my computer to be pretty.
This is what it does for most of the boot process: boot1.jpg It does this just before the screen where I enter my password. boot2.jpg This is how it looks when it shuts down: shutdown.jpg
Two 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.
I've used the following script here: [URL] to upgrade Alsa to 1.0.21 in Ubuntu 8.04. Now whenever I run:
Code:
sudo shutdown -h <time> or sudo reboot from the terminal I get a rather annoying beep sound. What's even more annoying is if I use the shutdown command to specify a time I get a beep every 10 minutes or so. I've tried disabling the terminal beep in the terminal profile, disabling the beep in System/Preferences/Sound, adding "blacklist pcspkr" to /etc/modprobe.d/blacklist, and running gconf-editor from the terminal and setting /desktop/gnome/peripherals/keyboard/bell_mode to 'off' rather than 'on'.
I use centro 5 to run a game server with the command ./srcds_run quit -game cstrike -nocrashdialog +map de_dust2 +maxplayers 36 +ip 95.154.192.34 +port 27015 -tickrate 67
which then starts a 36 slot CSS game server but as soon as i close putty it ends now i tried nohub ./srcds_run quit -game cstrike -nocrashdialog +map de_dust2 +maxplayers 36 +ip 95.154.192.34 +port 27015 -tickrate 67 and ./srcds_run quit -game cstrike -nocrashdialog +map de_dust2 +maxplayers 36 +ip 95.154.192.34 +port 27015 -tickrate 67 > srcds.log 2>&1 &
i'm woundering if it something to do with centro 5 why nohub isn't working becouse it works for others either
After 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%.
I got a question, is there a script or program that automaticly boots my server and shutdown at give hours of a dayI want to have my server running from 7am till 8pm ever weekday (Monday-Tuesday-Wednesday-Thursday-Friday)
How do I make a server wait on shutdown for a set amount of time?I tried making a service that just does Code: sleep 7m and made it first priority on shutdown but it seems to ignore itI'm pretty sure it runs... I'm currently testing that to make sure
I got a question, is there a script or program that automaticly boots my server and shutdown at give hours of a day I want to have my server running from 7am till 8pm ever weekday (Monday-Tuesday-Wednesday-Thursday-Friday) is this possible? I'm running a Ubuntu 10.04 server with Zentyal on
My RHEL Machine is a Build server and always gets shutdown / rebooted at around 5:30 every evening. No idea whats going on as developers were unable to connect to the machine since three days. When I am visiting the physical server probably next morning (since last 3 days)its doesn't show anything and all i reboot the machine and it comes up without any issue. how to troubleshoot?
I have Ubuntu 10.04 server edition which comes without any GUI.Some of the web applications are present on it.But the problem is from a past few days if I reboot then immediately after a reboot the server shows me a process polymouthd which takes 96% of CPU which makes my server damn slow is there a way to find out what is polymouthd doing in my server and how can I disable.
