Page History

...

ps -ef | grep java This should show three processes running 1 for ActiveMQ and 2 for the Trap Processor process.

It's a good idea to check that the disk hasn't filled up: df /var will tell you how full the disk is. If it is approaching 100%, then go and delete some of the logs detailed below.

You can also check that the port 162 is open and is being listened to by Java:

sudo netstat -tulpn

Look for the following lines:

udp 0 0 :::162 :::* 6554/java
udp 0 0 :::7500 :::* 6554/java

You will notice the process id 6554 will be one of the two Java processes of the Trap processor, seen when you run the ps - ef | grep java command. Obviously, the process id will change as the Trap processor is restarted over time .

Where Are The Logs?

/var/log/snmptraps/new-dashboard/TrapProcessor 

allLog.txt  errorLog.txt  warnLog.txt

/var/log/snmptraps/apache-activemq-5.10.0/data

audit.log

*** You Will Need To Start ActiveMQ BEFORE Starting The Trap Processor Process

To Stop And Start ActiveMQ:

...

kill -9 process_id_number_noted_down

*** Switch to user dante.sanigar

Navigate to /home/local/GEANT/dante.sanigar/TrapProcessor-1.0-SNAPSHOT

...