View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0000623bareos-coreinstaller / packagespublic2016-02-19 15:012017-06-08 15:37
Reportermonotek Assigned To 
PrioritynormalSeverityminorReproducibilityalways
Status closedResolutionfixed 
PlatformLinuxOSUbuntuOS Version14.04
Summary0000623: Can't start bareos-dir via init.d
DescriptionI have a bareos 15.2 director on Ubuntu 14.04 using packages from the official Bareos repositorys.

If i try to start or restart Bareos via "/etc/init.d/bareos-dir restart" i get the following error.

[code]
 * Restarting Bareos Director bareos-dir Checking Configuration and Database connection ...
19-Feb 14:54 bareos-dir: ERROR TERMINATION at parse_conf.c:204
Config error: Expected a Resource name identifier, got: find:
            : line 1, col 5 of file |find /etc/bareos/bareos-dir.d -name '*.conf' -type f -exec echo @{} ;
find: pred.c:1932: launch: Assertion `starting_desc >= 0' failed.

                                                                                                              [fail]
[/code]

If i use "service bareos-dir restart" it works.

[code]
 * Restarting Bareos Director bareos-dir Checking Configuration and Database connection ...
                                                                                                              [ OK ]
[/code]


TagsNo tags attached.

Activities

joergs

joergs

2016-02-19 15:49

developer   ~0002198

Please attach the relevant part of your configuration file (the lines that start with "@|").

Maybe different shells are used for "service" and "etc/init.d/bareos-dir".
monotek

monotek

2016-02-19 15:54

reporter   ~0002199

Last 4 Lines of my bareos-dir.conf:

#icnlude director conf
@|"find /etc/bareos/bareos-dir.d -name '*.conf' -type f -exec echo @{} \;"
# include client files
@|"find /etc/bareos/clients -name '*.conf' -type f -exec echo @{} \;"
joergs

joergs

2016-02-19 15:57

developer   ~0002200

please try
@|"sh -c '...'"
monotek

monotek

2016-02-19 16:21

reporter   ~0002201

does not help.

but just a moment ago, out of nothing, it worked again... until i reconnected via ssh. strange...
joergs

joergs

2016-03-14 10:49

developer   ~0002218

This seems as a problem of the find utility. bareos-dir runs as user bareos. find fails, if it is started in a directory, where the user has no permissions, see
https://bugs.launchpad.net/ubuntu/+source/findutils/+bug/1347788

I close this bug, as it is not a Bareos problem and there are ways to work around this problem.

Issue History

Date Modified Username Field Change
2016-02-19 15:01 monotek New Issue
2016-02-19 15:49 joergs Note Added: 0002198
2016-02-19 15:49 joergs Assigned To => joergs
2016-02-19 15:49 joergs Status new => feedback
2016-02-19 15:54 monotek Note Added: 0002199
2016-02-19 15:54 monotek Status feedback => assigned
2016-02-19 15:57 joergs Note Added: 0002200
2016-02-19 15:57 joergs Status assigned => feedback
2016-02-19 16:21 monotek Note Added: 0002201
2016-02-19 16:21 monotek Status feedback => assigned
2016-03-14 10:49 joergs Note Added: 0002218
2016-03-14 10:49 joergs Status assigned => resolved
2016-03-14 10:49 joergs Resolution open => fixed
2017-06-08 15:37 joergs Status resolved => closed
2017-06-08 15:37 joergs Assigned To joergs =>