From owner-freebsd-ports@FreeBSD.ORG Mon May 4 16:51:30 2009 Return-Path: Delivered-To: ports@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 4100B106566B for ; Mon, 4 May 2009 16:51:30 +0000 (UTC) (envelope-from michael.hughes@gmx.com) Received: from mail.gmx.com (mail.gmx.com [74.208.5.67]) by mx1.freebsd.org (Postfix) with SMTP id D85228FC32 for ; Mon, 4 May 2009 16:51:29 +0000 (UTC) (envelope-from michael.hughes@gmx.com) Received: (qmail invoked by alias); 04 May 2009 16:51:28 -0000 Received: from ssli-dhcp-233.ee.washington.edu (EHLO [128.208.233.233]) [128.208.233.233] by mail.gmx.com (mp-us001) with SMTP; 04 May 2009 12:51:28 -0400 X-Authenticated: #47177982 X-Provags-ID: V01U2FsdGVkX1+LaqRtL3SLgshoqoahCYkud2Ay/DhxcpDalOg7lE OEE/gth97suttj Message-ID: <49FF1D07.6000100@gmx.com> Date: Mon, 04 May 2009 09:51:19 -0700 From: Michael Hughes User-Agent: Thunderbird 2.0.0.19 (X11/20081227) MIME-Version: 1.0 To: Dan Langille References: <49FB4131.7010400@gmx.com> <49FB58C6.4070804@langille.org> In-Reply-To: <49FB58C6.4070804@langille.org> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Y-GMX-Trusted: 0 X-FuHaFi: 0.68 Cc: ports@FreeBSD.org Subject: Re: FreeBSD Port: bacula-client-3.0.0_1 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 04 May 2009 16:51:30 -0000 > 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