Hi folks.

I'm just replacing my old Fedora 14 based director / storage server with a
Fedora 17 due to the HDD failing.

However, a yum search bacula shows that the RPM's have changed. I no longer
see ones configured for Postgresql. Are they no longer required or is
Postgresql no longer supported?  I have installed

bacula-client-5.2.11-3.fc17.x86_64
bacula-console-5.2.11-3.fc17.x86_64
bacula-docs-5.2.11-1.fc17.noarch
bacula-libs-sql-5.2.11-3.fc17.x86_64
bacula-director-5.2.11-3.fc17.x86_64
bacula-console-bat-5.2.11-3.fc17.x86_64
bacula-common-5.2.11-3.fc17.x86_64
bacula-storage-5.2.11-3.fc17.x86_64
bacula-libs-5.2.11-3.fc17.x86_64
webacula-5.0.3-3.fc17.noarch

I have managed to start the director using systemd after copying across the
old /etc/bacula/. bconsole.conf and bacula-dir.conf are correct.

I haven't recovered the postgresql database.

The director started without errors and is running (appears in ps ax) but I
cannot connect using bconsole.

My questions are:

1) What is bacula using for the catalog storage (I haven't installed mysql)
2) What's the best way to trace the fault with bconsole? (iptables and
ip6tables are disabled)

--
Gary Stainburn
Group I.T. Manager
Ringways Garages http://www.ringways.co.uk

Hi Gary,

PostgreSQL is supported. The README.Fedora file in
/usr/share/doc/bacula-common-5.2.11/ contains all the details.

fs

Thanks for this Felix.

I've worked through it, including restoring the backup from the old server,
and restarted the director.

However bconsole still hangs and fails to access the director.

I did see entries in /var/log/messages complaining permission denied
on /var/log/bacula.log which didn't exist so I created that

touch /var/log/bacula.log
chown bacula:bacula /var/log/bacula.log
chmod 660 /var/log/bacula.log

(The FD still complained about /var/lib/bacula being missing too. That was
wrong in the RPM's back on F14).

which stopped the errors but didn't get the director working. The problem does
appear to be with the director as it doesn't appear in

netstat -a|grep bacu

although it does appear in

ps ax|grep bacu[l]
1012 ?        Ssl    
0:00 /usr/sbin/bacula-dir -f -c /etc/bacula/bacula-dir.conf -u bacula -g
bacula

Anyone got any ideas?
--
Gary Stainburn
Group I.T. Manager
Ringways Garages http://www.ringways.co.uk

Hello,

I'm the current mantainer of Bacula in Fedora, I stepped in as a mantainer
during the Fedora 15 cycle. One of the first thing I did was close all the
old bugs, including the one you mention.
I don't have the symptoms you describe.

The log file should be created automatically; and I don't have any
permission errors in the logfiles.
Do you have anything like the following in your /etc/bacula/bacula-dir.conf?

Catalog {
  append = "/var/log/bacula/bacula.log" = all, !skipped
}

There's no current bacula package in Fedora that owns /var/lib/bacula; it
seems a leftover from a previous installation.
Did you upgrade your distribution?

--Simone

--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).

btw, the File Daemon should have the following as the working directory in
/etc/bacula/bacula-fd.conf

FileDaemon {
  WorkingDirectory = /var/spool/bacula
}

Regards,
--Simone

--
You cannot discover new oceans unless you have the courage to lose sight of
the shore (R. W. Emerson).

Hello,

Catalog database is required for proper bacula operation. Do you have one?

In most cases this means that Director can't connect to the catalog
database.
The reason for  process bacula-dir existing at process list is that
Director tries to connect to the database a few times before it timeout.
But during an unsuccessful database connections you can't connect to the
director with bconsole.

best regards
--
Radosław Korzeniewski
radoslaw*******