Menu
▾
▴
[Bacula-bugs] [Bacula Bug Reports 0002283]: Database reconnect issue
|
From: Mantis B. T. <no...@bu...> - 2017-05-17 11:24:36
|
The following issue has been CLOSED ====================================================================== http://bugs.bacula.org/view.php?id=2283 ====================================================================== Reported By: murzzz Assigned To: ====================================================================== Project: Bacula Bug Reports Issue ID: 2283 Category: Director Tags: connection, database, Postgresql Reproducibility: always Severity: major Priority: normal Status: closed Resolution: no change required Fixed in Version: ====================================================================== Date Submitted: 2017-05-17 10:56 BST Last Modified: 2017-05-17 12:24 BST ====================================================================== Summary: Database reconnect issue Description: When bacula opens connect to database (Postgresql in my case), and then connection drops (server restart, network problem). Bacula doesn't try to reopen connection again but still trying to use that connect and fails. Currently have to restart Director to reestablish connection. Most of network software trying to reestablish connection with some timeout. Would be nice to have this behavior in bacula (probably as an option) Steps to Reproduce: Run any command that establish connection to database, restart database. ====================================================================== ---------------------------------------------------------------------- (0007513) kern (administrator) - 2017-05-17 12:24 http://bugs.bacula.org/view.php?id=2283#c7513 ---------------------------------------------------------------------- I really do not understand the reason for this bug report, because Bacula maintains no permanent connection with the database server. Every job that starts opens a new connection (sometimes during the job additional connections will be opened). As long as Bacula starts and remains running there is no reason to shut it down and restart it if there is a database failure. In the future, please post support questions such as this one to the bacula-users email list. Please open a bug report only if the users list confirms that you have run into a bug. Thanks. Issue History Date Modified Username Field Change ====================================================================== 2017-05-17 10:56 murzzz New Issue 2017-05-17 10:58 murzzz Tag Attached: connection 2017-05-17 10:58 murzzz Tag Attached: database 2017-05-17 10:58 murzzz Tag Attached: Postgresql 2017-05-17 12:24 kern Status new => closed 2017-05-17 12:24 kern Resolution open => no change required 2017-05-17 12:24 kern Note Added: 0007513 ====================================================================== |