On 2021-12-26 13:47, Graham Dicker wrote:
Thank you Josip this is very helpful. I have restored everything I had
tinkered with back to what it was, that is:
Removed specification of port and socket from /etc/my.cnf
Removed specification of port and socket from bacula-dir.conf
both of this were previously specifying the akonadi socket and port
3306
now './bacula' start from a console as root puts this message in the
log:
26-Dec 09:40 bacula-dir JobId 0: Fatal error: Could not open Catalog
"MyCatalog", database "bacula".
If I run mysql from a console as root then 'use bacula' succeeds and I
can
access the tables but if i try the same thing as a normal user I get:
MariaDB [(none)]> use bacula;
KMail/akonadi behaviour is still not normal. I have to click the Kmail
icon,
then the desktop, then KMail icon again to get it to start, and at
least
the first time of collecting my POP3 email takes a lot longer than
usual.
Graham
I see that my attempts to paste messages copied from a console window
into an
email are not working as I expect. Trying again...The message above
should
have read:
26-Dec 09:39 bacula-dir JobId 0: Fatal error: Could not open Catalog
"MyCatalog", database "bacula".
26-Dec 09:39 bacula-dir JobId 0: Fatal error: mysql.c:293 Unable to
connect to
MySQL server.
Database=bacula User=bacula
MySQL connect failed either server not running or your authorization is
incorrect.
26-Dec 09:39 bacula-dir ERROR TERMINATION
Please correct configuration file: /opt/bacula/etc/bacula-dir.conf
Ok. So, leave akonadi to use its own mysql instance and don't use it
for anything else. This is the default setup on the Centos/RHEL and
I assume that Suse is doing the same in that regards.
So, you need to configure your separate (I would say normal) mysql
service
which you can use for all your purposes (including bacula).
That would mean that you would need to configure your /etc/my.cnf
to point to the correct mysql data directory (e.g.
datadir=/var/lib/mysql),
you would need to define either some socket (e.g.
socket=/var/lib/mysql/mysql.sock)
or IP and port.
Then you would need to enable and start that service using the the
usual procedure that applies for you OS (probably using systemctl tool
as this is the most common thing these days, on Linux distributions).
Then you would need to create the database you plan to use for
bacula and its database user. After that you will need to populate
it with the bacula tables.
Be careful to use the correct credentials when connecting to the
database (make sure you are using the correct mysql service and
not the one dedicated to akonadi).
After that, you will need to reconfigure your bacula-dir.conf
the way it uses correct connection info and user credentials.
Regards!
--
Josip Deanovic
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users