All installation and configuration problems and questions
Moderators: gerski, enjay, williamconley, Op3r, Staydog, gardo, mflorell, MJCoate, mcargile, Kumba, Michael_N
by dspaan » Wed Oct 08, 2014 1:41 pm
Hello,
I have a vicidial server that has been migrated from another machine. It has been running fine for months now. However i still can't get rid of this error i keep getting. The script has to do with voicemails. I checked astguiclient.conf but the credentials in there are correct otherwise i would have a lot more real problems. the cron and custom users defined in there can connect fine when i type mysql -u cron -p or mysql -u custom -p and type in the password that's in astguiclient.conf.
So where is this error coming from?
From root@ Wed Oct 8 20:35:01 2014
Return-Path: <root@>
X-Original-To: root
Delivered-To: root@
Received: by (Postfix, from userid 0)
id 1C5BE43C9CC; Wed, 8 Oct 2014 20:35:01 +0200 (CEST)
From: root@
To: root@
Subject: Cron <root@cs1> /usr/share/astguiclient/AST_vm_update.pl
X-Cron-Env: <SHELL=/bin/sh>
X-Cron-Env: <HOME=/root>
X-Cron-Env: <PATH=/usr/bin:/bin>
X-Cron-Env: <LOGNAME=root>
X-Cron-Env: <USER=root>
Message-Id: <20141008183501.1C5BE43C9CC@l>
Date: Wed, 8 Oct 2014 20:35:01 +0200 (CEST)
problem connecting to "localhost", port 5038: Connection refused at /usr/share/astguiclient/AST_vm_update.pl line 177
Regards, Dennis
Vicibox 9.0.1
Version: 2.14b0.5
SVN Version: 3199
DB Schema Version: 1588
Build: 200310-1801
-
dspaan
-
- Posts: 1377
- Joined: Fri Aug 21, 2009 1:40 pm
- Location: The Netherlands
-
by boybawang » Wed Oct 08, 2014 9:34 pm
check if your asterisk process is running, port 5038 is the asterisk managers port and if you get a connection refused error it only means that asterisk is not running
-
boybawang
-
- Posts: 989
- Joined: Sat Nov 14, 2009 1:18 pm
- Location: Dumaguete City, Negros Oriental, Philippines
-
by geoff3dmg » Thu Oct 09, 2014 8:26 am
That's connecting to the management port (AMI) for asterisk. The access is controlled via /etc/asterisk/manager.conf. It's possible you have ACLs in that file or iptables firewall rules (iptables -L) refering to IPs that do not exist any more?
Another issue is if your asterisk version in Admin -> Servers doesn't match the version of asterisk that is running on the machine. There was a bug in some versions of Vicibox v5 where it set it to 1.4 after installing 1.8.
Vicibox 5.03 from .iso | VERSION: 2.10-451a BUILD: 140902-0816 | Asterisk 1.8.28.2-vici | Multi-Server | Amfeltec H/W Timing Cards | No Extra Software After Installation | Dell PowerEdge 1850 | Pentium 4 'Prescott' Xenon Quad @ 3.40GHz
-
geoff3dmg
-
- Posts: 403
- Joined: Tue Jan 29, 2013 4:35 am
- Location: Lancashire, UK
-
by dspaan » Thu Oct 09, 2014 7:29 pm
Asterisk is running fine otherwise we would not be able to do 10.000 calls a day.
This is a two server cluster setup with 1.4.39.2-vici which is also specified in the admin interface for each server. I have come across that vicibox bug as well a while ago with other servers
Also a while ago we cleaned out all old IP adresses in yast firewall but i'll check again and i'll also check asterisk manager.conf, thanks for the tips.
Regards, Dennis
Vicibox 9.0.1
Version: 2.14b0.5
SVN Version: 3199
DB Schema Version: 1588
Build: 200310-1801
-
dspaan
-
- Posts: 1377
- Joined: Fri Aug 21, 2009 1:40 pm
- Location: The Netherlands
-
Return to Support
Who is online
Users browsing this forum: Google [Bot] and 115 guests