Topic: DAR2 does not work after recent updates to 7.4

[HACKERSOFT]

Hello!

I'm wondering why dar2 backup suddenly stops working. It only creates a file db.zip in the desktop share after that, it stops and no backup created.

I verified via command/shell it is still the same, all it gets is:

Code: [Select]

/etc/e-smith/events/actions/dar2-backup FullSMEBackupHS
Connecting /mnt/dar2/FullSMEBackupHS to //hcs-niva-dt01/smeserver
Expanding /etc/dar2/FullSMEBackupHS template
Creating /mnt/dar2/FullSMEBackupHS/nisws1.niva-is.net/FullSMEBackupHS/db.zip
Expiring old backups
Executing pre-backup event

The process was indeed successful in connecting to the shares as well as writing to it since db.zip was created in the desktop share.

Any possible reasons for this or any possible solution?

I also tried updating dar2 but the update did not solve it.

Thanks in advance!

[CharlieBrady]

I'm wondering why dar2 backup suddenly stops working.

If dar2 backup has a problem, tell the bug tracker. See the BUGS link above.

[HACKERSOFT]

I've done that already under the dar2 bugzilla page but still no response.

BTW, I've uninstalled dar2 and tried the backup to workstation method but it also doesn't work right?

Anyone having the same issues?

Thanks!

[cactus]

I've done that already under the dar2 bugzilla page but still no response.

Please post a reference to this bug.

[HACKERSOFT]

Here's the bugtracker link:
http://bugs.contribs.org/show_bug.cgi?id=4857

[HACKERSOFT]

Now, after adding

--lock-tables=false

in the affected file, everything works back to normal.

googling tells me that it is an error in mysql and not on my part, so I turned lock-table to false... lol


Modify:
/etc/e-smith/events/pre-backup/S20mysql-dump-tables

to have this contents and everything will be back to normal:

Code: [Select]

#!/bin/sh
status=$(/sbin/e-smith/config getprop mysqld status)
if [ "$status" = "disabled" ]
then
    echo "mysqld is disabled - no tables dumped" >&2
    exit 0
fi
for db in $(mysql -BNre "show databases;")
do
    mysqldump --add-drop-table -QB "$db" --lock-tables=false -r /home/e-smith/db/mysql/"$db".dump || exit 1
done

[cactus]

Now, after adding

--lock-tables=false

in the affected file, everything works back to normal.

What affected file fo you mean?

error in mysql[/b] and not on my part, so I turned lock-table to false... lol

I would love to see the reference here as I doubt this is the issue nor the solution.

Modify: [/b]
/etc/e-smith/events/pre-backup/S20mysql-dump-tables


to have this contents and everything will be back to normal:

Code: [Select]

#!/bin/sh
status=$(/sbin/e-smith/config getprop mysqld status)
if [ "$status" = "disabled" ]
then
    echo "mysqld is disabled - no tables dumped" >&2
    exit 0
fi
for db in $(mysql -BNre "show databases;")
do
    mysqldump --add-drop-table -QB "$db" --lock-tables=false -r /home/e-smith/db/mysql/"$db".dump || exit 1
done

You are posting:
1. an modification to an undaignosed error here, at least I see nothing describing the cause, nor the error message here.
2. you are posting a fix in the forums, where you should have opened a bug report for it and add the fix there. This way if it really is an error or a bug it will most likely not be fixed and you solution is lost to others (and will also be lost om upgrades as well).

I seriously think you have deviced a work-around for something that should be fixed somewhere else, as I get the impression you have not found the root cause IMHO.

[CharlieBrady]

Please post all followup to the Bug Tracker.
http://bugs.contribs.org/show_bug.cgi?id=4857

[byte]

Locking thread this needs to be followed up on the bug reference. Thanks.