vicidial.org

Hi guys,


[Feb 5 02:49:12] WARNING[7857][C-00000021]: res_agi.c:2038 handle_connection: Connecting to '127.0.0.1:4577' failed for url 'agi://127.0.0.1:4577/call_log--HVcauses--PRI-----NODEBUG-----16--------------------)': Connection refused
[Feb 5 02:49:12] WARNING[7857][C-00000021]: res_agi.c:2098 launch_netscript: Couldn't connect to any host. FastAGI failed.

it will appear during predictive dialing method, but I don't see the error on manual dial method. Does anyone knows how to fix this error?

Vicibox 11.0.2 give a lot of headaches

Vicibox 11.0.2
Standlone set up

1) Welcome to the Party!

2) As you are obviously new here, I have some suggestions to help us all help you:

When you post, please post your entire configuration including (but not limited to) your installation method (11.X.X?) and vicidial version with build (VERSION: 2.X-XXXx ... BUILD: #####-####).

This IS a requirement for posting along with reading the stickies (at the top of each forum) and the manager's manual (available on EFLO.net, both free and paid versions)

You should also post: Asterisk version, telephony hardware (model number is helpful here), cluster information if you have one, and whether any other software is installed in the box. If your installation method is "manual/from scratch" you must post your operating system with version (and the .iso version from which you installed your original operating system) plus a link to the installation instructions you used. If your installation is "Hosted" list the site name of the host.

If this is a "Cloud" or "Virtual" server, please note the technology involved along with the version of that techology (EG: vSphere Version 6.X.X). If it is not, merely stating the Motherboard model # and CPU would be helpful.

Similar to This:

Vicibox 11.X.X from .iso | Vicidial X.X.X-XXX Build XXXXXX-XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation | Intel DG35EC Mbd | Core2Quad Q6600 CPUs

3) There is a "screen" listening on port 4577. Stage one is to confirm the screen is live. Stage two is to log in to the screen and see if there is a hint about the rejection. You can also "hip shoot" and verify that the user/password is correct for login.

4) Is this a fresh clean install? Did you upgrade a previous server? Did you import a database?

Did you try the fixes on the article i sent you?

Did you get this fixed? I am dealing with the same issue now for 3 days... cant seem to figure out why FastAGI is not even running on 12.0.2

/usr/share/astguiclient/FastAGI_log.pl --debugX
SERVER LOGGING ON: LEVEL-4 FILE-/var/log/astguiclient/FastAGIchildLOG.2025-02-06
2025/02/06-09:36:24 VDfastAGI (type Net::Server::PreFork) starting! pid(3241)
Resolved [*]:4577 to [::]:4577, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4577 on host :: with IPv6
2025/02/06-09:36:24 Can't connect to TCP port 4577 on :: [Invalid argument]
at line 66 in file /usr/lib/perl5/vendor_perl/5.26.1/Net/Server/Proto/TCP.pm
2025/02/06-09:36:24 Server closing!

kashinc wrote:/usr/share/astguiclient/FastAGI_log.pl --debugX
SERVER LOGGING ON: LEVEL-4 FILE-/var/log/astguiclient/FastAGIchildLOG.2025-02-06
2025/02/06-09:36:24 VDfastAGI (type Net::Server::PreFork) starting! pid(3241)
Resolved [*]:4577 to [::]:4577, IPv6
Not including resolved host [0.0.0.0] IPv4 because it will be handled by [::] IPv6
Binding to TCP port 4577 on host :: with IPv6
2025/02/06-09:36:24 Can't connect to TCP port 4577 on :: [Invalid argument]
at line 66 in file /usr/lib/perl5/vendor_perl/5.26.1/Net/Server/Proto/TCP.pm
2025/02/06-09:36:24 Server closing!

This appears to be a support request that should include your basic setup information. Vicibox installer full version seems present (likely) but missing vicidial complete version (which is required).

In this specific case it looks like you have a conflict resulting in IPv6 being necessary but not present, or at least not present at one crucial moment. It's also possible that IPv6 is present at the "wrong" moment.

The system is apparently resolving your host (localhost) to :: rather than 127.0.0.1 causing that script to crash. So your network configuration options are definitely at issue. Of course you could probably turn on IPv6 so :: would resolve or turn off IPv6 for whatever is looking for localhost to bind so it binds to 127.0.0.1 instead.

It's ALSO possible that an underlying change occurred in the OS networking defaults, but that won't change the solution just the cause.

try to disable ipv6

carpenox wrote:try to disable ipv6

at first my ipv6 in yast lan when I install the OS I disable it, maybe that is why I met fast agi failed error then my predictive dialing stop , but when I enable it again the IPv6 on yast lan then reboot server, the error is gone

hopefully that error will never come back

and thank you for your guides it helps me a lot also

thank you

rheymzkilove wrote:

carpenox wrote:try to disable ipv6

at first my ipv6 in yast lan when I install the OS I disable it, maybe that is why I met fast agi failed error then my predictive dialing stop , but when I enable it again the IPv6 on yast lan then reboot server, the error is gone

hopefully that error will never come back

and thank you for your guides it helps me a lot also

thank you

When you disable IPv6 at the OS level, you don't get an IPv6 address any more. But there are still apps looking for an IPv6 address and those fail because your system no longer understands IPv6. Usually it's only a couple applications, and convincing them to switch to "IPv4 only" mode can resolve the issue.

The reflex to shut down IPv6 is valid. One day soon I strongly suspect IPv6 will be the leading reason systems are hacked.

So probably better to set your firewall to reject all external IPv6 packets or learn to reconfigure those apps to not use IPv6. In the long run, of course. For now: Go make some money.