 |
By default reconnecting is disabled as it might lead to surprises. You can enable it or even say the director should see things as a fatal error and then your systemd will probably restart the director. I would not use it myself and not randomly restart your postgresql and if you do at a proper moment restart your director. You are looking for the Reconnect and ExitOnFatal keywords in the Catalog resources. Reconnect will only happen when the connection is not in the middle of a Transaction and its in no way a supported option. Given the complexity it might harm more then do good so that is why the default is off. |
|
|
In Bareos 16.2.4 on CentOS 7, ExitOnFatal = yes does not work here. I restart PostgreSQL, and then perform a bconsole status director. Log prints all the time in a loop: 14-Jun 18:53 backup-dir: Fatal Error at postgresql.c:670 because: Fatal database error 14-Jun 18:53 backup-dir JobId 0: Fatal error: sql_get.c:661 sql_get.c:661 query SELECT PoolId,Name,NumVols,MaxVols,UseOnce,UseCatalog,AcceptAnyVolume,AutoPrune,Recycle,VolRetention,VolUseDuration,MaxVolJobs,MaxVolFiles,MaxVolBytes,PoolType,LabelType,LabelFormat,RecyclePoolId,ScratchPoolId,ActionOnPurge,MinBlocksize,MaxBlocksize FROM Pool WHERE Pool.Name='Default' failed: no connection to the server I expect that the director exits on the fatal error as stated in the docs. bareos-dir -xc: Catalog { Name = "MyCatalog" DbAddress = "127.0.0.1" DbPort = 0 DbPassword = "****" DbUser = "bareos" DbName = "bareos" DbDriver = "postgresql" MultipleConnections = no ExitOnFatal = yes } |
|
|
For now I use "Reconnect = yes", which works when the db is restarted until ExitOnFatal works. |
|
|
Fix committed to bareos dev branch with changesetid 10827. |
- Anonymous
