Error Starting bareos-dir.d

90 views
Skip to first unread message

Freedomb

unread,
Feb 6, 2025, 1:49:24 PMFeb 6
to bareos-users
Hi team,

After the last BareOS update I can't start my bareos-dir.d

I found this error on journalctl -xe

Feb 06 18:41:11 orionvault bareos-dir[2411]: bareos-dir: dird/check_catalog.cc:72-0 Could not open Catalog "MyCatalog", database "bareos": Version error for database "bareos". Wanted 2240, got 2230
Feb 06 18:41:11 orionvault bareos-dir[2411]: bareos-dir ERROR TERMINATION
Feb 06 18:41:11 orionvault bareos-dir[2411]: Please correct the configuration in /etc/bareos/bareos-dir.d/*/*.conf
Feb 06 18:41:11 orionvault systemd[1]: bareos-director.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ An ExecStart= process belonging to unit bareos-director.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Feb 06 18:41:11 orionvault systemd[1]: bareos-director.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: http://www.ubuntu.com/support
░░
░░ The unit bareos-director.service has entered the 'failed' state with result 'exit-code'.


The other sevices is running good

systemctl status bareos-dir bareos-sd bareos-fd
× bareos-director.service - Bareos Director Daemon service
     Loaded: loaded (/usr/lib/systemd/system/bareos-director.service; enabled; preset: enabled)
     Active: failed (Result: exit-code) since Thu 2025-02-06 18:45:43 UTC; 41s ago
   Duration: 28ms
       Docs: man:bareos-dir(8)
    Process: 3968 ExecStart=/usr/sbin/bareos-dir -f (code=exited, status=1/FAILURE)
   Main PID: 3968 (code=exited, status=1/FAILURE)
        CPU: 22ms

Feb 06 18:45:43 orionvault systemd[1]: bareos-director.service: Scheduled restart job, restart counter is at 10.
Feb 06 18:45:43 orionvault systemd[1]: bareos-director.service: Start request repeated too quickly.
Feb 06 18:45:43 orionvault systemd[1]: bareos-director.service: Failed with result 'exit-code'.
Feb 06 18:45:43 orionvault systemd[1]: Failed to start bareos-director.service - Bareos Director Daemon service.

● bareos-storage.service - Bareos Storage Daemon service
     Loaded: loaded (/usr/lib/systemd/system/bareos-storage.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-02-06 18:34:31 UTC; 11min ago
       Docs: man:bareos-sd(8)
   Main PID: 959 (bareos-sd)
      Tasks: 2 (limit: 19103)
     Memory: 4.2M (peak: 4.7M)
        CPU: 38ms
     CGroup: /system.slice/bareos-storage.service
             └─959 /usr/sbin/bareos-sd -f

Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.
Feb 06 18:34:37 orionvault bareos-sd[959]:  * device S3 uses the droplet backend, please consider using the newer dplcompat backend.

● bareos-filedaemon.service - Bareos File Daemon service
     Loaded: loaded (/usr/lib/systemd/system/bareos-filedaemon.service; enabled; preset: enabled)
     Active: active (running) since Thu 2025-02-06 18:34:31 UTC; 11min ago
       Docs: man:bareos-fd(8)
   Main PID: 958 (bareos-fd)
      Tasks: 2 (limit: 19103)
     Memory: 3.3M (peak: 3.7M)
        CPU: 34ms
     CGroup: /system.slice/bareos-filedaemon.service
             └─958 /usr/sbin/bareos-fd -f

Feb 06 18:34:31 orionvault systemd[1]: Started bareos-filedaemon.service - Bareos File Daemon service.


I'm using the version bareos/bareos,now 24.0.1~pre53.6ffc81313-24 amd64 [installed]

Thank you

Philipp Storz

unread,
Feb 6, 2025, 2:18:04 PMFeb 6
to bareos...@googlegroups.com
Please read the docs:

https://docs.bareos.org/IntroductionAndTutorial/UpdatingBareos.html#updating-the-database-scheme

Am 06.02.25 um 19:49 schrieb Freedomb:
> Hi team,
>
> After the last BareOS update I can't start my bareos-dir.d
>
> I found this error on journalctl -xe
>
> /Feb 06 18:41:11 orionvault bareos-dir[2411]: bareos-dir: dird/check_catalog.cc:72-0 Could not open
> Catalog "MyCatalog", database "bareos": Version error for database "bareos". Wanted 2240, got 2230
> Feb 06 18:41:11 orionvault bareos-dir[2411]: bareos-dir ERROR TERMINATION
> Feb 06 18:41:11 orionvault bareos-dir[2411]: Please correct the configuration in /etc/bareos/bareos-
> dir.d/*/*.conf
> Feb 06 18:41:11 orionvault systemd[1]: bareos-director.service: Main process exited, code=exited,
> status=1/FAILURE
> ░░ Subject: Unit process exited
> ░░ Defined-By: systemd
> ░░ Support: http://www.ubuntu.com/support
> ░░
> ░░ An ExecStart= process belonging to unit bareos-director.service has exited.
> ░░
> ░░ The process' exit code is 'exited' and its exit status is 1.
> Feb 06 18:41:11 orionvault systemd[1]: bareos-director.service: Failed with result 'exit-code'.
> ░░ Subject: Unit failed
> ░░ Defined-By: systemd
> ░░ Support: http://www.ubuntu.com/support
> ░░
> ░░ The unit bareos-director.service has entered the 'failed' state with result 'exit-code'./
>
> The other sevices is running good
>
> /systemctl status bareos-dir bareos-sd bareos-fd
> Feb 06 18:34:31 orionvault systemd[1]: Started bareos-filedaemon.service - Bareos File Daemon service./
>
> I'm using the version bareos/bareos,now 24.0.1~pre53.6ffc81313-24 amd64 [installed]
>
> Thank you
>
> --
> 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-
> users+un...@googlegroups.com <mailto:bareos-users...@googlegroups.com>.
> To view this discussion visit https://groups.google.com/d/msgid/bareos-users/
> ca15ccc1-8fe7-4a1b-8067-2f6463a232b2n%40googlegroups.com <https://groups.google.com/d/msgid/bareos-
> users/ca15ccc1-8fe7-4a1b-8067-2f6463a232b2n%40googlegroups.com?utm_medium=email&utm_source=footer>.


--
Mit freundlichen Grüßen

Philipp Storz philip...@bareos.com
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/

Freedomb

unread,
Feb 6, 2025, 3:40:35 PMFeb 6
to bareos-users
Hi Philipp,

Worked, thanks 

Reply all
Reply to author
Forward
0 new messages