Just a quick update:
PR 2065 fixes the problem with dbconfig-common, so that after it is merged updates will work out of
the box.
Regards,
Philipp
Am 13.12.24 um 17:55 schrieb Philipp Storz:
Hello Seth,
probably you need to upgrade the database scheme.
see:
https://docs.bareos.org/IntroductionAndTutorial/UpdatingBareos.html#updating-the-database-scheme
This is usually done by the following commands run as root:
su postgres -c /usr/lib/bareos/scripts/update_bareos_tables
su postgres -c /usr/lib/bareos/scripts/grant_bareos_privileges
best regards,
Philipp
Am 13.12.24 um 17:46 schrieb Seth Galitzer:
My assistant upgraded today before I could tell them to wait. I've corrected new configs and
updated the database schema, and the dir refuses to start.
Most recent output from /etc/bareos/bareos.log:
13-Dec 10:30 bareos-dir ERROR TERMINATION
Please correct the configuration in /etc/bareos/bareos-dir.d/*/*.conf
Output from /var/log/syslog:
2024-12-13T10:40:12.713443-06:00 imperial systemd[1]: bareos-director.service: Start request
repeated too quickly.
2024-12-13T10:40:12.713873-06:00 imperial systemd[1]: bareos-director.service: Failed with result
'exit-code'.
2024-12-13T10:40:12.714046-06:00 imperial systemd[1]: Failed to start bareos-director.service -
Bareos Director Daemon service.
Output from journalctl -xe:
Dec 13 10:40:12 imperial systemd[1]: bareos-director.service: Start request
repeated too quickly.
Dec 13 10:40:12 imperial systemd[1]: bareos-director.service: Failed with
result 'exit-code'.
Subject: Unit failed
Defined-By: systemd
Support: https://www.debian.org/support
The unit bareos-director.service has entered the 'failed' state with result
'exit-code'.
Dec 13 10:40:12 imperial systemd[1]: Failed to start bareos-director.service - Bareos Director
Daemon service.
Subject: A start job for unit bareos-director.service has failed
Defined-By: systemd
Support: https://www.debian.org/support
A start job for unit bareos-director.service has finished with a failure.
The job identifier is 1408 and the job result is failed.
Basically, nothing useful is being logged. No pointers to actual problems in any existing conf
files. Any way to turn up logging verbosity to maybe help identify the problem?
This is running on debian 12. Problem persists after full reboot. SD and FD are starting fine on
this host. It's only the dir that fails. I'd really like to get this fixed before nightly jobs
start tonight.
Any advice is appreciated.
Thanks.
Seth
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bareos-
[email protected] <mailto:[email protected]>.
To view this discussion visit https://groups.google.com/d/msgid/bareos-users/
d528edd0-59eb-419c-8005-1214e2f19a18n%40googlegroups.com <https://groups.google.com/d/msgid/
bareos- users/d528edd0-59eb-419c-8005-1214e2f19a18n%40googlegroups.com?
utm_medium=email&utm_source=footer>.
--
Mit freundlichen Grüßen
Philipp Storz [email protected]
Bareos GmbH & Co. KG Phone: +49 221 63 06 93-92
http://www.bareos.com
Sitz der Gesellschaft: Köln | Amtsgericht Köln: HRA 29646
Geschäftsführer: Stephan Dühr, Jörg Steffens, Philipp Storz
Die "dass IT GmbH" wurde mit der "Bareos GmbH & Co. KG" verschmolzen,
siehe https://www.bareos.com/de/dassit-verschmelzung/
--
You received this message because you are subscribed to the Google Groups
"bareos-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/bareos-users/d83a1aed-ba12-48cd-aa27-086e4a0290b6%40bareos.com.
