It seems to me that there are a few issues here: 1. If you shutdown or upgrade a database while Bacula is running a Job, then Bacula will fail. The solution is: don't do that. Bacula has no explicit code to reconnect to a database after the database is successfully opened, and we don't plan to add any such code as it would render the data less secure.
2. It is possible that the network (if that is what you setup) connection between Bacula and the database server could be broken. In that case, since it is the database's client libraries that established the connection, it is their responsibility to manage the connection and reconnect if it is possible. If the database API supplies a call or flag that requests the client libraries to reconnect, we will (and in the case of MySQL where this exists do) use the API/flag. However, this still leaves it to the client libraries to manage the interface. 3. With most databases, you can set them up to use sockets rather than TCP/IP providing the database and the Director run on the same machine. This might reduce any disconnects that would occur via TCP/IP. 4. Bacula has a connection to the database open only when it is actually running a job, so if this error occurs, and the client library cannot reconnect by itself, Bacula will take the conservative point of view and fail the job. 5. There was one case of MySQL recently releasing a new version where they changed the API/flag that requests reconnect. This unfortunately resulted in a few dropped connections until we modified the Bacula code to correspond to the new MySQL coding. This should no longer be an issue if you are running any version of 1.38.11. 6. Some of the test results reported indicate that there may be a bug with specific versions of MySQL. The manual has pointers to how to resolve these disconnect issues for MySQL where they seem more common (I have never had one ...). Providing there are no Debian specific modifications to the cats directory source code, I recommend closing this bug report as there is no planned change to Bacula and no known bug in version 1.38.11 or greater. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
