Cause
During the boot process of each, the Watchd process of the server waits for up to two minutes for its reqsvr (request server) thread to initialize. If the two-minute waiting interval elapses, this server logs this alarm, and its boot process hangs. Meanwhile, if the other server boots subsequently, it becomes the active server.
If a server hangs during boot process when this alarm occurs, the external symptoms of this alarm resemble those of two other _WD alarms, #13 and #14. Therefore, you must carefully discriminate between these three events.
Proposed Solution
Procedure
- To determine the cause of this problem:
- Check if the Linux OS and the web interface are running, including the commands: telnet, statapp, server, logv, cat, grep, tail, vi.
- Check if the Watchdog application is active, but no other Communication Manager software is running.
- The almdisplay command displays no alarms, instead, the command returns the message:
almdisplay: 4: Unable to connect to MultiVantage
Caution:
The following procedure causes a brief service outage and must executed only at the convenience of the customer.
- Go to the Avaya Support website at http://support.avaya.com to open a service request.
- Enter server to check if the suspected server is the standby.
If necessary and at the customer convenience, enter server -if to force a server interchange.
- Reboot the standby server:
- From the Web interface, select Shutdown This Server.
- From the Linux command line, enter /sbin/shutdown -r now.
- Once the standby server restarts, check if the Event ID #5 was logged:
- From the Web interface, select .
- From the Linux command line, enter logv -w or by examining /var/log/ecs/wdlog log file.
- If rebooting the server does not help or if the problem persists, go to the Avaya Support website at http://support.avaya.com to open a service request.