Well, MariaDB is not MySQL -- there are a number of subtile difficulties
I had when I tried it.  One of the most common problems if you have two
DBs (typically the case in Postgresql) is that the socket port, which is
used by default, is different from the one that Bacula expect.

Best regards,
Kern

On 03/05/2017 09:10 PM, Erik P. Olsen wrote:
> On 2017-03-05 at 20:24:15 Josip Deanovic wrote:
>
>> On Sunday 2017-03-05 19:53:26 Erik P. Olsen wrote:
>>> Hello Kern,
>>>
>>> I have main.pdf downloaded and I believe I have followed the various
>>> steps in phase II to the letter. I have come to the point where I
>>> need some tools to diagnose what is wrong. I am pretty sure that
>>> the problem is due to some sort of security settings in the mysql
>>> database but I am not able to see what that could and the manual
>>> has not been to any help in that respect  
>> When in doubt always try to connect manually using the credentials
>> you plan to use from bacula-dir in order to rule out incorrect
>> database or network setup.
>>
>> For example, from the bacula-dir server you can try something like
>> this: mysql -h <dbhost> -u <dbuser> -p <dbname>
>>
>> The command above should prompt you for a password and if you are
>> able to connect then there is nothing wrong with the mysql setup.
>> Otherwise you need to setup your mysql database properly first.
>>
>> Regards
>>
> Thanks for your advice which I tried both with and without arguments
> and it apparently connected correctly - at least I got a welcome
> message from mariadb. So I guess it is safe to assume that the mysql
> database is properly setup.
>


------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________
Bacula-users mailing list
Bacula-users AT lists.sourceforge DOT net
https://lists.sourceforge.net/lists/listinfo/bacula-users