On 05/17/2013 19:00, tqz wrote:
> Hello All,
>
> I have set up bacula in the past, but am now installing the latest version
> 5.2.1.3 onto Ubuntu 12.04 with postgresql and am running into all sorts of
> issues!
>
> I setup bacula using the configuration files that I use on another server
> (lets call this server B), and have edited the files in the appropriate
> places i.e. the location of logs, address, and the catlog information.
>
> I then checked for errors in the files by running commands such as bacula-dir
> -t -c bacula-dir.conf . No issues, so started up bacula. I then did a dump of
> the bacula database from server B, and restored the bacula database on the
> server I just did the installation on. This worked fine, no issues.
>
> I then noticed the next day that the bacula daemon had stopped. So i
> restarted it, was fine, but then it stopped again. This kept happening.
>
> I looked at the log file which stated:-
>
> 14-May 16:03 bacula-dir JobId 0: Fatal error: Could not open Catalog
> "MyCatalog", database "bacula".
> 14-May 16:03 bacula-dir JobId 0: Fatal error: postgresql.c:248 Unable to
> connect to PostgreSQL server. Database=bacula User=bacula
> Possible causes: SQL server not running; password incorrect; max_connections
> exceeded.
> 14-May 16:03 bacula-dir ERROR TERMINATION
>
> But this error seemed to be occuring prior to my restore of the database.
>
> I have since been playing with the dir configuration file and the postgresql
> files but am not having any luck.
>
> Currently, the error I have is:-
> 17-May 16:28 bacula-dir JobId 0: Fatal error: Version error for database
> "bacula". Wanted 14, got 11
> 17-May 16:28 bacula-dir JobId 0: Fatal error: Could not open Catalog
> "MyCatalog", database "bacula".
> 17-May 16:28 bacula-dir JobId 0: Fatal error: Version error for database
> "bacula". Wanted 14, got 11
>
> But I have upgraded using the command - sudo ./update_bacula_tables
> which runs after giving me this error:-
> /etc/bacula/update_postgresql_tables: 16: [: 14: unexpected operator
>
> I have played around with the configuration file and currently, the lines
> which may possibly be giving me trouble is:-
>
> # Generic catalog service
> Catalog {
> Name = MyCatalog
>
> # Uncomment the following line if you want the dbi driver
> #dbdriver = "dbi:postgresql"; dbaddress =127.0.0.1; dbport =5432
> dbname = "bacula"; dbuser = "bacula"; dbpassword = "PASSWORD FOR USER
> BACULA";
>
> }
>
> Altering those lines i.e. by inputting the address of my server would give me
> the following error:-
> 17-May 15:04 bacula-dir JobId 0: Fatal error: Could not open Catalog
> "MyCatalog", database "bacula".
> 17-May 15:04 bacula-dir JobId 0: Fatal error: postgresql.c:248 Unable to
> connect to PostgreSQL server. Database=bacula User=bacula
> Possible causes: SQL server not running; password incorrect; max_connections
> exceeded.
> 17-May 15:04 bacula-dir ERROR TERMINATION
>
> Also, another strange thing im noticing since doing the restore, is that the
> bacula database is the exact same as server b's even though no backups are in
> fact occuring on server A.
>
> HELPPPP???
>
> T.
>
> +----------------------------------------------------------------------
> |This was sent by tqzelijah AT yahoo.co DOT uk via Backup Central.
> |Forward SPAM to abuse AT backupcentral DOT com.
> +----------------------------------------------------------------------
>
>
>
> ------------------------------------------------------------------------------
> AlienVault Unified Security Management (USM) platform delivers complete
> security visibility with the essential security capabilities. Easily and
> efficiently configure, manage, and operate all of your security controls
> from a single console and one unified framework. Download a free trial.
> http://p.sf.net/sfu/alienvault_d2d
> _______________________________________________
> Bacula-users mailing list
> Bacula-users AT lists.sourceforge DOT net
> https://lists.sourceforge.net/lists/listinfo/bacula-users
Hi,
Let me guess: you probably overwrote something in the catalog directory
of the new server. If you don't define the "Where =" in the restore Job
resource, it will be restored to the original location. And if your two
servers are almost identical, the directories most likely coincide.
If that's the case, and you don't have any data yet, you can just
reinitialize the database with:
./drop_bacula_tables
./make_bacula_tables
./grant_bacula_privileges
(you probably have those scripts in /usr/share/bacula)
-Jeff
------------------------------------------------------------------------------
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users
|
