Your message dated Wed, 01 Nov 2006 15:49:21 -0800 with message-id <[EMAIL PROTECTED]> and subject line Bug#396578: fixed in backupninja 0.9.4-4 has caused the attached Bug report 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 I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message ---Package: backupninja Version: 0.9.4-3 Severity: grave Info: >>>> starting action 15.pgsql (because of --now) Debug: yes Info: Using vserver 'db'. Debug: Examining vserver 'db'. Debug: chown 0 1 2 3 4 5 6 7 8 9 10 11 12 14 25 27 32 33 42 90 99 1000 /vservers/db/backup/postgresql chown: cannot access `1': No such file or directory chown: cannot access `2': No such file or directory chown: cannot access `3': No such file or directory chown: cannot access `4': No such file or directory chown: cannot access `5': No such file or directory chown: cannot access `6': No such file or directory chown: cannot access `7': No such file or directory chown: cannot access `8': No such file or directory chown: cannot access `9': No such file or directory chown: cannot access `10': No such file or directory chown: cannot access `11': No such file or directory chown: cannot access `12': No such file or directory chown: cannot access `14': No such file or directory chown: cannot access `25': No such file or directory chown: cannot access `27': No such file or directory chown: cannot access `32': No such file or directory chown: cannot access `33': No such file or directory chown: cannot access `42': No such file or directory chown: cannot access `90': No such file or directory chown: cannot access `99': No such file or directory chown: cannot access `1000': No such file or directory Debug: chmod 700 /vservers/db/backup/postgresql Debug: /usr/sbin/vserver db exec su - postgres -c "/usr/bin/pg_dumpall | /bin/gzip > /backup/postgresql/db.sql.gz" Warning: /bin/sh: /backup/postgresql/db.sql.gz: Permission denied Looking at the code, I found what was giving that behaviour: if [ $usevserver = yes ]; then pguid=`$VSERVER $vsname exec getent passwd $PGSQLUSER | awk -F: '{print $3}'` else pguid=`getent passwd postgres | awk -F: '{print $3}'` fi So it looks like PGSQLUSER wasnt set in my config and then getent matched all passwd entries, resulting in a wrong "chown $pguid $vroot$backupdir". Then I grep'ed backupninja source and didnt found any mention to PGSQLUSER other than this line at pgsql handler and the Changelog entry for 0.9.4 introducing this new variable. I'm wondering where to set this variable and if theres still a lot of hardcoded postgres user in this handler. -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (500, 'unstable') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/dash Kernel: Linux 2.6.18-1-686 Locale: LANG=fr_FR.UTF-8, LC_CTYPE=UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to fr_FR.UTF-8) Versions of packages backupninja depends on: ii bash 3.1-5 The GNU Bourne Again SHell ii dialog 1.0-20060221-1 Displays user-friendly dialog boxe ii gawk 1:3.1.5.dfsg-4 GNU awk, a pattern scanning and pr ii mawk 1.3.3-11 a pattern scanning and text proces backupninja recommends no packages. -- no debconf information -- intrigeri <[EMAIL PROTECTED]>
--- End Message ---
--- Begin Message ---Source: backupninja Source-Version: 0.9.4-4 We believe that the bug you reported is fixed in the latest version of backupninja, which is due to be installed in the Debian FTP archive: backupninja_0.9.4-4.diff.gz to pool/main/b/backupninja/backupninja_0.9.4-4.diff.gz backupninja_0.9.4-4.dsc to pool/main/b/backupninja/backupninja_0.9.4-4.dsc backupninja_0.9.4-4_all.deb to pool/main/b/backupninja/backupninja_0.9.4-4_all.deb A summary of the changes between this version and the previous one is attached. Thank you for reporting the bug, which will now be closed. If you have further comments please address them to [EMAIL PROTECTED], and the maintainer will reopen the bug report if appropriate. Debian distribution maintenance software pp. Micah Anderson <[EMAIL PROTECTED]> (supplier of updated backupninja package) (This message was generated automatically at their request; if you believe that there is a problem with it please contact the archive administrators by mailing [EMAIL PROTECTED]) -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Format: 1.7 Date: Fri, 13 Oct 2006 18:33:34 -0600 Source: backupninja Binary: backupninja Architecture: source all Version: 0.9.4-4 Distribution: unstable Urgency: high Maintainer: Micah Anderson <[EMAIL PROTECTED]> Changed-By: Micah Anderson <[EMAIL PROTECTED]> Description: backupninja - lightweight, extensible meta-backup system Closes: 395578 395928 396578 396632 Changes: backupninja (0.9.4-4) unstable; urgency=high . * Fix vrootdir bug in sys handler (Closes: #395928) * Fix typo in sys handler that broke vserver handling * Fix for config file permissions handling * Enhance sfdisk error/output handling, now warns when it cannot backup a partition table, and stays quiet when it can (Closes: #396632) * Fix support for configuring PGSQLUSER for real this time, and document it, previously this broke pgsql handling for vservers (Closes: #396578) * Fix rub fsck error, also changed to use internal vserver libraries * Fix missing binary-arch target in debian/rules (Closes: #395578) * Urgency set to high to fix RC bugs Files: b9f25054c077793a0f10a6c8746ce48e 631 admin optional backupninja_0.9.4-4.dsc d9608068b2f889fec500190780b8831f 13169 admin optional backupninja_0.9.4-4.diff.gz b5a5ba555dd9fbb033812b101e5f3cec 73906 admin optional backupninja_0.9.4-4_all.deb -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQFFSSAw9n4qXRzy1ioRAgPuAJ0fj1TMsuAjSI0X0MyRmR/gcshb7QCeJYW5 RpFvVdVZYxCsHC+ijG/ew0Q= =sA1X -----END PGP SIGNATURE-----
--- End Message ---
