Shutdown to a Halt and restart

I've got critical patching this weekend on 6 HP UX machines, back to back and the customer has requested to shutdown, and halt the machines and to bring it up at a later period. The thing is the servers are located offshore and we are just the support team. I have a special login thru a console where I can shutdown and bring up the servers.

Here's the shutdown and halt command:

shutdown -h now

What is the command to start up without actual pressing on the power on button?

Im using HP UX 11.31 here

Thanks in advance.

---------- Post updated 06-25-10 at 12:12 AM ---------- Previous update was 06-24-10 at 10:29 PM ----------

be kind and reply me please. I need to put up calendar notification for the guy to run commands on Sunday

Every Integrity server I've seen so far has some kind of remote management facility, most probably yours too. Just connect to the iLO card and you can power up/down the server.

If this is a cluster or there are NFS mounts you will need special instructions to shut down in a sensible manner. These instructions may or may not include a "shutdown" command.

You will need to know more about you "special login thru a console" and what piece of hardware you are connected to and how to toggle between console and server remote management. Is it an iLO (Integrated Lights-Out) or a MP (Management Processor) or a Web Console? We assume it is not just a telnet session.

The unix "shutdown" command just shuts down the Operating System and halts the processor. It does not turn the power off. Most remote power controls only control the system unit not any add-on hardware such as disc arrays.

Beware that unix "shutdown" does not shut down databases etc. unless "rc" scripts have been installed to achieve this.

If you are in a hurryand you have already closed all applications and client connection, this method answers any prompts:

cd /;/sbin/shutdown -h -y now

Hi all

Thanks for your replies. Unfortunately we don't have iLO for this particular client, just a remote console IP which can be accessed from telnet session. This box had vpar and npar which had to be turned off first then halt the system. it was a messy patching that weekend. Someone googled and found it had to be done from console itself, i think MP options.

Thanks all!

`init 5` powers off the box in Solaris.. Check it out whether it works in HP-UX as well.

See if you can find documentation on init. That should give you several levels of operation you can initiate from your login. Be careful though, you would need to use the same level of access to log in again.

u can try these

reboot
# shutdown -r -y now
or

# telinit S
# shutdown -y now # shutdown 0

hi there
m facing a very serious problem with my system
when i turn it ON everything seems to be working
like it comes till the linux starting modes and asks whether to start linux normally or failsafe mode selecting any of the two options it ends up at a state shown in the attached image
plz help me as soon as possible
regards

http://cid-8f2187e801f053f1.office.live.com/self.aspx/.Documents/1.jpg

You are having a kernel panic. I would run "fsck" on the file systems.

---------- Post updated at 08:37 AM ---------- Previous update was at 08:26 AM ----------

Looking closer I see the system is fscking itself. You might go to your support site for your server and OS to find out their recommendation for this issue.

If you like I can tell you some of the steps we take with our HP Proliant Servers and SCO Unix OS to deal with a kernel panic.

well mikep9 thank you for helpin me
but the thing is that i dont knw much abt the linux u can just take me as a newbee or a beginner
please tell me the steps you are talking about
tht ll b really gr8 of u
thanx

if you shutdown the server electrically there IS NO command to turn it back on, your OS is in a coma !! your CPU/RAM are empty .

If you dont have a remote management system that controls the power switch , you will have to ask the security gard to push the right button :slight_smile:

Ding! We have a winner!

If you want the box to shutdown and immediately come back, you can use some variant of reboot. If you want it to shutdown and then come back at a later time, you're SOL without special hardware or a human standing next to the box.

If you wanted to get wacky, you could have the box reboot into some kind of not-entirely active state, like single user mode, wait for a pre-determined amount of time, and then boot into the normal fully-active runlevel. You better be damn sure of yourself though, because if you make a single mistake, it won't come back and you'll need someone to debug it from the console.

Or, more sanely, you could reboot but disable whatever services you don't want running until the time has passed. EG If the reason you want it "off" for a while is to keep people from surfing your web server, disable the web server daemon, reboot, wait until the time is passed and then start the web server.

there's a feature on ethernet network cards that's called WOL (Wake-On Lan), this will turn your computer or server on, of course you have to configure it first. However they must be reachable from your place and poke a hole in the firewall to the port needed (I don't know what is it, prolly 23?).
From your computer you must use a program that sends this "magic packet" to each one of those IPs, and they will be powered-on.
Hope that helps

For a machine to wake up based on network activity, the machine cannot be shutdown.

The original poster specifically mentioned the machines would be shutdown (not asleep or in a sleep or suspended state).

Hi.

I have had a few boxes (old IBM Intellistations) that claimed to have this capability, but I don't recall ever enabling it because I didn't need it.

According to Wake-on-LAN - Wikipedia, the free encyclopedia there are a lot of variables to consider, but in at least some situations, all that is needed for wake-up is that the box be plugged into power, and receive the magic packet ... cheers, drl

It's not that simple. From the article you cited:

Plus, it has to be configured in the motherboard, BIOS, etc.

You're right, however I do not see a reason to keep the machines down, when you can just take down the services