[Bug 1451807] Re: mod-wsgi not working with Python 3.4
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mod-wsgi in Ubuntu. https://bugs.launchpad.net/bugs/1451807 Title: mod-wsgi not working with Python 3.4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mod-wsgi/+bug/1451807/+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 1446809] Re: denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Changed in: openldap (Debian) Status: Unknown = Fix Released -- 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/1446809 Title: denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+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 1366997] Re: Duplicate entry error for primary key following cluster size change
** Changed in: percona-cluster (Juju Charms Collection) Assignee: Edward Hope-Morley (hopem) = Mario Splivalo (mariosplivalo) ** Changed in: percona-cluster (Juju Charms Collection) Milestone: None = 15.04 ** Changed in: percona-cluster (Juju Charms Collection) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1366997 Title: Duplicate entry error for primary key following cluster size change To manage notifications about this bug go to: https://bugs.launchpad.net/codership-mysql/+bug/1366997/+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 1452237] [NEW] Powernap fails to start using systemctl ubuntu 15.04
Public bug reported: 1) lsb_release -rd Description:Ubuntu 15.04 Release:15.04 2)powernap: Installed: 2.21-0ubuntu1 Candidate: 2.21-0ubuntu1 Version table: *** 2.21-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3)the ability to stop and start powwernap when required 4) powernap starts on boot but doens't start after being stop via systemctl stop powernap Having upgraded from 14.10 to 15.04, powernap starts on boot but cannot be started via systemctl start powernap or service powernap start. the pwernap.service has a require network.service but my ubuntu 15.04 doesn't have one - insteasd it has network.target? are these the same - no idea. the contents of journalctl -xe from during boot are user@machine name:/var/log$ sudo journalctl -xe | grep powernap May 06 08:14:20 machine nameCRON[1330]: (root) CMD (/home/dub/Copy/scripts/nas/powernapSTART.sh) May 06 08:14:21 machine namesudo[1364]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/test -e /var/run/powernap.pid May 06 08:14:21 machine name sudo[1372]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start powernap -- Subject: Unit powernap.service has begun start-up -- Unit powernap.service has begun starting up. -- Subject: Unit powernap.service has finished start-up -- Unit powernap.service has finished starting up. Here is the process i follow from powernap running after startup stopping it via systemctl and then trying to start it again username@machinename:/var/log$ sudo journalctl -xe | grep powernap May 06 08:14:20 machinename CRON[1330]: (root) CMD (/home/username/Copy/scripts/nas/powernapSTART.sh) May 06 08:14:21 machinename sudo[1364]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/test -e /var/run/powernap.pid May 06 08:14:21 machinename sudo[1372]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start powernap -- Subject: Unit powernap.service has begun start-up -- Unit powernap.service has begun starting up. -- Subject: Unit powernap.service has finished start-up -- Unit powernap.service has finished starting up. May 06 08:46:25 machinename sudo[7103]: username : TTY=pts/0 ; PWD=/home/username ; USER=root ; COMMAND=/bin/systemctl status powernap -l username@machinename:/var/log$ ps -ef | grep powernap root 1702 1 2 08:14 ?00:03:38 /usr/bin/python /usr/sbin/powernapd username 23367 20992 0 11:10 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ clear username@machinename:/var/log$ ps -ef | grep powernap root 1702 1 2 08:14 ?00:03:39 /usr/bin/python /usr/sbin/powernapd username 23392 20992 0 11:10 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ ls /var/run/ acpid.socket ConsoleKit crond.reboot docker.pid initctl log mount pm-utils resolvconfrpc_pipefs screen sshd.pid tmpfiles.d uuidd apache2 console-kit-daemon.pid dbus docker.sock initramfs lvm mysqldpowernap rpcbind rsyslogd.pid sendsigs.omit.d sysconfig udevwatershed atd.pid couchpotato dmeventd-client headphones irqbalance.pid minidlna network powernap.pid rpcbind.lock sabnzbdplus shm systemduser avahi-daemon crond.pid dmeventd-server htpcmanager.pid lock motd.dynamic ntpd.pid pppconfig rpcbind.sock samba sshd thermald utmp username@machinename:/var/log$ more /var/run/powernap.pid 1702 username@machinename:/var/log$ sudo systemctl stop powernap username@machinename:/var/log$ ps -ef | grep powernap username 23728 20992 0 11:13 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ more /var/run/powernap.pid /var/run/powernap.pid: No such file or directory username@machinename:/var/log$ sudo systemctl start powernap username@machinename:/var/log$ ps -ef | grep powernap username 23768 20992 0 11:14 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ more /var/run/powernap.pid 23758 username@machinename:/var/log$ sudo systemctl status powernap â powernap.service - PowerNap Loaded: loaded (/lib/systemd/system/powernap.service; disabled; vendor preset: enabled) Active: inactive (dead) May 06 11:11:32 machinename systemd[1]: Stopping PowerNap... May 06 11:11:32 machinename powerwake-now[23536]: Sending powernap the 'wakeup' signal May 06 11:13:02 machinename systemd[1]: powernap.service stop-sigterm timed out. Killing. May 06 11:13:02 machinename systemd[1]: powernap.service: main process exited, code=killed, status=9/KILL May 06 11:13:02 machinename systemd[1]: Stopped PowerNap. May 06 11:13:02 machinename systemd[1]: Unit powernap.service entered failed state. May 06 11:13:02 machinename
[Bug 1446809] Re: denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Description changed: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] TBD [Other Info] - + * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html + * Patches backported: + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) -- 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/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+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 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes
Thanks Chris, Doing that right now and re-attaching debdiffs for Vivid. Thanks for reviewing all this. -Rafael ** Patch removed: vivid_libibverbs_1.1.8-1ubuntu2.debdiff https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4388003/+files/vivid_libibverbs_1.1.8-1ubuntu2.debdiff ** Patch removed: vivid_libmlx4_1.0.6-1ubuntu1.debdiff https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4388004/+files/vivid_libmlx4_1.0.6-1ubuntu1.debdiff ** Patch removed: vivid_tgt_1.0.43-0ubuntu5.debdiff https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4388005/+files/vivid_tgt_1.0.43-0ubuntu5.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1409904/+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 1450091] Re: tgt does not auto-start on Vivid
Ah, ugly, it seems that sudo systemctl enable tgt does work, even though some parts fail: dooferlad@homework2:/etc$ sudo systemctl enable tgt Synchronizing state for tgt.service with sysvinit using update-rc.d... Executing /usr/sbin/update-rc.d tgt defaults Executing /usr/sbin/update-rc.d tgt enable Failed to execute operation: No such file or directory tgt is now starting. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1450091 Title: tgt does not auto-start on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1450091/+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 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Patch added: lp1446809_precise.debdiff https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+attachment/4392199/+files/lp1446809_precise.debdiff -- 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/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+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 1452237] Re: Powernap fails to start using systemctl ubuntu 15.04
reinstalled the package using sudo apt-get --reinstall install powernap hewre is the output:- username@machinename:~/scripts$ ps -ef | grep powernap root 1892 1 1 11:27 ?00:03:36 /usr/bin/python /usr/sbin/powernapd username 25396 6158 0 14:33 pts/000:00:00 grep --color=auto powernap username@machinename:~/scripts$ sudo systemctl status powernapclear â powernapclear.service Loaded: not-found (Reason: No such file or directory) Active: inactive (dead) username@machinename:~/scripts$ clear username@machinename:~/scripts$ sudo systemctl status powernap â powernap.service - PowerNap Loaded: loaded (/lib/systemd/system/powernap.service; enabled; vendor preset: enabled) Active: active (running) since Wed 2015-05-06 11:27:17 BST; 3h 6min ago Main PID: 1892 (powernapd) CGroup: /system.slice/powernap.service ââ1892 /usr/bin/python /usr/sbin/powernapd May 06 11:27:16 machinename systemd[1]: Starting PowerNap... May 06 11:27:17 machinename systemd[1]: Started PowerNap. username@machinename:~/scripts$ ps -ef | grep powernap root 1892 1 1 11:27 ?00:03:37 /usr/bin/python /usr/sbin/powernapd username 25429 6158 0 14:33 pts/000:00:00 grep --color=auto powernap username@machinename:~/scripts$ more /var/run/powernap.pid 1892 username@machinename:~/scripts$ sudo systemctl stop powernap username@machinename:~/scripts$ ps -ef | grep powernap username 25595 6158 0 14:35 pts/000:00:00 grep --color=auto powernap username@machinename:~/scripts$ more /var/run/powernap.pid /var/run/powernap.pid: No such file or directory username@machinename:~/scripts$ sudo systemctl status powernap â powernap.service - PowerNap Loaded: loaded (/lib/systemd/system/powernap.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Wed 2015-05-06 14:35:23 BST; 29s ago Process: 25489 ExecStop=/usr/sbin/powerwake-now (code=exited, status=0/SUCCESS) Main PID: 1892 (code=killed, signal=KILL) May 06 11:27:16 machinename systemd[1]: Starting PowerNap... May 06 11:27:17 machinename systemd[1]: Started PowerNap. May 06 14:33:53 machinename systemd[1]: Stopping PowerNap... May 06 14:33:53 machinename powerwake-now[25489]: Sending powernap the 'wakeup' signal May 06 14:35:23 machinename systemd[1]: powernap.service stop-sigterm timed out. ...g. May 06 14:35:23 machinename systemd[1]: powernap.service: main process exited, co...LL May 06 14:35:23 machinename systemd[1]: Stopped PowerNap. May 06 14:35:23 machinename systemd[1]: Unit powernap.service entered failed state. May 06 14:35:23 machinename systemd[1]: powernap.service failed. Hint: Some lines were ellipsized, use -l to show in full. username@machinename:~/scripts$ sudo systemctl status powernap -l â powernap.service - PowerNap Loaded: loaded (/lib/systemd/system/powernap.service; enabled; vendor preset: enabled) Active: failed (Result: signal) since Wed 2015-05-06 14:35:23 BST; 32s ago Process: 25489 ExecStop=/usr/sbin/powerwake-now (code=exited, status=0/SUCCESS) Main PID: 1892 (code=killed, signal=KILL) May 06 11:27:16 machinename systemd[1]: Starting PowerNap... May 06 11:27:17 machinename systemd[1]: Started PowerNap. May 06 14:33:53 machinename systemd[1]: Stopping PowerNap... May 06 14:33:53 machinename powerwake-now[25489]: Sending powernap the 'wakeup' signal May 06 14:35:23 machinename systemd[1]: powernap.service stop-sigterm timed out. Killing. May 06 14:35:23 machinename systemd[1]: powernap.service: main process exited, code=killed, status=9/KILL May 06 14:35:23 machinename systemd[1]: Stopped PowerNap. May 06 14:35:23 machinename systemd[1]: Unit powernap.service entered failed state. May 06 14:35:23 machinename systemd[1]: powernap.service failed. username@machinename:~/scripts$ sudo systemctl start powernap -l Failed to start powernap.service: Unit network.service failed to load: No such file or directory. username@machinename:~/scripts$ sudo service powernap start Failed to start powernap.service: Unit network.service failed to load: No such file or directory. username@machinename:~/scripts$ -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to powernap in Ubuntu. https://bugs.launchpad.net/bugs/1452237 Title: Powernap fails to start using systemctl ubuntu 15.04 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/powernap/+bug/1452237/+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 1451232] Re: container does not receive IP address after 15.04 upgrade
And, so far, these steps are needed each time I reboot. 2 reboots after initial success. As you suggested, stopping and restarting the lxc-net systemd job is necessary. Just starting it does not work. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1451232 Title: container does not receive IP address after 15.04 upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1451232/+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 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes
vivid_tgt_1.0.43-0ubuntu4.1.debdiff ** Patch added: vivid_tgt_1.0.43-0ubuntu4.1.debdiff https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4392210/+files/vivid_tgt_1.0.43-0ubuntu4.1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1409904/+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 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes
vivid_libibverbs_1.1.8-1ubuntu1.1.debdiff ** Patch added: vivid_libibverbs_1.1.8-1ubuntu1.1.debdiff https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4392208/+files/vivid_libibverbs_1.1.8-1ubuntu1.1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1409904/+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 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes
Re-attaching vivid debdiffs (with corrections proposed by Chris Arges) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1409904/+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 1409904] Re: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes
vivid_libmlx4_1.0.6-1ubuntu0.1.debdiff ** Patch added: vivid_libmlx4_1.0.6-1ubuntu0.1.debdiff https://bugs.launchpad.net/ubuntu/+source/libibverbs/+bug/1409904/+attachment/4392209/+files/vivid_libmlx4_1.0.6-1ubuntu0.1.debdiff -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libibverbs in Ubuntu. https://bugs.launchpad.net/bugs/1409904 Title: Needed patches for InfiniBand Support: Flow Steering and Offload Support + Fixes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/corosync/+bug/1409904/+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 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Summary changed: - denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) + [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) -- 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/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+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 1450091] Re: tgt does not auto-start on Vivid
Thank you for taking the time to report this bug and helping to make Ubuntu better. Some parts failing is bug 1447807, but perhaps tgt not starting by default is a separate bug, so leaving this open for now. ** Tags added: systemd-boot -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tgt in Ubuntu. https://bugs.launchpad.net/bugs/1450091 Title: tgt does not auto-start on Vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tgt/+bug/1450091/+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 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Description changed: [Impact] * slapd in OpenLDAP before 2.4.30 allows remote attackers to cause a denial of service (assertion failure and daemon exit) via an LDAP search query with attrsOnly set to true, which causes empty attributes to be returned. * Trusty ships 2.4.31 which comes with a fix for this. [Test Case] TBD [Regression Potential] - TBD + * this set of patches adds validations to avoid segfaults, so no + regression is expected. [Other Info] * Upstream bug report http://www.openldap.org/its/index.cgi/Software%2520Bugs?id=7143 * http://people.canonical.com/~ubuntu-security/cve/2012/CVE-2012-1164.html * Patches backported: - - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) - - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) - - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=ef2f5263de8802794e528cc2648ecfca369302ae (p1) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=430256fafb85028443d7964a5ab1f4bbf8b2db38 (p2) + - http://www.openldap.org/devel/gitweb.cgi?p=openldap.git;a=commit;h=463c1fa25d45e393dc1f1ea235286f79e872fad0 (p3) -- 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/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+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 1452457] Re: Please import golang-1.4.2 from debian/sid
*** This bug is a duplicate of bug 1362741 *** https://bugs.launchpad.net/bugs/1362741 This will need a merge as Ubuntu currently has a delta against Debian on golang. Matthias, can you take care of this please or do you need someone else to contribute the merge? Dave, I could but the current state is sufficient - without a release- specific bug task we mean the development release. ** This bug has been marked a duplicate of bug 1362741 update golang packages to 1.4.2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1452457 Title: Please import golang-1.4.2 from debian/sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457/+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 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
** Tags added: sts -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+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 1452457] Re: Please import golang-1.4.2 from debian/sid
*** This bug is a duplicate of bug 1362741 *** https://bugs.launchpad.net/bugs/1362741 On 05/07/2015 01:11 AM, Robie Basak wrote: *** This bug is a duplicate of bug 1362741 *** https://bugs.launchpad.net/bugs/1362741 This will need a merge as Ubuntu currently has a delta against Debian on golang. Matthias, can you take care of this please or do you need someone else to contribute the merge? sorry, other priorities at the moment. feel free to steal the merge. don't drop the fake packages yet. not a final solution, but we shouldn't regress. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1452457 Title: Please import golang-1.4.2 from debian/sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457/+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 1362741] Re: update golang packages to 1.4.2
** Tags added: upgrade-software-version ** Changed in: golang (Ubuntu) Status: Confirmed = Triaged ** Changed in: golang (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1362741 Title: update golang packages to 1.4.2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1362741/+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 1007273] Re: autofs does not start automatically after reboot
I've had this problem with every version of Ubuntu up to and including 15.04. Having a system that actually authenticates with NIS and allows automounting when I log in always requires some kind of hack like this. It's really annoying. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to autofs5 in Ubuntu. https://bugs.launchpad.net/bugs/1007273 Title: autofs does not start automatically after reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/autofs5/+bug/1007273/+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 1450043] Re: spice package for trusty contains a malformed patch
** Also affects: spice (Ubuntu Trusty) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to spice in Ubuntu. https://bugs.launchpad.net/bugs/1450043 Title: spice package for trusty contains a malformed patch To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/spice/+bug/1450043/+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 1443429] Please test proposed package
Hello Chuck, or anyone else affected, Accepted horizon into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/horizon/1:2014.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! -- 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/1443429 Title: [SRU] juno 2014.2.3 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1443429/+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 1443429] Re: [SRU] juno 2014.2.3 point release
Hello Chuck, or anyone else affected, Accepted cinder into utopic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/cinder/1:2014.2.3-0ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: cinder (Ubuntu Utopic) Status: New = Fix Committed ** Changed in: horizon (Ubuntu Utopic) Status: New = 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/1443429 Title: [SRU] juno 2014.2.3 point release To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ceilometer/+bug/1443429/+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 1452237] Re: Powernap fails to start using systemctl ubuntu 15.04
** Description changed: 1) lsb_release -rd Description:Ubuntu 15.04 Release:15.04 2)powernap: Installed: 2.21-0ubuntu1 Candidate: 2.21-0ubuntu1 Version table: *** 2.21-0ubuntu1 0 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages 100 /var/lib/dpkg/status 3)the ability to stop and start powwernap when required 4) powernap starts on boot but doens't start after being stop via systemctl stop powernap Having upgraded from 14.10 to 15.04, powernap starts on boot but cannot be started via systemctl start powernap or service powernap start. the pwernap.service has a require network.service but my ubuntu 15.04 doesn't have one - insteasd it has network.target? are these the same - no idea. the contents of journalctl -xe from during boot are user@machine name:/var/log$ sudo journalctl -xe | grep powernap May 06 08:14:20 machine nameCRON[1330]: (root) CMD (/home/dub/Copy/scripts/nas/powernapSTART.sh) May 06 08:14:21 machine namesudo[1364]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/test -e /var/run/powernap.pid May 06 08:14:21 machine name sudo[1372]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start powernap -- Subject: Unit powernap.service has begun start-up -- Unit powernap.service has begun starting up. -- Subject: Unit powernap.service has finished start-up -- Unit powernap.service has finished starting up. Here is the process i follow from powernap running after startup stopping it via systemctl and then trying to start it again username@machinename:/var/log$ sudo journalctl -xe | grep powernap May 06 08:14:20 machinename CRON[1330]: (root) CMD (/home/username/Copy/scripts/nas/powernapSTART.sh) May 06 08:14:21 machinename sudo[1364]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/test -e /var/run/powernap.pid May 06 08:14:21 machinename sudo[1372]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start powernap -- Subject: Unit powernap.service has begun start-up -- Unit powernap.service has begun starting up. -- Subject: Unit powernap.service has finished start-up -- Unit powernap.service has finished starting up. May 06 08:46:25 machinename sudo[7103]: username : TTY=pts/0 ; PWD=/home/username ; USER=root ; COMMAND=/bin/systemctl status powernap -l username@machinename:/var/log$ ps -ef | grep powernap root 1702 1 2 08:14 ?00:03:38 /usr/bin/python /usr/sbin/powernapd username 23367 20992 0 11:10 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ clear username@machinename:/var/log$ ps -ef | grep powernap root 1702 1 2 08:14 ?00:03:39 /usr/bin/python /usr/sbin/powernapd username 23392 20992 0 11:10 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ more /var/run/powernap.pid 1702 username@machinename:/var/log$ sudo systemctl stop powernap username@machinename:/var/log$ ps -ef | grep powernap username 23728 20992 0 11:13 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ more /var/run/powernap.pid /var/run/powernap.pid: No such file or directory username@machinename:/var/log$ sudo systemctl start powernap username@machinename:/var/log$ ps -ef | grep powernap username 23768 20992 0 11:14 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ more /var/run/powernap.pid 23758 username@machinename:/var/log$ sudo systemctl status powernap â powernap.service - PowerNap Loaded: loaded (/lib/systemd/system/powernap.service; disabled; vendor preset: enabled) Active: inactive (dead) May 06 11:11:32 machinename systemd[1]: Stopping PowerNap... May 06 11:11:32 machinename powerwake-now[23536]: Sending powernap the 'wakeup' signal May 06 11:13:02 machinename systemd[1]: powernap.service stop-sigterm timed out. Killing. May 06 11:13:02 machinename systemd[1]: powernap.service: main process exited, code=killed, status=9/KILL May 06 11:13:02 machinename systemd[1]: Stopped PowerNap. May 06 11:13:02 machinename systemd[1]: Unit powernap.service entered failed state. May 06 11:13:02 machinename systemd[1]: powernap.service failed. May 06 11:14:03 machinename systemd[1]: Starting PowerNap... May 06 11:14:03 machinename systemd[1]: Started PowerNap. May 06 11:14:03 machinename powerwake-now[23761]: Sending powernap the 'wakeup' signal username@machinename:/var/log$ sudo journalctl -xe | grep powernap May 06 08:14:20 machinename CRON[1330]: (root) CMD (/home/username/Copy/scripts/nas/powernapSTART.sh) May 06 08:14:21 machinename sudo[1364]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/test -e /var/run/powernap.pid May 06 08:14:21 machinename sudo[1372]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start powernap -- Subject:
[Bug 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
I'm seeing this problem in another environment, similar deployment (3 lxc containers) Apr 20 16:39:26 juju-machine-3-lxc-4 crm_verify[31774]: notice: crm_log_args: Invoked: crm_verify -V -p Apr 20 16:39:27 juju-machine-3-lxc-4 cibadmin[31786]: notice: crm_log_args: Invoked: cibadmin -p -P Apr 20 16:50:01 juju-machine-3-lxc-4 cib[780]:error: pcmk_cpg_dispatch: Connection to the CPG API failed: Library error (2) Apr 20 16:50:01 juju-machine-3-lxc-4 cib[780]:error: cib_cs_destroy: Corosync connection lost! Exiting. Apr 20 16:50:01 juju-machine-3-lxc-4 crmd[785]:error: crmd_quorum_destroy: connection terminated Apr 20 16:50:01 juju-machine-3-lxc-4 attrd[783]:error: pcmk_cpg_dispatch: Connection to the CPG API failed: Library error (2) Apr 20 16:50:01 juju-machine-3-lxc-4 stonith-ng[781]:error: pcmk_cpg_dispatch: Connection to the CPG API failed: Library error (2) Apr 20 16:50:01 juju-machine-3-lxc-4 crmd[785]: notice: crmd_exit: Forcing immediate exit: Link has been severed (67) Apr 20 16:50:01 juju-machine-3-lxc-4 lrmd[782]: warning: qb_ipcs_event_sendv: new_event_notification (782-785-6): Bad file descriptor (9) Apr 20 16:50:01 juju-machine-3-lxc-4 lrmd[782]: warning: send_client_notify: Notification of client crmd/8ad990ba-cf09-4ba3-b74b-a7d05d377a1b failed Apr 20 16:50:01 juju-machine-3-lxc-4 lrmd[782]:error: crm_abort: crm_glib_handler: Forked child 760 to record non-fatal assert at logging.c:63 : Source ID 4601370 was not found when attempting to remove it Apr 20 16:50:01 juju-machine-3-lxc-4 pacemakerd[773]:error: pcmk_child_exit: Child process cib (780) exited: Invalid argument (22) Apr 20 16:50:01 juju-machine-3-lxc-4 pacemakerd[773]: notice: pcmk_process_exit: Respawning failed child process: cib Apr 20 16:50:01 juju-machine-3-lxc-4 pacemakerd[773]:error: pcmk_child_exit: Child process crmd (785) exited: Link has been severed (67) Apr 20 16:50:01 juju-machine-3-lxc-4 pacemakerd[773]: notice: pcmk_process_exit: Respawning failed child process: crmd Apr 20 16:50:01 juju-machine-3-lxc-4 attrd[783]: crit: attrd_cs_destroy: Lost connection to Corosync service! Apr 20 16:50:01 juju-machine-3-lxc-4 attrd[783]: notice: main: Exiting... Apr 20 16:50:01 juju-machine-3-lxc-4 attrd[783]: notice: main: Disconnecting client 0x7ff985e478e0, pid=785... Apr 20 16:50:01 juju-machine-3-lxc-4 pacemakerd[773]:error: pcmk_cpg_dispatch: Connection to the CPG API failed: Library error (2) Apr 20 16:50:01 juju-machine-3-lxc-4 pacemakerd[773]:error: mcp_cpg_destroy: Connection destroyed Apr 20 16:50:01 juju-machine-3-lxc-4 attrd[783]:error: attrd_cib_connection_destroy: Connection to the CIB terminated... Apr 20 16:50:01 juju-machine-3-lxc-4 cib[761]:debug: crm_update_callsites: Enabling callsites based on priority=7, files=(null), functions=(null), formats=(null), tags=(null) Apr 20 16:50:01 juju-machine-3-lxc-4 crmd[767]:debug: crm_update_callsites: Enabling callsites based on priority=7, files=(null), functions=(null), formats=(null), tags=(null) Apr 20 16:50:01 juju-machine-3-lxc-4 crmd[767]: notice: main: CRM Git Version: 42f2063 Apr 20 16:50:01 juju-machine-3-lxc-4 stonith-ng[781]:error: stonith_peer_cs_destroy: Corosync connection terminated Apr 20 16:50:01 juju-machine-3-lxc-4 cib[761]: notice: crm_cluster_connect: Connecting to cluster infrastructure: corosync Apr 20 16:50:01 juju-machine-3-lxc-4 cib[761]:error: cluster_connect_cpg: Could not connect to the Cluster Process Group API: 2 Apr 20 16:50:01 juju-machine-3-lxc-4 cib[761]: crit: cib_init: Cannot sign in to the cluster... terminating Apr 20 16:50:02 juju-machine-3-lxc-4 crmd[767]: warning: do_cib_control: Couldn't complete CIB registration 1 times... pause and retry Apr 20 16:50:05 juju-machine-3-lxc-4 crmd[767]: warning: do_cib_control: Couldn't complete CIB registration 2 times... pause and retry These are the only processes running in one of the nodes: root 782 0.0 0.0 81464 1828 ?Ss Feb12 25:13 /usr/lib/pacemaker/lrmd haclust+ 784 0.0 0.0 73920 776 ?Ss Feb12 8:25 /usr/lib/pacemaker/pengine root 780 0.8 0.0 130256 4152 ?Ssl 16:50 0:00 /usr/sbin/corosync A possible explanation could be: http://thread.gmane.org/gmane.linux.highavailability.corosync/592/focus=639 I only have logs for one of the nodes, I'm trying to get logs of the other 2 nodes to get a better understanding of what was happening with the communication. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or
[Bug 1452457] Re: Please import golang-1.4.2 from debian/sid
** Tags added: upgrade-software-version -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1452457 Title: Please import golang-1.4.2 from debian/sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457/+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 1439649] Re: Pacemaker unable to communicate with corosync on restart under lxc
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: lxc (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1439649 Title: Pacemaker unable to communicate with corosync on restart under lxc To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1439649/+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 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using ldapsearch and sasl with ssl or tls
I highly fear that the code cannot be changed that easily because Microsoft screwed up the RFC. The RFC (https://tools.ietf.org/html/rfc4752#section-3.1) says: 3.1. Client Side of Authentication Protocol Exchange The client calls GSS_Init_sec_context, passing in input_context_handle of 0 (initially), mech_type of the Kerberos V5 GSS-API mechanism [KRB5GSS], chan_binding of NULL, and targ_name equal to output_name from GSS_Import_Name called with input_name_type of GSS_C_NT_HOSTBASED_SERVICE (*) and input_name_string of service@hostname where service is the service name specified in the protocol's profile, and hostname is the fully qualified host name of the server. When calling the GSS_Init_sec_context, the client MUST pass the integ_req_flag of TRUE (**). If the client will be requesting a security layer, it MUST also supply to the GSS_Init_sec_context a mutual_req_flag of TRUE, and a sequence_req_flag of TRUE. If the client will be requesting a security layer providing confidentiality protection, it MUST also supply to the GSS_Init_sec_context a conf_req_flag of TRUE. The client then responds with the resulting output_token. If GSS_Init_sec_context returns GSS_S_CONTINUE_NEEDED, then the client should expect the server to issue a token in a subsequent challenge. The client must pass the token to another call to GSS_Init_sec_context, repeating the actions in this paragraph. The Cyrus SASL implementation is correct and Microsoft's is not! Any thoughts? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using ldapsearch and sasl with ssl or tls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+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 1450642] Re: seccomp missing many new syscalls
Since 2.1.1-1ubuntu1~vivid1 is already in wily, I cannot accept this into vivid. Can you change the string in wily to not include ~vivid1 please? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libseccomp in Ubuntu. https://bugs.launchpad.net/bugs/1450642 Title: seccomp missing many new syscalls To manage notifications about this bug go to: https://bugs.launchpad.net/snappy-ubuntu/+bug/1450642/+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 1452457] [NEW] Please import golang-1.4.2 from debian/sid
Public bug reported: Please import golang-1.4.2 from debian/sid into Wily https://packages.debian.org/sid/golang ** Affects: golang (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1452457 Title: Please import golang-1.4.2 from debian/sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457/+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 1452457] Re: Please import golang-1.4.2 from debian/sid
Robie, do you have permissions to target this bug to W only? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to golang in Ubuntu. https://bugs.launchpad.net/bugs/1452457 Title: Please import golang-1.4.2 from debian/sid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/golang/+bug/1452457/+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 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using ldapsearch and sasl with ssl or tls
Here is a follow on the comment above:
I have changes the GSSAPI mech plugin source code:
diff --git a/plugins/gssapi.c b/plugins/gssapi.c
index 2fd1b3b..39302cd 100644
--- a/plugins/gssapi.c
+++ b/plugins/gssapi.c
@@ -1583,20 +1583,9 @@ static int gssapi_client_mech_step(void *conn_context,
}
/* Setup req_flags properly */
- req_flags = GSS_C_INTEG_FLAG;
- if (params-props.max_ssf params-external_ssf) {
- /* We are requesting a security layer */
- req_flags |= GSS_C_MUTUAL_FLAG | GSS_C_SEQUENCE_FLAG;
- /* Any SSF bigger than 1 is confidentiality. */
- /* Let's check if the client of the API requires confidentiality,
- and it wasn't already provided by an external layer */
- if (params-props.max_ssf - params-external_ssf 1) {
- /* We want to try for privacy */
- req_flags |= GSS_C_CONF_FLAG;
- }
- }
-
- if (params-props.security_flags SASL_SEC_PASS_CREDENTIALS) {
+ req_flags = GSS_C_MUTUAL_FLAG;
+
+if (params-props.security_flags SASL_SEC_PASS_CREDENTIALS) {
req_flags = req_flags | GSS_C_DELEG_FLAG;
}
And reran ldapsearch with -ZZ (STARTTLS) and whom, it did work. I tried
without TLS too. Everything is shiny in Wireshark. TLS encrypted data,
fully opaque, unencrypted data, fully browsable.
This code definitively requires polish as long as the SASL RFC is not
violated. I am willing to provide a quality patch for that.
Unfortunately, I have another patch pending on the Cyrus SASL mailing
list w/o any response at the moment. Maybe someone could step up:
http://asg.andrew.cmu.edu/archive/message.php?mailbox=archive.cyrus-
saslmsg=10230
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cyrus-sasl2 in Ubuntu.
https://bugs.launchpad.net/bugs/1015819
Title:
sb_sasl_generic_pkt_length: received illegal packet length when using
ldapsearch and sasl with ssl or tls
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+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 1452237] Re: Powernap fails to start using systemctl ubuntu 15.04
** Description changed: 1) lsb_release -rd Description:Ubuntu 15.04 Release:15.04 2)powernap: - Installed: 2.21-0ubuntu1 - Candidate: 2.21-0ubuntu1 - Version table: - *** 2.21-0ubuntu1 0 - 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages - 100 /var/lib/dpkg/status + Installed: 2.21-0ubuntu1 + Candidate: 2.21-0ubuntu1 + Version table: + *** 2.21-0ubuntu1 0 + 500 http://gb.archive.ubuntu.com/ubuntu/ vivid/main amd64 Packages + 100 /var/lib/dpkg/status 3)the ability to stop and start powwernap when required 4) powernap starts on boot but doens't start after being stop via systemctl stop powernap Having upgraded from 14.10 to 15.04, powernap starts on boot but cannot be started via systemctl start powernap or service powernap start. the pwernap.service has a require network.service but my ubuntu 15.04 doesn't have one - insteasd it has network.target? are these the same - no idea. - the contents of journalctl -xe from during boot are + the contents of journalctl -xe from during boot are user@machine name:/var/log$ sudo journalctl -xe | grep powernap May 06 08:14:20 machine nameCRON[1330]: (root) CMD (/home/dub/Copy/scripts/nas/powernapSTART.sh) May 06 08:14:21 machine namesudo[1364]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/test -e /var/run/powernap.pid May 06 08:14:21 machine name sudo[1372]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start powernap -- Subject: Unit powernap.service has begun start-up -- Unit powernap.service has begun starting up. -- Subject: Unit powernap.service has finished start-up -- Unit powernap.service has finished starting up. Here is the process i follow from powernap running after startup stopping it via systemctl and then trying to start it again username@machinename:/var/log$ sudo journalctl -xe | grep powernap May 06 08:14:20 machinename CRON[1330]: (root) CMD (/home/username/Copy/scripts/nas/powernapSTART.sh) May 06 08:14:21 machinename sudo[1364]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/usr/bin/test -e /var/run/powernap.pid May 06 08:14:21 machinename sudo[1372]: root : TTY=unknown ; PWD=/root ; USER=root ; COMMAND=/bin/systemctl start powernap -- Subject: Unit powernap.service has begun start-up -- Unit powernap.service has begun starting up. -- Subject: Unit powernap.service has finished start-up -- Unit powernap.service has finished starting up. May 06 08:46:25 machinename sudo[7103]: username : TTY=pts/0 ; PWD=/home/username ; USER=root ; COMMAND=/bin/systemctl status powernap -l username@machinename:/var/log$ ps -ef | grep powernap root 1702 1 2 08:14 ?00:03:38 /usr/bin/python /usr/sbin/powernapd username 23367 20992 0 11:10 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ clear username@machinename:/var/log$ ps -ef | grep powernap root 1702 1 2 08:14 ?00:03:39 /usr/bin/python /usr/sbin/powernapd username 23392 20992 0 11:10 pts/000:00:00 grep --color=auto powernap - username@machinename:/var/log$ ls /var/run/ - acpid.socket ConsoleKit crond.reboot docker.pid initctl log mount pm-utils resolvconfrpc_pipefs screen sshd.pid tmpfiles.d uuidd - apache2 console-kit-daemon.pid dbus docker.sock initramfs lvm mysqldpowernap rpcbind rsyslogd.pid sendsigs.omit.d sysconfig udevwatershed - atd.pid couchpotato dmeventd-client headphones irqbalance.pid minidlna network powernap.pid rpcbind.lock sabnzbdplus shm systemduser - avahi-daemon crond.pid dmeventd-server htpcmanager.pid lock motd.dynamic ntpd.pid pppconfig rpcbind.sock samba sshd thermald utmp + username@machinename:/var/log$ more /var/run/powernap.pid 1702 username@machinename:/var/log$ sudo systemctl stop powernap username@machinename:/var/log$ ps -ef | grep powernap username 23728 20992 0 11:13 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ more /var/run/powernap.pid /var/run/powernap.pid: No such file or directory username@machinename:/var/log$ sudo systemctl start powernap username@machinename:/var/log$ ps -ef | grep powernap username 23768 20992 0 11:14 pts/000:00:00 grep --color=auto powernap username@machinename:/var/log$ more /var/run/powernap.pid 23758 username@machinename:/var/log$ sudo systemctl status powernap â powernap.service - PowerNap -Loaded: loaded (/lib/systemd/system/powernap.service; disabled; vendor preset: enabled) -Active: inactive (dead) + Loaded: loaded (/lib/systemd/system/powernap.service; disabled; vendor preset: enabled) + Active: inactive (dead)
[Bug 1452451] [NEW] failed to change apparmor profile to lxc-container-default-with-nesting
Public bug reported: I develop and maintain the unity8-lxc package (lp:unity8-preview-lxc) which uses an unpacked Ubuntu Next Desktop ISO as a privileged rootfs. It uses the lxc-container-default-with-nesting apparmor profile since we'd like to support containers within this. When I try to do a lxc-start. lxc-wait(RUNNING), and lxc-attach for the first time in my setup script, I get the following error: lxc_container: lsm/apparmor.c: apparmor_process_label_set: 183 No such file or directory - failed to change apparmor profile to lxc-container- default-with-nesting I believe this is a race because if I introduce a sleep of say 0.5 seconds between the lxc-wait and lxc-attach, then it works. It also works for any subsequent lxc-start/lxc-wait/lxc-attach after this failure. Please let me know if I can provide more info. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: lxc 1.1.2-0ubuntu3 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Wed May 6 16:47:14 2015 InstallationDate: Installed on 2013-03-18 (779 days ago) InstallationMedia: Ubuntu 12.10 Quantal Quetzal - Release amd64 (20121017.5) SourcePackage: lxc UpgradeStatus: Upgraded to vivid on 2014-10-20 (198 days ago) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1452451 Title: failed to change apparmor profile to lxc-container-default-with- nesting To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1452451/+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 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
** Tags removed: patch -- 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/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+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 1411623] Re: mail -N not working
This bug was fixed in the package bsd-mailx - 8.1.2-0.20141216cvs-2 --- bsd-mailx (8.1.2-0.20141216cvs-2) unstable; urgency=medium * Add 27-Fix-getopt-string.patch to fix `-N' flag that does not take an argument (LP: #1411623). -- Robert Luberda rob...@debian.org Sun, 15 Mar 2015 11:27:33 +0100 ** Changed in: bsd-mailx (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bsd-mailx in Ubuntu. https://bugs.launchpad.net/bugs/1411623 Title: mail -N not working To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/bsd-mailx/+bug/1411623/+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 1015819] Re: sb_sasl_generic_pkt_length: received illegal packet length when using ldapsearch and sasl with ssl or tls
I can confirm that this bug is still present in the most recent versions of OpenLDAP and SASL. Johnny Westerlund's statement is correct but the tip isn't. Here is the deal: https://msdn.microsoft.com/en-us/library/cc223500.aspx Active Directory does not support GSS-API integrity/confidentiality over TLS encrypted sockets. Unfortumately, you cannot disable integrity in SASL. It is enabled by default. maxssf=0 does not work and gives you: ldap_sasl_interactive_bind_s: Local error (-2) additional info: SASL(-1): generic failure: GSSAPI Error: A required input parameter could not be read (Unknown error) Here is the code in question: https://github.com/michael-o/cyrus- sasl/blob/master/plugins/gssapi.c#L1586-L1596 FWIT: This fails on RHEL, FreeBSD and HP-UX, it fails everywhere with MIT Kerberos. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to cyrus-sasl2 in Ubuntu. https://bugs.launchpad.net/bugs/1015819 Title: sb_sasl_generic_pkt_length: received illegal packet length when using ldapsearch and sasl with ssl or tls To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cyrus-sasl2/+bug/1015819/+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 1446809] Re: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164)
The attachment lp1446809_precise.debdiff seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the patch flag from the attachment, remove the patch tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.] ** Tags added: patch -- 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/1446809 Title: [SRU] denial of service via an LDAP search query with attrsOnly set to true (CVE-2012-1164) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1446809/+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 1409639] Re: juju needs to support systemd for = vivid
** Tags added: systemd vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1409639 Title: juju needs to support systemd for = vivid To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1409639/+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 1284641] Re: problem with paths with spaces with 12.04 client with 14.04 server
Is there a timeframe for this fix being included in 14.04? I was able to work around it by recompiling apache with the referenced patch, but it would be great to have fixed in the official packages. -- 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/1284641 Title: problem with paths with spaces with 12.04 client with 14.04 server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1284641/+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 1411582] Re: Azure data source should auto-detect ephemeral disk location
This bug was fixed in the package walinuxagent - 2.0.12-0ubuntu2~14.04.0 --- walinuxagent (2.0.12-0ubuntu2~14.04.0) trusty; urgency=medium * Backport from Ubuntu 15.04 (LP: #1442392): - Support page blob for status blob - Fix extension status on disable success - Update shared config handler -- Ben Howard ben.how...@ubuntu.com Thu, 16 Apr 2015 11:53:56 -0600 ** Changed in: walinuxagent (Ubuntu Trusty) Status: New = Fix Released ** Changed in: walinuxagent (Ubuntu Utopic) Status: New = 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/1411582 Title: Azure data source should auto-detect ephemeral disk location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1411582/+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 1411582] Re: Azure data source should auto-detect ephemeral disk location
This bug was fixed in the package walinuxagent - 2.0.12-0ubuntu2~14.10.0 --- walinuxagent (2.0.12-0ubuntu2~14.10.0) utopic; urgency=medium * Backport from Ubuntu 15.04 (LP: #1442392): - Support page blob for status blob - Fix extension status on disable success - Update shared config handler -- Ben Howard ben.how...@ubuntu.com Thu, 16 Apr 2015 11:53:56 -0600 -- 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/1411582 Title: Azure data source should auto-detect ephemeral disk location To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1411582/+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 1442392] Re: [SRU][FFE] update walinuxagent to 2.0.12
This bug was fixed in the package walinuxagent - 2.0.12-0ubuntu2~14.04.0 --- walinuxagent (2.0.12-0ubuntu2~14.04.0) trusty; urgency=medium * Backport from Ubuntu 15.04 (LP: #1442392): - Support page blob for status blob - Fix extension status on disable success - Update shared config handler -- Ben Howard ben.how...@ubuntu.com Thu, 16 Apr 2015 11:53:56 -0600 ** Changed in: walinuxagent (Ubuntu Trusty) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1442392 Title: [SRU][FFE] update walinuxagent to 2.0.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1442392/+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 1444037] Re: juju-core 1.22.1 is not packaged in Ubuntu
Hello Oleg, or anyone else affected, Accepted juju-core into trusty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/juju- core/1.22.1-0ubuntu0.14.04.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance! ** Changed in: juju-core (Ubuntu Trusty) Status: In Progress = Fix Committed ** Tags added: verification-needed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1444037 Title: juju-core 1.22.1 is not packaged in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1444037/+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 1442392] Re: [SRU][FFE] update walinuxagent to 2.0.12
This bug was fixed in the package walinuxagent - 2.0.12-0ubuntu2~14.10.0 --- walinuxagent (2.0.12-0ubuntu2~14.10.0) utopic; urgency=medium * Backport from Ubuntu 15.04 (LP: #1442392): - Support page blob for status blob - Fix extension status on disable success - Update shared config handler -- Ben Howard ben.how...@ubuntu.com Thu, 16 Apr 2015 11:53:56 -0600 ** Changed in: walinuxagent (Ubuntu Utopic) Status: Fix Committed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1442392 Title: [SRU][FFE] update walinuxagent to 2.0.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1442392/+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 1442392] Update Released
The verification of the Stable Release Update for walinuxagent has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to walinuxagent in Ubuntu. https://bugs.launchpad.net/bugs/1442392 Title: [SRU][FFE] update walinuxagent to 2.0.12 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/walinuxagent/+bug/1442392/+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 1452402] [NEW] getrandom() stucks when process has no read permission on /dev/urandom
Public bug reported:
ubuntu-core/15.04/edge
armhf
getrandom() stucks when process has no read permission on /dev/urandom.
It should return an error.
Easy example to reproduce in golang:
//
package main
import (
crypto/rand
io
)
func main() {
p := make([]byte, 16)
if _, err := io.ReadFull(rand.Reader, p); err != nil { // --- stuck!
println(err)
return
}
println(p)
}
//
The internal implementation of reading from rand.Reader contains getrandom()
syscall:
https://golang.org/src/crypto/rand/rand_linux.go
** Affects: ubuntu
Importance: Undecided
Status: New
** Information type changed from Private Security to Public
** Package changed: libseccomp (Ubuntu) = ubuntu
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to libseccomp in Ubuntu.
https://bugs.launchpad.net/bugs/1452402
Title:
getrandom() stucks when process has no read permission on /dev/urandom
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+bug/1452402/+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 1452087] Re: slapd [or its init script] does not create necessary directory for nssov socket and fails to start
there was an apparmor message logged:
May 6 22:52:05 server kernel: audit: type=1400
audit(1430967118.381:12): apparmor=DENIED operation=mkdir
profile=/usr/sbin/slapd name=/run/nslcd/ pid=1419 comm=slapd
requested_mask=c denied_mask=c fsuid=108 ouid=108
adding to /etc/apparmor.d/local/usr.sbin.slapd [among some other
things]:
/etc/ldap/pki/** rw,
/{,var/}run/slapd/* rw,
/{,var/}run/nslcd/ rw,
/{,var/}run/nslcd/* rw,
seems to have addressed that, but the directory still isn't created.
temporarily changing /run/ to 777 seem to reinforce rtandy's reference.
the directory is then created, but not with adequate permissions:
dr-xr-xr-x 2 openldap openldap 40 May 6 23:01 nslcd/
slapd[2357]: nssov: bind() to /var/run/nslcd/socket failed: Permission
denied
adjusting them manually after creation confirms this, and slapd then
starts.
at the moment, i've added the following to the init script:
NSSOV_SOCKETDIR='/var/run/nslcd'
start_slapd() {
[ -d ${NSSOV_SOCKETDIR} ] || ( mkdir -m 755 ${NSSOV_SOCKETDIR} ; \
chown openldap.openldap ${NSSOV_SOCKETDIR} )
which solves the problem for me [albeit the wrong way, imo], since it's
blindly doing it regardless of if the overlay is actually in use.
--
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/1452087
Title:
slapd [or its init script] does not create necessary directory for
nssov socket and fails to start
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openldap/+bug/1452087/+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 1452312] [NEW] glance-registry process spins if rsyslog restarted with syslog logging enabled
Public bug reported:
When configured to log to syslog, if the rsyslog process is restarted,
then the glance-registry process goes into a spin, consuming 100% of CPU
- strace:
poll([{fd=3, events=POLLOUT|POLLERR|POLLHUP}, {fd=5,
events=POLLIN|POLLPRI|POLLERR|POLLHUP}], 2, 6) = 1 ([{fd=3,
revents=POLLOUT}])
sendto(3, 142015-05-06 14:58:16.186 2579..., 112, 0, NULL, 0) = -1 ENOTCONN
(Transport endpoint is not connected)
gettimeofday({1430924440, 430244}, NULL) = 0
poll([{fd=3, events=POLLOUT|POLLERR|POLLHUP}, {fd=5,
events=POLLIN|POLLPRI|POLLERR|POLLHUP}], 2, 6) = 1 ([{fd=3,
revents=POLLOUT}])
sendto(3, 142015-05-06 14:58:16.186 2579..., 112, 0, NULL, 0) = -1 ENOTCONN
(Transport endpoint is not connected)
This maybe related to bug 1081022 but that should have only impacted
12.04 deployments.
ProblemType: Bug
DistroRelease: Ubuntu 14.04
Package: glance-registry 1:2014.1.4-0ubuntu2
ProcVersionSignature: User Name 3.13.0-51.84-generic 3.13.11-ckt18
Uname: Linux 3.13.0-51-generic x86_64
ApportVersion: 2.14.1-0ubuntu3.10
Architecture: amd64
Date: Wed May 6 15:00:00 2015
Ec2AMI: ami-0350
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small.osci
Ec2Kernel: aki-0002
Ec2Ramdisk: ari-0002
PackageArchitecture: all
SourcePackage: glance
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.glance.glance.registry.conf: [deleted]
modified.conffile..etc.glance.glance.registry.paste.ini: [deleted]
** Affects: glance (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images trusty
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to glance in Ubuntu.
https://bugs.launchpad.net/bugs/1452312
Title:
glance-registry process spins if rsyslog restarted with syslog logging
enabled
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/glance/+bug/1452312/+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 1452312] Re: glance-registry process spins if rsyslog restarted with syslog logging enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glance (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1452312 Title: glance-registry process spins if rsyslog restarted with syslog logging enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1452312/+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 1452312] Re: glance-registry process spins if rsyslog restarted with syslog logging enabled
Raising a task for eventlet as this appears to be related to https://gist.github.com/temoto/8259860 ** Also affects: python-eventlet (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to glance in Ubuntu. https://bugs.launchpad.net/bugs/1452312 Title: glance-registry process spins if rsyslog restarted with syslog logging enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1452312/+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 1452312] Re: glance-registry process spins if rsyslog restarted with syslog logging enabled
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: python-eventlet (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1452312 Title: glance-registry process spins if rsyslog restarted with syslog logging enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1452312/+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 1452312] Re: glance-registry process spins if rsyslog restarted with syslog logging enabled
I'm reticent to pull in the patch detail in #3 as this is not upstream - the codebase in the master branch is fundamentally the same as that found in eventlet in 14.04. ** Changed in: python-eventlet (Ubuntu) Importance: Undecided = High ** Changed in: glance (Ubuntu) Importance: Undecided = High ** Also affects: python-eventlet (Ubuntu Wily) Importance: High Status: Confirmed ** Also affects: glance (Ubuntu Wily) Importance: High Status: Confirmed ** Also affects: python-eventlet (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: glance (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: python-eventlet (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: glance (Ubuntu Trusty) Importance: Undecided Status: New ** Also affects: python-eventlet (Ubuntu Vivid) Importance: Undecided Status: New ** Also affects: glance (Ubuntu Vivid) Importance: Undecided Status: New ** No longer affects: glance (Ubuntu) ** Changed in: glance (Ubuntu Trusty) Status: New = Invalid ** Changed in: glance (Ubuntu Utopic) Status: New = Invalid ** Changed in: glance (Ubuntu Vivid) Status: New = Invalid ** Changed in: glance (Ubuntu Wily) Status: Confirmed = Invalid ** Changed in: python-eventlet (Ubuntu Trusty) Status: New = Confirmed ** Changed in: python-eventlet (Ubuntu Trusty) Importance: Undecided = High ** Changed in: python-eventlet (Ubuntu Wily) Status: Confirmed = New ** Changed in: python-eventlet (Ubuntu Vivid) Importance: Undecided = High ** Changed in: python-eventlet (Ubuntu Utopic) Importance: Undecided = High ** Changed in: glance (Ubuntu Wily) Importance: High = Undecided -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1452312 Title: glance-registry process spins if rsyslog restarted with syslog logging enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1452312/+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 1452318] [NEW] Faulty behavior when resuming from suspend
Public bug reported: Waking from suspend, everything seems normal, except the graphical elements and text on my desktop are not drawn properly. Sometimes, moving the mouse over icons can cause them to be redrawn, sometimes not. It appears not to matter how I initiate the suspend (e.g. by closing laptop lid, or by calling pm-suspend explicitly) and it appears not to matter whether I am using an external display or the laptop's own screen. All other hardware appears to be working, and I can restart the laptop by clicking where the icons ought to be. The only symptom seems to be that the drawing does not happen correctly. I'm not sure what additional information I should provide to help diagnose the problem, so please advise me. Also, if this is more likely to be a xfce issue, then please change the package on the bug report. ProblemType: Bug DistroRelease: Ubuntu 15.04 Package: pm-utils 1.4.1-15 ProcVersionSignature: Ubuntu 3.19.0-16.16-generic 3.19.3 Uname: Linux 3.19.0-16-generic x86_64 NonfreeKernelModules: openafs ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CurrentDesktop: XFCE Date: Wed May 6 17:17:51 2015 InstallationDate: Installed on 2015-05-04 (1 days ago) InstallationMedia: Xubuntu 15.04 Vivid Vervet - Release amd64 (20150422.1) PackageArchitecture: all SourcePackage: pm-utils UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: pm-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug vivid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pm-utils in Ubuntu. https://bugs.launchpad.net/bugs/1452318 Title: Faulty behavior when resuming from suspend To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pm-utils/+bug/1452318/+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 1452558] Re: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build
** Tags removed: need-duplicate-check -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1452558 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1452558/+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 1028682] Re: precise uec builds eat 100% cpu on launch, check-apt and rsyslogd
[Expired for cloud-init (Ubuntu) because there has been no activity for 60 days.] ** Changed in: cloud-init (Ubuntu) Status: Incomplete = Expired -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to the bug report. https://bugs.launchpad.net/bugs/1028682 Title: precise uec builds eat 100% cpu on launch, check-apt and rsyslogd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1028682/+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 1452558] [NEW] openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build
Public bug reported: paxterra@reshma:~$ sudo apt-get 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. 1 not fully installed or removed. After this operation, 0 B of additional disk space will be used. Do you want to continue? [Y/n] y Setting up rabbitmq-server (3.2.4-1) ... chown: cannot access ‘/var/lib/rabbitmq’: No such file or directory dpkg: error processing package rabbitmq-server (--configure): subprocess installed post-installation script returned error exit status 1 Errors were encountered while processing: rabbitmq-server E: Sub-process /usr/bin/dpkg returned an error code (1) paxterra@reshma:~$ ProblemType: Package DistroRelease: Ubuntu 14.04 Package: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1 ProcVersionSignature: Ubuntu 3.13.0-52.85-generic 3.13.11-ckt18 Uname: Linux 3.13.0-52-generic x86_64 ApportVersion: 2.14.1-0ubuntu3.10 Architecture: amd64 DKMSKernelVersion: 3.13.0-52-generic Date: Thu May 7 10:39:58 2015 DuplicateSignature: dkms:openvswitch-datapath-dkms:2.0.2-0ubuntu0.14.04.1:configure: error: Linux kernel in /lib/modules/3.13.0-52-generic/build is version 3.13.11, but version newer than 3.12.x is not supported InstallationDate: Installed on 2015-02-16 (79 days ago) InstallationMedia: Ubuntu-Server 14.04.1 LTS Trusty Tahr - Release amd64 (20140722.3) PackageArchitecture: all PackageVersion: 2.0.2-0ubuntu0.14.04.1 SourcePackage: openvswitch Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openvswitch (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvswitch in Ubuntu. https://bugs.launchpad.net/bugs/1452558 Title: openvswitch-datapath-dkms 2.0.2-0ubuntu0.14.04.1: openvswitch kernel module failed to build To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvswitch/+bug/1452558/+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 1452312] Re: glance-registry process spins if rsyslog restarted with syslog logging enabled
Also confirmed with kilo - using eventlet 0.16.0 ** Changed in: python-eventlet (Ubuntu Vivid) Status: New = Confirmed ** Changed in: python-eventlet (Ubuntu Wily) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-eventlet in Ubuntu. https://bugs.launchpad.net/bugs/1452312 Title: glance-registry process spins if rsyslog restarted with syslog logging enabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-eventlet/+bug/1452312/+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
