Trap Receiver thread causes services to not start after reboot
search cancel

Trap Receiver thread causes services to not start after reboot


Article ID: 220112


Updated On:


CA Network Flow Analysis (NetQos / NFA)


If you reboot a NFA Console and notice that the NetQoS Reporter/Analyzer Services as well as the CA NFA OData Service is stopped, your Trap Receiver thread in the NetQoS Manager Service may be corrupting the MySQL database causing MySQL to startup and process through the ibd sequence logs to recover.

To know if this is your issue, go to the Manager Service Log20xx-xx-xx.log log in the x:\CA\NFA\REPORTER\Logs directory and look for messages like this:

16:46:27 5 - TrapService: Starting

16:46:30 5 - TrapService: CAPC connection detected.  Initializing trap service.

16:46:30 2 - TrapService: Unable to initialize listener on Ё$

16:46:30 2 - TrapService: Unable to initialize listener on

16:59:18 2 - Email Scheduler: Stopping Thread Handler

16:59:18 5 - TrapService: Stopping

17:00:03 1 - NetQoS.Background.Manager.BackgroundManager: Thread did not shutdown orderly and had to be aborted after waiting 45.0512947 seconds




This is caused by the Trap Receiver thread of the NetQoS Reporter/Analyzer Manager Service attempting to use port 162 on the NFA Console to listen for SNMP Traps from the NFA Harvester while the Microsoft Windows SNMP Trap Service is running already and trying to do the same thing. What ends up happening is that the next time you try to stop the NetQoS Reporter/Analyzer Manager Service, the Trap Receiver thread hangs and MySQL force closes the connections made from that thread which causes minor MySQL corruption. Upon starting MySQL, the process will attempt to roll back changes and go through the ibd sequence logs to make sure there are no data loss issues. During the process, services which rely on MySQL will fail to connect to MySQL. This explains why the NetQoS Services and the CA NFA OData Service can't make connections to MySQL. 


In order to resolve this, simple open Windows Services and stop the SNMP Trap service. Right click and go to properties, where you can set the service to, 'Disabled'.

If the service is already stopped and you see the messages in the logs I listed above, you may need to search the server for a 3rd party trap receiver program and disable it.