vicidial.org

Hi,
I have installed the latest version of the ViciBox 4.0.2 today and I am getting the below error message while running the ADMIN_backup.pl
"mysqldump: Got error: 1105: Unknown error when doing refresh"
how can I fix this.
Regards..
Vijay

Single Server | ViciBox.x86_64-4.0.2 | VERSION: 2.6-392a | BUILD: 130102-1135 | No other hardware

add --help to the command and get all the options.

then try to use the debug option which may shed some light on the topic.

also verify that you have no "crashed tables" by using the mysqlcheck command with autorepair (mentioned many times here and elsewhere).

if that fails, it's not a bad idea to backup everything but the database to be sure that's the only problem. then try your own mysqldump (manual backup to text file) to see if it's a basic problem ...

mysqldump asterisk -u cron -p1234 > /tmp/2013-01-23_2235_SampleBackup_Asterisk.sql

Thank you very much for the quick reply. I have tested the database and can’t find any crashed tables and able to do the manual backup. I am suspecting the problem from the flush logs, if I remove the flush-logs from the ADMIN_backup.pl (line no 298 & 299) the error message is not getting. Kindly note that I have installed a new server for the test purpose and also getting the same error message.
Regards..
Vijay

if a fresh install exhibits the same behavior, it is worth a post in the Vicidial Issue Tracker (and post a link here) IF it is related to the latest SVN and not part of the Vicibox install itself. Hard to tell whether it is installer related or vicidial code related.

Thanks....

I have reported to the Vicidial issue tracker (http://www.vicidial.org/VICIDIALmantis/view.php?id=640)

Regards...
Vijay

Solution:

Code: Select all

/bin/chmod 655 /var/log/mysql

Tested and working on Vicibox 4.0.3

Moving this post to the Vicibox board as this will need to be fixed in the .iso installer.

Perhaps this will cause Kumba to create "4.0.4"?

Hi Guys,

This issue hasn't been fixed yet. Still getting the issue with Version: 2.8b0.5 | SVN Version: 2020 | DB Schema Version: 1355.

The chmod fix mentioned above does sort it out - Thanks!

Rudolf