[pkg-bacula-devel] Bug#843838: Bug#843838: Bug#843838: Fail to access config file
Sven Hartge
sven at svenhartge.de
Thu Nov 10 16:04:52 UTC 2016
On 10.11.2016 16:41, Jörg Frings-Fürst wrote:
> Am Donnerstag, den 10.11.2016, 09:25 +0100 schrieb Sven Hartge:
>> Was the system in question at some time in the past cloned/copied via
>> rsync (without using --numeric-ids) or any other method while having
>> been bootet from a rescue medium like GRML or Knoppix?
> One year ago I have move the system 1:1 (tested) to a new hardrive.
> And the error occurred after the last update.
The error is triggered by a change in the way the daemons are started,
as indicated in the changelog, but the core error is the wrong group
(dirmngr != bacula) on your system.
I really think this happened during your system move (it happened to me
as well in the past, forgot to add --numeric-ids to rsync) but you did
not notice it, because most users either matched or the programs don't
care about them, because they are started as root.
I guess if you check other dynamic system users (meaning users created
by packaging scripts and not hardcoded into base-passwd) and groups you
will still find additional mismatches somewhere in /etc and other places.
Grüße,
Sven.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: OpenPGP digital signature
URL: <http://lists.alioth.debian.org/pipermail/pkg-bacula-devel/attachments/20161110/71feecd6/attachment-0003.sig>
More information about the pkg-bacula-devel
mailing list