09.12.2012 Views

Server Alarms - Avaya Support

Server Alarms - Avaya Support

Server Alarms - Avaya Support

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Server</strong> <strong>Alarms</strong><br />

Table 41: _WD <strong>Alarms</strong> 3 of 16<br />

Event<br />

ID<br />

Alarm<br />

Level<br />

Alarm Text, Cause/Description, Recommendation<br />

5 MIN “WARNING: timeout waiting for reqsvr to initialize” — During each server’s<br />

boot process, the server’s Watchd process waits up to 2 minutes for its<br />

“reqsvr” (request server) thread to initialize. If the 2-minute waiting interval<br />

elapses, this server logs this alarm, and its boot process hangs.<br />

(Meanwhile, if the other server is already booted or subsequently boots, it<br />

assumes the active role.)<br />

In that (when this alarm occurs) a server hangs during its booting process,<br />

this alarm’s external symptoms resemble those of two other _WD alarms,<br />

#13 (Except S8500) and #14 (Except S8500). Therefore, carefully<br />

discriminate between these three events.<br />

1. To inspect the symptoms of this problem, verify that the:<br />

a. Linux OS and the Web interface are up (including the commands:<br />

telnet, statapp, server, logv, cat, grep, tail, vi, etc.)<br />

b. Watchdog application is partially up, but no other Communication<br />

Manager software is up<br />

c. The almdisplay command displays no alarms. Instead, the<br />

command returns the message:<br />

“almdisplay: 4: Unable to connect to<br />

MultiVantage”<br />

Since the following commands cause a brief service outage, they should<br />

only be executed at the customer’s convenience.<br />

2. Escalate this problem for explicit guidance with the following steps.<br />

3. Enter server to verify that the suspected server is the standby.<br />

If necessary and at the customer’s convenience, enter server -if<br />

to force a server interchange.<br />

4. Reboot the standby server, either from the:<br />

- Web interface, by selecting Shutdown This <strong>Server</strong><br />

- Linux command line, by entering /sbin/shutdown -r now<br />

5. Once the standby server has booted, verify that Event ID #5 was<br />

logged, either using the:<br />

- Web interface, by selecting Diagnostics > View System Logs and<br />

Watchdog Logs<br />

- Linux command line, by entering logv -w or, directly, by<br />

examining /var/log/ecs/wdlog.<br />

128 Maintenance <strong>Alarms</strong> for <strong>Avaya</strong> Communication Manager, Media Gateways and <strong>Server</strong>s<br />

3 of 16

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!