by muyousif » Tue Sep 01, 2015 11:59 am
Hi,
I am having an issue, vicidial service not starting at the boot automatically. If I start manually it starts without any error. Following are the details of vicidial service which I got from yast services detail section...
vicidial.service - LSB: Vicidial Call Center Suit xx
xx Loaded: loaded (/etc/init.d/vicidial) xx
xx Active: failed (Result: exit-code) since Tue 2015-09-01 21:41:56 PKT; 3min 43s ago xx
xx Process: 1244 ExecStart=/etc/init.d/vicidial start (code=exited, status=1/FAILURE) xx
xx xx
xxSep 01 21:41:51 milvik-t2 vicidial[1244]: DBI connect('asterisk:192.168.172.91:3306','cron',...) failed: Can't connect to MySQL server on '192.168.172.91' (113) at xx
xxSep 01 21:41:51 milvik-t2 vicidial[1244]: Couldn't connect to database: Can't connect to MySQL server on '192.168.172.91' (113) at /usr/share/astguiclient/AST_resetxx
xxSep 01 21:41:53 milvik-t2 vicidial[1244]: Starting Asterisk Unable to connect to remote asterisk (does /run/asterisk/asterisk.ctl exist?) xx
xxSep 01 21:41:54 milvik-t2 vicidial[1244]: DBI connect('asterisk:192.168.172.91:3306','cron',...) failed: Can't connect to MySQL server on '192.168.172.91' (113) at xx
xxSep 01 21:41:54 milvik-t2 vicidial[1244]: Couldn't connect to database: Can't connect to MySQL server on '192.168.172.91' (113) at /usr/share/astguiclient/start_astxx
xxSep 01 21:41:54 milvik-t2 vicidial[1244]: ..failed xx
xxSep 01 21:41:56 milvik-t2 vicidial[1244]: Started Vicidial xx
xxSep 01 21:41:56 milvik-t2 systemd[1]: vicidial.service: control process exited, code=exited status=1 xx
xxSep 01 21:41:56 milvik-t2 systemd[1]: Failed to start LSB: Vicidial Call Center Suit. xx
xxSep 01 21:41:56 milvik-t2 systemd[1]: Unit vicidial.service entered failed state.
and below are the details when I start vicidial service manually using /etc/init.t/vicidial start
vicidial.service - LSB: Vicidial Call Center Suit xx x
xpostfixxx Loaded: loaded (/etc/init.d/vicidial) xx x
xpurge-kxx Active: active (running) since Tue 2015-09-01 21:55:19 PKT; 3min 3s ago xx x
xrpcbindxx Process: 2509 ExecStart=/etc/init.d/vicidial start (code=exited, status=0/SUCCESS) xx x
xrsyslogxx CGroup: /system.slice/vicidial.service xx w
xsshd xx ├─3101 /usr/bin/SCREEN -S astshell20150901215512 xx x
xsuse-stxx ├─3102 /bin/sh xx x
xSuSEfirxx ├─3106 SCREEN -L -S asterisk xx x
xSuSEfirxx ├─3107 /bin/sh xx x
xsystemdxx └─3112 /usr/sbin/asterisk -vvvvvvvvvvvvvvvvvvvvvgcT xx x
xsystemdxx xx x
xuser@0 xxSep 01 21:55:12 milvik-t2 vicidial[2509]: Starting Asterisk Unable to connect to remote asterisk (does /run/asterisk/asterisk.ctl exist?) xx x
xvicidiaxxSep 01 21:55:13 milvik-t2 vicidial[2509]: started screen xx x
xxdm xxSep 01 21:55:14 milvik-t2 vicidial[2509]: changed directory xx x
xYaST2-FxxSep 01 21:55:15 milvik-t2 vicidial[2509]: started new screen session xx x
xYaST2-SxxSep 01 21:55:16 milvik-t2 vicidial[2509]: detached screens xx x
xasterisxxSep 01 21:55:17 milvik-t2 vicidial[2509]: raised ulimit open files xx x
xatd xxSep 01 21:55:17 milvik-t2 vicidial[2509]: Asterisk started... screen logging on xx x
xautofs xxSep 01 21:55:17 milvik-t2 vicidial[2509]: ..done xx v
xautovt@xxSep 01 21:55:19 milvik-t2 vicidial[2509]: Started Vicidial xx x
xautoyasxxSep 01 21:55:19 milvik-t2 systemd[1]: Started LSB: Vicidial Call Center Suit.
I can confirm firewall is disabled at database server. Other telephony is quite able to connect with database server. Any idea why I am having this issue??
ViciBox v.6.0.3 | VERSION: 2.14-685a BUILD: 180825-2100| Asterisk 1.8.29 | Cluster: 1 DB: 16Core@2.67GHz 16RAM | 1 WEB: 8Core@2.50GHz 16RAM | 8 Tel: QuadCore@2.93GHz 8RAM