DB backup ist still not working in 5.1.33 Beta 7, so the db overwritten problems mentioned in another thread arem hardly to handle. Is there any chance to analyse this issue again?
The issue was the mysql socket specified in your host name: "localhost:/tmp/mysql5.sock". While php's mysql_connect can process that, the mysqldump command line utility can't handle socket specification in the host name and needs it in a separate -S parameter. I've changed WSN's backup utility so that it splits off the socket into the separate parameter, and it works for you now.
0/5
1
2
3
4
5
Sorry, you don't have permission to post posts. Log in, or register if you haven't yet.
Comments on Backup Database no error but backup.sql
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
Hi Paul,
Backup Database writes "The backup file has been generated." but backup.sql has a size of 0KB (empty) and a timestamp from now.
Thanx,
Frank
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
Not reproducible, backups write fine here.
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
Do you have any tips for me for tracing or debugging this sitution. Changing the "Debug Level" don't help me an further.
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
If your host's security settings prevent doing backups, I added a notice to explain that a couple betas ago.
If you're in apache mode without suPHP, it could be an admin directory permissions issue.
Maybe it's possible for mysqldump to not be on the server, or to not be accessible without some sort of absolute path, but I doubt it.
Otherwise, as always, site inspection service is the easy way to tell.
Forum Regular
Usergroup: Customer
Joined: Dec 20, 2007
Location: Germany
Total Topics: 33
Total Comments: 106
DB backup ist still not working in 5.1.33 Beta 7, so the db overwritten problems mentioned in another thread arem hardly to handle. Is there any chance to analyse this issue again?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
The only way I can tell you what's going on is if you let me have a look at it: http://www.wsnlinks.com/inspection.html
It's not a generic issue, it's specific to your server configuration.
It is a *nix host and not in safe_mode?
developer
Usergroup: Administrator
Joined: Dec 20, 2001
Location: Diamond Springs, California
Total Topics: 61
Total Comments: 7868
The issue was the mysql socket specified in your host name: "localhost:/tmp/mysql5.sock". While php's mysql_connect can process that, the mysqldump command line utility can't handle socket specification in the host name and needs it in a separate -S parameter. I've changed WSN's backup utility so that it splits off the socket into the separate parameter, and it works for you now.