Filter
Top Products
Server Alarms
86 Maintenance Procedures for Avaya Communication Manager 3.0, Media Gateways and Servers
7 MIN “service prune could not be restarted” — The prune service is not running.
The hard disk’s partition usage is not being monitored or cleaned.
1. Enter /sbin/service prune restart to restart the prune service.
2. If the service restarts, manually clear the alarm, either from the:
● Web interface, by selecting Alarms and Notification, the
appropriate alarm, and Clear
● Linux command line, by entering almclear -n #id
If not, escalate this problem for explicit guidance with steps 2a
through 3
a. Enter grep svc_mon /var/log/messages to investigate why the
daemon failed.
b. If this problem affects call processing, continue with the following
steps now.
If not, continue only at the customer’s convenience – since the
following commands cause a brief service outage.
The following commands cause a brief service outage.
c. If the grep command’s output does not help:
● S8700 | 8710: 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.
● S8500: Proceed to Step e.
If necessary and at the customer’s convenience, enter server -if to
force a server interchange.
d.
S8700 | 8710: Reboot the standby server, either from the:
● Web interface, by selecting Shutdown This Server
● Linux command line, entering /sbin/shutdown -r now
e.
S8500: Reboot the server, either from the:
● Web interface, by selecting Shutdown This Server
● Linux command line, entering /sbin/shutdown -r now
3. If rebooting the standby does not help or if the problem recurs, escalate
the problem to the next higher tier.
Table 23: SVC_MON Alarms in Media Server (continued)
Event
ID
Alarm
Level
Alarm Text, Cause/Description, Recommendation
7 of 8