[Bug 1375072] [NEW] logrotate for smbd log restarts nmbd instead of smbd
*** This bug is a security vulnerability ***
Public security bug reported:
Marking security because this causes loss of logging information.
1 /var/log/samba/log.smbd {
2 weekly
3 missingok
4 rotate 7
5 postrotate
6 [ ! -f /var/run/samba/nmbd.pid ] || kill -HUP `cat
/var/run/samba/nmbd.pid`
7 endscript
8 compress
9 notifempty
10 }
Please see line 6 - although we are rotating log.smbd,
logrotate is asked to send the HUP signal to the wrong process, nmbd.
In two places, nmbd.pid must be replaced by smbd.pid,
otherwise processes continue to log into a compressed/deleted logfile, causing
logs to get lost.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: samba 2:3.4.7~dfsg-1ubuntu3.15
ProcVersionSignature: Ubuntu 2.6.32-65.131-generic-pae 2.6.32.63+drm33.26
Uname: Linux 2.6.32-65-generic-pae i686
Architecture: i386
Date: Mon Sep 29 02:06:53 2014
ProcEnviron:
PATH=(custom, no user)
LANG=de_DE.UTF-8
SHELL=/bin/bash
SambaServerRegression: No
SourcePackage: samba
** Affects: samba (Ubuntu)
Importance: Undecided
Status: Confirmed
** Tags: apport-bug i386 lucid
** Information type changed from Private Security to Public Security
** Changed in: samba (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to samba in Ubuntu.
https://bugs.launchpad.net/bugs/1375072
Title:
logrotate for smbd log restarts nmbd instead of smbd
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1375072/+subscriptions
--
Ubuntu-server-bugs mailing list
Ubuntu-server-bugs@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1305232] Re: Postfix fails to start, failure to copy certificates
Key is adding -not -xtype l which weeds out stuff that is a symbolic link when dereferenced. This is only true for broken (dangling) symbolic links. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1305232 Title: Postfix fails to start, failure to copy certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1305232/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1305232] [NEW] Postfix fails to start, failure to copy certificates
Public bug reported: Postfix frequently fails to start after security updates to the ca- certificates package because upgrading the latter sometimes leaves dangling symlinks behind. If that happens, the /etc/init.d/postfix script aborts. # handle files in subdirectories (cd $ca_path find . -name '*.pem' -print0 | cpio -0pdL --quiet $dest_dir) 2/dev/null || (log_failure_msg failure copying certificates; exit 1) The usual fix on a high level is dpkg-reconfigure --priority=high ca- certificates; however, I would propose to change the find command as follows: # handle files in subdirectories (cd $ca_path find . -name '*.pem' -not -xtype l -print0 | cpio -0pdL --quiet $dest_dir) 2/dev/null || (log_failure_msg failure copying certificates; exit 1) This would then skip printing broken symbolic links, and prevent cpio from choking on them. ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: postfix 2.9.6-1~12.04.1 ProcVersionSignature: Ubuntu 3.11.0-19.33~precise1-generic 3.11.10.5 Uname: Linux 3.11.0-19-generic i686 NonfreeKernelModules: nvidia ApportVersion: 2.0.1-0ubuntu17.6 Architecture: i386 Date: Wed Apr 9 20:20:17 2014 EcryptfsInUse: Yes MarkForUpload: True ProcEnviron: LANGUAGE=de_DE:de:en_GB:en TERM=xterm PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: postfix UpgradeStatus: Upgraded to precise on 2012-11-01 (523 days ago) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1305232 Title: Postfix fails to start, failure to copy certificates To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1305232/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
How do you make sure there is only one account per init script? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to fetchmail in Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1021699] Re: fetchmail: IDLE - multiple daemons should be started
The limitation is documented, and I have always been considering killing the IDLE option upstream. Some server NOTIFY extension that is not as limited as IDLE is, might help, but I don't know how widespread that is. Else fetchmail would have to undergo internal restructuring and go on wasting sockets. For large POP toasters, you can't use IDLE anyways, on medium-sized, you might run out of file descriptors. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to fetchmail in Ubuntu. https://bugs.launchpad.net/bugs/1021699 Title: fetchmail: IDLE - multiple daemons should be started To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1021699/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1025051] Re: package fetchmail 6.3.21-2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 6
You can safely assume that unless someone deliberately changed the Debian/Ubuntu scripts and left relevant information in the changes file, the bug persists. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to fetchmail in Ubuntu. https://bugs.launchpad.net/bugs/1025051 Title: package fetchmail 6.3.21-2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1025051/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1025051] Re: package fetchmail 6.3.21-2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 6
The resolution is bogus. The installation must be possible regardless of changed configuration. ** Changed in: fetchmail (Ubuntu) Status: Invalid = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to fetchmail in Ubuntu. https://bugs.launchpad.net/bugs/1025051 Title: package fetchmail 6.3.21-2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1025051/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1025051] Re: package fetchmail 6.3.21-2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 6
s/installation/deinstallation/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to fetchmail in Ubuntu. https://bugs.launchpad.net/bugs/1025051 Title: package fetchmail 6.3.21-2 failed to install/upgrade: subprocess installed pre-removal script returned error exit status 6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/fetchmail/+bug/1025051/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 718188] Re: dovecot won't be restarted after failure
ping - this still hurts on natty. Please fix! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dovecot in Ubuntu. https://bugs.launchpad.net/bugs/718188 Title: dovecot won't be restarted after failure To manage notifications about this bug go to: https://bugs.launchpad.net/dovecot/+bug/718188/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 1026261] Re: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep
Fix confirmed for precise; not tested on the others. Can this be fixed for natty please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1026261 Title: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1026261] Re: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1026261 Title: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1026261] [NEW] [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep
Public bug reported: Since the (overdue) update from maverick to natty, my Postfix no longer recognizes the certificates. Apparently the reason is that the smtp_tls_CApath, which is set to /etc/ssl/certs, is improperly copied into the chroot area, namely to /var/spool/postfix/etc/ssl/certs/etc/ssl/certs, rather than /var/spool/postfix/etc/ssl/certs where it belongs. In /etc/postfix/main.cf, I have smtp_tls_CApath = /etc/ssl/certs and smtp runs chrooted (from looking at /etc/postfix/master.cf). The certificate bundle appears to be setup properly, only the .pem/.0 files from the directory seem to be affected. Workaround: sudo postconf -e smtp_tls_CAfile=/etc/ssl/certs/ca-certificates.crt sudo service postfix restart From looking at what I get when running sh -x postfix, it would seem that + find /etc/ssl/certs -print0 + cpio -0pdL /var/spool/postfix/etc/ssl/certs.NEW causes the duplication of paths - the cpio input file list is fully concatenated to the cpio destination path. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: postfix 2.8.5-2~build0.11.04 ProcVersionSignature: Ubuntu 2.6.38-15.61-generic-pae 2.6.38.8 Uname: Linux 2.6.38-15-generic-pae i686 NonfreeKernelModules: nvidia Architecture: i386 Date: Wed Jul 18 19:30:51 2012 EcryptfsInUse: Yes ProcEnviron: LANGUAGE=de_DE:de:en_GB:en PATH=(custom, no user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: postfix UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 natty regression-release -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1026261 Title: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1026261] Re: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep
** Attachment added: result from running sh -x /etc/init.d/postfix start https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+attachment/3227425/+files/postfix-log.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1026261 Title: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1026261] Re: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep
** Attachment added: result from find /var/spool/postfix/etc to show actual directory layout https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+attachment/3227428/+files/var-spool-postfix-etc.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/1026261 Title: [regression] mail stalls; postfix chroot setup nests /etc/ssl/certs to deep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/1026261/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 998766] [NEW] package samba 2:3.5.8~dfsg-1ubuntu2.5 failed to install/upgrade: ErrorMessage: Unterprozess neues post-removal-Skript gab den Fehlerwert 2 zurück
Public bug reported: This happened during an upgrade with sudo do-release-upgrade from natty (11.04) to oneiric (11.10) which is supposed to be an intermediate step on the way to 12.04. Note that the questions asked by apport about the samba setup (which clients fail to connect, what my setup is) are entirely besides the point -- I assume samba to be a dependency that other packages rely on. ProblemType: Package DistroRelease: Ubuntu 11.04 Package: samba 2:3.5.8~dfsg-1ubuntu2.5 ProcVersionSignature: Ubuntu 2.6.38-15.59-generic 2.6.38.8 Uname: Linux 2.6.38-15-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Sun May 13 16:16:38 2012 ErrorMessage: ErrorMessage: Unterprozess neues post-removal-Skript gab den Fehlerwert 2 zurück OtherFailedConnect: Yes SambaServerRegression: Yes SmbConfIncluded: No SourcePackage: samba Title: package samba 2:3.5.8~dfsg-1ubuntu2.5 failed to install/upgrade: ErrorMessage: Unterprozess neues post-removal-Skript gab den Fehlerwert 2 zurück UpgradeStatus: Upgraded to natty on 2012-05-13 (0 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package natty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/998766 Title: package samba 2:3.5.8~dfsg-1ubuntu2.5 failed to install/upgrade: ErrorMessage: Unterprozess neues post-removal-Skript gab den Fehlerwert 2 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/998766/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 998766] Re: package samba 2:3.5.8~dfsg-1ubuntu2.5 failed to install/upgrade: ErrorMessage: Unterprozess neues post-removal-Skript gab den Fehlerwert 2 zurück
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in Ubuntu. https://bugs.launchpad.net/bugs/998766 Title: package samba 2:3.5.8~dfsg-1ubuntu2.5 failed to install/upgrade: ErrorMessage: Unterprozess neues post-removal-Skript gab den Fehlerwert 2 zurück To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/998766/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 807153] Re: DNSSEC-enabled named sometimes does not die on service bind9 stop
Am 02.05.2012 18:46, schrieb Ben Bird: I have the same scenario of IPv6 + bind9 + dnssec. b-coleman's suspicion that this is related to debian bug# 578052 seems plausible. I upgraded my affected machine to Precise (12.04), and the problem has stopped. The problem isn't with the init script as in the Debian bug, but instead with bind9 itself, which won't die. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: DNSSEC-enabled named sometimes does not die on service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777855] Re: resolver failures without even sending queries, break Postfix
So what's the state of the fix for the earlier affected releases, esp. LTS servers? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777855 Title: resolver failures without even sending queries, break Postfix To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/777855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 777855] Re: resolver failures without even sending queries, break Postfix
Am 06.08.2011 17:05, schrieb Clint Byrum: I think we can also close the task on Postfix, since this is a glibc issue, unless there is something we can do to postfix to fix this. Postfix is one of the few software packages whose default configuration (in newer Postfix versions) triggers this bug. If you choose to fix glibc through SRUs, then you can, of course, close the Postfix relation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777855 Title: resolver failures without even sending queries, break Postfix To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/777855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777855] Re: resolver failures without even sending queries, break Postfix
** Changed in: eglibc (Ubuntu Natty) Status: New = Confirmed ** Changed in: postfix (Ubuntu Natty) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777855 Title: resolver failures without even sending queries, break Postfix To manage notifications about this bug go to: https://bugs.launchpad.net/glibc/+bug/777855/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 807153] Re: named does not shut down after service bind9 stop
Marked Confirmed ** Changed in: bind9 (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: named does not shut down after service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 807153] Re: named does not shut down after service bind9 stop
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bind9 in Ubuntu. https://bugs.launchpad.net/bugs/807153 Title: named does not shut down after service bind9 stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/807153/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 807153] [NEW] named does not shut down after service bind9 stop
Public bug reported: I am running the standard natty BIND9 package in an IPv6- and DNSSEC- enabled configuration as a resolver. The zones are unaltered. After service bind9 stop (or equivalently service bind9 restart), named receives and logs the control command, but remains running. I have to use SIGKILL to get rid of it. I already had to do that during the latest security upgrade. Tagging regression-update. lsof reports: COMMAND PID USER FD TYPE DEVICE SIZE/OFFNODE NAME named 25405 bind cwdDIR 252,1 4096 2388192 /var/cache/bind named 25405 bind rtdDIR 252,1 4096 2 / named 25405 bind txtREG 252,1 522128 2037772 /usr/sbin/named named 25405 bind memREG 252,151728 2019878 /lib/x86_64-linux-gnu/libnss_files-2.13.so named 25405 bind memREG 252,147680 2019885 /lib/x86_64-linux-gnu/libnss_nis-2.13.so named 25405 bind memREG 252,197248 2019875 /lib/x86_64-linux-gnu/libnsl-2.13.so named 25405 bind memREG 252,135712 2019876 /lib/x86_64-linux-gnu/libnss_compat-2.13.so named 25405 bind memREG 252,114280 2019505 /lib/x86_64-linux-gnu/libgpg-error.so.0.8.0 named 25405 bind memREG 252,167856 2152536 /usr/lib/x86_64-linux-gnu/libtasn1.so.3.1.9 named 25405 bind memREG 252,1 543104 2019851 /lib/x86_64-linux-gnu/libm-2.13.so named 25405 bind memREG 252,1 499320 2019792 /lib/x86_64-linux-gnu/libgcrypt.so.11.6.0 named 25405 bind memREG 252,1 659656 2152547 /usr/lib/x86_64-linux-gnu/libgnutls.so.26.14.12 named 25405 bind memREG 252,1 105168 2037664 /usr/lib/libsasl2.so.2.0.23 named 25405 bind memREG 252,196816 2019516 /lib/x86_64-linux-gnu/libz.so.1.2.3.4 named 25405 bind memREG 252,1 101192 2019889 /lib/x86_64-linux-gnu/libresolv-2.13.so named 25405 bind memREG 252,110160 2019843 /lib/x86_64-linux-gnu/libkeyutils.so.1.3 named 25405 bind memREG 252,114696 2019849 /lib/x86_64-linux-gnu/libdl-2.13.so named 25405 bind memREG 252,131104 2152677 /usr/lib/x86_64-linux-gnu/libkrb5support.so.0.1 named 25405 bind memREG 252,114544 2019670 /lib/x86_64-linux-gnu/libcom_err.so.2.1 named 25405 bind memREG 252,1 158080 2150312 /usr/lib/x86_64-linux-gnu/libk5crypto.so.3.1 named 25405 bind memREG 252,1 803128 2152585 /usr/lib/x86_64-linux-gnu/libkrb5.so.3.3 named 25405 bind memREG 252,1 229688 2036171 /usr/lib/libGeoIP.so.1.4.7 named 25405 bind memREG 252,1 1638120 2019728 /lib/x86_64-linux-gnu/libc-2.13.so named 25405 bind memREG 252,1 1388664 2039673 /usr/lib/libxml2.so.2.7.8 named 25405 bind memREG 252,1 140254 2019888 /lib/x86_64-linux-gnu/libpthread-2.13.so named 25405 bind memREG 252,118832 2020006 /lib/libcap.so.2.20 named 25405 bind memREG 252,155504 490901 /usr/lib/liblber-2.4.so.2.5.6 named 25405 bind memREG 252,1 298304 490678 /usr/lib/libldap_r-2.4.so.2.5.6 named 25405 bind memREG 252,1 1494392 2151244 /usr/lib/x86_64-linux-gnu/libdb-4.8.so named 25405 bind memREG 252,1 343392 2037182 /usr/lib/libisc.so.62.1.1 named 25405 bind memREG 252,130672 2038203 /usr/lib/libisccc.so.60.0.0 named 25405 bind memREG 252,1 125272 2038571 /usr/lib/libisccfg.so.62.0.0 named 25405 bind memREG 252,146880 2038897 /usr/lib/libbind9.so.60.0.4 named 25405 bind memREG 252,1 1620736 2019544 /lib/libcrypto.so.0.9.8 named 25405 bind memREG 252,1 217816 2151205 /usr/lib/x86_64-linux-gnu/libgssapi_krb5.so.2.2 named 25405 bind memREG 252,1 1542624 2038650 /usr/lib/libdns.so.69.1.2 named 25405 bind memREG 252,171584 2038578 /usr/lib/liblwres.so.60.0.1 named 25405 bind memREG 252,1 141088 2019706 /lib/x86_64-linux-gnu/ld-2.13.so named 25405 bind0u CHR1,3 0t06437 /dev/null named 25405 bind1u CHR1,3 0t06437 /dev/null named 25405 bind2u CHR1,3 0t06437 /dev/null named 25405 bind3w FIFO0,8 0t0 6115524 pipe named 25405 bind4u unix 0x880056944340 0t0 6115539 socket named 25405 bind5u CHR1,3 0t06437 /dev/null named 25405 bind6r FIFO0,8 0t0 6115035 pipe named 25405 bind8w FIFO0,8 0t0 6115035 pipe named 25405 bind9u
[Bug 777356] Re: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors
Guys, can we please stop distracting with lame excuses for not going for bugfix releases, or backports of another feature release? This particular regression was already fixed by the upstream maintainers in a particular bugfix-only release series of Postfix (2.7.1 is 2.7.0 + fixes), so any any further discussion is a waste of time. Any breaking- out of particular fixes to keep SRU policies not only misses further fixes that have been tested and released by the upstream, but also entails the risk of breaking the patched version. Let's get 2.7.3 into -proposed, shout for testers and see if regression- proposed bugs crop up, and re-release through -updates if nothing bad happens. I understand that few packages qualify for release-updates, but I know how strict Wietse is about changes to a .0 release. And it's certainly not the user's fault that ancient versions got picked up in the release rolling process - these, too, need care. And in particular, regression fixing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777356 Title: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777356] Re: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors
make that 2.7.4. Admittedly even 2.7.1 was past the lucid release, but the upstream has fixed this regression one full year and four days ago. Can we now start the fixing? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777356 Title: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 777356] Re: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors
Am 16.05.2011 20:44, schrieb Chuck Short: We could backport this fix, however as a rule we dont update package in release through the normal channels. However this can be requested as a backport as well. Please see: ironyGreat rules if the upstream release series is bugfixes-only./irony Quite unsensible IMO. Seriously, what good is cherrypicking fixes if the backport is less tested than the upstream bugfix patches? If the Postfix releases were to bring features, I'd understand that, but for Postfix and GCC and similar packages where the point-releases are regression-only or bugfix-only patches, a backport is less tested, thus more dangerous, than just reviewing the point-release patch. Anyways, I don't care how Ubuntu will choose to fix this regression, but I do care that it happens soon. -- Matthias Andree -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777356 Title: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777868] [NEW] Postfix smtp can no longer resolve localhost - regression from maverick.
Public bug reported: Binary package hint: postfix I have a particular Postfix relay configuration where I need to forward SMTP to an SSH tunnel, and configure a relayhost_maps (sender_dependent actually) as [localhost]:12345. This worked in maverick, but fails in natty. The new Postfix 2.8 release strips RES_DEFNAMES from _res.options (the resolver flags) by default, which triggers a resolver bug reported separately as Launchpad Bug #777855. Note that this is not a Postfix bug, but a bug in eglibc - I am filing this as Postfix bug to document the issue and for possible workarounds should an eglibc resolution not be viable. A possible workaround, but dangerous, is to tweak Postfix's resolver flags as in http://marc.info/?l=postfix-usersm=130459442830727w=2 by setting smtp_dns_resolver_options=res_defnames, but that causes false resolver results for some. Please see the entire thread at http://marc.info/?t=13045616412r=1w=2 for a discussion. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: postfix 2.8.2-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-9.43-generic 2.6.38.4 Uname: Linux 2.6.38-9-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Thu May 5 16:04:14 2011 ProcEnviron: LANGUAGE=de:en PATH=(custom, no user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: postfix UpgradeStatus: Upgraded to natty on 2011-05-02 (3 days ago) ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug natty regression-release -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777868 Title: Postfix smtp can no longer resolve localhost - regression from maverick. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777868] Re: Postfix smtp can no longer resolve localhost - regression from maverick.
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777868 Title: Postfix smtp can no longer resolve localhost - regression from maverick. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777868] Re: Postfix smtp can no longer resolve localhost - regression from maverick.
No improvement in 2.8.2-1ubuntu2 from -updates, and with a fundamentally different cause, so removing duplicate mark. ** This bug is no longer a duplicate of bug 764096 DNS hostname lookups fail in chroot after natty upgrade -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777868 Title: Postfix smtp can no longer resolve localhost - regression from maverick. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777868] Re: Postfix smtp can no longer resolve localhost - regression from maverick.
Additional remark: Bug #764096 is about an incomplete chroot setup caused by the start script. To differentially diagnose this, I had ruled a broken chroot setup out in my testing by forcing smtp(8) outside the chroot per master.cf. This bug is fundamentally a resolver bug, exhibited through a change in Postfix's default policy which flags to pass to/strip from res_search(). Arguably I should be using 127.0.0.1 or ::1 instead of localhost (suggested by Victor Duchovni on postfix-users) to skip the DNS indirection, but localhost has been working well since Ubuntu 9.10 or so, so I'd taken the time to notify Ubuntu in addition to the upstream. I see this bug as a tracking bug for if and only if you want to provide a workaround in Postfix (as suggested initially) while Bug #777855 is still unfixed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777868 Title: Postfix smtp can no longer resolve localhost - regression from maverick. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777033] [NEW] installation lacks RELEASE_NOTES-2.6 documentation file
Public bug reported: Binary package hint: postfix /usr/share/doc/postfix/RELEASE_NOTES.gz references a RELEASE_NOTES-2.6 documentation file that isn't installed, neither as part of postfix, nor postfix-doc. Please add this file. ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: postfix 2.7.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 2.6.32-31.61-generic-pae 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-generic-pae i686 Architecture: i386 Date: Wed May 4 13:26:31 2011 ProcEnviron: LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: postfix ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777033 Title: installation lacks RELEASE_NOTES-2.6 documentation file -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777033] Re: installation lacks RELEASE_NOTES-2.6 documentation file
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777033 Title: installation lacks RELEASE_NOTES-2.6 documentation file -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777356] [NEW] [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors
Public bug reported: Binary package hint: postfix I've been bitten by a Postfix SMTP/LMTP implementation defect that has been fixed in one of the upstream patch-level releases 2.7.X. Basically Postfix sends XFORWARD PORT=unknown ... to amavsid via LMTP. Amavisd later returns the same attribute to smtpd, which complains noisily in the log. Please upgrade the Postfix package to 2.7.3 to collect all bug fixes. If that runs counter to your policy and you rather want each bug reported separately to justify wasting developer time, you can extract the fix from postfix-2.7-patch01.gz, available from all Postfix download mirrors, for instance, http://www.artfiles.org/postfix.org/postfix- release/official/postfix-2.7-patch01.gz Details on the problem: http://news.gmane.org/find- root.php?message_id=%3c4DC190BC.6020805%40gmx.de%3e ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: postfix 2.7.0-1ubuntu0.1 ProcVersionSignature: Ubuntu 2.6.32-31.61-generic-pae 2.6.32.32+drm33.14 Uname: Linux 2.6.32-31-generic-pae i686 Architecture: i386 Date: Wed May 4 20:56:47 2011 ProcEnviron: PATH=(custom, user) LANG=de_DE.UTF-8 SHELL=/bin/bash SourcePackage: postfix ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid regression-release -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777356 Title: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 777356] Re: [fixed upstream] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors
** Summary changed: - [fixed upstream] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors + [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors ** Tags added: regression ** Tags added: regression-release ** Tags removed: regression -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to postfix in Ubuntu. https://bugs.launchpad.net/bugs/777356 Title: [fixed upstream, regression] Postfix smtp does not skip unknown XFORWARD attributes, causing SMTP syntax errors -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 576633] [NEW] package bacula-director-pgsql 5.0.1-1ubuntu1 failed to install/upgrade:
Public bug reported: Binary package hint: bacula This happens on regular upgrade (from Desktop) from Ubuntu 9.10 to 10.04. ProblemType: Package DistroRelease: Ubuntu 10.04 Package: bacula-director-pgsql 5.0.1-1ubuntu1 ProcVersionSignature: Ubuntu 2.6.31-21.59-generic Uname: Linux 2.6.31-21-generic x86_64 NonfreeKernelModules: fglrx Architecture: amd64 Date: Thu May 6 22:43:55 2010 ErrorMessage: ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück SourcePackage: bacula Title: package bacula-director-pgsql 5.0.1-1ubuntu1 failed to install/upgrade: ** Affects: bacula (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- package bacula-director-pgsql 5.0.1-1ubuntu1 failed to install/upgrade: https://bugs.launchpad.net/bugs/576633 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 576633] Re: package bacula-director-pgsql 5.0.1-1ubuntu1 failed to install/upgrade:
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/47960248/Dependencies.txt ** Attachment added: VarLogDistupgradeAptlog.gz http://launchpadlibrarian.net/47960249/VarLogDistupgradeAptlog.gz ** Attachment added: VarLogDistupgradeApttermlog.gz http://launchpadlibrarian.net/47960250/VarLogDistupgradeApttermlog.gz ** Attachment added: VarLogDistupgradeLspcitxt.gz http://launchpadlibrarian.net/47960251/VarLogDistupgradeLspcitxt.gz ** Attachment added: VarLogDistupgradeMainlog.gz http://launchpadlibrarian.net/47960252/VarLogDistupgradeMainlog.gz ** Attachment added: VarLogDistupgradeSystemstatetargz.gz http://launchpadlibrarian.net/47960253/VarLogDistupgradeSystemstatetargz.gz ** Attachment added: VarLogDistupgradeTermlog.gz http://launchpadlibrarian.net/47960254/VarLogDistupgradeTermlog.gz -- package bacula-director-pgsql 5.0.1-1ubuntu1 failed to install/upgrade: https://bugs.launchpad.net/bugs/576633 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
Re: [Bug 165184] Re: amavisd-new + spamassassin: cronjob spams root user
That's not a complete solution; since the job keeps complaining if bayes is disabled. -- amavisd-new + spamassassin: cronjob spams root user https://bugs.launchpad.net/bugs/165184 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 165184] Re: amavisd-new + spamassassin: cronjob spams root user
So, I see three options to fix this, which one to use isn't my call to decide: 1. patch spamassassin package, to make sure sa-learn doesn't complain if use_bayes is set to 0 2. patch amavisd-new package, to not run sa-learn if use_bayes is set to 0. There should be a way to query SpamAssassin's configuration from a script - if there is, just use it. 3. add /etc/default/* parameter to disable spamassassin's Bayes filtering, which would require subsequent changes to amavisd-new (don't run sa-learn - but beware of remaining cleanups when this option is set to 0 after some use) and spamassassin (to translate the /etc/default/* to use_bayes 0). I personally prefer #2 as the cleanest solution: amavisd-new owns the offending cronjob, so amavisd-new is the package that also has to deal with undesired side effects. -- amavisd-new + spamassassin: cronjob spams root user https://bugs.launchpad.net/bugs/165184 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to amavisd-new in ubuntu. -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
