[prev in list] [next in list] [prev in thread] [next in thread]
List: bacula-bugs
Subject: [Bacula-bugs] [Bacula Bug Reports 0001943]: Bacula director crashes if it reaches the max number con
From: Mantis Bug Tracker <nobody () bugs ! bacula ! org>
Date: 2016-01-22 17:37:01
Message-ID: c82ed14c786e298135db56d5f41c1ab8 () bugs ! bacula ! org
[Download RAW message or body]
Issue 0001943 is now monitored by user dodomeiro.
======================================================================
http://bugs.bacula.org/view.php?id=1943
======================================================================
Reported By: hbrown
Assigned To:
======================================================================
Project: Bacula Bug Reports
Issue ID: 1943
Category: Director
Reproducibility: always
Severity: crash
Priority: normal
Status: closed
Resolution: fixed
Fixed in Version:
======================================================================
Date Submitted: 2012-10-13 00:02 BST
Last Modified: 2016-01-22 17:37 GMT
======================================================================
Summary: Bacula director crashes if it reaches the max number
connections to MySQL server
Description:
I have the Bacula director and storage daemon, plus its MySQL database, all
running on the same host. If I run more backup jobs at one time than the
maximum number of connections the MySQL server will allow, then the Bacula
director will crash.
Originally, the maximum number of connections was set to 150, and so 151
simultaneous jobs would crash the director. I've since increased this to 500 as
a workaround. I understand that bad things are liable to happen if the director
can't contact the MySQL server, but crashing seems less than optimal to me. If
I've misunderstood what should happen, please let me know.
Thanks kindly for your attention, and please let me know if you need any further
information.
Steps to Reproduce:
1. Set the max connections in MySQL to 150 (the default).
2. Get more than 150 jobs running.
3. Director crashes.
Additional Information:
I'm running version 5.5.27 of MySQL, Oracle Community edition.
I've attached the backtrace I get from Bacula; I've only edited out the
passwords.
======================================================================
----------------------------------------------------------------------
(0006534) marcovw (viewer) - 2012-11-06 14:34
http://bugs.bacula.org/view.php?id=1943#c6534
----------------------------------------------------------------------
It seems we are trying to send the error to the database over a closed
connection that ain't going to work. So we better not try that.
Issue History
Date Modified Username Field Change
======================================================================
2012-10-13 00:02 hbrown New Issue
2012-10-13 00:02 hbrown File Added: backtrace.txt
2012-11-06 13:56 marcovw Assigned To => marcovw
2012-11-06 13:56 marcovw Status new => assigned
2012-11-06 14:34 marcovw Note Added: 0006534
2012-11-06 14:35 marcovw Assigned To marcovw =>
2012-11-06 14:35 marcovw Status assigned => closed
2012-11-06 14:35 marcovw Resolution open => fixed
2012-11-06 14:35 marcovw Fixed in Version => 5.2.14 (never
released)
======================================================================
------------------------------------------------------------------------------
Site24x7 APM Insight: Get Deep Visibility into Application Performance
APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
Monitor end-to-end web transactions and take corrective actions now
Troubleshoot faster and improve end-user experience. Signup Now!
http://pubads.g.doubleclick.net/gampad/clk?id=267308311&iu=/4140
_______________________________________________
Bacula-bugs mailing list
Bacula-bugs@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-bugs
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic