Thanks a lot. I did not suspect duplicity because it seemed to me quite
stable. But in fact it is not. Duplicity really changed the permissions.
The user proxy in the rescue system has the same uid than the user man
in Debian. It is reproducible now. Better I start a complete new
installation now. Fortunately I was still testing the backup procedures.


I will ask someone of the duplicity guys or use something different.
Thank you very much. 

Hartmut 

root@sysresccd /root % duplicity -t 4D --file-to-restore
var/cache/man/id/ ftp://XXXXXX@XXXXXX
/mnt/backup/tmp/4D_var_cache_man_id
root@sysresccd /root % ls /mnt/backup/tmp/4D_var_cache_man_id -l
total 32
-rw-r--r-- 1 man root 190 Nov 9 09:36 CACHEDIR.TAG
drwxr-sr-x 2 man root 4096 Nov 9 09:35 cat1
drwxr-sr-x 2 man root 4096 Nov 9 09:35 cat5
drwxr-sr-x 2 man root 4096 Nov 9 09:35 cat8
-rw-r--r-- 1 man root 13559 Nov 12 18:44 index.db
root@sysresccd /root % chroot /mnt/backup /bin/bash
root@sysresccd:/# ls /tmp/4D_var_cache_man_id/ -l
total 32
-rw-r--r-- 1 proxy root 190 Nov 9 10:36 CACHEDIR.TAG
drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat1
drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat5
drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat8
-rw-r--r-- 1 proxy root 13559 Nov 12 19:44 index.db

Am 2014-11-16 22:45, schrieb [email protected]: 

> This is an automatic notification regarding your Bug report
> which was filed against the man-db package:
> 
> #769802: man-db: cron.daily fails: "fopen: Permission denied"
> 
> It has been closed by Colin Watson <[email protected]>.
> 
> Their explanation is attached below along with your original report.
> If this explanation is unsatisfactory and you have not received a
> better one in a separate message then please contact Colin Watson 
> <[email protected]> by
> replying to this email.
> 
> Received: (at 769802-close) by bugs.debian.org; 16 Nov 2014 21:43:56 +0000
> X-Spam-Checker-Version: SpamAssassin 3.3.2-bugs.debian.org_2005_01_02
> (2011-06-06) on buxtehude.debian.org
> X-Spam-Level: 
> X-Spam-Status: No, score=-8.3 required=4.0 
> tests=BAYES_00,FROMDEVELOPER,GENDER,
> HAS_BUG_NUMBER,RCVD_IN_DNSWL_LOW autolearn=ham
> version=3.3.2-bugs.debian.org_2005_01_02
> X-Spam-Bayes: score:0.0000 Tokens: new, 14; hammy, 151; neutral, 108; spammy,
> 0. spammytokens: hammytokens:0.000-+--rw-r, 0.000-+--UD:cron.daily,
> 0.000-+--cron.daily, 0.000-+--crondaily, 0.000-+--H*u:1.5.21
> Return-path: <[email protected]>
> Received: from b.a.painless.aa.net.uk ([81.187.30.65])
> by buxtehude.debian.org with esmtps (TLS1.0:DHE_RSA_AES_256_CBC_SHA1:256)
> (Exim 4.80)
> (envelope-from <[email protected]>)
> id 1Xq7bv-0008Qt-Vm
> for [email protected]; Sun, 16 Nov 2014 21:43:56 +0000
> Received: from 
> 3.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.4.1.b.e.2.f.f.b.0.b.8.0.1.0.0.2.ip6.arpa 
> ([2001:8b0:bff2:eb14::3] helo=riva.pelham.vpn.ucam.org)
> by a.painless.aa.net.uk with esmtps (TLSv1:AES128-SHA:128)
> (Exim 4.77)
> (envelope-from <[email protected]>)
> id 1Xq7br-0006P9-8n
> for [email protected]; Sun, 16 Nov 2014 21:43:51 +0000
> Received: from ns1.pelham.vpn.ucam.org ([172.20.153.2] helo=riva.ucam.org)
> by riva.pelham.vpn.ucam.org with esmtps (TLS1.2:DHE_RSA_AES_128_CBC_SHA1:128)
> (Exim 4.80)
> (envelope-from <[email protected]>)
> id 1Xq7bq-0000fV-Av
> for [email protected]; Sun, 16 Nov 2014 21:43:50 +0000
> Date: Sun, 16 Nov 2014 21:43:49 +0000
> From: Colin Watson <[email protected]>
> To: [email protected]
> Subject: Re: Bug#769802: man-db: cron.daily fails: "fopen: Permission denied"
> Message-ID: <[email protected]>
> References: <[email protected]>
> <[email protected]>
> <[email protected]>
> MIME-Version: 1.0
> Content-Type: text/plain; charset=utf-8
> Content-Disposition: inline
> Content-Transfer-Encoding: 8bit
> In-Reply-To: <[email protected]>
> User-Agent: Mutt/1.5.21 (2010-09-15)
> 
> On Sun, Nov 16, 2014 at 07:29:45PM +0100, Hartmut Brüning wrote:
> 
>> Wow! It is this: -rwxr-xr-x 1 root root 133728 Nov 3 22:39 /usr/bin/mandb 
>> /var/cache/man/id/: total 40 drwxr-sr-x 5 proxy root 4096 Nov 16 15:23 . 
>> drwxr-sr-x 33 man root 4096 Nov 16 16:16 .. -rw-r--r-- 1 proxy root 190 Nov 
>> 9 10:36 CACHEDIR.TAG drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat1 
>> drwxr-sr-x 2 proxy root 4096 Nov 9 10:35 cat5 drwxr-sr-x 2 proxy root 4096 
>> Nov 9 10:35 cat8 -rw-r--r-- 1 root root 13513 Nov 12 19:44 index.db I am 
>> trying to find out how this could have happen.
> 
> Ah, you said you'd used duplicity. At least some versions of duplicity
> have a terrible flaw whereby it stores ownership information about files
> by user/group name rather than number. This means that you cannot
> safely use it, for example, to restore a full-system backup when running
> from a live CD, because user and group names and numbers are not going
> to match up. I had a very similar experience with duplicity some years
> ago, and as a result of this and other flaws concluded that it was
> unsuitable for use as a full-system backup program, and could only
> reasonably be used on a smaller scale, perhaps for backing up a single
> user's home directory.
> 
> I'm afraid you're in for a rather tedious exercise of finding all the
> incorrect users and groups of files on your system; there will likely be
> more than just this, and when I had this experience I was forced to
> manually check through all the files not owned by either root or my own
> user. But it isn't a bug in man-db.
> 
> Good luck,
> 
> Package: man-db
> Version: 2.7.0.2-3
> Severity: important
> 
> Dear Maintainer,
> 
> I have mails from Cron about mandb. I think, it is not the problem of bug
> #209185.
> 
> If I execute the command from crom.daily manualy as root, I get the following
> 
> root@XXXXXX:~# start-stop-daemon --start --pidfile /dev/null --startas
> /usr/bin/mandb --oknodo --chuid man --iosched idle -- --no-purge
> Processing manual pages under /usr/share/man...
> Processing manual pages under /usr/share/man/id...
> fopen: Permission denied
> 
> I can execute /usr/bin/mandb as root without problems.
> 
> I attached the output of strace -f.
> 
> Please notice that the system information that reportbug attaches to this bug
> report is not correct. The bug occurs on my server and I wrote the bug on my
> desktop. My server has a fresh stable installation switched to jessie directly
> after installation. Everything is up to date. The man-db version is 2.7.0.2-3.
> 
> I did some complete backup and restore cycles with duplicity before in order 
> to
> stress the backup procedure. But I don't think that this broke some of the 
> file
> attributes. Everything should be in the original state.
> 
> -- System Information:
> Debian Release: jessie/sid
> APT prefers testing
> APT policy: (500, 'testing')
> Architecture: amd64 (x86_64)
> Foreign Architectures: i386
> 
> Kernel: Linux 3.17-1-amd64 (SMP w/2 CPU cores)
> Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> 
> Versions of packages man-db depends on:
> ii bsdmainutils 9.0.6
> ii debconf [debconf-2.0] 1.5.53
> ii dpkg 1.17.21
> ii groff-base 1.22.2-8
> ii libc6 2.19-13
> ii libgdbm3 1.8.3-13+b1
> ii libpipeline1 1.4.0-1
> ii zlib1g 1:1.2.8.dfsg-2
> 
> man-db recommends no packages.
> 
> Versions of packages man-db suggests:
> ii chromium [www-browser] 38.0.2125.101-3
> ii groff 1.22.2-8
> ii iceweasel [www-browser] 31.2.0esr-3
> ii konqueror [www-browser] 4:4.14.2-1
> ii less 458-3
> ii opera [www-browser] 12.16.1860
> ii rekonq [www-browser] 0.9.2-1
> ii w3m [www-browser] 0.5.3-19
> 
> -- debconf information excluded
 

Reply via email to