Details
-
Type: Task
-
Status: Closed
-
Priority: Critical
-
Resolution: Fixed
-
Affects Version/s: 2.0.0
-
Fix Version/s: 2.01
-
Component/s: Admax Deployment Service
-
Labels:None
-
Environment:
all
-
Sprint:Sprint 2
Description
This task covers a script that monitors the admax listener for AML-896.
To test this, deploy bidmgr build 6 (2.0.1 release) and edit the TSAApp crontab to add the new entry
bidmgr build 6
http://pulse.ri.thesearchagency.com:8080/browse/projects/SMB%20Core%20-%20Bid%20Manager%20-%202.0.0-RC1/home/
Crontab entry to add:
*/1 * * * * /usr/local/tsa/bidmgr/monitor-admax-listener.sh
Use cases to test:
1) insert error in to the log file
echo 'Cannot find object in dispatcher with id' >> /var/local/tsa/log/tsa-admax-jmslistener/tsa-admax-jmslistener.log
Check /var/local/tsa/log/monitor-admax-listener.log to make sure it restarts the listener
2) shut down the listener end check monitor-admax-listener.log to make sure it says it can't find the log file and won't take any action.
3) if heartbeats don't work, the monitor script will call send_alarm.sh. disable heartbeats on the listener, then follow step 1 to trigger a restart, and it should call send_alarm.sh
Related commit:
https://github.com/thesearchagency/core/commit/44134c3c51ae2c3416c763d61f3861d3e407e7a1
Attachments
Issue Links
- depends on
-
AML-896 jmslistener lost connection attempting to Update Campaign.
- Closed