$modx_backup_dir = $_SERVER['DOCUMENT_ROOT'].'/[b]your-directory[/b]/';
Error message and exit itself comes from line 1293 to 1296 of /manager/includes/document.parser.class.inc (MODx 0.9.6).
if (!$ds) { echo "Error while inserting event log into database."; exit(); }
In testing I commented this out which resolved the issue, as well as allowing the DB to be added to the .zip archive again (it hasn’t done that for a while on any of my sites).
Obviously this really isn’t the way to deal with these bugs in a sensible fashion.
So I suppose the more pertinent question is how do we get the event inserted into the database successfully, and therefore remove the error message?
#!/bin/bash
## setup date
suffix=`date +%Y%m%d`
##define the destination directory
dest=logs
##define a thing to do
cmd='/usr/bin/mysqldump'
## create directory in destination path
## name the created directory e.g. 20080431
path="${dest}/${suffix}"
mkdir -p ${path}
##go to that directopy
cd ${path}
## dump the required databases
## insert here
## <db-adress> e.g. mysql5.mydomain.com
##
## <db-user> johndoe
## pls note that there thre is no space between the -u and the username
## eg. -ujohndoe
##
## <db-password> database password
##
## pls note that there thre is no space between the -p and the password
## eg. -pverysecret
##
## <filename>
## a senseful name for your db backup eg yourdomain.com.sql
##
mysqldump -h <db-adress> --all-databases -u<dbuser> -p<db-password> --add-drop-table --create-options > <filename>
##
## after dumping zip every file created in that directory
gzip *
## if you want you can
## delete old dumps (retain 5 days)
find ${dest} -mtime +5 -exec rm {} \;
What’s going on here. I’ve tried version 0.7 up to the current 0.9.4 and they all do the same thing. Am I missing some configuration setting?