Avaya 03-300430 Home Security System User Manual


  Open as PDF
of 2574
 
Server Alarms
106 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
13
(Except
S8500)
(
cont’d)
MIN 4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
- Linux command line, by entering /sbin/shutdown -r now
5. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
14
(Except
S8500)
MIN “ERROR in req2svr.p trying to create heartbeat thread, errno=<x>” — After
the “reqsvr” (request server) creates a duplicate socket (see Event ID #13
(Except S8500)), it tries to create a heart beating thread. This alarm
indicates that reqsvr could not create the thread. (Meanwhile, if the other
server is already started or subsequently starts, it assumes the active role.)
In that (when this alarm occurs) a server hangs, this alarm’s external
symptoms resemble those of two other _WD alarms, #5
and #13 (Except
S8500). Therefore, carefully discriminate between these three events.
1. To inspect the symptoms of this problem, verify that the:
a. Linux OS and the Web interface are up (including the commands:
telnet, statapp, server, logv, cat, grep, tail, vi, etc.)
b. Watchdog application is partially up, but all other Communication
Manager processes are up, either using the:
- Web interface, by selecting View Process Status
- Linux command line, by entering statapp
c. The almdisplay -v command shows Event #14’s message
string
Since the following commands cause a brief service outage, they should
only be executed at the customer’s convenience.
2. Escalate this problem for explicit guidance with the following steps.
3. Enter server to verify that the suspected server is the standby.
If necessary and at the customer’s convenience, enter server -if
to force a server interchange.
4. Reboot the standby server, either from the:
- Web interface, by selecting Shutdown This Server
5. If rebooting the server does not help or if the problem recurs, escalate
the problem to the next higher tier.
Table 31: _WD Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
7 of 15