VICI Broke after changing IP Address
Posted: Mon Oct 22, 2007 11:56 amI wish I was the ADMIN_update_server_ip.pl before I changed the ip address, but it is too late now.
I had a working vici installation on slack12. Everything was running smoothly. Now I put the server on the production network and changed the ip. I got asterisk and all my trunks to the pbx working. But I noticed vici is just not working.
Heres what I did to remedy the problem. I got a lot further from when I started, but I am left at a point where there is noone in my session.
1. Changed the ip in inet1.conf
2. dumped mysql. did a search and replace to put the new ip in. reloaded the database with the new ip.
3. modified /etc/astguiclient.conf to use the new hostname.
Screen is dying and not much is working at this point.
4. Ran all crons manually.. Which helped my find that i need the IP in astguiclient.conf rather then the hostname.
5. the stuff in apache is using localhost, so there is no issue there.
Reboot
No I am getting noone is in my session.
My list is active
my phone is active
my campaign is active.
This campaign has 1 active lists and 0 inactive lists
This campaign has 82 leads to be dialed in those lists
This campaign has 6 leads in the dial hopper
After reboot it dialed one number.
Now i cannot load anything in. My newly loaded list (the same as i used before) says there is only 1 lead.
I manually populated the vicidial_list table as well, and it still says one lead.
root@vici:/var/log/astguiclient# /usr/share/astguiclient/AST_VDhopper.pl --debug
----- DEBUG -----
TIME DEBUG: -8.00|-7|1| GMT: 16:54
SELECT * FROM vicidial_lists where active='N';Inactive Lists: 0
CALLBACK HOLD: 0|SELECT count(*) FROM vicidial_callbacks where callback_time <= '2007-10-22 9:54:57' and status='ACTIVE';|
CAMPAIGNS TO PROCESSES HOPPER FOR: 2|1
Starting hopper run for 100 campaign- GMT: 24hours HOPPER: 5
hopper DONE cleared: 0E0
hopper GMT BAD cleared: 0E0
hopper READY count: 0
hopper too low (0|5) starting hopper dump
campaign lists count: 1 | '101'
no lead filter defined for campaign: 100
leads to call count: 1
NO SHUFFLE-NEW-LEADS INTO HOPPER DEFINED FOR LEAD ORDER
Getting Leads to add to hopper
NO RECYCLE-LEADS INTO HOPPER DEFINED
lead call order: order by lead_id desc
Adding to hopper: 0
DONE with this campaign
I had a working vici installation on slack12. Everything was running smoothly. Now I put the server on the production network and changed the ip. I got asterisk and all my trunks to the pbx working. But I noticed vici is just not working.
Heres what I did to remedy the problem. I got a lot further from when I started, but I am left at a point where there is noone in my session.
1. Changed the ip in inet1.conf
2. dumped mysql. did a search and replace to put the new ip in. reloaded the database with the new ip.
3. modified /etc/astguiclient.conf to use the new hostname.
Screen is dying and not much is working at this point.
4. Ran all crons manually.. Which helped my find that i need the IP in astguiclient.conf rather then the hostname.
5. the stuff in apache is using localhost, so there is no issue there.
Reboot
No I am getting noone is in my session.
My list is active
my phone is active
my campaign is active.
This campaign has 1 active lists and 0 inactive lists
This campaign has 82 leads to be dialed in those lists
This campaign has 6 leads in the dial hopper
After reboot it dialed one number.
Now i cannot load anything in. My newly loaded list (the same as i used before) says there is only 1 lead.
I manually populated the vicidial_list table as well, and it still says one lead.
root@vici:/var/log/astguiclient# /usr/share/astguiclient/AST_VDhopper.pl --debug
----- DEBUG -----
TIME DEBUG: -8.00|-7|1| GMT: 16:54
SELECT * FROM vicidial_lists where active='N';Inactive Lists: 0
CALLBACK HOLD: 0|SELECT count(*) FROM vicidial_callbacks where callback_time <= '2007-10-22 9:54:57' and status='ACTIVE';|
CAMPAIGNS TO PROCESSES HOPPER FOR: 2|1
Starting hopper run for 100 campaign- GMT: 24hours HOPPER: 5
hopper DONE cleared: 0E0
hopper GMT BAD cleared: 0E0
hopper READY count: 0
hopper too low (0|5) starting hopper dump
campaign lists count: 1 | '101'
no lead filter defined for campaign: 100
leads to call count: 1
NO SHUFFLE-NEW-LEADS INTO HOPPER DEFINED FOR LEAD ORDER
Getting Leads to add to hopper
NO RECYCLE-LEADS INTO HOPPER DEFINED
lead call order: order by lead_id desc
Adding to hopper: 0
DONE with this campaign