Your message dated Thu, 10 Nov 2016 20:45:03 +0100
with message-id <871syjnmps.fsf...@arioch.leonhardt.eu>
and subject line Re: Bug#843838: Fail to access config file
has caused the Debian Bug report #843838,
regarding Fail to access config file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
843838: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=843838
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: bacula-director
Version: 7.4.4+dfsg-3
Severity: grave
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Hi,
after upgrade baculu bacule-director don't start anymore.
Nov 10 07:39:29 merkur systemd[1]: Starting Bacula Director Daemon service...
Nov 10 07:39:29 merkur bacula-dir[24610]: bacula-dir: ERROR TERMINATION at
parse_conf.c:919
Nov 10 07:39:29 merkur bacula-dir[24610]: Config error: Cannot open config file
"/etc/bacula/bacula-dir.conf": Keine Berechtigung
Nov 10 07:39:29 merkur bacula-dir[24610]: 10-Nov 07:39 bacula-dir: ERROR
TERMINATION at parse_conf.c:919
Nov 10 07:39:29 merkur bacula-dir[24610]: Config error: Cannot open config file
"/etc/bacula/bacula-dir.conf": Keine Berechtigung
Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Control process
exited, code=exited status=1
Nov 10 07:39:29 merkur systemd[1]: Failed to start Bacula Director Daemon
service.
Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Unit entered failed
state.
Nov 10 07:39:29 merkur systemd[1]: bacula-director.service: Failed with result
'exit-code'.
- -- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (900, 'testing'), (800, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.7.0-1-amd64 (SMP w/6 CPU cores)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages bacula-director depends on:
ii bacula-common 7.4.4+dfsg-3
ii bacula-director-mysql 7.4.4+dfsg-3
ii bsd-mailx [mailx] 8.1.2-0.20160123cvs-3
ii init-system-helpers 1.45
ii libc6 2.24-5
ii libcap2 1:2.25-1
ii libgcc1 1:6.2.0-10
ii libssl1.0.2 1.0.2j-1
ii libstdc++6 6.2.0-10
ii libwrap0 7.6.q-25
ii lsb-base 9.20161101
ii ucf 3.0036
ii zlib1g 1:1.2.8.dfsg-2+b3
bacula-director recommends no packages.
Versions of packages bacula-director suggests:
pn bacula-doc <none>
- -- no debconf information
-----BEGIN PGP SIGNATURE-----
iQIcBAEBCgAGBQJYJBd7AAoJEAn4nzyModJdEP4QAI9Sud21FefTt6l0SXzBmBsq
Fqu7EAF+0xgHUE0S+1JaVLV8DyjGtGNiQi06vKWC6AdExJG21MeoVmeQrs42pqYS
7kRfGNlUsvg/hYKQa+tO1pJcUW7Qw7uw9jbzUUA7s1jBecIBFi28V+s9W9ai0rtR
Og46QbQ81j/x6P4OnZ86MM6L4/RbRxWq+C9QRo0NjGju52JSvtCFTjKdEGguBYSZ
Wc0yCrI+L2Ncbh6WJqdp0xMA8B8vKQw12BrJxYur0E++ZBeXbNMGbAgnrfz3HvRJ
qWxOmqO0R2Zh+ZdgHvdd50+Zm/IqiZVORd8lEoNd9T5KHYWrxBSei3yyNN+b0oGK
nFgPm0YRpf3x6dKKkIuCov8Qg458rkbOWx45BJeU40BBkVovcBc7+wEvREfGLKgs
CtamdWJUQtmu3tPUYh/4rloZdnq3rvY89tShGa6tUIWFblw85gl9zeVssrZo5OSC
JorkJdn9HJ9KFunmqR4I0i+uaCdZOnLZD8YKBt1sK1GNxBP4XbIaEb7JnfZM2vrq
ap7dH84sdXPHoLkX9vG6UcNYzFASR/0X0EbXeNWdEYBsZBG8VDdizam3oOu+zV9w
7nki7PHvQxinkLX8QIMVr5ZKCTIPUTv3pl9netMAy75/FhL89wgYrjBmL6aBhWLx
RyqFIztZEZgYA344ldDc
=hKUx
-----END PGP SIGNATURE-----
--- End Message ---
--- Begin Message ---
Hi Jörg,
Sven Hartge <s...@svenhartge.de> writes:
> On 10.11.2016 18:51, Jörg Frings-Fürst wrote:
>> But also I have no idea from where the dirmngr comes.
> I also have no idea, but I find it very suspicious that every group that
> should be "bacula" is "dirmngr" on your system, as if someone/something
> changed /etc/group or replaced it with a one not belonging to the system.
I first thought you maybe deliberately changed the group ownership of
your config files, but if you don't know either, I agree with Sven that
you have a local error with file ownerships or a messed up /etc/groups.
As I wrote earlier, please fix group ownerships of your config files to
be "bacula" or otherwise make sure the daemons have access to them for
reading.
I'm closing this bug as it's not a problem with the debian packages. If
you want to discuss this issue further, please respect the
"Reply-To"-Header.
Thanks,
Carsten
--- End Message ---
