Page 1 of 1

MySQL connect error when copying custom fields

PostPosted: Mon Aug 18, 2014 3:47 pm
by dspaan
Hi all,

I have a ViCibox two server cluster which has been running fine and still is. I just created a new list and tried to copy custom fields from an old list to the new one and i get this:

MySQL connect ERROR:

The rest of the screen is blank and the fields are not copied.

The particular thing about this cluster is that it used to be a single server install before this and i moved it over from another host.
This is a ViCibox 3.1.15 install
VERSION: 2.8-426a
BUILD: 140214-1643

I tried checking various logs but the only thing i could find is this in /var/mail/root:
DBI connect('asterisk:localhost:3306','custom',...) failed: Access denied for user 'custom'@'localhost' (using password: YES) at$
Couldn't connect to database: Access denied for user 'custom'@'localhost' (using password: YES) at /usr/share/astguiclient/ADMIN$


DBD::mysql::st execute failed: MySQL server has gone away at /usr/share/astguiclient/AST_conf_update.pl line 364.
executing: SELECT extension,conf_exten from conferences where server_ip='xx.xx.xx.xx' and extension is NOT NULL and extension !=$


But these errors were not generated at the time of copying the custom fields.

I did
mysql -u custom -p
and noticed i could not login with the password custom1234 that was specified in astguiclient.conf so i changed it to blank in astguiclient.conf (which works). But this did not resolve my problem.

Re: MySQL connect error when copying custom fields

PostPosted: Tue Aug 19, 2014 1:39 pm
by striker
change it to cron and 1234
or create new user in mysql as custom with pass custom1234

Re: MySQL connect error when copying custom fields

PostPosted: Tue Aug 19, 2014 5:20 pm
by dspaan
Thanks Striker, changing it to cron/1234 worked.

Re: MySQL connect error when copying custom fields

PostPosted: Mon Sep 08, 2014 3:37 am
by dspaan
Update, creating new users custom@% and custom@localhost seemed to be the final fix, otherwise you would still get custom field errors because the cron user i made earlier did not have the proper permissions (create and alter).