[Bug 869750] Re: dovecot install failed
-- 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/869750 Title: dovecot install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/869750/+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 869750] [NEW] dovecot install failed
Public bug reported: vladimir@volgedu:~$ sudo apt-get dist-upgrade Reading package lists... Done Building dependency tree Reading state information... Done Calculating upgrade... Done 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. 2 not fully installed or removed. After this operation, 0B of additional disk space will be used. Do you want to continue [Y/n]? y Setting up dovecot-common (1:1.2.9-1ubuntu6.5) ... Creating generic self-signed certificate: /etc/ssl/certs/dovecot.pem (replace with hand-crafted or authorized one if needed). hostname: Name or service not known dpkg: error processing dovecot-common (--configure): subprocess installed post-installation script returned error exit status 1 dpkg: dependency problems prevent configuration of dovecot-pop3d: dovecot-pop3d depends on dovecot-common (= 1:1.2.9-1ubuntu6.5); however: Package dovecot-common is not configured yet. dpkg: error processing dovecot-pop3d (--configure): dependency problems - leaving unconfigured No apport report written because the error message indicates its a followup error from a previous failure. Errors were encountered while processing: dovecot-common dovecot-pop3d E: Sub-process /usr/bin/dpkg returned an error code (1) Description:Ubuntu 10.04.3 LTS Release:10.04 dovecot-common: Installed: 1:1.2.9-1ubuntu6.5 Candidate: 1:1.2.9-1ubuntu6.5 Version table: *** 1:1.2.9-1ubuntu6.5 0 500 http://ru.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 1:1.2.9-1ubuntu6.4 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 1:1.2.9-1ubuntu6 0 500 http://ru.archive.ubuntu.com/ubuntu/ lucid/main Packages dovecot-pop3d: Installed: 1:1.2.9-1ubuntu6.5 Candidate: 1:1.2.9-1ubuntu6.5 Version table: *** 1:1.2.9-1ubuntu6.5 0 500 http://ru.archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 100 /var/lib/dpkg/status 1:1.2.9-1ubuntu6.4 0 500 http://security.ubuntu.com/ubuntu/ lucid-security/main Packages 1:1.2.9-1ubuntu6 0 500 http://ru.archive.ubuntu.com/ubuntu/ lucid/main Packages ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: dovecot-pop3d 1:1.2.9-1ubuntu6.5 ProcVersionSignature: Ubuntu 2.6.32-28.55-server 2.6.32.27+drm33.12 Uname: Linux 2.6.32-28-server x86_64 Architecture: amd64 Date: Thu Oct 6 17:44:08 2011 InstallationMedia: Ubuntu-Server 10.04 LTS "Lucid Lynx" - Release amd64 (20100427) SourcePackage: dovecot ** Affects: dovecot (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lucid -- 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/869750 Title: dovecot install failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dovecot/+bug/869750/+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 869411] Re: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty
OK. It was a lot easier just to keep the packaging the same then, so that's what I've done. The debian dir for the reuploaded SRU is the same as what's in natty-updates/security now except for the changelog entry. -- 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/869411 Title: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/869411/+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 869411] Re: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty
I'm fine with updating to the new upstream version, but I don't like backporting the whole package. There's quite a lot of packaging changes there, including: * bumping the debhelper compat level to 7: This might expose bugs in earlier debhelper versions which we haven't encountered in oneiric * changing the init script quite radically: formally it breaks feature freeze; at the risk factor, the current postfix init script has never been in a stable release yet, so got comparatively little testing; IMHO it is too much risk to throw it at stable users as it changes expected behaviour and causes conffile prompts. * other changes like debian/copyright and the apport integration; these seem harmless, and I'd be willing to take them for an SRU. FYI, I won't ever agree to a blanket MRE that includes packaging changes. All other MREs that we have, like postgresql or firefox only cover updating the upstream bits, but keeping the packaging structure, scripts, conffiles, etc. unchanged. -- 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/869411 Title: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/869411/+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 869411] Re: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty
Passed the QA regression test (with -1, -2 doesn't affect the binary packages). root@utest-nns32:/tmp/qa-regression-testing/scripts# python ./test-postfix.py -vRunning test: './test-postfix.py' distro: 'Ubuntu 11.04' kernel: '2.6.38-11.50 (Ubuntu 2.6.38-11.50-generic-pae 2.6.38.8)' arch: 'i386' uid: 0/0 SUDO_USER: '') test_00_listening (__main__.PostfixTest) Postfix is listening ... ok test_10_commands (__main__.PostfixTest) Basic SMTP commands ... ok test_10_sending_mail_direct (__main__.PostfixTest) Mail delivered normally ... ok test_10_sending_mail_direct_auth (__main__.PostfixTest) Mail authentication ... ok test_10_sending_mail_direct_auth_full (__main__.PostfixTest) Mail delivered with authentication ... ok test_10_sending_mail_direct_with_tls (__main__.PostfixTest) Mail delivered normally with TLS ... ok test_10_sending_mail_forward_normal (__main__.PostfixTest) Mail delivered via .forward ... ok test_10_sending_mail_forward_xternal (__main__.PostfixTest) Mail processed by commands in .forward ... ok test_11_security_CVE_2008_2936 (__main__.PostfixTest) CVE-2008-2936 fixed ... ok test_20_sasldb_cram_md5 (__main__.PostfixTest) Test sasldb CRAM-MD5 ... ok test_20_sasldb_digest_md5 (__main__.PostfixTest) Test sasldb DIGEST-MD5 is supported ... ok test_20_sasldb_login (__main__.PostfixTest) Test sasldb LOGIN is supported ... ok test_20_sasldb_plain (__main__.PostfixTest) Test sasldb PLAIN ... ok test_21_security_CVE_2011_1720 (__main__.PostfixTest) CVE-2011-1720 fixed ... ok test_99_restore (__main__.PostfixTest) Restore configuration ... ok -- Ran 15 tests in 80.701s OK root@utest-nns32:/tmp/qa-regression-testing/scripts# apt-cache policy postfix postfix: Installed: 2.8.5-1~build0.11.04 Candidate: 2.8.5-1~build0.11.04 Version table: *** 2.8.5-1~build0.11.04 0 500 http://ppa.launchpad.net/postfix-support/sru/ubuntu/ natty/main i386 Packages 100 /var/lib/dpkg/status 2.8.2-1ubuntu2.1 0 500 http://ro.archive.ubuntu.com/ubuntu/ natty-updates/main i386 Packages 500 http://security.ubuntu.com/ubuntu/ natty-security/main i386 Packages 2.8.2-1ubuntu1 0 500 http://ro.archive.ubuntu.com/ubuntu/ natty/main i386 Packages ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2008-2936 ** CVE added: http://www.cve.mitre.org/cgi- bin/cvename.cgi?name=2011-1720 ** Description changed: Pilot SRU for postfix post-release updates per TB on 10/6/11/ + + TEST CASE: Run the QA regression test suite (done). Install postfix + and verify it installs, starts, stops, sends mail. -- 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/869411 Title: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/869411/+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 869684] [NEW] 530 login incorrect error after upgrade to Oneiric
Public bug reported: After upgrading to Oneiric, any attempt to login to my vsftpd server fails with a 530 login incorrect error. This occurs with both local user and anonymous logins. There is a pam_ldap error in the system log file, if that helps. Attached is my vsftpd.conf file. ** 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/869684 Title: 530 login incorrect error after upgrade to Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/869684/+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 869684] Re: 530 login incorrect error after upgrade to Oneiric
** Attachment added: "Config file" https://bugs.launchpad.net/bugs/869684/+attachment/2520964/+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/869684 Title: 530 login incorrect error after upgrade to Oneiric To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/869684/+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 868753] Re: qemu+ssh connections to a remote libvirt fail
What is the arch of both? is one 32-bit and one 64? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/868753 Title: qemu+ssh connections to a remote libvirt fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/868753/+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 529714] Re: rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r()
** Also affects: banshee (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: eglibc (Ubuntu Precise) Importance: Undecided Status: New ** Also affects: samba (Ubuntu Precise) Importance: Undecided Status: New ** Changed in: eglibc (Ubuntu Precise) Status: New => Confirmed ** Tags removed: rls-mgr-o-tracking -- 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/529714 Title: rhythmbox crashed with SIGSEGV in _nss_wins_gethostbyname_r() To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/529714/+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 869411] Re: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty
** Changed in: postfix (Ubuntu) Status: New => Invalid ** Changed in: postfix (Ubuntu Natty) Importance: Undecided => Wishlist ** Changed in: postfix (Ubuntu Natty) Status: New => In Progress ** Changed in: postfix (Ubuntu Natty) Assignee: (unassigned) => Scott Kitterman (kitterman) -- 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/869411 Title: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/869411/+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 869492] Re: 'timed out' to console message and no instance data found in start
This bug was fixed in the package cloud-init - 0.6.1-0ubuntu22 --- cloud-init (0.6.1-0ubuntu22) oneiric; urgency=low * DataSourceEc2: catch a socket timeout when with a slow metadata service (LP: #869492). -- Scott MoserThu, 06 Oct 2011 17:11:29 -0400 ** Changed in: cloud-init (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/869492 Title: 'timed out' to console message and no instance data found in start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/869492/+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 869590] Re: KVM migration fails when tunnelled due to parsing error in qemu monitor
This bug does not affect Maverick and higher as they are based from a version including the upstream fix already. I forgot to mention by here are the information of my affected system : # lsb_release -rd Description: Ubuntu 10.04.3 LTS Release: 10.04 # apt-cache policy libvirt-bin libvirt-bin: Installed: 0.7.5-5ubuntu27.16 Candidate: 0.7.5-5ubuntu27.16 Version table: *** 0.7.5-5ubuntu27.16 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 0.7.5-5ubuntu27 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/869590 Title: KVM migration fails when tunnelled due to parsing error in qemu monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869590/+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 869553] Re: Apparmor prevents KVM tunnelled migration
The bug #869590 (https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869590) was opened for the qemuMonitrText migration parsing error. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/869553 Title: Apparmor prevents KVM tunnelled migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869553/+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 869590] Re: KVM migration fails when tunnelled due to parsing error in qemu monitor
When looking at the upstream git I found that Daniel P. Berrange had already fixed that in commit 0d3eee7fe8bcaa49. I have extract only the portion of this commit that touches src/qemu/qemu_monitor_text.c and created a debdiff with it. ** Patch added: "Fix parsing of 'info migration' reply" https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869590/+attachment/2520342/+files/lp-869590.kvm-tunnelled-migration-fix.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/869590 Title: KVM migration fails when tunnelled due to parsing error in qemu monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869590/+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 869590] [NEW] KVM migration fails when tunnelled due to parsing error in qemu monitor
Public bug reported: While attempting a live migration tunnelled like this : virsh migrate --live --tunnelled --p2p guest1 qemu+ssh://192.168.99.3/system the source host (node1) logs this error : Oct 6 17:44:06 node2 libvirtd: 17:44:06.513: error : qemuMonitorTextGetMigrationStatus:982 : internal error cannot parse migration data transferred statistic 1052 kbytes#015#012remaining ram: 539972 kbytes#015#012total ram: 541024 kbytes#015#012 And the guest VM freezes and start consuming 100% CPU infinitely. ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/869590 Title: KVM migration fails when tunnelled due to parsing error in qemu monitor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869590/+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 869553] Re: Apparmor prevents KVM tunnelled migration
** Summary changed: - KVM migration fails when tunnelled + Apparmor prevents KVM tunnelled migration -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/869553 Title: Apparmor prevents KVM tunnelled migration To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869553/+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 862558] Re: cobbler-enlist is not checking for return codes enough
** Tags removed: rls-mgr-o-tracking ** Tags added: rls-mgr-p-tracking -- You received this bug notification because you are a member of Ubuntu Server Team, which is a bug assignee. https://bugs.launchpad.net/bugs/862558 Title: cobbler-enlist is not checking for return codes enough To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cobbler-enlist/+bug/862558/+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 869553] Re: KVM migration fails when tunnelled
Adding the following to /etc/apparmor.d/abstractions/libvirt-qemu : /{,var/}run/libvirt/qemu/* rw, After fixing the Apparmor profile, the migration still fails but not due to Apparmor getting in the way. Instead it blocks on another bug (that deserves a separated bug in LP) : Oct 6 17:30:13 node2 libvirtd: 17:30:13.139: error : qemuMonitorTextGetMigrationStatus:982 : internal error cannot parse migration data transferred statistic 1052 kbytes#015#012remaining ram: 539972 kbytes#015#012total ram: 541024 kbytes#015#012 Note that using a regular migration (no "--p2p --tunnelled" flags) works. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/869553 Title: KVM migration fails when tunnelled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869553/+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 869553] [NEW] KVM migration fails when tunnelled
Public bug reported: While attempting a live migration the destination host (node1) logs this : Oct 5 17:13:56 node1 kernel: [ 1418.872987] type=1503 audit(1317849236.311:29): operation="mknod" pid=1975 parent=1 profile="libvirt-4aa60863-6b03-2f19-897f-4de6d12c96e1" requested_mask="c::" denied_mask="c::" fsuid=0 ouid=0 name="/var/ run/libvirt/qemu/qemu.tunnelmigrate.dest.guest1" The source system was running this command : root@node2:~# virsh migrate --live --p2p --tunnelled guest1 qemu+ssh://192.168.88.51/system Both systems are running the same distro and package versions : # lsb_release -rd Description:Ubuntu 10.04.3 LTS Release:10.04 # apt-cache policy libvirt-bin libvirt-bin: Installed: 0.7.5-5ubuntu27.16 Candidate: 0.7.5-5ubuntu27.16 Version table: *** 0.7.5-5ubuntu27.16 0 500 http://archive.ubuntu.com/ubuntu/ lucid-updates/main Packages 500 http://archive.ubuntu.com/ubuntu/ lucid-security/main Packages 100 /var/lib/dpkg/status 0.7.5-5ubuntu27 0 500 http://archive.ubuntu.com/ubuntu/ lucid/main Packages ** Affects: libvirt (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/869553 Title: KVM migration fails when tunnelled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/869553/+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 869492] Re: 'timed out' to console message and no instance data found in start
** Changed in: cloud-init (Ubuntu) Milestone: None => ubuntu-11.10 ** Tags added: server-o-rs ** Changed in: cloud-init (Ubuntu) Status: New => Fix Committed ** Changed in: cloud-init (Ubuntu) Importance: Undecided => High ** Changed in: cloud-init (Ubuntu) Assignee: (unassigned) => Scott Moser (smoser) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/869492 Title: 'timed out' to console message and no instance data found in start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/869492/+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 843701] Re: CVE-2011-3190 Apache Tomcat Authentication bypass and information disclosure
** Changed in: tomcat6 (Ubuntu Hardy) Status: In Progress => Invalid ** Changed in: tomcat6 (Ubuntu Lucid) Status: In Progress => Fix Committed ** Changed in: tomcat6 (Ubuntu Maverick) Status: In Progress => Fix Committed ** Changed in: tomcat6 (Ubuntu Natty) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tomcat6 in Ubuntu. https://bugs.launchpad.net/bugs/843701 Title: CVE-2011-3190 Apache Tomcat Authentication bypass and information disclosure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tomcat5.5/+bug/843701/+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 869492] Re: 'timed out' to console message and no instance data found in start
** Branch linked: lp:cloud-init -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/869492 Title: 'timed out' to console message and no instance data found in start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/869492/+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 869492] Re: 'timed out' to console message and no instance data found in start
I can reproduce this from inside this instance with the following program: #!/usr/bin/python import urllib2, sys, socket def doget(iurl, timeout): reason = None try: req = urllib2.Request(iurl) resp = urllib2.urlopen(req, timeout=timeout) except urllib2.HTTPError as e: reason = "http error [%s]" % e.code except urllib2.URLError as e: reason = "url error [%s]" % e.reason except socket.timeout as e: reason = "socket timeout [%s]" % e if reason: print "Fail: %s" % reason doget(sys.argv[1],float(sys.argv[2])) I run it and see the following output: $ ./test-timeout.py http://169.254.169.254/latest/meta-data/instance-id 1 Fail: socket timeout [timed out] It seams that urllib2 does not catch socket timeouts, so we'll have to add that catch, and I think we should probably up the default timeout. ** Description changed: - I launched an instance on a nova cloud, and it was unreachable. + I launched an instance on a nova cloud, and it was unreachable. Upon investigation of the console log, I found: | cloud-init start-local running: Thu, 06 Oct 2011 19:57:29 +. up 4.02 seconds | no instance data found in start-local - | ci-info: lo: 1 127.0.0.1 255.0.0.0 + | ci-info: lo: 1 127.0.0.1 255.0.0.0 | ci-info: eth0 : 1 10.55.60.69 255.255.255.0 02:16:3e:5b:c5:b8 | ci-info: route-0: 0.0.0.0 10.55.60.1 0.0.0.0 eth0 UG | ci-info: route-1: 10.55.60.0 0.0.0.0 255.255.255.0 eth0 U | cloud-init start running: Thu, 06 Oct 2011 19:57:29 +. up 4.24 seconds | timed out | no instance data found in start | mountall: Event failed | * Stopping Handle applying cloud-config^[[74G[ OK ] After a reboot, investigation of cloud-init log showed: - | 2011-10-06 19:57:29,793 - DataSourceEc2.py[DEBUG]: Searching the following metadata urls: ['http://169.254.169.254'] - | 2011-10-06 19:57:31,797 - __init__.py[DEBUG]: Did not find data source. searched classes: ['DataSourceNoCloudNet', 'DataSourceOVFNet', 'DataSourceEc2'] + | 2011-10-06 19:57:29,793 - DataSourceEc2.py[DEBUG]: Searching the following metadata urls: ['http://169.254.169.254'] + | 2011-10-06 19:57:31,797 - __init__.py[DEBUG]: Did not find data source. searched classes: ['DataSourceNoCloudNet', 'DataSourceOVFNet', 'DataSourceEc2'] The 'Did not find' came from cloudinit/__init__.py, meaning DataSourceEc2.py returned. The strange thing is that it seems DataSourceEc2 did not retry at all. I'm not sure why it would not. I believe that we're simply hitting a timeout on the Metadata service on the attempt to get instance-id. Previously (as seen in bug 745930) this would be handled and retried. The intent was that we would see a long series of retries. We've since added a 'timeout=timeout' where the value of timeout defaults to '2' to the urlopen call. It seems that for whatever reason, we're not catching that timeout and trying again. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu20 ProcVersionSignature: User Name 3.0.0-12.19-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Thu Oct 6 20:18:55 2011 Ec2AMI: ami-00ac Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: - PATH=(custom, user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) + + + related bugs: + * bug 851159: ec2 metadata service is very slow + * bug 745930: timeout on metadata service in natty after retry -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/869492 Title: 'timed out' to console message and no instance data found in start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/869492/+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 869492] Re: 'timed out' to console message and no instance data found in start
** Attachment added: "console output of first boot (failed)" https://bugs.launchpad.net/bugs/869492/+attachment/2519592/+files/console-first-boot.txt -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/869492 Title: 'timed out' to console message and no instance data found in start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/869492/+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 869492] [NEW] 'timed out' to console message and no instance data found in start
Public bug reported: I launched an instance on a nova cloud, and it was unreachable. Upon investigation of the console log, I found: | cloud-init start-local running: Thu, 06 Oct 2011 19:57:29 +. up 4.02 seconds | no instance data found in start-local | ci-info: lo: 1 127.0.0.1 255.0.0.0 | ci-info: eth0 : 1 10.55.60.69 255.255.255.0 02:16:3e:5b:c5:b8 | ci-info: route-0: 0.0.0.0 10.55.60.1 0.0.0.0 eth0 UG | ci-info: route-1: 10.55.60.0 0.0.0.0 255.255.255.0 eth0 U | cloud-init start running: Thu, 06 Oct 2011 19:57:29 +. up 4.24 seconds | timed out | no instance data found in start | mountall: Event failed | * Stopping Handle applying cloud-config^[[74G[ OK ] After a reboot, investigation of cloud-init log showed: | 2011-10-06 19:57:29,793 - DataSourceEc2.py[DEBUG]: Searching the following metadata urls: ['http://169.254.169.254'] | 2011-10-06 19:57:31,797 - __init__.py[DEBUG]: Did not find data source. searched classes: ['DataSourceNoCloudNet', 'DataSourceOVFNet', 'DataSourceEc2'] The 'Did not find' came from cloudinit/__init__.py, meaning DataSourceEc2.py returned. The strange thing is that it seems DataSourceEc2 did not retry at all. I'm not sure why it would not. I believe that we're simply hitting a timeout on the Metadata service on the attempt to get instance-id. Previously (as seen in bug 745930) this would be handled and retried. The intent was that we would see a long series of retries. We've since added a 'timeout=timeout' where the value of timeout defaults to '2' to the urlopen call. It seems that for whatever reason, we're not catching that timeout and trying again. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cloud-init 0.6.1-0ubuntu20 ProcVersionSignature: User Name 3.0.0-12.19-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Thu Oct 6 20:18:55 2011 Ec2AMI: ami-00ac Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.large Ec2Kernel: unavailable Ec2Ramdisk: unavailable PackageArchitecture: all ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: cloud-init UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: cloud-init (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug ec2-images oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cloud-init in Ubuntu. https://bugs.launchpad.net/bugs/869492 Title: 'timed out' to console message and no instance data found in start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/869492/+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 737027] Re: kpartx udev rule is broken
The '-part' is an argument to the '-p' switch, so it also needs removed from the kpartx command, and needs to follow the '-p' switch to dmraid, if that switch is added there, but I do not think it should be, for the same reason that it should be removed from kpartx. The reason that dmraid handles the partitions itself instead of allowing kpartx to do it is because when it deactivates an array, it must remove the partitions first, therefore, it must parse the partition tables to figure out which partitions need removed. This needs resolved before the partition handling can be removed from dmraid and kpartx relied on to do it instead. Unfortunately, the kernel currently lacks a mechanism to propagate a removal request or a surprise removal notice up the device stack, which dmraid would need to properly tear down the dmraid device. Without that, it can not properly handle device shutdown without its partition code ( and can't handle it properly even as it is now, if the partition is part of LVM ). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to multipath-tools in Ubuntu. https://bugs.launchpad.net/bugs/737027 Title: kpartx udev rule is broken To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dmraid/+bug/737027/+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 868753] Re: qemu+ssh connections to a remote libvirt fail
Hi Serge, These hosts are in the QA lab, and only accessible via a SSH proxy. Firewalls are certainly in place, but no custom libvirt customisation to my knowledge. We can get you access if you need. Interestingly, via the proxy I get this: [cerdea-aws]cerdea@xango3:~$ virsh -c qemu+ssh://aldebaran/system list --all error: packet 1550146349 bytes received from server too large, want 262144 error: failed to connect to the hypervisor [cerdea-aws]cerdea@xango3:~$ And, if I am local at aldebaran: cerdea@aldebaran~:$ virsh -c qemu+ssh://aldebaran/system list --all cerdea@aldebaran's password: Id Name State -- 1058 8913cfbf-4757-491f-b8c5-02df75d18f6e running cerdea@aldebaran:~$ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/868753 Title: qemu+ssh connections to a remote libvirt fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/868753/+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 855994] Re: Sharing service installation failed
** Package changed: ubuntu => samba (Ubuntu) -- 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/855994 Title: Sharing service installation failed To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/855994/+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 869411] [NEW] SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty
Public bug reported: Pilot SRU for postfix post-release updates per TB on 10/6/11/ ** Affects: postfix (Ubuntu) Importance: Undecided Status: New ** Affects: postfix (Ubuntu Natty) Importance: Undecided Status: New ** Also affects: postfix (Ubuntu Natty) Importance: Undecided Status: New -- 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/869411 Title: SRU tracking bug for postfix 2.8.2 -> 2.8.5 for natty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/869411/+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 855994] [NEW] Sharing service installation failed
You have been subscribed to a public bug: I've tried to share a folder from this Oneiric machine, but the normal process (check the "share this folder" -> install Samba server, etc.) is not working. The error "Sharing service installation failed" pops up with this explanation "Sharing service installation has failed. Would you like to retry the installation?" (Retry/Cancel buttons are there). Retry is not working either. This worked flawless in Natty. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: samba (not installed) ProcVersionSignature: Ubuntu 3.0.0-11.18-generic 3.0.4 Uname: Linux 3.0.0-11-generic x86_64 ApportVersion: 1.23-0ubuntu1 Architecture: amd64 Date: Thu Sep 22 02:45:07 2011 InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta amd64 (20110901) ProcEnviron: PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: nautilus 1:3.1.92-0ubuntu2 gvfs 1.9.5-0ubuntu2 SambaClientRegression: Yes SourcePackage: samba UpgradeStatus: Upgraded to oneiric on 2011-09-01 (19 days ago) ** Affects: samba (Ubuntu) Importance: Undecided Status: Confirmed ** Tags: amd64 apport-bug oneiric running-unity -- Sharing service installation failed https://bugs.launchpad.net/bugs/855994 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 869364] Re: cgconfig gets confused with /cgroups fstab entry
This is happening because you can't have multiple mounts of cgroups with different compositions. Ideally I'd say the cgroup-bin postinst should forcibly umount any other /cgroup mounts, but if, as in your case, the user had cgroup in his fstab, that would continue to cause troubles. Perhaps the package postinst should simply provide a more meaningful warning message if it finds cgroups already mounted, and ask the user to resolve the situation? ** Changed in: libcgroup (Ubuntu) Status: New => Confirmed ** Changed in: libcgroup (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/869364 Title: cgconfig gets confused with /cgroups fstab entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/869364/+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 869364] Re: cgconfig gets confused with /cgroups fstab entry
I'm not sure what ends up doing the unclean unmount of /cgroup when you try to start cgconfig, but an strace of /usr/sbin/cgconfigparser -l /etc/cgconfig.conf shows: stat64("/sys/fs//cgroup/cpu", 0xbfb057c0) = -1 ENOENT (No such file or directory) mkdir("/sys", 0775) = -1 EEXIST (File exists) mkdir("/sys/fs", 0775) = -1 EEXIST (File exists) mkdir("/sys/fs//cgroup", 0775) = -1 EEXIST (File exists) mkdir("/sys/fs//cgroup/cpu", 0775) = 0 mount("cgroup", "/sys/fs//cgroup/cpu", "cgroup", 0, "cpu") = -1 EBUSY (Device or resource busy) oldumount("/sys/fs//cgroup/cpu")= -1 EINVAL (Invalid argument) rmdir("/sys/fs//cgroup/cpu")= 0 oldumount("/sys/fs/cgroup/cpuacct") = -1 ENOENT (No such file or directory) rmdir("/sys/fs/cgroup/cpuacct") = -1 ENOENT (No such file or directory) oldumount("/sys/fs/cgroup/devices") = -1 ENOENT (No such file or directory) rmdir("/sys/fs/cgroup/devices") = -1 ENOENT (No such file or directory) oldumount("/sys/fs/cgroup/memory") = -1 ENOENT (No such file or directory) rmdir("/sys/fs/cgroup/memory") = -1 ENOENT (No such file or directory) oldumount("/sys/fs/cgroup/freezer") = -1 ENOENT (No such file or directory) rmdir("/sys/fs/cgroup/freezer") = -1 ENOENT (No such file or directory) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/869364 Title: cgconfig gets confused with /cgroups fstab entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/869364/+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 850602] Re: block migration needs to copy backing file
** Changed in: nova (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/850602 Title: block migration needs to copy backing file To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/850602/+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 869364] Re: cgconfig gets confused with /cgroups fstab entry
-- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/869364 Title: cgconfig gets confused with /cgroups fstab entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/869364/+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 869364] [NEW] cgconfig gets confused with /cgroups fstab entry
Public bug reported: Following previous documentation I'd seen in the natty time frame, and are also documented at lxc upstream (http://lxc.teegra.net/), I had a line like the following in /etc/fstab: none /cgroups cgroup defaults 0 0 Then, I found out about cgroup-bin, and thought that looked like the "supported" way to get cgroups mounted. So, I did: $ sudo apt-get install cgroup-bin That ended with: Setting up libcgroup1 (0.37.1-1ubuntu7) ... Setting up cgroup-bin (0.37.1-1ubuntu7) ... start: Job failed to start invoke-rc.d: initscript cgconfig, action "start" failed. dpkg: error processing cgroup-bin (--configure): subprocess installed post-installation script returned error exit status 1 Processing triggers for libc-bin ... ldconfig deferred processing now taking place Errors were encountered while processing: cgroup-bin E: Sub-process /usr/bin/dpkg returned an error code (1) Then, an 'apt-get -f install' showed: Setting up cgroup-bin (0.37.1-1ubuntu7) ... cgconfig start/running So I thought all was well, and some strange transient error. After reboot, though, I come into the following state: $ grep cgroup /proc/mounts $ sudo status cgconfig $ grep cgconfig /var/log/kern.log Oct 6 17:21:53 server-2206 kernel: [ 33.803611] init: cgconfig pre-start process (697) terminated with status 3 Then, trying to fix the situation shows the issue: $ sudo mount /cgroup none /cgroup cgroup rw,relatime,perf_event,blkio,net_cls,freezer,devices,memory,cpuacct,cpu,cpuset 0 0 $ sudo start cgconfig $ grep cgroup /proc/mounts $ sudo mount -av mount: proc already mounted on /proc mount: /dev/vdb already mounted on /mnt mount: none already mounted on /cgroup nothing was mounted $ ls /cgroup/ $ grep cgroup /proc/mounts Basically, if you have cgroups mounted, 'start cgconfig' will fail, and unmount your existing cgroup mount point, leaving you broken, and even 'mount' is confused by the state of the world (it thinks /cgroup was already mounted, when it is not). This will happen on every boot. [1] http://lxc.teegra.net/ ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: cgroup-bin 0.37.1-1ubuntu7 ProcVersionSignature: User Name 3.0.0-12.19-virtual 3.0.4 Uname: Linux 3.0.0-12-virtual i686 ApportVersion: 1.23-0ubuntu1 Architecture: i386 Date: Thu Oct 6 17:06:28 2011 Ec2AMI: ami-00ad Ec2AMIManifest: FIXME Ec2AvailabilityZone: nova Ec2InstanceType: m1.small Ec2Kernel: unavailable Ec2Ramdisk: unavailable ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: libcgroup UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: libcgroup (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug ec2-images i386 oneiric -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/869364 Title: cgconfig gets confused with /cgroups fstab entry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/869364/+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 868897] Re: Terminate instance results in traceback: OSError: [Errno 9] Bad file descriptor
*** This bug is a duplicate of bug 868349 *** https://bugs.launchpad.net/bugs/868349 Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: nova (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/868897 Title: Terminate instance results in traceback: OSError: [Errno 9] Bad file descriptor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868897/+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 868349] Re: instances do not stop correctly
I reinstalled all from scratch (Ubuntu Oneiric and Nova Diablo), and indeed the bug was still there. After applying your patch, the problem was solved! Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/868349 Title: instances do not stop correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868349/+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 868753] Re: qemu+ssh connections to a remote libvirt fail
@hggdh, thanks for submitting this bug. I tried to reproduce it with a new uptodate natty and a new uptodate oneiric host. But from the oneiric host, virsh -c qemu+ssh://ubuntu@10.55.60.90/session list --all worked, and I was able to start and watch and destroy a VM. Is there anything else unusual about these hosts? Firewalling or custom libvirt configuration? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/868753 Title: qemu+ssh connections to a remote libvirt fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/868753/+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 868349] Re: instances do not stop correctly
This bug was fixed in the package nova - 2011.3-0ubuntu6 --- nova (2011.3-0ubuntu6) oneiric; urgency=low * debian/patches/backport-libvirt-console-pipe.patch: - Patch updated to fix race on instance termination (LP: #868349) -- Robie BasakWed, 05 Oct 2011 17:37:49 +0100 ** Changed in: nova (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/868349 Title: instances do not stop correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868349/+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 838581] Re: Failures in db_pool code: 'NoneType' object has no attribute '_keymap' or not returning rows.
I patched my api.py to revert the db_pool complexities, but it still gives error like this when spawning 25+ instances at once: 2011-10-06 16:36:58,945 DEBUG nova.network.manager [6bf528ce-4e3d-4061-bd3b-1d25602a59ef None None] Leased IP |10.0.0.24| from (pid=27883) lease_fixed_ip /usr/lib/python2.7/dist-packages/nova/network/manager.py:645 ERROR nova.rpc [-] Exception during message handling (nova.rpc): TRACE: Traceback (most recent call last): (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/rpc/impl_kombu.py", line 620, in _process_data (nova.rpc): TRACE: rval = node_func(context=ctxt, **node_args) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 221, in allocate_for_instance (nova.rpc): TRACE: ips = super(FloatingIP, self).allocate_for_instance(context, **kwargs) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 444, in allocate_for_instance (nova.rpc): TRACE: requested_networks=requested_networks) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 171, in _allocate_fixed_ips (nova.rpc): TRACE: vpn=vpn, address=address) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/network/manager.py", line 615, in allocate_fixed_ip (nova.rpc): TRACE: instance_id) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/api.py", line 347, in fixed_ip_associate_pool (nova.rpc): TRACE: instance_id, host) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 101, in wrapper (nova.rpc): TRACE: return f(*args, **kwargs) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/nova/db/sqlalchemy/api.py", line 724, in fixed_ip_associate_pool (nova.rpc): TRACE: # then this has concurrency issues (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 1652, in first (nova.rpc): TRACE: ret = list(self[0:1]) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 1560, in __getitem__ (nova.rpc): TRACE: return list(res) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/orm/query.py", line 1823, in instances (nova.rpc): TRACE: fetch = cursor.fetchall() (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2528, in fetchall (nova.rpc): TRACE: l = self.process_rows(self._fetchall_impl()) (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2497, in _fetchall_impl (nova.rpc): TRACE: self._non_result() (nova.rpc): TRACE: File "/usr/lib/python2.7/dist-packages/sqlalchemy/engine/base.py", line 2502, in _non_result (nova.rpc): TRACE: "This result object does not return rows. " (nova.rpc): TRACE: ResourceClosedError: This result object does not return rows. It has been closed automatically. (nova.rpc): TRACE: ERROR nova.rpc [-] Returning exception This result object does not return rows. It has been closed automatically. to caller -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/838581 Title: Failures in db_pool code: 'NoneType' object has no attribute '_keymap' or not returning rows. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/838581/+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 867469] Re: package mysql-server-5.1 5.1.54-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
All I did to run into this problem on multiple computers is try to install mysql-server on Ubuntu 11.04 on 64-bit. When I installed the Ubuntu 10.04 LTS version in virtual box I was able to install mysql-server. Hope that helps! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/867469 Title: package mysql-server-5.1 5.1.54-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/867469/+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 868349] Re: instances do not stop correctly
** Changed in: nova (Ubuntu) Status: Confirmed => Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/868349 Title: instances do not stop correctly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868349/+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 825124] Re: package squid 2.7.STABLE7-1ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please could you examine the file /var/log/squid/cache.log and post the part of the file corresponding to the time that you tried to install/upgrade. Be sure to check and remove any private information from the file before posting it. Then set the Status of this bug back to New so that it does not expire. This will help us to find and resolve the problem. ** Changed in: squid (Ubuntu) Status: New => Incomplete -- 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/825124 Title: package squid 2.7.STABLE7-1ubuntu12.3 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/825124/+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 832111] Re: lxc instances never leave 'terminating' after terminate-instances
Yes the patch hasnt been accepted yet, so this still remains an issue. ** Changed in: nova (Ubuntu) Status: Incomplete => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/832111 Title: lxc instances never leave 'terminating' after terminate-instances To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/832111/+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 823878] Re: smbd failed to start after system restart
Vasya, If you manually change /etc/samba/smb.conf to have smbd bind to a specific interface, you also need to edit /etc/init/smbd.conf to make sure the smbd is started only after that particular interface is up, in the style "start on (local-filesystems and net-device-up IFACE=eth0)" (as described in https://bugs.launchpad.net/ubuntu/+source/samba/+bug/771305/comments/17). Ideally upstart would pick up on this automatically, but we also have to cater for environments where a network might not come up until much later if at all, and local access to smbd over loopback should still be available in that case (see https://bugs.launchpad.net/ubuntu/+source/samba/+bug/771305/comments/10). It is unfortunate that a sysadmin would have to know to do this when adding interfaces/bind interfaces only to smbd, so I'm leaving this bug open in case someone can come up with a way of solving this problem without issues in both cases. I'm setting Importance to Low as this workaround is available and the problem only occurs when the sysadmin changes smb.conf by hand. ** Summary changed: - smbd failed to start after system restart + "bind interfaces only" requires a manual change to /etc/init/smbd.conf ** Changed in: samba (Ubuntu) Importance: Medium => Low -- 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/823878 Title: "bind interfaces only" requires a manual change to /etc/init/smbd.conf To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/823878/+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 868379] Re: nat setup left around after removing/stopping libvirt-bin
Thanks for the prompt response. I have to say I don't really agree with this reasoning: the virbr0 interface is created and managed by libvirt, and after libvirt is removed it will currently disappear on system restart. I have a hard time imagining someone removing libvirt and intending/expecting their libvirt-managed vm+net setup to be left running and disappearing/breaking on next reboot. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/868379 Title: nat setup left around after removing/stopping libvirt-bin To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/868379/+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 868538] Re: /etc/init.d/xinetd kills LXC container's xinetd
** Bug watch added: Debian Bug tracker #644515 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644515 ** Also affects: xinetd (Debian) via http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=644515 Importance: Unknown Status: Unknown ** Changed in: xinetd (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/868538 Title: /etc/init.d/xinetd kills LXC container's xinetd To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/868538/+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 868753] Re: qemu+ssh connections to a remote libvirt fail
** Changed in: libvirt (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/868753 Title: qemu+ssh connections to a remote libvirt fail To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/868753/+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 590929] Re: [SRU] eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT configs)
** Changed in: eucalyptus Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to eucalyptus in Ubuntu. https://bugs.launchpad.net/bugs/590929 Title: [SRU] eucalyptus create and delete volumes sometimes fail on lvm commands (POC + ENT configs) To manage notifications about this bug go to: https://bugs.launchpad.net/eucalyptus/+bug/590929/+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 868538] Re: /etc/init.d/xinetd kills LXC container's xinetd
On Thu 2011-10-06 (09:41), Robie Basak wrote: > Setting Importance to Low as this bug applies only to an unusual > configuration and there is a workaround available. LXC is not unusual, because it is part of LTS! A LTS package should not break another package! And what workaround? -- Ullrich Horlacher Server- und Arbeitsplatzsysteme Rechenzentrum E-Mail: horlac...@rus.uni-stuttgart.de Universitaet Stuttgart Tel:++49-711-685-65868 Allmandring 30 Fax:++49-711-682357 70550 Stuttgart (Germany) WWW:http://www.rus.uni-stuttgart.de/ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/868538 Title: /etc/init.d/xinetd kills LXC container's xinetd To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/868538/+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 868897] Re: Terminate instance results in traceback: OSError: [Errno 9] Bad file descriptor
*** This bug is a duplicate of bug 868349 *** https://bugs.launchpad.net/bugs/868349 Dup of 868349. I've fixed this already, waiting on merge request. ** This bug has been marked a duplicate of bug 868349 instances do not stop correctly -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/868897 Title: Terminate instance results in traceback: OSError: [Errno 9] Bad file descriptor To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/868897/+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 868538] Re: /etc/init.d/xinetd kills LXC container's xinetd
Setting Importance to Low as this bug applies only to an unusual configuration and there is a workaround available. ** Changed in: xinetd (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/868538 Title: /etc/init.d/xinetd kills LXC container's xinetd To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/868538/+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 867469] Re: package mysql-server-5.1 5.1.54-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions: * Is this reproducible? * If so, what specific steps should we take to recreate this bug? This will help us to find and resolve the problem. ** Changed in: mysql-5.1 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/867469 Title: package mysql-server-5.1 5.1.54-1ubuntu4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.1/+bug/867469/+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 869017] [NEW] Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used)
You have been subscribed to a public bug by Paul Sladen (sladen): James Rice of Jump Networks noticed that there is a screen-blanker enabled on Ubuntu Server. James notes that this blanking is not enabling DPMS power saving (thereby negating any power-saving benefit), and is simply turning the screen content blank. This means that the crash output is invisible which is unhelpful on a server (virtual or otherwise). Ideally the screen should (at a minimum) be turned on and unblanked at the point of an OOPs/crash being printed. ** Affects: ubuntu Importance: Undecided Status: New -- Ubuntu server enables screenblanking, concealing crashdumps (DPMS is not used) https://bugs.launchpad.net/bugs/869017 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. -- 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 865219] Re: update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
*** This bug is a duplicate of bug 868176 *** https://bugs.launchpad.net/bugs/868176 ** Summary changed: - update-alternatives problem with lightdm-gtk-greeter + update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links ** Also affects: lightdm (Ubuntu Oneiric) Importance: Undecided Status: Confirmed ** Also affects: samba (Ubuntu Oneiric) Importance: Undecided Status: Invalid ** Changed in: lightdm Status: New => Invalid ** Changed in: lightdm (Ubuntu Oneiric) Status: Confirmed => Triaged ** Changed in: lightdm (Ubuntu Oneiric) Importance: Undecided => High -- 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/865219 Title: update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk- greeter-ubuntu.conf: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/865219/+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 865219] Re: update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
*** This bug is a duplicate of bug 868176 *** https://bugs.launchpad.net/bugs/868176 duplicate bug #868176? -- 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/865219 Title: update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk- greeter-ubuntu.conf: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/865219/+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 729780] Re: bind9 fails to create pid file.
** Changed in: bind9 (Ubuntu) Status: Expired => Incomplete -- 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/729780 Title: bind9 fails to create pid file. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bind9/+bug/729780/+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 865221] Re: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 2
*** This bug is a duplicate of bug 868176 *** https://bugs.launchpad.net/bugs/868176 ** This bug is no longer a duplicate of bug 865219 update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links ** This bug has been marked a duplicate of bug 868176 package lightdm-gtk-greeter 1.0.1-0ubuntu1 failed to install/upgrade: lightdm-gtk-greeter: config file '/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf' is a circular link -- 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/865221 Title: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: sub-processo script post-installation instalado retornou estado de saída de erro 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/865221/+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 865219] Re: update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links
*** This bug is a duplicate of bug 868176 *** https://bugs.launchpad.net/bugs/868176 ** This bug has been marked a duplicate of bug 868176 package lightdm-gtk-greeter 1.0.1-0ubuntu1 failed to install/upgrade: lightdm-gtk-greeter: config file '/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf' is a circular link -- 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/865219 Title: update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk- greeter-ubuntu.conf: Too many levels of symbolic links To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/865219/+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 867571] Re: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 868176 *** https://bugs.launchpad.net/bugs/868176 ** This bug is no longer a duplicate of bug 865219 update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links ** This bug has been marked a duplicate of bug 868176 package lightdm-gtk-greeter 1.0.1-0ubuntu1 failed to install/upgrade: lightdm-gtk-greeter: config file '/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf' is a circular link -- 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/867571 Title: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/867571/+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 865832] Re: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2
*** This bug is a duplicate of bug 868176 *** https://bugs.launchpad.net/bugs/868176 ** This bug is no longer a duplicate of bug 865219 update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links ** This bug has been marked a duplicate of bug 868176 package lightdm-gtk-greeter 1.0.1-0ubuntu1 failed to install/upgrade: lightdm-gtk-greeter: config file '/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf' is a circular link -- 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/865832 Title: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/865832/+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 613619] Re: qemu-kvm misinterprets LVM volume geometry
Serge, sorry, can't tell. I did not install any new virtual machine for some time. The existing ones are running reliably (see above). So I actually don't know whether this problem still exists. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu-kvm in Ubuntu. https://bugs.launchpad.net/bugs/613619 Title: qemu-kvm misinterprets LVM volume geometry To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/613619/+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 867574] Re: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 868176 *** https://bugs.launchpad.net/bugs/868176 ** This bug is no longer a duplicate of bug 865219 update-alternatives: error: cannot stat /etc/lightdm/lightdm-gtk-greeter-ubuntu.conf: Too many levels of symbolic links ** This bug has been marked a duplicate of bug 868176 package lightdm-gtk-greeter 1.0.1-0ubuntu1 failed to install/upgrade: lightdm-gtk-greeter: config file '/etc/lightdm/lightdm-gtk-greeter-ubuntu.conf' is a circular link -- 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/867574 Title: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/867574/+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 865219] Re: update-alternatives problem with lightdm-gtk-greeter
** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Changed in: lightdm (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/865219 Title: update-alternatives problem with lightdm-gtk-greeter To manage notifications about this bug go to: https://bugs.launchpad.net/lightdm/+bug/865219/+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 867571] Re: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 865219 *** https://bugs.launchpad.net/bugs/865219 ** This bug has been marked a duplicate of bug 865219 update-alternatives problem with lightdm-gtk-greeter -- 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/867571 Title: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/867571/+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 867574] Re: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2
*** This bug is a duplicate of bug 865219 *** https://bugs.launchpad.net/bugs/865219 ** This bug is no longer a duplicate of bug 867571 package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 ** This bug has been marked a duplicate of bug 865219 update-alternatives problem with lightdm-gtk-greeter -- 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/867574 Title: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: subprocess installed post-installation script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/867574/+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 865832] Re: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2
*** This bug is a duplicate of bug 865219 *** https://bugs.launchpad.net/bugs/865219 ** This bug has been marked a duplicate of bug 865219 update-alternatives problem with lightdm-gtk-greeter -- 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/865832 Title: package samba-common-bin 2:3.5.11~dfsg-1ubuntu2 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/865832/+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 866565] Re: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: subprocess new post-removal script returned error exit status 2
*** This bug is a duplicate of bug 862129 *** https://bugs.launchpad.net/bugs/862129 ** This bug has been marked a duplicate of bug 862129 package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: subprocess new post-removal script returned error exit status 2 -- 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/866565 Title: package samba 2:3.5.8~dfsg-1ubuntu2.3 failed to install/upgrade: ErrorMessage: subprocess new post-removal script returned error exit status 2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/866565/+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 522710] Re: libvirtd does not have a man page
** Changed in: libvirt (Debian) Status: Unknown => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libvirt in Ubuntu. https://bugs.launchpad.net/bugs/522710 Title: libvirtd does not have a man page To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/522710/+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 868538] Re: /etc/init.d/xinetd kills LXC container's xinetd
The attachment "xinetd.patch" of this bug report has been identified as being a patch. The ubuntu-reviewers team has been subscribed to the bug report so that they can review the patch. In the event that this is in fact not a patch you can resolve this situation by removing the tag 'patch' from the bug report and editing the attachment so that it is not flagged as a patch. Additionally, if you are member of the ubuntu- sponsors please also unsubscribe the team from this bug report. [This is an automated message performed by a Launchpad user owned by Brian Murray. Please contact him regarding any issues with the action taken in this bug report.] ** Tags added: patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/868538 Title: /etc/init.d/xinetd kills LXC container's xinetd To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/868538/+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 868538] Re: /etc/init.d/xinetd kills LXC container's xinetd
** Also affects: lxc Importance: Undecided Status: New ** Patch added: "xinetd.patch" https://bugs.launchpad.net/lxc/+bug/868538/+attachment/2516322/+files/xinetd.patch -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to xinetd in Ubuntu. https://bugs.launchpad.net/bugs/868538 Title: /etc/init.d/xinetd kills LXC container's xinetd To manage notifications about this bug go to: https://bugs.launchpad.net/lxc/+bug/868538/+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