Bug#843838: [pkg-bacula-devel] Bug#843838: Bug#843838: Fail to access config file

2016-11-10 Thread Jörg Frings-Fürst
Am Donnerstag, den 10.11.2016, 17:04 +0100 schrieb Sven Hartge:
> 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.
> 

I guess that the error is the wrong group. But the error comes not from
use rsync without --numeric-ids. I don't use rsync, I have moved the
hard disk with dd.

But also I have no idea from where the dirmngr comes.

A note:

If you change "the way the daemons are started" please check and change
the required user/group.

> Grüße,
> Sven.
> 

CU
Jörg

-- 
New:
GPG Fingerprint: 63E0 075F C8D4 3ABB 35AB  30EE 09F8 9F3C 8CA1 D25D
GPG key (long) : 09F89F3C8CA1D25D
GPG Key: 8CA1D25D
CAcert Key S/N : 0E:D4:56

Old pgp Key: BE581B6E (revoked since 2014-12-31).

Jörg Frings-Fürst
D-54470 Lieser

Threema: SYR8SJXB

IRC: j_...@freenode.net
 j_...@oftc.net

My wish list: 
 - Please send me a picture from the nature at your home.


signature.asc
Description: This is a digitally signed message part


Bug#843838: [pkg-bacula-devel] Bug#843838: Bug#843838: Fail to access config file

2016-11-10 Thread Sven Hartge
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.



signature.asc
Description: OpenPGP digital signature