vicibox not syncing to db after upgrade

[Op3r]

Hello,

I have this old vicibox 8.1 server running on a cluster. I updated the db and the web servers to the newest svn. And now when I updated the asterisk servers to the new svn of vicidial, it wont sync to the db anymore. On the reports page its red and when I run this: /usr/share/astguiclient/AST_update.pl --debugX I get this:

2020-12-21 15:10:36|STARTING NEW MANAGER TELNET CONNECTION||ATTEMPT|ONE DAY INTERVAL:12000||
pattern match timed-out at /usr/share/astguiclient/AST_update.pl line 470

Now I have turned on another server, installed 8.1, updated the vicidial svn to 3337 even updated the asterisk to asterisk 13.30-vici and it syncs with the db.

Now im getting cross eyed on where are the differences. Any direction should I look?

Thanks!

[williamconley]

You say "sync" like there's a replication or other complex mysql process involved.

But in this case, telnet will attempt to log in at the behest of perl, and it will await a specific pattern of characters in the response from the server, and then toss in more instructions. It never gets the expected pattern and times out.

You should execute whatever it's executing from the linux CLI and find out what's happening. Often the Version of Asterisk is incorrect, resulting in a mismatch in what the technical responses/requests must be. One character off and "poof" it no longer works.

Be sure you asterisk in /etc/astguiclient.conf matches what the installer expected (eg: including the ".X" in "11.X" if that was the chosen option) along with the asterisk version in Admin->servers for this server. The problem can require re-installing Vicidial (perl install.pl) to re-install the sample configuration files if there is any change, since the install.pl script makes decisions based on the value in astguiclient.conf.

If you have a functional server, you can compare the values and use them from the functional one ONLY if the asterisk version in operation is identical. It also helps if asterisk hasn't crashed (that tends to reduce the likelihood of success a bit).

[Op3r]

Hi Bill,

Im dealing something like this



The version on astguiclient.conf and server settings of asterisk are correct.

So I need somewhere to look for.

[williamconley]

I hate to be picky, but "correct" isn't a version number.

Perhaps you should post the values from astguiclient.conf and admin->servers and asterisk -V?

[carpenox]

pattern mismatch is usually due to a password being wrong in manager.conf

[williamconley]

pattern mismatch is usually due to a password being wrong in manager.conf

it has never been that for us. there's always a technical glitch somewhere, usually mismatch on the versioning.

that being said: since we never modify the passwords in the manager.conf file, it would be ... awkward if that were wrong. at least since version 2.0.5 when we used to also install FreePBX on the same server. Back then we modified a lot more files for combining the two calling systems.

[Op3r]

Hello,

Thought so at first but I looked:




I thought i was dumb enough to have not notice the manager.conf and astguiclient.conf but no sir. So this has me stumped.

[Op3r]

pattern mismatch is usually due to a password being wrong in manager.conf

it has never been that for us. there's always a technical glitch somewhere, usually mismatch on the versioning.

that being said: since we never modify the passwords in the manager.conf file, it would be ... awkward if that were wrong. at least since version 2.0.5 when we used to also install FreePBX on the same server. Back then we modified a lot more files for combining the two calling systems.

unless the server is public facing and supporting remote agents that have dynamic ips, theres no way I leave the manager.conf password on default lol.

[carpenox]

ok so put the version as 13.34.0-vici if thats what your using

[williamconley]

I would like to be sure.

Code: Select all

asterisk -V

and Admin->Servers

Also, to be sure that the astguiclient.conf version was correct when you installed via install.pl and it grabbed the sample files, either install.pl again (and be sure to select sample conf files) or diff the sip.conf against the sip.conf's in the SVN trunk folder. If it matches the asterisk 1.4 version, it's wrong and you should probably install.pl again.

If all that fails, resort to actual troubleshooting. Mimic what it's doing on the linux cli and see first person what's happening. This may require adding debug out put to the perl script to get the commands to run if debugX doesn't provide it all.

pattern mismatch is usually due to a password being wrong in manager.conf

it has never been that for us. there's always a technical glitch somewhere, usually mismatch on the versioning.

that being said: since we never modify the passwords in the manager.conf file, it would be ... awkward if that were wrong. at least since version 2.0.5 when we used to also install FreePBX on the same server. Back then we modified a lot more files for combining the two calling systems.

unless the server is public facing and supporting remote agents that have dynamic ips, theres no way I leave the manager.conf password on default lol.

If you have a Vicidial server on the public internet and think that manager.conf is the problem, you may have a very bad day in your future. Do not put Vicidial on the net without whitelisting. Ever. [insert Jaws theme here]

[Op3r]

Apparently if you do reload dialplan on system settings it does reload all the dialplan on the asterisk servers connected to the db. However the report page still says its red :/ damnit.

I looked at the logs on both non working telephony server and the working one and the output was the same. even on the /var/log/astguiclient logs output is the same.

[williamconley]

the listen screen should be the one keeping it from being red. see what's happening on the listen screen.

[carpenox]

try putting 13.34.0-vici as the asterisk version during the install.pl portion

[williamconley]

try putting 13.34.0-vici as the asterisk version during the install.pl portion

Nope. That's not one of the options. Stick to the options provided. Don't make something up. There's a list and later functions will parse based on that list and the answer must match precisely. If there's no match it'll "default" to asterisk 1.4 settings, which won't work. This is a known bug for Vicibox 7. In some versions It will install as asterisk "11" instead of "11.X" and break sip becuase the parser will then choose the sip file that works in asterisk 1.4 and before instead of 1.8 and beyond.

[carpenox]

well, thats what i personally used for asterisk 13.34.0-vici and 13.38.0-vici for svn version 3337 during the install.pl and my servers are all green.

[williamconley]

And I've gone past that speed trap 100 times and not been stopped. Doesn't mean I'm going to tell everyone else that they'll be lucky every time, too, so go ahead and hit 70mpg (it'll be fine! I do it all the time!). Best practices ... can save hair. Some of us have precious little left and don't need that level of risk.

[carpenox]

hahaha ok, to each their own. i'd wanna keep what little hair i had left too if that were the case, lol. i just hit 40 this week so i can relate :-p

[williamconley]

You did not "hit" 40. You cruised into 40. When you "hit" it'll be that half century millstone. Be sure you get your "Happy Half Century" birthday cards. And the prostate check. Marvelous birthday presents, those.

[carpenox]

You did not "hit" 40. You cruised into 40. When you "hit" it'll be that half century millstone. Be sure you get your "Happy Half Century" birthday cards. And the prostate check. Marvelous birthday presents, those.

yea, not looking forward to those fun times of prostate checks :-O

[Op3r]

so I tried doing what carpenox suggested and still nope.

Code: Select all

# Asterisk version VICIDIAL is installed for
VARasterisk_version => 13.34.0-vici

and when I looked and connected to screen astlisten it only shows this:

Code: Select all

----- AMI Version 2.10.5 -----


Nothing more.

Anywhere should I look into?

The crontab looks like this:

Code: Select all


sea2-AST3:~ # crontab -l
# DO NOT EDIT THIS FILE - edit the master and reinstall.
# (/tmp/rootcron installed on Fri Dec 18 09:11:39 2020)
# (Cronie version 4.2)
### keepalive script for astguiclient processes
* * * * * /usr/share/astguiclient/ADMIN_keepalive_ALL.pl

### Compress astguiclient log files and remove old ones
25 2 * * * /usr/bin/find /var/log/astguiclient -maxdepth 1 -type f -mtime +1 -print | grep -v \.xz | xargs xz -9 >/dev/null 2>&1
28 0 * * * /usr/bin/find /var/log/astguiclient -maxdepth 1 -type f -mtime +30 -print | xargs rm -f

### remove and rotate old asterisk logs
29 0 * * * /usr/bin/find /var/log/asterisk -maxdepth 3 -type f -mtime +30 -print | xargs rm -f
30 0 * * * /usr/bin/find / -maxdepth 1 -name "screenlog.0*" -mtime +7 -print | xargs rm -f
31 0 * * * /usr/bin/find /tmp -maxdepth 1 -type f -mtime +7 -print | xargs rm -f
32 0 * * * /usr/bin/find /var/log/asterisk -maxdepth 1 -type f -mtime +1 -print | grep -v \.xz | xargs xz >/dev/null 2>&1

### recording mixing/compressing/ftping scripts
#0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_mix.pl --MIX
0,3,6,9,12,15,18,21,24,27,30,33,36,39,42,45,48,51,54,57 * * * * /usr/share/astguiclient/AST_CRON_audio_1_move_VDonly.pl
1,4,7,10,13,16,19,22,25,28,31,34,37,40,43,46,49,52,55,58 * * * * /usr/share/astguiclient/AST_CRON_audio_2_compress.pl --MP3
#2,5,8,11,14,17,20,23,26,29,32,35,38,41,44,47,50,53,56,59 * * * * /usr/share/astguiclient/AST_CRON_audio_3_ftp.pl --MP3 --run-check
#0 1 * * * /usr/share/astguiclient/AST_CRON_audio_4_ftp2.pl --ftp-server=server.ip --ftp-login=user --ftp-pass=pass --ftp-directory=/ --ftp-persistent --ftp-validate --transfer-limit=100000 --list-limit=100000

### remove old recordings more than 7 days old, and delete originals after 1 day
#24 0 * * * /usr/bin/find /var/spool/asterisk/monitorDONE -maxdepth 2 -type f -mtime +7 -print | xargs rm -f
24 1 * * * /usr/bin/find /var/spool/asterisk/monitorDONE/ORIG -maxdepth 2 -type f -mtime +1 -print | xargs rm -f

### kill Hangup script for Asterisk updaters
* * * * * /usr/share/astguiclient/AST_manager_kill_hung_congested.pl

### updater for voicemail
* * * * * /usr/share/astguiclient/AST_vm_update.pl

### updater for conference validator
* * * * * /usr/share/astguiclient/AST_conf_update.pl

### reset several temporary-info tables in the database
2 1 * * * /usr/share/astguiclient/AST_reset_mysql_vars.pl

### Reboot nightly to manage asterisk issues and memory leaks - uncomment if issues arise
#30 6 * * * /sbin/reboot

### remove text to speech file more than 4 days old
#20 0 * * * /usr/bin/find /var/lib/asterisk/sounds/tts/ -maxdepth 2 -type f -mtime +4 -print | xargs rm -f

### Update agent records with the IP of the phone they are logging in on
#*/5 * * * * /usr/share/astguiclient/AST_phone_update.pl --agent-lookup

### Delete voicemail that is older then 60 days
#0 2 * * * /usr/local/bin/vmspool_manager.pl --active --age=60

### ViciBox integrated firewall, by default just load the VoIP Black list and reload it every 4 hours
### You can lock everyone out of your server if you set this wrong, so understand what you are doing!!!
@reboot /usr/local/bin/VB-firewall.pl --voipbl --noblack --quiet
0 */6 * * * /usr/local/bin/VB-firewall.pl --voipbl --noblack --flush --quiet


My screen looks like this:

Code: Select all

There are screens on:
        1477.ASTfastlog (Detached)
        1474.ASTVDremote        (Detached)
        1471.ASTVDauto  (Detached)
        1468.ASTlisten  (Detached)
        1460.ASTsend    (Detached)
        1457.ASTupdate  (Detached)
        1397.asterisk   (Detached)
        1392.astshell20201222091357     (Detached)
8 Sockets in /var/run/screens/S-root.



and my Asterisk is normal with this:

Code: Select all

Connected to Asterisk 13.34.0-vici currently running on sea2-AST3 (pid = 1423)
sea2-AST3*CLI>
sea2-AST3*CLI>
  == Manager 'sendcron' logged on from 127.0.0.1
  == Manager 'sendcron' logged off from 127.0.0.1


[carpenox]

with no errors and everything running like that, do the servers work for calls?

[Op3r]

It gives me time sync.

[Op3r]

So vicibox 8.1 needs to have the ntp set on crontab.

I have to add ntp on crontab to make it work.

Thanks all.

[carpenox]

good shit, nice post back