Date: Mon, 04 May 2009 09:51:19 -0700 From: Michael Hughes <michael.hughes@gmx.com> To: Dan Langille <dan@langille.org> Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: bacula-client-3.0.0_1 Message-ID: <49FF1D07.6000100@gmx.com> In-Reply-To: <49FB58C6.4070804@langille.org> References: <49FB4131.7010400@gmx.com> <49FB58C6.4070804@langille.org>
next in thread | previous in thread | raw e-mail | index | archive | help
> Have you raised this issue on the bacula users mailing list? If so, > what is the URL into the archives so we can investigate. In response to your question, I have raised the issue on the bacula-users mailing list, although I haven't had any responses yet. I came to the conclusion about the client and director incompatibility through our own testing and a couple forum threads I found web searching. We upgraded the bacula client port which upgraded the bacula-fd daemon running from 2.4.4 to 3.0.1. No configuration files were changed, and backups ran properly prior to the port upgrade. I have checked the obvious, such as the port being closed by a firewall or the network interface not being up. Which left me testing for incompatibilities between the director and client because of the major version number change. I did find these related threads in the bacula-users archive http://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg34494.html and http://www.mail-archive.com/bacula-users@lists.sourceforge.net/msg34494.html Michael Hughes SSLI/MTML Labs Student System Administrator
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?49FF1D07.6000100>