12-23-2019
Hi Neo and rbattel
my system are using GPFS(archive directory) and raw devices with Oracle RAC on the hacmp.
I think the reason why A-system has down itself is that B-system is down due to system bug and all oracle sessions of B-system node are moved to A-system, which causes huge IO on A-system. The sync time of the A-system was slowed down, and as a result, the system was down when the dead man switch limit was reached.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
help, what is the difference between core dump and panic dump? (1 Reply)
Discussion started by: aileen
1 Replies
2. HP-UX
hi friends,
i know that when there is a crash then that memory image is
put into /var/adm/crash
but if the system hangs up and if i have access to console of
that machine then how can i take the crash dump manully.
thanks (2 Replies)
Discussion started by: mxms755
2 Replies
3. Solaris
Can anyone of you help me in enabling crash dump on Solaris 5.5.1 (1 Reply)
Discussion started by: csreenivas
1 Replies
4. AIX
Hi Guys,
I have two nodes clustered. Each node is AIX 5.2 & they are clustered with HACMP 5.2. The mode of the cluster is Active/Passive which mean one node is the Active node & have all resource groups on it & the 2nd node is standby.
Last Monday I noted that all resource groupes have been... (2 Replies)
Discussion started by: aldowsary
2 Replies
5. Solaris
hi ,
i have machine that is crashed
how i can enable core dump file & how can i find it ? :confused: (4 Replies)
Discussion started by: lid-j-one
4 Replies
6. UNIX for Advanced & Expert Users
Hi.
I have started heartbeat on two redhat servers. Using eth0.
Before I start heartbeat I can ping the two server to each other.
Once I start heartbeat both the server become active as they both have warnings that the other node is dead.
Also I am not able to ping each other. After stopping... (1 Reply)
Discussion started by: amrita garg
1 Replies
7. AIX
Hi Guys,
I have to design a multinode hacmp cluster and am not sure if the design I am thinking of makes any sense.
I have to make an environment that currently resides on 5 nodes more resilient but I have the constrain of only having 4 frames. In addition the business doesnt want to pay for... (7 Replies)
Discussion started by: zxmaus
7 Replies
8. AIX
Hi
I had an active passive cluster. Node A went down and all resource groups moved to Node B.
Now we brought up Node A. What is the procedure to bring everything back to Node A.
Node A #lssrc -a | grep cl
clcomdES clcomdES 323782 active
clstrmgrES cluster... (9 Replies)
Discussion started by: samsungsamsung
9 Replies
9. HP-UX
Hi Experts,
I have configured HP-UX Service Guard cluster and it dumps crash every time i reboot a cluster node. Can anyone please help me to prevent these unnecessary crash dumps at the time of rebooting SG cluster node?
Thanks in advance.
Vaishey (2 Replies)
Discussion started by: Vaishey
2 Replies
10. OS X (Apple)
MacPro (2013) 12-Core, 64GB RAM (today's crash):
panic(cpu 2 caller 0xffffff7f8b333ad5): userspace watchdog timeout: no successful checkins from com.apple.WindowServer in 120 seconds
service: com.apple.logd, total successful checkins since load (318824 seconds ago): 31883, last successful... (3 Replies)
Discussion started by: Neo
3 Replies
LEARN ABOUT ULTRIX
shutdown
shutdown(8) System Manager's Manual shutdown(8)
Name
shutdown - close down the system at a given time
Syntax
/etc/shutdown [ -k ] [ -r ] [ -h ] [ -o ] time [ warning-message ... ]
Description
The command provides an automated shutdown procedure that a superuser can use to notify users when the system is shutting down.
The time is the time at which will bring the system down. It may be the word `now', indicating an immediate shutdown, or specify a future
time in one of two formats: + number or hour : min. The first form brings the system down in number minutes. The second brings the system
down at the time of day indicated, using a 24-hour clock format.
At intervals which get shorter as shutdown nears, warning messages are displayed at the terminals of all users on the system. Warning mes-
sages are also sent to users who are logged in to a remote system that has mounted a file system or directory from the local system using
NFS. Five minutes before shutdown, or immediately if shutdown is timed for less than five minutes, logins are disabled by creating and
writing a message there. If this file exists when a user attempts to log in, prints its contents and exits. The file is removed just
before exits.
At shutdown time, a message is written in the file This message contains the time of shutdown, who ran shutdown, and the reason. Then, a
terminate signal is sent at to bring the system to single-user state.
If the or options are used, then executes or avoids shutting the system down (respectively). The option is for use by only. It indicates
to that it is being called by and not to return to the user.
You should place the time of the shutdown and the warning message in Use the message to inform the users about when the system will be back
up and why it is going down.
Restrictions
You can kill the system only between now and 23:59, if you use the absolute time for shutdown.
Files
Tells login not to let anyone log in
Log file for successful shutdowns
See Also
login(1), wall(1), halt(8), opser(8), reboot(8), rwalld(8c)
shutdown(8)