On 4/28/2013 12:33 PM, Marc Chamberlin wrote:
> On 4/26/2013 12:15 PM, Bruno Friedmann wrote:
>> On Friday 26 April 2013 10.47:22 Marc Chamberlin wrote:
>>> I guess I was asking this question on the wrong newsgroup (bacula-users)
>>> thinking it was the place to ask for support... Anywise, got a
>>> suggestion that this might be a more appropriate group (which I didn't
>>> know about), so apologies if you saw this thread over there because I am
>>> now repeating my question over here.. You can look at my thread (same
>>> subject) over there to see how far I got with my questions/explanations....
>>>
>>> This may be a Linux (openSuSE) distro error, but not knowing the internals
>>> of how Bacula gets configured, I thought I would ask my question here
>>> first.
>>>
>>> I get Bacula from the openSuSE (12.3) repositories, and as such I do not
>>> have to compile/install Bacula from source, theoretically. The repository
>>> contains what are called meta packages for Bacula, which select from a set
>>> of other Bacula packages that have been pre-configured for whatever
>>> database type one wishes to use. I chose the one for usage with MySQL.
>>>
>>> The installation went fine, I set up MySQL with out any problem, and
>>> everything checked out OK. However, when I started up the Bacula daemons,
>>> and it tried to do it's first backup, I encountered an error when it tried
>>> to create a backup of the catalog itself and got an error message reporting
>>> that there was no such file or directory called pg_dump.
>>>
>>> I tracked this error to the shell script file - make_catalog_backup - where
>>> I discovered that pg_dump is a file that is to be used when using
>>> PostgreSQL. I also learned that this script expects the name of the
>>> database type to be passed in as the 5th parameter, and if it does not
>>> recognize the database type, it was defaulting to using PostgreSQL. I
>>> hacked this script and changed the default database type to mysql and that
>>> worked!
>>>
>>> Note: the backups of various other computers on my network is working fine,
>>> and the usage of the MariaDB database is working correctly for everything
>>> else, so I believe I have installed Bacula correctly.
>>>
>>> So for my questions -
>>>
>>> 1. Shouldn't the default database type in this script have been set
>>> (automagically) to mysql when the openSuSE developers set up Bacula for
>>> distribution? I presume they built it with the .configure parameter set to
>>> mysql for the MySQL meta package that I installed.
>>>
>>> 2. My second question is a bit more nuanced. OpenSuSE12.3 is no longer
>>> supplying MySQL. Instead they are supplying MariaDB which is supposed to be
>>> 100% compatible with MySQL (so they claim). I do not know where or how the
>>> make_catalog_backup script is called from, so I don't know what got passed
>>> in as the 5th parameter specifying the database type, but I wonder if this
>>> changeover to using MariaDB instead of MySQL might have confused things?
>>>
>>> 3. Is this a bug that should be reported to the Bacula developers, or to the
>>> OpenSuSE distro/packaging team?
>>>
>>> Thanks in advance for any info/advice offered.... Marc..
>> Hello Marc, please open always firstly a bug on bugzilla.novell.com for the
>> package ( the easyest way is doing it from the obs link )
> Thanks Bruno for your reply. I have reported this as a bug to openSuSE -
> https://bugzilla.novell.com/show_bug.cgi?id=817556
> (I remain a bit dubious that this is their fault, but will follow
> developments with interest!)
>> Please specify which repository you are using
> The repository I used to install Bacula from was
> http://download.opensuse.org/repositories/Archiving:/Backup/openSUSE_12.3
>
> And mostly ( I've to read this mail very quickly due to time constraint)
> Your trouble come from the fact you use the old script (still there for
> historical reason)
> make_backup_catalog.pl is your new friend.
>
> That may be the case, but keep in mind that I did not call
> make_backup_catalog myself directly (i.e. via a command line). That is
> something that is being done for me, by the bacula daemons, when they
> backup the catalog as per my scheduling configuration. I don't have any
> idea how or where this script was called from.
>> About MariaDb, it should work out of the box, if not also bug me on
>> bugzilla.o.o
>>
> What is bugzilla.o.o?
>
> Marc...
>
>
Well never mine! I went back and investigated our bacula-dir.conf file,
and apparently sometime in the past the make_catalog_backup.pl file was
failing to work. So we had commented it out and forced the usage of the
older make_catalog_backup script file. When we upgraded, we simply
ported over the configuration files (which are rather complicated, so we
don't want to have to redo them) but I guess we should have checked them
to be sure they were OK...
Anywise, I reconfigured to use the .pl version and it appears to be
working without any change. SO chalk this up to our bad.. Thanks for
being patient with us...
Marc...
--
"The Truth is out there" - Spooky
------------------------------------------------------------------------------
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr
_______________________________________________
Bacula-devel mailing list
Bacula-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-devel
