System Backup removes /tmp ?

[Watje6]

This morning after our server made an remote System Backup mysqld wouldn't start anymore.

-

When I looked into "View Last Backup Log":

Performing MySQL backup
Stage 1 MySQL backup: Completed
Transfering full-mysql.tar.gz to 192.168.2.20: Completed
Transfering full-mysql.md5 to 192.168.2.20: Completed
Stage 2 MySQL backup: Stage 3 MySQL backup:
MySQL could not be started, aborting...

-

Then I looked into the mysqld log:

060318 7:03:05 [Note] /usr/sbin/mysqld: Normal shutdown
060318 7:03:07 InnoDB: Starting shutdown...
060318 7:03:09 InnoDB: Shutdown completed; log sequence number 0 14391144
060318 7:03:09 [Note] /usr/sbin/mysqld: Shutdown complete
060318 07:03:10 mysqld ended
060318 07:04:01 mysqld started
^G/usr/sbin/mysqld: Can't read dir of '/tmp/' (Errcode: 2)
^G/usr/sbin/mysqld: Can't create/write to file '/tmp/ibylpFXR' (Errcode: 2)
060318 7:04:02 InnoDB: Error: unable to create temporary file; errno: 2
060318 7:04:02 [ERROR] Can't init databases
060318 7:04:02 [ERROR] Aborting
060318 7:04:02 [Note] /usr/sbin/mysqld: Shutdown complete

-

Before the backup everything was ok, but after the backup the /tmp directory was removed
We are using the remote System Backup for about 8 months and never had this problem. Does anybody knows why /tmp was deleted ?

 

[nobaloney]

What do you mean by "remote system backup"?

Do you mean the admin level system backup?

That doesn't delete anything.

Jeff

 

[Watje6]

Yes it is the System Backup at the Admin Level and we use the remote transfer option. Before the backup was made, mysql was running fine, and after the backup, mysql wouldn't start because /tmp was gone.

 

[nobaloney]

Interesting. It's been a while since I've read the sysbk code; but I don't remember seeing anywhere where sysbk should be able to do that.

Although it might if you make /tmp your backup directory; the code could allow it to do that, though I haven't checked.

Jeff