Written By: |
Jeremy Boilard |
|---|---|
|
Manufacturer: |
Avaya |
|
Product: |
Session Manager |
|
Version: |
8.3.3 but present with other releases |
|
Patch Information: |
|
|
Ticket Number(s): |
Description:
Session Manager traps are not being sent from Avaya Session Manager.
Solution:
Log event service is likely in need of a restart.
1. Check configuration of snmp daemon
[root@MANsmgt ~]# grep -i 10.1.161.236 /var/net-snmp/snmpd.conf
targetAddr 0x31302e312e3136302e3233365f56325f31 .1.3.6.1.6.1.1
0x0a01a1ec00a2 3000 3 "10.1.161.236_V2_1" 10.1.161.236_V2_1 3 1
targetParams 10.1.161.236_V2_1 1 2 snmpcomm 1 3 1
2. Check status of snmpd
[root@smgt ~]# systemctl status snmpd â snmpd.service - Simple Network Management Protocol (SNMP) Daemon. Loaded: loaded (/etc/systemd/system/snmpd.service; enabled; vendor preset: disabled) Active: active (running) since Tue 2023-08-22 17:33:51 EDT; 2 days ago Main PID: 32177 (snmpd) CGroup: /system.slice/snmpd.service ââ32177 /usr/sbin/snmpd -LS0-6d -f
3. Check status of spiritAgent
[root@smgt ~]# systemctl status spiritAgent â spiritAgent.service - Avaya SPIRIT Agent Loaded: loaded (/etc/systemd/system/spiritAgent.service; disabled; vendor preset: disabled) Active: active (running) since Tue 2023-08-22 17:34:28 EDT; 2 days ago Process: 990 ExecStart=/opt/spirit/bin/wrapper-linux-x86-64 /opt/spirit/wrapper.config wrapper.syslog.ident=spiritAgent wrapper.daemonize=TRUE wrapper.pidfile=/opt/spirit/pids/spiritAgent.pid (code=exited, status=0/SUCCESS) Process: 987 ExecStartPre=/opt/spirit/scripts/Update/updateNMS.sh (code=exited, status=0/SUCCESS) Process: 984 ExecStartPre=/opt/Avaya/Session_Manager/bin/spirit_createDBSchema.sh (code=exited, status=0/SUCCESS) Process: 973 ExecStartPre=/opt/Avaya/Session_Manager/bin/spirit_checkAgentMgmtXML.sh (code=exited, status=0/SUCCESS) Process: 969 ExecStartPre=/usr/bin/rm -rf /opt/spirit/*.logbuff (code=exited, status=0/SUCCESS) Process: 965 ExecStartPre=/usr/bin/rm -rf /opt/spirit/persist/messages/*.ser (code=exited, status=0/SUCCESS) Process: 963 ExecStartPre=/usr/bin/rm -rf /opt/spirit/persist/messages/*.xml (code=exited, status=0/SUCCESS) Process: 418 ExecStartPre=/usr/bin/find /opt/spirit -exec chown spirit:susers {} ; (code=exited, status=0/SUCCESS) Main PID: 993 (wrapper-linux-x) CGroup: /system.slice/spiritAgent.service ââ993 /opt/spirit/bin/wrapper-linux-x86-64 /opt/spirit/wrapper.con... ââ997 /usr/java/latest/bin/java -Dspirit.config.dir=/opt/spirit/co...
4. Check running SM services
[root@smgt ~]# statapp
Watchdog 9/ 9 UP
logevent 0/ 13 DOWN
postgres-db 33/ 33 UP
mgmt 212/212 UP
WebSphere 232/232 UP
CDRService 16/ 16 UP
cassandra 81/ 81 UP
sal-agent 50/ 50 UP
secmod 4/ 4 UP# logevent service is not running
5. Manually start logevent service
[root@MANsmgt ~]# start -s logevent addsvc succeeded
6. Check running SM services again to validate changes
[root@smgt ~]# statapp
Watchdog 9/ 9 UP
logevent 0/ 13 DOWN
postgres-db 33/ 33 UP
mgmt 212/212 UP
WebSphere 232/232 UP
CDRService 16/ 16 UP
cassandra 81/ 81 UP
sal-agent 50/ 50 UP
secmod 4/ 4 UP# logevent service is still down
7. Check status of individual logevent service
[root@MANsmgt ~]# service logevent status Redirecting to /bin/systemctl status logevent.service â logevent.service - Logging Event Server Loaded: loaded (/etc/systemd/system/logevent.service; enabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2023-08-25 15:13:16 EDT; 1min 41s ago Process: 13676 ExecStopPost=/usr/bin/rm -f /var/opt/lock/logEventCode.pipe (code=exited, status=0/SUCCESS) Process: 13673 ExecStartPre=/usr/bin/chown spirit:susers /var/log/Avaya/watchd/event.log (code=exited, status=1/FAILURE) Process: 13670 ExecStartPre=/usr/bin/chown root:susers /var/log/Avaya/watchd (code=exited, status=0/SUCCESS) Process: 13668 ExecStartPre=/usr/bin/chmod 770 /var/log/Avaya/watchd (code=exited, status=0/SUCCESS) Process: 13666 ExecStartPre=/usr/bin/mkfifo -m 666 /var/opt/lock/logEventCode.pipe (code=exited, status=0/SUCCESS) Aug 25 15:13:16 MANsmgt.centragroup.net systemd[1]: Starting Logging Event Server... Aug 25 15:13:16 MANsmgt.centragroup.net systemd[1]: logevent.service: control process ...1 Aug 25 15:13:16 MANsmgt.centragroup.net systemd[1]: Failed to start Logging Event Server. Aug 25 15:13:16 MANsmgt.centragroup.net systemd[1]: Unit logevent.service entered fail.... Aug 25 15:13:16 MANsmgt.centragroup.net systemd[1]: logevent.service failed. Hint: Some lines were ellipsized, use -l to show in full.
Service failing due to issues with watchd
8. Examine generated watchd logs for issues
[root@smgt ~]# cd /var/log/Avaya/watchd
[root@smgt watchd]# ls wdlog wdlog.1 wdlog.2 wdlog.3 wdlog.4 wdlog.5 wdlog.6 wdlog_p
[root@smgt watchd]# ls -ltr
total 6720
-rw-r-----+ 1 root susers ?? 65501 Feb 15 ??2023 wdlog_p
-rw-r-----+ 1 root susers 1048610 Aug 17 05:19 wdlog.6
-rw-r-----+ 1 root susers 1048719 Aug 18 18:32 wdlog.5
-rw-r-----+ 1 root susers 1048650 Aug 20 07:45 wdlog.4
-rw-r-----+ 1 root susers 1048630 Aug 21 20:58 wdlog.3
-rw-r-----+ 1 root susers 1048663 Aug 23 09:40 wdlog.2
-rw-r-----+ 1 root susers 1048622 Aug 24 22:53 wdlog.1
-rw-r-----+ 1 root susers ??473129 Aug 25 15:13 wdlo
File owner is root, but should be spirit to allow for writing to file
Good File Example:
[isadmin@SM01 watchd]$ ls -ltr
total 8
-rw-r-----+ 1 spirit susers 1810 Aug 16 23:20 event.log.2023-08-16_23-20-18-010
-rw-rw-r--+ 1 spirit susers ??956 Aug 18 10:15 event.log
9. Make a new log file
[root@smgt watchd]# touch event.log
10. Check file permissions
[root@smgt watchd]# ls -ltr total 6728 -rw-r-----+ 1 root ?? susers ??
11. Adjust file permissions and validate
[root@smgt watchd]# chmod 664 event.log
[root@smgt watchd]# ls -ltr
total 6728
-rw-r-----+ 1 root susers 65501 Feb 15 2023 wdlog_p
-rw-r-----+ 1 root susers 1048610 Aug 17 05:19 wdlog.6
-rw-r-----+ 1 root susers 1048719 Aug 18 18:32 wdlog.5
-rw-r-----+ 1 root susers 1048650 Aug 20 07:45 wdlog.4
-rw-r-----+ 1 root susers 1048630 Aug 21 20:58 wdlog.3
-rw-r-----+ 1 root susers 1048663 Aug 23 09:40 wdlog.2
-rw-r-----+ 1 root susers 1048622 Aug 24 22:53 wdlog.1
-rw-rw-r--+ 1 spirit susers 0 Aug 25 15:29 event.log
12. Validate service status
[root@smgt watchd]# statapp
Watchdog 9/ 9 UP
logevent 13/ 13 UP
postgres-db 30/ 30 UP
mgmt 405/405 UP
WebSphere 274/274 UP
CDRService 16/ 16 UP
cassandra 76/ 76 UP
sal-agent 49/ 49 UP
secmod 4/ 4 UP
13.Validate service functionality through test alarm
[root@MANsmgt watchd]# sh generateTestAlarmSM.sh
Test alarm generated.
Found the logevent service down. Found from the process where it was failing (watchd). As root created an event.log file and gave it correct permissions. Once that was completed the service started and SNMP traps worked successful.
Disclaimer: intlx Solutions Knowledge Base
The information contained in this knowledge base ("Content") is provided for informational purposes only and is intended to be a general resource. intlx Solutions does not guarantee the accuracy, completeness, or timeliness of the Content.
Use at Your Own Risk: By accessing and using the Content, you agree that you do so at your own risk. intlx Solutions assumes no responsibility for any errors or omissions in the Content, nor for any damages or losses you may suffer arising out of or related to the use of the Content.
Current Customers: If you are a current intlx Solutions customer and have questions or require further clarification on any information presented here, please do not hesitate to contact our support team directly. They are available to assist you and ensure you have the most up-to-date information specific to your needs.
Not a Customer? If you are not currently an intlx Solutions customer but are interested in learning more about our solutions and how we can help your business, please click here. We look forward to the opportunity to discuss your needs and explore how a partnership with intlx Solutions can benefit you.
Thank you for your understanding.