vicidial.org

But if click on the specific item itself, the actual status is green. The system is working. This is an intial setup. When I could not get the ip address of the conference and vicidial conferences to change using the update_server_ip at root login and at the inital login Network eth0 configure file, I follow one person suggestion to going direct to MySql to change ip and reboot. Ip did finally got changed for both types of conferences. But after running 2 update statements, the false red status shows up when clik on GoAdmin via web admin login. The statements were: UPDATE conferences SET server_ip=new ip where server_ip='', and UPDATE vicidial_conferences SET server_ip=new ip where server_ip=''. Noting my mistake that I should have typed where server_ip=old ip instead of 2 single quote '', i reran same 2 statements but this time with where server_ip=old ip. I am not sure this was the cause of the false RED status. Does anyone know where I can go to correct this issue? Thanks in advance.

1) moved to goautodial board, as these features are part of the goautodial shell.

2) when you post, please post your entire configuration including (but not limited to) your installation method and vicidial version with 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 "from scratch" you must post your operating system and should also post the .iso version from which you installed your original operating system.

Similar to This:

GoAutoDial CE 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

Is your system ... not working? Or are you just freakin' about a red light?

Im not sure if it will help at this point but I would recommend viewing the astguiclient.conf file and see which IP is still being used under VARDB = "XXX.XXX.XXX.XXX" by running the command below.

Code: Select all

nano /etc/astguiclient.conf

After finding the DB IP address run

Code: Select all

update_server_ip

in interactive mode and use the DB IP address for the old IP address then your current one in the new IP address field.

one of our servers is having this problem. the status says its off yet its on and working properly.

Version is latest download from GoAutoDial site:
Vicidial SVN 2.4-309a BUILD: 110430-1642
Asterisk 1.4.39.1-vici
Dahdi 2.4.1
VtigerCRM 5.1.0
(Not use) Sangoma 3.5.20
CentOS 5.6 as base (modified kernel as usual)
Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation.

System is working but seeing red is just annoying in Admin page. When it was not working, it was about a message saying your conference number is invalid which was caused by having the old ip 192.168.1.2 in conferences and vicidial_conferences.

As for astguiclient.conf, I went in and replace the original ip of 192.168.1.2 with the same new ip as the server and database. I did run the update_server_ip at my first login after install completed. Rebooted, recheck and confirm ip did change in astguiclient. But status still show red for 3 items of subject line in Admin page.

I must add that even after I update all 192.168.1.2 (old ip) in astguiclient with new ip, the ip did not get updated when I clik on Vicidial|Admin|Conferences and Vicidial Conferences. Not until I ran the command and statements: Mysql -p and update statements posted in very first posting, then the ip finally got updated for the conferences. Right after MySql running, this was when false RED status appear.

ok, does this red status cause any break (or accompany any break) in functionality? or is it JUST that red that annoys you? (and can you post an image of the red in question?)

My admin guy was testing the redundancy by pulling the primary drive out. the next day, the RED status went away. Thanks.

Goautodial CE 2.1
Vicidial version 2.4-309a
build:110430-1642
asterisk 1.4.39.1
no extra hardware.
no addons.


Same here (RED ON ASTERISK APACHE AND MYSQL)

It's a 3 month server everything is running well.

I tought it was normal till i came across this thread

My admin guy was testing the redundancy by pulling the primary drive out

please explain how he did it.

A screenshot
http://www.sendspace.com/file/bsrwda

ok, does this red status cause any break (or accompany any break) in functionality? or is it JUST that red that annoys you?

it is JUST that red that scares me

The redundancy was software base. At time of installaton of CE 2.1 iso, Centos 5.6 allows him set 1 drive as primary and second drive as a mirror. My RED issue went after primary is inserted back and wait for next day. It probably took a few hours. When it was RED, everything was functional as normal.