Show Posts
1
Running WombatDialer / Dailer Status Flapping
« on: February 09, 2015, 18:19:49 »
Hi there, I'm running Wombat 0.8.0 on CentOS 7 with MySQL 5.5. The dialer seems to be working correctly but the dialer status on the home page flaps between ready (with all the expected status info) and down. With INFO level logging turned on, below you can see a snippet of what the flapping looks like in wombat.log. More log output is here: http://pastebin.com/a34TvcV2
Restarting Wombat seems to fix the issue until the next dialing campaign is run. I'm not certain if the flapping starts during or after the campaign but something about the campaign definitely triggers the issue. Is there something in particular I should be looking for? Any help you can provide would be much appreciated.
Thanks!
9-Feb-2015 8:26:38 AM ch.loway.app.wombat.dialer.WombatDialerProcess processMessage
INFO: [READY] - WBT Message received :F:WD/ThreadSetup#1 T:WD/WOMBAT#4 MsgWombatStatus R:true
9-Feb-2015 8:26:38 AM ch.loway.app.wombat.dialer.WombatDialerProcess processMessageReadyMode
INFO: Get Wombat status F:WD/ThreadSetup#1 T:WD/WOMBAT#4 MsgWombatStatus R:true
9-Feb-2015 8:26:38 AM ch.loway.tpf.gwt.srv.servlets.ResourceConsole blankOut
INFO: Will close connection com.mysql.jdbc.Connection@1c927710
9-Feb-2015 8:26:38 AM ch.loway.app.wombat.AMI.AstManagerProcess processMessagesFromMaster
INFO: Message from master: F:WD/ThreadSetup#1 T:WD/AMI-74.121.34.5:5038#5 MsgAmiStatus R:true
9-Feb-2015 8:26:40 AM ch.loway.app.wombat.AMI.AstManagerProcess logIO
INFO: BlockRead (optime:0)
Event: PeerStatus
Address: 74.121.35.97:1029
Privilege: system,all
PeerStatus: Registered
Peer: SIP/450
ChannelType: SIP
EDIT: Well it doesn't seem like the issue started during or directly after the campaign. The last one we ran went from 1400-1700 (give or take 10 mins) but it ran successfully all the way through. It wasn't until nearly 1800 that the issue came up again. See log output here: http://pastebin.com/WZdXherY
Restarting Wombat seems to fix the issue until the next dialing campaign is run. I'm not certain if the flapping starts during or after the campaign but something about the campaign definitely triggers the issue. Is there something in particular I should be looking for? Any help you can provide would be much appreciated.
Thanks!
9-Feb-2015 8:26:38 AM ch.loway.app.wombat.dialer.WombatDialerProcess processMessage
INFO: [READY] - WBT Message received :F:WD/ThreadSetup#1 T:WD/WOMBAT#4 MsgWombatStatus R:true
9-Feb-2015 8:26:38 AM ch.loway.app.wombat.dialer.WombatDialerProcess processMessageReadyMode
INFO: Get Wombat status F:WD/ThreadSetup#1 T:WD/WOMBAT#4 MsgWombatStatus R:true
9-Feb-2015 8:26:38 AM ch.loway.tpf.gwt.srv.servlets.ResourceConsole blankOut
INFO: Will close connection com.mysql.jdbc.Connection@1c927710
9-Feb-2015 8:26:38 AM ch.loway.app.wombat.AMI.AstManagerProcess processMessagesFromMaster
INFO: Message from master: F:WD/ThreadSetup#1 T:WD/AMI-74.121.34.5:5038#5 MsgAmiStatus R:true
9-Feb-2015 8:26:40 AM ch.loway.app.wombat.AMI.AstManagerProcess logIO
INFO: BlockRead (optime:0)
Event: PeerStatus
Address: 74.121.35.97:1029
Privilege: system,all
PeerStatus: Registered
Peer: SIP/450
ChannelType: SIP
EDIT: Well it doesn't seem like the issue started during or directly after the campaign. The last one we ran went from 1400-1700 (give or take 10 mins) but it ran successfully all the way through. It wasn't until nearly 1800 that the issue came up again. See log output here: http://pastebin.com/WZdXherY