Hi All,
First of all, a HUGE thank you to Kern and the Bacula developers for
such an amazing piece of software. I have been working with Bacula for
about a year now and recently took on full support for a large Bacula
installation (~1700 clients backing up between 1-2TB/day). Based on my
experience I am extremely appreciative this software was written and is
as well maintained as it is. Thank you. =)
I am posting to this list because I have encountered a problem and
believe I've exhausted my resources (bug reports, existing posts to
mailing lists, documentation) so I was hoping for some guidance from the
community. Thank you in advance for your consideration.
I have been happily running bacula-server-5.0.3 with postgresql-9.0.5_1
on a FreeBSD 8 server until an ill-fated chain of events led to me to
have to upgrade bacula-server to 5.2.2 before I had a chance to test it
in a development environment. Although I followed the release notes by
upgrading the storage nodes and running 'update_bacula_tables,' since
the upgrade the server (director) has crashed twice in 5 days and I've
had to manually restart it a couple of times after normal queries like
"status storage=X" appear to hang.
Based on analysis of Munin graphs that report things like PostgreSQL
connections, PostgreSQL locks, process states, network connections
(netstat), and memory utilization it appears that something significant
has changed between 5.0.3 and 5.2.2 that is leaving a very high number
of PostgreSQL connections in Idle state instead of being closed. When
Bacula crashes the PostgreSQL connections graph shows a large number of
connections in "Waiting for lock" state. At the same time looking at
the PostgreSQL locks graph shows a very large number of
"ShareRowExclusive" and "AccessShare" locks which is behaviour we didn't
see prior to upgrading to 5.2.2. If anyone would like a copy of these
graphs I can send them to you directly or post them to the mailing list
if that is allowed.
I know that 5.2.3 was released on 12/16 and saw that there was a bug fix
with update stats that I thought may be related to what I'm seeing
however have not updated because 5.2.3 has yet to make it into the
FreeBSD ports collection. Based on the problem I described does this
sound like something that may have been fixed in 5.2.3? If not, does
anyone have other ideas on what I can do to troubleshoot?
Thanks again for your insight and help with this,
Jenny =)
--
=======================================================
Jennifer R. Aquilino
S&T IT Support
Lawrence Livermore National Laboratory
Mail Stop L-556
7000 East Avenue
Livermore, CA 94550
Voice: (925)-424-4585
Fax: (925)-423-8719
Email: aquili...@llnl.gov
========================================================
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
