Callback Daemon don't start

Druid · **Posted:** Fri Jul 23, 2010 5:52 pm

Hi all,

i have fresh centos-release-5-5.el5.centos with 2.6.18-194.el5 and last A2Billing from Trunk

i have Calback installed:

Code:

easy_install dist/callback_daemon-1.0.prod_r1527-py2.5.egg
cp a2b-callback-daemon.rc /etc/init.d/a2b-callback-daemon
chmod +x /etc/init.d/a2b-callback-daemon
chkconfig --add a2b-callback-daemon
chkconfig a2b-callback-daemon on

Start from CLI

Code:

service a2b-callback-daemon start
Starting a2b-callback-daemon:                              [  OK  ]

After server restart in LOG

Code:

"2010-07-23 19:11:21,273 - callbackLogger - MainThread - INFO - info message"
"2010-07-23 19:11:21,274 - callbackLogger - MainThread - WARNING - warn message"
"2010-07-23 19:11:21,274 - callbackLogger - MainThread - ERROR - error message"
"2010-07-23 19:11:21,274 - callbackLogger - MainThread - CRITICAL - critical message"
"2010-07-23 19:11:21,640 - root - MainThread - ERROR - stopping with an exception"
Traceback (most recent call last):
  File "/usr/lib/python2.4/site-packages/callback_daemon-1.0.prod_r1527-py2.5.egg/callback_daemon/daemon.py", line 200, in start
  File "/usr/lib/python2.4/site-packages/callback_daemon-1.0.prod_r1527-py2.5.egg/callback_daemon/a2b_callback_daemon.py", line 110, in run
  File "/usr/lib/python2.4/site-packages/callback_daemon-1.0.prod_r1527-py2.5.egg/callback_daemon/database.py", line 83, in __init__
  File "/usr/lib/python2.4/site-packages/callback_daemon-1.0.prod_r1527-py2.5.egg/callback_daemon/database.py", line 138, in db_connect
ConnectionError: (OperationalError) (2002, "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (2)") None None
"2010-07-23 19:11:21,642 - root - MainThread - INFO - stopped"

And manuall start from CLI:

Code:

service a2b-callback-daemon start
a2b_callback_daemon is stopped
Starting a2b-callback-daemon:                              [  OK  ]

and in LOG

Code:

"2010-07-23 19:25:13,900 - callbackLogger - MainThread - INFO - info message"
"2010-07-23 19:25:13,901 - callbackLogger - MainThread - WARNING - warn message"
"2010-07-23 19:25:13,901 - callbackLogger - MainThread - ERROR - error message"
"2010-07-23 19:25:13,903 - callbackLogger - MainThread - CRITICAL - critical message"
"2010-07-23 19:25:14,242 - root - MainThread - INFO - ------ Starting Callback Daemon ------ 
"
"2010-07-23 19:25:14,242 - root - MainThread - INFO - waiting..."
"2010-07-23 19:25:19,255 - root - MainThread - INFO - waiting..."
"2010-07-23 19:25:24,263 - root - MainThread - INFO - waiting..."

Why not start automatically?

Please help me!

jroper · **Joined:** Fri Jun 23, 2006 3:56 pm **Posts:** 4065

Hi

The callback daemon must start after asterisk, and if you restart asterisk, then so must the callback daemon be restarted.

In your case, being FreePBX based, asterisk is started by amportal start in /etc/rc.d/rc.local which starts a long time after all the services have started, including your chkconfig statement.

So I would remove the chkconfig for the daemon, and start it manually with a line UNDER amportal start, like service a2b-callback-daemon start. (or service a2b-callback-daemon restart)

Joe

Druid · **Posted:** Sat Jul 24, 2010 11:44 am

Big Thanks Joe!

provided by Star2Billing S.L.

Callback Daemon don't start

Who is online