Project

General

Profile

Actions

Bug #4307

closed

bacula-fd configuration is mangled

Added by Dan Langille about 9 years ago. Updated about 9 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
01/26/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.2
Affected Architecture:

Description

This is what pfSense 2.2 shows me for my bacula-fd configuration:

Director { 
     Name = bacula-dir #bast
     Password = "not my real password" 
    }
Messages { 
     Name = Standard 
     director  = -dir = all, !skipped, !restored
    }
FileDaemon { 
     Name = -fd #
     FDport = 9102
     WorkingDirectory = /var/db/bacula
     Pid Directory = /var/run
    Maximum Concurrent Jobs = 20
    }

The problem is the line: Name = -fd #

The UI does not specify a place where the Name can be entered.


Files

patch.bacula-client.xml (464 Bytes) patch.bacula-client.xml fix typo Dan Langille, 01/30/2015 11:01 AM
Actions #1

Updated by Dan Langille about 9 years ago

Oh, now that I notice it: "director = -dir" would normally be "director = bacula-dir", that it is, it would match the value from the "Name =" parameter on line 2.

Actions #2

Updated by Dan Langille about 9 years ago

The UI also has a typo: Diector

Actions #4

Updated by Dan Langille about 9 years ago

I do not know how to fix the mangled FailDaemon name, but I see the cause.

                $baculaclient_conf .= "FileDaemon { \n\t Name = {$LocalDirector}-fd #\n\t FDport = {$port}\n\t WorkingDirectory.....

Line 113 of bacula-client.inc. That LocalDirector is not defined. Seems like a copy/paste error to me.

None of the three 'Director type' gives a working configuration file.

If I knew how to change the files on the readonly disk. I would fix this myself.

Any ETA for a fix? After upgrade, I have no backups of the system via Bacula.

Actions #6

Updated by Dan Langille about 9 years ago

I deleted the package and tried to use pkg as described at https://doc.pfsense.org/index.php/Installing_FreeBSD_Packages.

Failed:

[2.2-RELEASE][admin@pfsense.int.unixathome.org]/root: pkg
The package management tool is not yet installed on your system.
Do you want to fetch and install it now? [y/N]: y
Bootstrapping pkg from pkg+http://pkg.FreeBSD.org/freebsd:10:x86:64/latest, please wait...
Verifying signature with trusted certificate pkg.freebsd.org.2013102301... done
pkg: failed to extract pkg-static: Can't create '/usr/local/sbin/pkg-static'
[2.2-RELEASE][admin@pfsense.int.unixathome.org]/root: 
Actions #7

Updated by Jim Pingle about 9 years ago

  • Status changed from New to Feedback

I just pushed a fix, there were some path issues in the config and startup script and such.

Seems to work OK here with the new code:

*status client=pfs22-test-fd
Connecting to Client pfs22-test-fd at 192.168.x.50:9102

pfs22-test-fd Version: 7.0.5 (28 July 2014)  amd64-portbld-freebsd10.0 freebsd 10.0-STABLE
Daemon started 09-Feb-15 12:12. Jobs: run=0 running=0.
[...]

Once you see the new version available in the package list, reinstall the package and give it another try.

Actions #8

Updated by Dan Langille about 9 years ago

This is fixed for me. Thank you.

Actions #9

Updated by Jim Pingle about 9 years ago

  • Status changed from Feedback to Closed

Thanks for the feedback, I'll close this out.

If you have any ideas on how to simplify the GUI for this to make it less confusing, we can open a new ticket for that.

Actions

Also available in: Atom PDF