Backup result: Error : -- MySQL dump 10.9

Using my Dolibarr
1

Not sure if it’s a bug…

I have being using dolibarr 2.8, 3.0 and 3.0.1 for a while
2.8 for production and 3.0 (and 3.0.1) for testing adapting a module. no problems untill a few hours ago…

when we finally decided to migrate to 3.0.1 I got this message when I was trying to backup in 3.0.1 (database already migrated to 3.0.1 by dolibarr install script)

Backup result:
Error : -- MySQL dump 10.9
I get the sql file with an .err extension
with or without compression is the same
Any ideas
thanks in advance for any help

2

Can you open the file .err and tell what is content ?

3

Thanks Eldy…
I can’t see anything different from any other sql file i’ve generated before.
I can’t even find any “error” reference inside the .err file generated.
even more… if I change file (delete .err extension) and use it as a normal sql file… it seems to be working oka without any data loss… as far as I can see, but this message doesn’t let me be 100% of the reliability of my backup file… and data.

I’ve installed a clean copy of dolibarr 3.0.1 with a newly created database and I get the same error message… without dataeven loades just fresh installl no data ata all.

I’m pretty sure we have made no changes in mysql and also… backup is working fine in 2.8.1
I don´t know what else should I look or test… again , any help would be really nice…
attached a clean install backup file “----.err” zipped
Regards
Alejandro

mysqldump_doli30_3.zip (36.9 KB)

4

This is reason:

To know if a backup was successfull, dolibarr looks into file for the line
“-- Dump completed”

This line should appears at end of file.
It seems your mysql does not report this line anymore. Can you run the mysqldump command manually to see if this line is present ?

If not, can you run again and add parameter
–dump-date
and tell if this add the line ?

5

Thanks again Eldy.

This is command line shown in 3.0.1:
Backup has been launched with the following command:
mysqldump doli30 -h localhost -u “user” -l --single-transaction -K --add-drop-table --tables --hex-blob -p “password”
Backup result:
Error : – MySQL dump 10.9

And this is command line shown in dolibarr 2.8.1:

Backup will be done through the following command:
mysqldump doli -h localhost -u “user” -l --single-transaction -K --add-drop-database --add-drop-table --tables --hex-blob -p “password”

Backup result:
Backup file successfully generated.
Generated files can now be downloaded

Same server both cases (same mysql php etc)

command line runs ok but
I cant find “-- Dump completed” neither in 2.8.1 file nor in 3.0.1 files

Trying to add option gives me this error:

mysqldump doli -h localhost -u “user” -l --single-transaction -K --dump-date --add-drop-database --add-drop-table --tables --hex-blob -p “password”
mysqldump: unknown option ‘–dump-date’

Could it be that dolibarr 2.8.1 didn’t check dump completed?
and now it does (I’ve never used 2.9)
maybe ther is an option to enable this in mysql

no idea by my side…

6

Yes, in 2.8 there was no check.
With 3.0.1 there is but it looks like check works only for very recent mysqldump command.

7

Thanks again
So… may I disregard this error, as a temporary workarround?
or could I get this check working…
It’s a just me situation? anyone else is having this issue?
(yes , I know… too many questions together)
A.

8

I think you can ignore error.
I made a fix to test dump complete on another string.

9

Thanks again Eldy!