Today (Saturday) We will make some minor tuning adjustments to MySQL.

You may experience 2 up to 10 seconds "glitch time" when we restart MySQL. We expect to make these adjustments around 1AM Eastern Daylight Saving Time (EDT) US.

Can HPOV monitor server hung state ?

Login or Register to Reply

Thread Tools Search this Thread
# 8  
You must develop your own detection algorithms.

Nothing is difficult if you put your mind to it.

Your brain has 100 billion neurons. That is more neurons in your brain than all the stars in our galaxy.

Algorithms are not difficult!

Just do it.
Login or Register to Reply

Thread Tools Search this Thread
Search this Thread:
Advanced Search

More UNIX and Linux Forum Topics You Might Find Helpful
Server hung, is this a stack trace?
Hi everyone, Our Red Hat server hung yesterday, and I managed to log into the console and see the following message: RIP: 0010: mwait_idle_with_hints+0x66/ 0x67 RSP: 0018:ffffffff80457f40 EFLAGS: 00000046 RAX: 0000000000000010 RBX: ffff810c20075910 RCX: 0000000000000001 RDX:...... Linux
How to find the process which is caused system hung state?
when system is hung state due to swap, we will reboot it through ILO. i want to know which process caused system hung.... Red Hat
Red Hat
Server hung with firmware error
Hi all We've had an issue over the weekend when one of the SUSE Linux Enterprise Server 11 hung and had to be rebooted. The thing is that I got the ticket alert for a FS exceeding its usage at about 22:41:49 PM on 23 March. I checked the dmesg, the messages log and the boot.msg but all I found...... SuSE
close_wait connections causing a server to hung
Hi Guys, Just wondering if anyone of you have been in a situation where you end up having around 100 close_wait connections and seems to me those connections are locking up resources/processes in the server so unless the server is rebooted those processes won't be released by the close_wait...... UNIX for Advanced & Expert Users
UNIX for Advanced & Expert Users
Server hung
So my server was hung when I came in this morning. It was responding to pings, but the console and telnet sessions would not respond. There was no disk activity. The display said FA1F which I discovered that the "A" represents a high CPU load. I tired several things to get it going but was forced...... HP-UX
sac(1M)                                                   System Administration Commands                                                   sac(1M)

sac - service access controller
sac -t sanity_interval /usr/lib/saf/sac
The Service Access Controller (SAC) is the overseer of the server machine. It is started when the server machine enters multiuser mode. The SAC performs several important functions as explained below. Customizing the SAC Environment When sac is invoked, it first looks for the per-system configuration script /etc/saf/_sysconfig. sac interprets _sysconfig to customize its own environment. The modifications made to the SAC environment by _sysconfig are inherited by all the children of the SAC. This inherited environment may be modified by the children. Starting Port Monitors After it has interpreted the _sysconfig file, the sac reads its administrative file /etc/saf/_sactab. _sactab specifies which port moni- tors are to be started. For each port monitor to be started, sac forks a child (see fork(2)) and creates a utmpx entry with the type field set to LOGIN_PROCESS. Each child then interprets its per-port monitor configuration script /etc/saf/pmtag/_config , if the file exists. These modifications to the environment affect the port monitor and will be inherited by all its children. Finally, the child process execs the port monitor, using the command found in the _sactab entry. (See sacadm; this is the command given with the -c option when the port monitor is added to the system.) Polling Port Monitors to Detect Failure The -t option sets the frequency with which sac polls the port monitors on the system. This time may also be thought of as half of the max- imum latency required to detect that a port monitor has failed and that recovery action is necessary. Administrative functions The Service Access Controller represents the administrative point of control for port monitors. Its administrative tasks are explained below. When queried (sacadm with either -l or -L), the Service Access Controller returns the status of the port monitors specified, which sacadm prints on the standard output. A port monitor may be in one of six states: ENABLED The port monitor is currently running and is accepting connections. See sacadm(1M) with the -e option. DISABLED The port monitor is currently running and is not accepting connections. See sacadm with the -d option, and see NOTRUNNING, below. STARTING The port monitor is in the process of starting up. STARTING is an intermediate state on the way to ENABLED or DISABLED. FAILED The port monitor was unable to start and remain running. STOPPING The port monitor has been manually terminated but has not completed its shutdown procedure. STOPPING is an intermediate state on the way to NOTRUNNING. NOTRUNNING The port monitor is not currently running. (See sacadm with -k.) This is the normal "not running" state. When a port moni- tor is killed, all ports it was monitoring are inaccessible. It is not possible for an external user to tell whether a port is not being monitored or the system is down. If the port monitor is not killed but is in the DISABLED state, it may be possible (depending on the port monitor being used) to write a message on the inaccessible port telling the user who is trying to access the port that it is disabled. This is the advantage of having a DISABLED state as well as the NOTRUNNING state. When a port monitor terminates, the SAC removes the utmpx entry for that port monitor. The SAC receives all requests to enable, disable, start, or stop port monitors and takes the appropriate action. The SAC is responsible for restarting port monitors that terminate. Whether or not the SAC will restart a given port monitor depends on two things: o The restart count specified for the port monitor when the port monitor was added by sacadm; this information is included in /etc/saf/pmtag/_sactab. o The number of times the port monitor has already been restarted.
sac uses pam(3PAM) for session management. The PAM configuration policy, listed through /etc/pam.conf, specifies the session management module to be used for sac. Here is a partial pam.conf file with entries for sac using the UNIX session management module. sac session required If there are no entries for the sac service, then the entries for the "other" service will be used.
-t sanity_interval Sets the frequency (sanity_interval) with which sac polls the port monitors on the system.
/etc/saf/_sactab /etc/saf/_sysconfig /var/adm/utmpx /var/saf/_log
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWcsu | +-----------------------------+-----------------------------+
pmadm(1M), sacadm(1M), fork(2) pam(3PAM), pam.conf(4), attributes(5), pam_authtok_check(5), pam_authtok_get(5), pam_authtok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5), pam_unix_session(5)
The pam_unix(5) module is no longer supported. Similar functionality is provided by pam_authtok_check(5), pam_authtok_get(5), pam_auth- tok_store(5), pam_dhkeys(5), pam_passwd_auth(5), pam_unix_account(5), pam_unix_auth(5), and pam_unix_session(5). SunOS 5.10 23 Oct 2002 sac(1M)

Featured Tech Videos