Sponsored Content
Top Forums UNIX for Advanced & Expert Users emergency shutdown best practices. Post 302244828 by broli on Wednesday 8th of October 2008 04:49:00 PM
Old 10-08-2008
Quote:
Originally Posted by jsw371
Thanks for the help.

for host in `cat hostlist`; do ssh $host shutdown <arguments>;done

will work for me.
that will work if you have a unix server with a simple config, totally managed trough systemv scripts.

but, in reality, you have server with multiple services, servers containing multiple virtual servers.
some services need to be properly shutdown with some command, and some even need some time since you issue the stop command before you could actually bring down the Os itself.
that is why i pointed that instead of the shutdown command, use a script.
it should be named the same way, in the same path on all servers to allow a simple while in the "master" server.

and each script will be responsible for all the logic for the stop procedure of this weird services that cant simple be killed. the sleeps to ensure they have some time to end correctly, ect

i remember one place i used to work, they used a protocol over tcp/ip to transfer messages between servers.
you had one gateway, receiving msg, distributing them to the proper apps and databases, and replying to them.
this gateway was also listening to other gateways in other countries from the same company.
the thing is that you couldnt simple kill everything down.
you had to isse stop commands to all the backends, to stop answering requests, but dont kill the current ones, after some time (something like 10 mins)
in the meant time, you had to tell the gateway there was problems, so it had time to tell others gateways, so they could start answering the request sent to him.
after all the backends where stoped, , you had to stop the gateway.

and that is a simple example. i have seen way more complicated companies, where they had multiple machines working in line.
they neede a complete hour to shutdown the hole procesing line, without lossing data in between
 

8 More Discussions You Might Find Interesting

1. SCO

Emergency boot

I need to boot an OpenServer 5.0.5 server but I don't have emergency boot disks for it. There are some boot disks of other servers. Can I use these disks, changing defbootstr ?. How ?. The fact is that administrator can't login as root and it seems to be a corrupted auth system issue. Other... (2 Replies)
Discussion started by: dags
2 Replies

2. Shell Programming and Scripting

Need Emergency help with script!

I'm trying to write a script to push out to all our servers some Veritas add-ons. I want the script to push to all servers and if there server hardware matches the uname -i statement, it will install a additional add-on.. The script keeps giving me a error on line 29. Here is the script.... (3 Replies)
Discussion started by: soupbone38
3 Replies

3. UNIX for Dummies Questions & Answers

Script to force Oracle database shutdown when shutdown immediate does not work

I have Oracle 9i R2 on AIX 5.2. My Database is running in shared server mode (MTS). Sometimes when I shutdown the database it shutsdown cleanly in 4-5 mints and sometimes it takes good 15-20 minutes and then I get some ora-600 errors and only way to shutdown is by opening another session and... (7 Replies)
Discussion started by: aixhp
7 Replies

4. Ubuntu

Emergency help with ubuntu

Hi guys i have some question about ubuntu(10.10) 1.what time scheduling & page replacement algorithm have been used in ubuntu 2.how to create a process 3.how to kill a process 4.how to send information to a process 5.how to see a process 6.how to increase priority of a process 7.how to... (1 Reply)
Discussion started by: mortez28
1 Replies

5. Solaris

Emergency !!!Help Please--- NFS

Hi Guru's, I am unable to mount NFS share on unix system (DG/UX) which is nfs client. Error: mount: /nfsshare: Invalid argument mount: giving up on: /mountpoint i tried following commands mount -t nfs remotehost:/nfsshare /mountpoint Error: mount: /nfsshare: Invalid... (1 Reply)
Discussion started by: Justin John
1 Replies

6. Solaris

Best practices

Dear all, Kinda lame question but i'd like to hear your experiences and advice. Question in short ----------------- What permission should a mount point "ideally" have - i think it's root. Ex:- /usr/app/ i'd set the app to be owned by root and within /usr/app i would create another... (1 Reply)
Discussion started by: ossupport55
1 Replies

7. Shell Programming and Scripting

UNIX emergency

can anyone please tell me that how can i boot unix from a cd? full procedure. it's an emergency. reply asap (1 Reply)
Discussion started by: niket agarwal
1 Replies

8. Linux

Virtualization best practices

Hello admins and gurus I have a controversial topic: now we are investing in a new Linux OS that will hold our Sybase database. The server will virtualized on a VMware server hosted on SAN storage. Now the question is, when we install the database engine is it better - in terms of performance -... (1 Reply)
Discussion started by: abohmeed
1 Replies
gateways(4)						     Kernel Interfaces Manual						       gateways(4)

NAME
gateways - Specifies Internet routing information to the routed daemon SYNOPSIS
/etc/gateways DESCRIPTION
The /etc/gateways file identifies gateways for the routed daemon. Ordinarily, the routed daemon queries the network and builds routing tables. The routed daemon builds the tables from routing information transmitted by other hosts directly connected to the network. How- ever, there may be gateways that this command cannot identify through its queries. These unidentified gateways are known as distant gate- ways. Such gateways should be identified in the /etc/gateways file, which the routed daemon reads when it starts. The general format of an file entry in the /etc/gateways file is: Destination Name1 gateway Name2 metric Value Type The following is a brief description of each element in an /etc/gateways file entry: A keyword that indicates whether the route is to a network or to a specific host. The two possible keywords are net and host. The name associated with Destination. Name1 can be either a symbolic name (as used in the /etc/hosts or /etc/networks file) or an Internet address specified in dotted-decimal format. An indicator that the following string identifies the gateway host. The name or address of the gateway host to which messages should be forwarded. An indicator that the next string represents the hop count to the destination host or network. The hop count, or number of gateways, from the local network to the destination network. A keyword that indicates whether the gateway should be treated as active, passive, or external. The three possible keywords are as follows: An active gateway is treated like a network interface. That is, it is expected to exchange RIP (Routing Information Protocol) routing information. Information about it is maintained in the internal routing tables as long as it is active and is included in any routing information that is transmitted through RIP. If it does not respond for a period of time, the route associated with it is deleted from the internal routing tables. A passive gateway is not expected to exchange RIP routing information. Information about it is maintained in the routing tables indefinitely and is included in any routing information that is transmitted through RIP. An external gateway is identified to inform the routed daemon that another routing process will install such a route and that alternative routes to that destination should not be installed. Information about external gateways is not maintained in the internal rout- ing tables and is not transmitted through RIP. Note that these routes must be to networks. EXAMPLES
To specify a route to a network through a gateway host with an entry in the gateways file, enter: net net2 gateway host4 metric 4 passive This example specifies a route to a network, net2, through the gateway host4. The hop count metric to net2 is 4, and the gateway is treated as passive. To specify a route to a host through a gateway host with an entry in the gateways file, enter: host host2 gate- way host4 metric 4 passive This example specifies a route to a host, host2, through the gateway host4. The hop count metric to host2 is 4, and the gateway is treated as passive. To specify a route to a host through an active Internet gateway with an entry in the gateways file, enter: host host10 gateway 192.100.11.5 metric 9 active This example specifies a route to a specific host, host10, through the gateway 192.100.11.5. The hop count metric to host10 is 9 and the gateway is treated as active. To specify a route to a host through a passive Internet gateway with an entry in the gateways file, enter: host host10 gateway 192.100.11.5 metric 9 passive This example specifies a route to a specific host, host10, through the gateway 192.100.11.5. The hop metric count to host10 is 9 and the gateway is treated as passive. To specify a route to a network through an external gateway, enter a line in the following format: net net5 gateway host7 metric 11 external This example specifies a route to a network, net5, through the gateway host7. The hop count metric to net5 is 11 and the gateway is treated as external (that is, it is not advertised through RIP, but is advertised through an unspecified routing protocol). RELATED INFORMATION
Daemons: gated(8), routed(8) delim off gateways(4)
All times are GMT -4. The time now is 02:11 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy