[Bug 1158141] Re: apache2 forward proxy socket read error
Same problem here. Works fine with 1.9.0+svn250-3 Broken with 1.9.0+svn250-5 (Package for vivid, installed on a trusty) Btw, Robie, if you snub one user, in reality you also snub hundreds of others who find his bug report by googling for the same symptoms, so please be a bit more helpful. It reflects badly on the community. ... and if it is not the same problem, maybe the real bug is that the error message is just so goddamn vague. Even with -v (verbose) there was not more detail than "error: Socket read error". -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1158141 Title: apache2 forward proxy socket read error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1158141/+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 1158141] Re: apache2 forward proxy socket read error
Found it. Actually it was due to both a pecularity in the proxy server I wanted to get through, and a bug in how proxytunnel sets SNI. It seems that our proxy server ignores SNI in SSLv3, but considers it in TLSv1. And proxytunnel sets the wrong SNI. proxytunnel ---> proxy1 (the one I want to get through) ---> proxy2 (my Apache) ---> ssh. After sending CONNECT proxy2:443 to the proxy1 (in order to be connected through to proxy2), it starts negotiating the SSL session with proxy2. It would be logical to base that negotiation on the host name of proxy2. However, proxytunnel mistakenly includes proxy1 as the SNI in that negotiation. With the result that the "evil" proxy1, which snoops at the initial part of the negotiation (which is still clear-text...), sees that SNI, then ignores the host that it got in the CONNECT header, and instead attempts to connect to the host that it saw in the SNI, which would be itself (proxy1 instead of proxy2). In my case, just dropping the SNI setting code in stream_enable_ssl in pstream.c fixed the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to apache2 in Ubuntu. https://bugs.launchpad.net/bugs/1158141 Title: apache2 forward proxy socket read error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1158141/+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 1394764] [NEW] package slapd 2.4.21-0ubuntu5.6 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
Public bug reported: The problem occured while upgrading from 10.04 to 12.04 ProblemType: Package DistroRelease: Ubuntu 10.04 Package: slapd 2.4.21-0ubuntu5.6 ProcVersionSignature: Ubuntu 3.0.0-32.51~lucid1-server 3.0.69 Uname: Linux 3.0.0-32-server x86_64 Architecture: amd64 Date: Thu Nov 20 22:44:26 2014 ErrorMessage: ErrorMessage: subprocess new pre-installation script returned error exit status 1 SourcePackage: openldap Title: package slapd 2.4.21-0ubuntu5.6 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 ** Affects: openldap (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package lucid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1394764 Title: package slapd 2.4.21-0ubuntu5.6 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1394764/+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 1394764] Re: package slapd 2.4.21-0ubuntu5.6 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1
I'd gladly try to manually install this cyrus-sasl2 2.1.25.dfsg1-3ubuntu0.1 , but where can I find it? Any other idea how to look for this configuration issue? Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap in Ubuntu. https://bugs.launchpad.net/bugs/1394764 Title: package slapd 2.4.21-0ubuntu5.6 failed to install/upgrade: ErrorMessage: subprocess new pre-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1394764/+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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
Since I disabled smbpasswd-migrate, I now get the following in my auth.log Oct 15 09:45:28 crmm vsftpd: PAM unable to dlopen(/lib/security/pam_smbpass.so): libgpg-error.so.0: failed to map segment from shared object: Cannot allocate memory Oct 15 09:45:28 crmm vsftpd: PAM adding faulty module: /lib/security/pam_smbpass.so Despite these messages, login of both anonymous and local users succeeds however. Remove the package libpam-smbpass altogether makes the messages disappear, however we need libpam-smbpass for other reasons. Any ideas? Interestingly enough, the message also goes away when disabling blowfish authentication while still keeping libpam-smbpass around. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/723603/+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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
Clarification: smbpasswd-migrate not winbind After disabling this in /usr/share/pam-configs/smbpasswd-migrate, it does indeed work now. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/723603/+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 375569] Re: gnome-screensaver failure - can't access samba password database - not running as root
The thing is, this isn't really a bug at all. gnome-screensaver is working exactly as it's supposed to, as is pam_smbpass; it just logs (at severity LOG_DEBUG) a notice that the smbpasswd database is not being updated, because the process isn't running as root. The issue is that this is being called from each executable that uses pam, including those that don't have the right to change samba passwords, such as squid_auth, or vsftpd. The effect is not only log spam, but also authentication failures (in case of vsftpd: bug #723603). Solution: Remove the following lines from /usr/share/pam-configs/smbpasswd-migrate and re-run pam-auth-update : Auth-Initial: optionalpam_smbpass.so migrate Auth-Final: optionalpam_smbpass.so migrate -- 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/375569 Title: gnome-screensaver failure - can't access samba password database - not running as root To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/375569/+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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
*** This bug is a duplicate of bug 831907 *** https://bugs.launchpad.net/bugs/831907 This bug was (accidentally?) marked as a duplicate of an unrelated bug (certificates, whereas this one is about anonymous ftp). How can we undo this? Thanks -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/723603/+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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
Re-tested on Ubuntu 10.04.2 LTS, vsftpd 2.2.2-3ubuntu6.2 == Bug still present ** Changed in: vsftpd (Ubuntu) Status: Expired = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/723603/+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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
The problem with pam_shells and local_enable+anonymous_enable occurs when starting vsftpd via 'service vsftpd start'. The only reason why I mentioned starting it manually at all was because that is what I did to more precisely trace the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable -- 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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
** Attachment added: auth.log https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/723603/+attachment/1872452/+files/auth.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable -- 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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
** Attachment added: vsftpd.log https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/723603/+attachment/1872453/+files/vsftpd.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable -- 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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
It seems to complain about pam_shells. And indeed, after commenting this out, the problem goes away, even with both anonymous_enable and local_enable set to YES. The problem becomes different when starting vsftpd from the command line instead of using service vsftpd start: # ftp localhost Connected to localhost.localdomain. 220 (vsFTPd 2.2.2) Name (localhost:root): aknaff 331 Please specify the password. Password: ltdb: tdb(/var/lib/samba/group_mapping.ldb): tdb_mmap failed for size 77824 (Cannot allocate memory) Login failed. Another weird thing is that the process spawned by vsftpd.log per user has the following in /proc/pid/limits Max address space 104857600104857600 bytes The master process doesn't, it has: Max address space unlimitedunlimited bytes -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable -- 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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
** Attachment added: vsftpd.conf file https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/723603/+attachment/1869629/+files/vsftpd.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable -- 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 723603] [NEW] vsftpd no longer supports both anonymous_enable and local_enable
Public bug reported: Binary package hint: vsftpd In 10.04, it is no longer possible to set up vsftpd in such a way that it allows both anonymous and identified logins. If you set the following in your vsftpd.conf, local users cannot login. In older versions, this was still possible. anonymous_enable=YES local_enable=YES - # lsb_release -rd Description:Ubuntu 10.04.2 LTS Release:10.04 # apt-cache policy vsftpd vsftpd: Installed: 2.2.2-3ubuntu6 Candidate: 2.2.2-3ubuntu6 Version table: *** 2.2.2-3ubuntu6 0 500 http://lu.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status Expected: - both identified (aknaff) and anonymous (ftp) users should log in What happened: - identified user (aknaff) could not log in. Setting anonymous_enable to YES enables identified login (aknaff), but (obviously) disables anonymous (ftp) login ** Affects: vsftpd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable -- 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 723603] Re: vsftpd no longer supports both anonymous_enable and local_enable
Indeed. Sorry for the confusion -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in ubuntu. https://bugs.launchpad.net/bugs/723603 Title: vsftpd no longer supports both anonymous_enable and local_enable -- 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 685590] Re: dovecot 1.2.9 not compatible with thunderbird
Ooops... actually, what seemed to have happened is that after adding lucid-proposed to /etc/apt/sources.list, I had accidentally left our own private repository in as well (lll), so all I did was just re-adding our own private version... Sorry for that confusion. That being said, is there an easy way to: 1) apt-get'ing something from a _specific_ repository or 2) find out where a given installed package came from -- 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/685590 Title: dovecot 1.2.9 not compatible with thunderbird -- 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 685590] Re: dovecot 1.2.9 not compatible with thunderbird
I ended up manually de-installing our locally made dovecot package (also numbered 1.2.12), and then everything worked fine. The version from proposed works as expected, thanks. -- 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/685590 Title: dovecot 1.2.9 not compatible with thunderbird -- 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 687535] [NEW] upstart loses track of ssh daemon after reload ssh
Public bug reported: When sshd gets a signal 1 for reload, it forks a new process and ditches the old. This causes upstart to believe that ssh has crashed, and loses track of it. A second reload (or any other initctl operation on ssh) will thus say: reload: Unknown instance: There would be 2 ways to fix this: 1. Don't have ssh fork on relod, but keep the same pid 2. Use a different mechanism in upstart to keep track of ssh. Maybe a pid file? Just tracking children of the exited ssh won't work, or it might accidentally track a particular session rather than the master, if somebody just happens to log in close to reload time. # lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 # dpkg -l openssh-server | cat Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ NameVersion Description +++-===-==-= ii openssh-server 1:5.3p1-3ubuntu4 secure shell (SSH) server, for secure access from remote machines # dpkg -l upstart Desired=Unknown/Install/Remove/Purge/Hold | Status=Not/Inst/Cfg-files/Unpacked/Failed-cfg/Half-inst/trig-aWait/Trig-pend |/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad) ||/ Name VersionDescription +++-==-==- ii upstart0.6.5-7event-based init daemon ** Affects: openssh (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh -- 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 687535] Re: upstart loses track of ssh daemon after reload ssh
So why bother having an upstart or init at all, and not start and stop everything manually? Similar issue exists with squid (bug 573853) Upstart is a nice concept, and really improved boot times. It would even be better if it was more reliable. These glitches break web administration tools which call service xxx start/stop/reload to do their thing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh -- 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 685590] Re: dovecot 1.2.9 not compatible with thunderbird
** Changed in: dovecot (Ubuntu) Status: Incomplete = Confirmed -- 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/685590 Title: dovecot 1.2.9 not compatible with thunderbird -- 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 685201] Re: shutdown_lifetime setting behavior does not match doc
** Changed in: squid (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. https://bugs.launchpad.net/bugs/685201 Title: shutdown_lifetime setting behavior does not match doc -- 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 687535] Re: upstart loses track of ssh daemon after reload ssh
Alain, I understand your frustration. think a little more serious than Low, Thanks for your insight. as existence of a workaround only barely mitigates the impact of this. Just a note about this workaround: kill -9 `pidof sshd` will saw off the branch on which you're sitting if you happen to manage the system remotely. A safer workaround would be kill -9 `cat /var/run/sshd.pid` The problem, I think, is that we're using expect fork I think what's definitely needed is a way to make upstart track processes by pidfile. and I'm not sure why, when sshd has -D Indeed, that seems to work (just tested it). So, why does ssh fork on reload in the case without -D, if it works without this fork with -D? I'm not going to mark it Invalid yet though. Why do you think this bug should be marked invalid (/etc/init/ssh.conf is part of the openssh-server .deb)? Especially after basically agreeing with me... In general, in Ubuntu, triagers are far too quick to mark bugs as invalid, leading to situations where real problems still aren't fixed in the next release, or problems in LTS releases go unfixed for over a year. that we should always track the children as the main process. This is tricky for processes such as ssh, as upstart might end up accidentally tracking one particular session, rather than the master. Just imagine if a user logs in at exactly the moment where the admin issues a reload ssh. Init would then not know which child to track (new master, or the session of the user who just logged in). And in the case of squid, upstart would not even know that something is amiss as here the issue is about some intermediate process _not_ exiting when it should, so upstart would not know that something is amiss until after the first reload (... causing that first reload to be ignored...). A safer alternative would be to optionally track by pidfile (which could be monitored by inotify, and re-read after a child exits). Of course, existence of pid listed in pidfile should be verified by sending it a -0 signal, so that upstart wouldn't get confused by stale pid files. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in ubuntu. https://bugs.launchpad.net/bugs/687535 Title: upstart loses track of ssh daemon after reload ssh -- 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 685590] Re: dovecot 1.2.9 not compatible with thunderbird
Yes, it is reproducible: just connect to dovecot with thunderbird imap. We use Maildir. The bug occurs even for new users. In case I wasn't clear: this is a show stopper bug, which prevents the most popular client from connecting to dovecot, and as such is of high importance. Well, people could still use horde webmail, but it'd be rather inconvenient. -- 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/685590 Title: dovecot 1.2.9 not compatible with thunderbird -- 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 685201] Re: shutdown_lifetime setting behavior does not match doc
2.7.STABLE7-1ubuntu12 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. https://bugs.launchpad.net/bugs/685201 Title: shutdown_lifetime setting behavior does not match doc -- 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 685590] [NEW] dovecot 1.2.9 not compatible with thunderbird
Public bug reported: Lucid (LTS) ships with dovecot 1.2.9 by default. When a user attempts to log in to dovecot using thunderbird, the following is logged, and thunderbird doesn't manage to get folder contents: Dec 5 19:26:43 hal dovecot: imap-login: Login: user=aknaff, method=PLAIN, rip=87.240.204.33, lip=158.64.72.230, TLS Dec 5 19:26:43 hal dovecot: IMAP(aknaff): Panic: file cmd-list.c: line 242 (ns_get_listed_prefix): assertion failed: (match == IMAP_MATCH_YES) Dec 5 19:26:43 hal dovecot: IMAP(aknaff): Raw backtrace: /usr/lib/dovecot/imap(+0xaeb8a) [0x7f4447a8bb8a] - /usr/lib/dovecot/imap(+0xaebf7) [0x7f4447a8bbf7] - /usr/lib/dovecot/imap(+0xae238) [0x7f4447a8b238] - /usr/lib/dovecot/imap(+0x249f0) [0x7f4447a019f0] - /usr/lib/dovecot/imap(+0x24c7d) [0x7f4447a01c7d] - /usr/lib/dovecot/imap(cmd_list_full+0x4c6) [0x7f4447a029f6] - /usr/lib/dovecot/imap(+0x28fad) [0x7f4447a05fad] - /usr/lib/dovecot/imap(+0x2908d) [0x7f4447a0608d] - /usr/lib/dovecot/imap(client_handle_input+0x135) [0x7f4447a062c5] - /usr/lib/dovecot/imap(client_input+0x5f) [0x7f4447a06baf] - /usr/lib/dovecot/imap(io_loop_handler_run+0xbd) [0x7f4447a9408d] - /usr/lib/dovecot/imap(io_loop_run+0x18) [0x7f4447a93478] - /usr/lib/dovecot/imap(main+0x58e) [0x7f4447a0ec5e] - /lib/libc.so.6(__libc_start_main+0xfd) [0x7f444704ac4d] - /usr/lib/dovecot/imap(+0x21979) [0x7f44479fe979] Dec 5 19:26:43 hal dovecot: dovecot: child 28850 (imap) killed with signal 6 (core dumps disabled) Reverting back to 1.1.11 (from previous version) makes it work again. Rolling forward to versions more recent than 1.2.9 (from maverick or natty) doesn't work due to dependencies. The dovecot community seems to have known about this bug since December 2009, and apparently have a fix. Wouldn't it be appropriate to make a version with this fix in available for lucid, which is an LTS version, and not supposed to ship with such show-stopper bugs (makes dovecot basically unusable, as a majority of users have thunderbird). Thanks. http://www.dovecot.org/list/dovecot/2009-December/045522.html ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New -- 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/685590 Title: dovecot 1.2.9 not compatible with thunderbird -- 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 573853] Re: Cannot control squid Unknown instance
It seems that what is happening is that squid forks twice to demonize, but the middle process forgets to exit, and keeps hanging around. # ps auxww | fgrep squid root 2593 0.0 0.1 31792 4884 ?S01:27 0:03 /usr/bin/perl /usr/sbin/squid-prefetch root 14719 0.0 0.0 24796 1076 ?Ss 14:26 0:00 /usr/sbin/squid proxy14721 2.2 0.2 40212 10352 ?Sl 14:26 0:00 (squid) root 14753 0.0 0.0 7576 820 pts/0S+ 14:26 0:00 fgrep squid # cat /var/run/squid.pid 14721 Here, 14719 is the son of the process started by init. It forks yet again, giving 14721, the program which does the actual work. Usually daemons do this in order to become fully independent of the program which launched them (so that they become inherited by init rather than whatever script launched them). However, when doing this, the middle process (14719) must exit, rather than staying around. The result of this is that upstart becomes confused and thinks 14719 is the actual daemon, and sends it the signals instead of 14721. However, 14719 is not prepared to handle any signal, including SIGHUP, and so it exits without passing anything on to its child. Upstart notices 14719's exit, and thinks that squid is now fully gone, but it is not, as 14721 still happily chuggs along. Adding SQUID_ARGS=-N to /etc/default/squid, and commenting out expect fork from /etc/init/squid fixes the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. https://bugs.launchpad.net/bugs/573853 Title: Cannot control squid Unknown instance -- 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 573853] Re: Cannot control squid Unknown instance
Not adding -N, but instead replacing expect fork with expect daemon does not work as upstart will wait for the middle process to exit, which it never does. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. https://bugs.launchpad.net/bugs/573853 Title: Cannot control squid Unknown instance -- 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 685201] [NEW] shutdown_lifetime setting behavior does not match doc
Public bug reported: Binary package hint: squid When shutting down squid, squid waits for 30 seconds (shutdown_lifetime setting) even if no active client is present, however, the doc says it would. Moreover the doc says that this also applies to SIGHUP, but (fortunately...) it doesn't. Proposed fix: 1. Change the code to only wait if there are indeed clients connected. If last client disconnected before wait time is up, exit at that point. 2. Change doc to say When SIGTERM is received, the cache is put into... rather than When SIGTERM or SIGHUP is received... ** Affects: squid (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in ubuntu. https://bugs.launchpad.net/bugs/685201 Title: shutdown_lifetime setting behavior does not match doc -- 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 514883] Re: dialog-based applications seem sluggish
Still an issue in 10.04.1 -- dialog-based applications seem sluggish https://bugs.launchpad.net/bugs/514883 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 442498] Re: openldap install bare bones need default DIT separate package
Seconded. Please provide a backport to lucid! -- openldap install bare bones need default DIT separate package https://bugs.launchpad.net/bugs/442498 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap 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 675052] [NEW] Upgrade from hardy (8.04) to lucid (10.04) sets bad permissions on olcDatabase={-1}frontend, cn=config
Public bug reported:
When upgrading from hardy to lucid, the following permissions are set on
the frontend :
# {-1}frontend, config
dn: olcDatabase={-1}frontend,cn=config
olcAccess: {0}to * by dn.exact=gidNumber=0+uidNumber=0,cn=peercred,cn=external
,cn=auth manage by * break
instead of:
dn: olcDatabase={-1}frontend,cn=config
olcAccess: {0}to * by
dn.exact=dn.exact=gidNumber=0+uidNumber=0,cn=peercred,cn=external manage by *
break
olcAccess: {1}to dn.base= by * read
olcAccess: {2}to dn.base=cn=subschema by * read
The result of this is that the rootDse cannot be loaded by the anon user
(testable using ldapsearch -x -b -s base +), which prevents SASL binds
with Unix user from working (ldapsearch -U user )
** Affects: openldap (Ubuntu)
Importance: Undecided
Status: New
--
Upgrade from hardy (8.04) to lucid (10.04) sets bad permissions on
olcDatabase={-1}frontend,cn=config
https://bugs.launchpad.net/bugs/675052
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openldap 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 370271] Re: During dist upgrade from 8.10 to 9.04 with mailman got exit status 1
Chuck, the comment you replied to didn't really confirm that the problem was solved. More to the contrary, the problem still exists, and even was so bad that Craig gave up on it and decided to just wait for the next version... ... which eventually turned out to be as broken as 9.04 because nobody would fix this bug as it was marked invalid. This is still a problem while upgrading from 8.04 to 10.04 . These are consecutive LTS versions, so this upgrade path should be feasible. -- During dist upgrade from 8.10 to 9.04 with mailman got exit status 1 https://bugs.launchpad.net/bugs/370271 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman 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 666625] [NEW] slapd no longer installs default database since 10.04
Public bug reported: Up to 9.04, slapd's postinstall script installed a default LDAP database (with a DN derived from the server's hostname) if none was present already. Since 10.04, it only installs the cn=config space, but no user data. Moreover, there is no utility present to do this easily manually. ** Affects: openldap (Ubuntu) Importance: Undecided Status: New -- slapd no longer installs default database since 10.04 https://bugs.launchpad.net/bugs/25 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openldap 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 554928] Re: cannot follow symlinks on any samba share
Just a remark for those gotten bitten by this behavior, and want to avoid similar occurrences in the future: The samba team doesn't read distribution's bug trackers, but they do have their own list: samba-techni...@lists.samba.org The samba team lives under the impression that only a tiny minority of people are affected by this bug, and they can only be convinced otherwise if more people make their voices heard. So if you care, drop a note to samba-techni...@lists.samba.org Thanks, Alain -- cannot follow symlinks on any samba share https://bugs.launchpad.net/bugs/554928 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 563752] [NEW] 3.0.28a-1ubuntu4.11 has new unix extensions parameter default to yes, wreaking havoc on existing configs
Public bug reported: Binary package hint: samba 3.0.28a-1ubuntu4.11 has a new unix extensions parameter default to yes, wreaking havoc on existing configs by disabling wide links In order to respect principle of least surprise, any new parameters which can break existing config should default to no, or to whatever value preserves existing functionality. Moreover, it would be useful if unix extensions could be specified by share, rather than globally (maybe then, it could even be automatically turned off on those shares that have wide links) ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 3.0.28a-1ubuntu4.11 has new unix extensions parameter default to yes, wreaking havoc on existing configs https://bugs.launchpad.net/bugs/563752 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 563752] Re: 3.0.28a-1ubuntu4.11 has new unix extensions parameter default to yes, wreaking havoc on existing configs
Thinking about this somewhat more, several other solutions to the problem may be considered: 1. If wide links = yes and unix extensions = yes are both present on a share, do it the other way round: disable unix extensions rather than wide links. 2. Even better: _only_ disable the call to make symlinks (... that's the only one with a security implication, right?...) 3. And still better: only disallow to create symlinks that point outside of the share (so that the only such symlinks would be those set up manually, for instance by the administrator) -- 3.0.28a-1ubuntu4.11 has new unix extensions parameter default to yes, wreaking havoc on existing configs https://bugs.launchpad.net/bugs/563752 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba 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 514883] Re: dialog-based applications seem sluggish
I just tried it (with a 9.04 image), it doesn't help. -- dialog-based applications seem sluggish https://bugs.launchpad.net/bugs/514883 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm 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 514883] Re: dialog-based applications seem sluggish
The problem also exists for bash commandline. Cursor keys are handled with a one-second delay (approx.), whereas other keys are handled immediately. My previous interpretation was apparently wrong: the problem is not related to any output that the program performs in reaction to receiving the cursor key, but rather to the reception of the cursor key input itself. -- dialog-based applications seem sluggish https://bugs.launchpad.net/bugs/514883 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm 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 514883] [NEW] dialog-based applications seem sluggish
Public bug reported: Binary package hint: kvm When running a dialog-based application (such as Ubuntu's text mode installer) within kvm, it feels very sluggish. If I press cursor-down or up, it takes more than a second until the highlighted bar moves up or down. Typing text in a (dialog) text fields seems ok though. This is _not_ a bug in the guest, as on a physical machine it is fast and snappy. Moreover, if kvm is run in vnc mode, it is fast and snappy as well 1. lsb_release -rd Description:Ubuntu 9.04 Release:9.04 2. apt-cache policy kvm kvm: Installed: 1:84+dfsg-0ubuntu12.4 Candidate: 1:84+dfsg-0ubuntu12.4 Version table: *** 1:84+dfsg-0ubuntu12.4 0 500 http://fr.archive.ubuntu.com jaunty-updates/main Packages 100 /var/lib/dpkg/status 1:84+dfsg-0ubuntu11 0 500 http://fr.archive.ubuntu.com jaunty/main Packages 3. What I expect to happen Kvm should react immediately at first cursor movement. If for some reason (slow screen updates?), it should only start deferring or dropping updates if the screen update queue already has some updates being processed. 4. What happened instead First screen refresh apparently was already delayed (maybe trying to wait for more in order to batch them together?) ** Affects: kvm (Ubuntu) Importance: Undecided Status: New -- dialog-based applications seem sluggish https://bugs.launchpad.net/bugs/514883 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to kvm 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
