Hello,
2012/11/7 Gary Stainburn
> I haven't recovered the postgresql database.
Catalog database is required for proper bacula operation. Do you have one?
> The director started without errors and is running (appears in ps ax) but I
> cannot connect using bconsole.
In most cases this means th
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
On 7 November 2012 17:34, Simone Caronni wrote:
> Hello,
>
> I'm the current mantainer of Bacula in Fedora, I stepped i
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 h
On Wednesday 07 November 2012 12:51:35 Felix Schwarz wrote:
> 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,
Hi Gary,
PostgreSQL is supported. The README.Fedora file in
/usr/share/doc/bacula-common-5.2.11/ contains all the details.
fs
--
LogMeIn Central: Instant, anywhere, Remote PC access and management.
Stay in control, upda
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 supporte
