vicidial.org

Hi,

Fresh install of 2.2.0 upgraded the DB table from 2.0.5. Machine worked fine with zero issues for a entire day.

We then changed the database name and we updated /etc/astguiclient.conf and have had nonstop issues since then. The hopper will load some leads, then they all disappear and the system will not rebuild config files. Seems very weird after all that was done was a DB name change!

We have rebooted and verified the database is not corrupt and in good working order.

Can anyone give us some suggestions on what else to look at with this issues?

Machine is a fresh install of CentOS 5.5 64 bit.

Thanks!

when you post, please post your entire configuration including (but not limited to) your installation method, vicidial version and build, 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.

Similar to This:
Vicibox X.X from .iso | Vicidial X.X.X Build XXXX | Asterisk X.X.X | Single Server | No Digium/Sangoma Hardware | No Extra Software After Installation

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)
____

have you considered changing the name of the table BACK?

Do you guys know each other? http://www.vicidial.org/VICIDIALforum/v ... hp?t=12912

Maybe you just shouldn't edit a database on Friday the 13th?

Hi,

Base install of Centos 5.5 64 bit, version 2.2.1-237 build 100510-2015, Asterisk 1.4.27, asterisk/web on one machine, database on separate, no other software and a single Quad port Sangoma card.


Tried doing a reinstall of Vici for the heck of it, same problems still, very odd.

Everything was working great until we changed the DB name :p

Thanks for any insight on this.

when you did your "reinstall" did you actually reinstall from the .iso (wiping the old system away)?

if so, and you had the same problem, you have a problem with your data and/or methodology because the .iso does not have that issue on install otherwise ...

so you'll need to start with the basic troubleshooting techniques

Stage 1)

Code: Select all

screen -list

asterisk -R

post output from those two.