From: Marcin K. <ha...@pl...> - 2012-03-12 08:53:24
|
Hello. I've recently switched my Bacula from 5.0.3 to 5.2.6. I'm using PostgreSQL for storing Bacula database. Everything was working fine on 5.0.3 with my 70GB database. However first night after upgrade director has died during backup corrupting my database completly. I was about to clean my database anyway so I've removed everything and done clean 5.2.6 install. Everything seemed fine, but during nightly backup director has died again. Bacula log said: 12-Mar 06:23 bacula-sd JobId 109: Spooling data again ... 12-Mar 06:34 bacula-sd JobId 109: User specified spool size reached. 12-Mar 06:34 bacula-sd JobId 109: Writing spooled data to Volume. Despooling 42,949,689,946 bytes ... 12-Mar 06:44 bacula-sd JobId 109: Despooling elapsed time = 00:10:06, Transfer rate = 70.87 M Bytes/second 12-Mar 06:44 bacula-sd JobId 109: Spooling data again ... 12-Mar 06:57 bacula-sd JobId 109: User specified spool size reached. 12-Mar 06:57 bacula-sd JobId 109: Writing spooled data to Volume. Despooling 42,949,689,861 bytes ... 12-Mar 07:08 bacula-sd JobId 109:12-Mar 07:35 bacula-dir JobId 0: Fatal error: Could not open database "bacula". 12-Mar 07:36 bacula-dir JobId 0: Fatal error: Query failed: INSERT INTO Log (JobId, Time, LogText) VALUES (0,'2012-03-12 07:35:30','bacula-dir JobId 0: Fatal error: Could not open database "bacula". '): ERR=no connection to the server Quick check and PostgreSQL said that it has reached maximum connections limit of 200 hence disallowing any new connections. Another quick check of process and connections logs and it looks like Bacula has problems with handling PostgreSQL connections correctly (doesn't close them?). There were 200 connections from Bacula to database, all in idle state according to ps: 6775 ? Ss 0:00 postgres: bacula bacula 127.0.0.1(44645) idle I just started director again this morning and launched single test job. Now its running for 26 minutes and I already have four idle connections to database. It seems that new connection appears after each data despooling. Any chances for quick patch fixing this problem? M. |