Why does system automatically reboot when it uses VCS (veritas clustered) file system?
Issue
- System with
VCS
is automatically rebooting with following error messages in the logs:
Jun 23 14:34:02 host1 vasproxyd[23496]: ERROR: Make sure that there is valid [vasproxyd] section in the /etc/opt/quest/vas/vas.conf file (error 22)
Jun 23 14:34:42 host1 Had[28669]: VCS CRITICAL V-16-1-50086 Swap usage on host1 is 91%
Jun 23 14:36:38 host1 Had[28669]: VCS CRITICAL V-16-1-50086 CPU usage on host1 is 100%
Jun 23 14:49:52 host1 syslogd 1.4.1: restart.
[...]
Jun 24 10:40:31 host1 RFDW_LldnMKSUNCRIT: CHECK_VCS FAILED resources detected. Investigate.
Jun 24 10:40:31 host1 last message repeated 2 times
Jun 24 10:40:44 host1 logger: TSG-SYSLOG-CHECK-MESSAGE-104043
Jun 24 10:41:26 host1 Had[27832]: VCS CRITICAL V-16-1-50086 Swap usage on host1 is 99%
Jun 24 10:41:31 host1 vasproxyd[22764]: ERROR: Make sure that there is valid [vasproxyd] section in the /etc/opt/quest/vas/vas.conf file (error 22)
Jun 24 10:43:08 host1 Had[27832]: VCS CRITICAL V-16-1-50086 CPU usage on host1 is 100%
Jun 24 10:50:07 host1 syslogd 1.4.1: restart.
Environment
- Red Hat Enterprise Linux 5.
- Veritas cluster server (VCS)
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.