[Bug 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
Sure thing: $ sudo systemctl status ssh [sudo] password for andrewta: ● ssh.service - OpenBSD Secure Shell server Loaded: loaded (/lib/systemd/system/ssh.service; enabled; vendor preset: enabled) Active: failed (Result: start-limit) since Wed 2016-02-24 14:44:04 CST; 20s ago Process: 918 ExecStart=/usr/sbin/sshd -D $SSHD_OPTS (code=exited, status=255) Main PID: 918 (code=exited, status=255) Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code.../a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-...'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time ove...t. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Start request repeated to...y. Feb 24 14:44:04 janus-40 systemd[1]: Failed to start OpenBSD Secure Shell s...r. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'start...'. Hint: Some lines were ellipsized, use -l to show in full. journalctl -u ssh -- Logs begin at Wed 2016-02-24 14:44:03 CST, end at Sat 2016-02-27 12:32:17 CST. -- Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:03 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:03 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Unit entered failed state. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Failed with result 'exit-code'. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Service hold-off time over, scheduling restart. Feb 24 14:44:04 janus-40 systemd[1]: Stopped OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: Started OpenBSD Secure Shell server. Feb 24 14:44:04 janus-40 systemd[1]: ssh.service: Main process exited, code=exited, status=255/n/a -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+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 1549473] Re: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
After boot starting ssh has never fails to start and correctly runs. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+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 1549473] [NEW] ssh will not start at boot: systemctl status ssh -> output is listed as failed 255.
Public bug reported: Using apt I have reinstalled and purged both ssh and openssh-server. apt-get remove --purge ssh openssh-server reinstalled updated and on boot the ctl status is failed 255 After much forum research and attempts to default solutions, the final word was that reinstall usually fixes this issue. With the issue usually stemming from ssh service trying to start before network services are available. Currently I have no logs available with journalctl -u sshd | tail -100 I can provide info pertaining to this on request. ProblemType: Bug DistroRelease: Ubuntu 15.10 Package: ssh 1:6.9p1-2ubuntu0.1 ProcVersionSignature: Ubuntu 4.2.0-30.35-generic 4.2.8-ckt3 Uname: Linux 4.2.0-30-generic x86_64 ApportVersion: 2.19.1-0ubuntu5 Architecture: amd64 CurrentDesktop: LXDE Date: Wed Feb 24 14:27:55 2016 InstallationDate: Installed on 2016-02-09 (15 days ago) InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Release amd64 (20151021) PackageArchitecture: all SourcePackage: openssh UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: openssh (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug boot ssh wily -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1549473 Title: ssh will not start at boot: systemctl status ssh -> output is listed as failed 255. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1549473/+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 1518440] Re: tgt fails to install in LXD
I think this fix should be back ported to trusty so that we can eventually install MAAS in a LXD environment. -- 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/1518440 Title: tgt fails to install in LXD To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1518440/+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 1545913] Re: [FFe] juju-core 2.0
** Changed in: juju-core (Ubuntu) Status: Confirmed => New -- 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/1545913 Title: [FFe] juju-core 2.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/juju-core/+bug/1545913/+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 1384503] Re: rsync fails on large files with compression
Excluding all compression options was not an acceptable solution for me. What has worked since I initially found this problem back in August was to install rsync from the utopic repository where the bug was fixed. That same version (3.1.1-3) is still available in vivid and wily unchanged as far as I can tell. Example: wget http://mirrors.kernel.org/ubuntu/pool/main/r/rsync/rsync_3.1.1-3_amd64.deb sudo dpkg -i rsync_3.1.1-3_amd64.deb Or for x86: wget http://mirrors.kernel.org/ubuntu/pool/main/r/rsync/rsync_3.1.1-3_i386.deb sudo dpkg -i rsync_3.1.1-3_i386.deb Problem solved. -- 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/1384503 Title: rsync fails on large files with compression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+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 1510345] Re: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
Looks like I was premature in my last reply. ami-bfb5ead5 just came up. I'll have to double check this bug report with one of our customers. -- 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/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1510345/+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 1510345] Re: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
OK it looks like the bug was fixed for the hvm:ebs-ssd (General Purpose SSD) AMI builds and not hvm:ebs (standard/magnetic EBS). For example, in ubuntu-wily-15.10-amd64-server-20160105.1 for us-east-1: * ami-bfb5ead5 ( hvm:ebs ) - FAILS * ami-15b7e87f ( hvm:ebs-ssd ) - WORKS for enhanced networking instance launches. -- 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/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1510345/+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 1510345] Re: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules
Do we have any updates for fixing these AMIs for instance types that have enhanced networking enabled? -- 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/1510345 Title: [SRU] Cloud Images do not bring up networking w/ certain virtual NICs due to device naming rules To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1510345/+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 1531322] [NEW] package haproxy 1.5.15-1ppa1~wily failed to install/upgrade: subprocess installed post-installation script returned error exit status 1
Public bug reported: Downgrade haproxy 1.6 to 1.5.15 reports that it failed on reboot of machine. But in fact, it worked. ProblemType: Package DistroRelease: Ubuntu 16.04 Package: haproxy 1.5.15-1ppa1~wily ProcVersionSignature: Ubuntu 3.16.0-57.77~14.04.1-generic 3.16.7-ckt20 Uname: Linux 3.16.0-57-generic x86_64 ApportVersion: 2.19.3-0ubuntu2 Architecture: amd64 Date: Tue Jan 5 09:55:53 2016 DuplicateSignature: Installing new version of config file /etc/init.d/haproxy ... Job for haproxy.service failed because the control process exited with error code. See "systemctl status haproxy.service" and "journalctl -xe" for details. invoke-rc.d: initscript haproxy, action "start" failed. dpkg: error processing package haproxy (--configure): subprocess installed post-installation script returned error exit status 1 ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2015-07-08 (181 days ago) InstallationMedia: Ubuntu 14.04.2 LTS "Trusty Tahr" - Release amd64 (20150218.1) RelatedPackageVersions: dpkg 1.18.3ubuntu1 apt 1.1.10 SourcePackage: haproxy Title: package haproxy 1.5.15-1ppa1~wily failed to install/upgrade: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to xenial on 2015-12-22 (14 days ago) modified.conffile..etc.haproxy.haproxy.cfg: [modified] mtime.conffile..etc.haproxy.haproxy.cfg: 2016-01-05T11:04:22.198685 ** Affects: haproxy (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package need-duplicate-check xenial -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to haproxy in Ubuntu. https://bugs.launchpad.net/bugs/1531322 Title: package haproxy 1.5.15-1ppa1~wily 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/haproxy/+bug/1531322/+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 1311387] Re: postinst fails when installing on a low memory system
Another work around is to disable "performance_schema" This was not enabled by default in the 5.5 packages AFAIK. Disabling it allows MySql 5.6 to install/start on a 512mb server for me. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1311387 Title: postinst fails when installing on a low memory system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1311387/+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 1312936] Re: Post-installation script fails on systems with too little memory
*** This bug is a duplicate of bug 1311387 *** https://bugs.launchpad.net/bugs/1311387 ** This bug has been marked a duplicate of bug 1311387 postinst fails when installing on a low memory system -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1312936 Title: Post-installation script fails on systems with too little memory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1312936/+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 1311387] Re: postinst fails when installing on a low memory system
Interestingly, using 5.6.27-0ubuntu0.14.04.1 on 14.04 on a 512mb server consistently fails to install while 5.6.27-0ubuntu1 with 15.10 doesn't. I don't see any obvious configuration difference scanning the diff though. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1311387 Title: postinst fails when installing on a low memory system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1311387/+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 1516471] [NEW] systemd init scripts not setting correct conf file
Public bug reported:
In january the trove install packages were changed to use systemd in this
commit:
http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/wily/openstack-trove/wily/revision/21
This caused all services to startup using the same configuration file.
trove16464 1 0 Nov13 ?00:09:24 /usr/bin/python
/usr/bin/trove-api --config-file=/etc/trove/trove.conf
--log-file=/var/log/trove/trove-api.log
trove16510 1 0 Nov13 ?00:09:13 /usr/bin/python
/usr/bin/trove-conductor --config-file=/etc/trove/trove.conf
--log-file=/var/log/trove/trove-conductor.log
trove16574 16464 0 Nov13 ?00:00:00 /usr/bin/python
/usr/bin/trove-api --config-file=/etc/trove/trove.conf
--log-file=/var/log/trove/trove-api.log
trove16575 16464 0 Nov13 ?00:00:00 /usr/bin/python
/usr/bin/trove-api --config-file=/etc/trove/trove.conf
--log-file=/var/log/trove/trove-api.log
trove16576 16510 0 Nov13 ?00:00:02 /usr/bin/python
/usr/bin/trove-conductor --config-file=/etc/trove/trove.conf
--log-file=/var/log/trove/trove-conductor.log
trove16579 16510 0 Nov13 ?00:00:02 /usr/bin/python
/usr/bin/trove-conductor --config-file=/etc/trove/trove.conf
--log-file=/var/log/trove/trove-conductor.log
trove28190 1 0 14:32 ?00:00:00 /usr/bin/python
/usr/bin/trove-taskmanager --config-file=/etc/trove/trove.conf
--log-file=/var/log/trove/trove-taskmanager.log
You will notice that all services are using trove.conf when they should
be using trove-conductor.conf, trove-taskmanager.conf etc
The *.init.in files need updating to include settings like:
CONFIG_FILE=/etc/${PROJECT_NAME}/trove-taskmanager.conf
** Affects: openstack-trove (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to openstack-trove in Ubuntu.
https://bugs.launchpad.net/bugs/1516471
Title:
systemd init scripts not setting correct conf file
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/openstack-trove/+bug/1516471/+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 1512603] Re: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid
The init.d script was a broken symlink to nut-client, so I just copied the systemd unit from an earlier package, and it works fine now. -- 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/1512603 Title: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1512603/+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 1512603] [NEW] nut-monitor systemd service is absent in nut-client package since Ubuntu vivid
Public bug reported: The systemd unit for the upsmon has disapperared from nut-client package since Ubuntu trusty: http://packages.ubuntu.com/trusty/amd64/nut-client/filelist (2.7.1-1ubuntu1) vs http://packages.ubuntu.com/vivid/amd64/nut-client/filelist (2.7.1-1ubuntu4) ** Affects: nut (Ubuntu) Importance: Undecided Status: New ** Package changed: kexec-tools (Ubuntu) => nut (Ubuntu) ** Description changed: - The systemd service for the upsmon has disapperared from nut-client - package since Ubuntu trusty: + The systemd unit for the upsmon has disapperared from nut-client package + since Ubuntu trusty: http://packages.ubuntu.com/trusty/amd64/nut-client/filelist (2.7.1-1ubuntu1) vs http://packages.ubuntu.com/vivid/amd64/nut-client/filelist (2.7.1-1ubuntu4) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nut in Ubuntu. https://bugs.launchpad.net/bugs/1512603 Title: nut-monitor systemd service is absent in nut-client package since Ubuntu vivid To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nut/+bug/1512603/+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 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
Hi Colin, I believe you now have access to the necessary hardware, but please let me know if this is still an issue. Thanks. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+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 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
Great! Many thanks... -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+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 1494602] Re: qemu-system-x86 nested virtualisation is broken on AMD system
Sorry, I changed the status of this bug by accident. But should it still be 'incomplete'? ** Changed in: qemu (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1494602 Title: qemu-system-x86 nested virtualisation is broken on AMD system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1494602/+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 1494602] Re: qemu-system-x86 nested virtualisation is broken on AMD system
** Changed in: qemu (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1494602 Title: qemu-system-x86 nested virtualisation is broken on AMD system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1494602/+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 1494602] Re: qemu-system-x86 nested virtualisation is broken on AMD system
Hello, here is the extra information you have asked for. Instance 37aa aka kvm id 677 is my currently running test instance, but I have given you the full ps output you have asked for. 18429 is the PID for this instance. instance-37aa 12396aff-3f84-4ceb-9791-d20cf656fb35 http://openstack.org/xmlns/libvirt/nova/1.0;> qemu9 2015-09-10 06:14:59 4096 10 0 30 1 andrew.spi...@unimelb.edu.au pt-489 4194304 4194304 1 1024 /machine OpenStack Foundation OpenStack Nova 2015.1.1-a41-g26267dc-trusty 534d4349-0002-5290-2500-529025005ccf 12396aff-3f84-4ceb-9791-d20cf656fb35 hvm destroy restart destroy /usr/bin/qemu-system-x86_64 libvirt-12396aff-3f84-4ceb-9791-d20cf656fb35 libvirt-12396aff-3f84-4ceb-9791-d20cf656fb35 root@cc3:~# ps -auxww | egrep -e '(qemu|kvm)' libvirt+ 815 0.3 0.7 8928504 1037444 ? Sl Sep10 21:43 /usr/bin/qemu-system-x86_64 -name instance-3798 -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu Opteron_G4,+perfctr_nb,+perfctr_core,+topoext,+nodeid_msr,+lwp,+wdt,+skinit,+ibs,+osvw,+cr8legacy,+extapic,+cmp_legacy,+fxsr_opt,+mmxext,+osxsave,+monitor,+ht,+vme -m 4096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid cd51f9ff-4175-4a95-abca-49fdcad12316 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2014.2.1-a153-g68554dc-trusty,serial=534d4349-0002-5290-2500-529025005ccf,uuid=cd51f9ff-4175-4a95-abca-49fdcad12316 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-3798.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/in stances/cd51f9ff-4175-4a95-abca-49fdcad12316/disk,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/nova/instances/cd51f9ff-4175-4a95-abca-49fdcad12316/disk.local,if=none,id=drive-virtio-disk1,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x5,drive=drive-virtio-disk1,id=virtio-disk1 -netdev tap,fd=28,id=hostnet0,vhost=on,vhostfd=29 -device virtio-net-pci,netdev=hostnet0,id=net0,mac=fa:16:3e:f6:fa:4a,bus=pci.0,addr=0x3 -chardev file,id=charserial0,path=/var/lib/nova/instances/cd51f9ff-4175-4a95-abca-49fdcad12316/console.log -device isa-serial,chardev=charserial0,id=serial0 -chardev pty,id=charserial1 -device isa-serial,chardev=charserial1,id=serial1 -device usb-tablet,id=input0 -vnc 0.0.0.0:4 -k en-us -device cirrus-vga,id=video0,bus=pci.0,addr=0x2 -device virtio-balloon-pci,id=balloon0,bus=pci.0,addr=0x6 -msg timestamp=on root 821 0.0 0.0 0 0 ?SSep10 0:00 [kvm-pit/815] libvirt+ 1120 0.3 0.8 8928360 1054916 ? Sl Sep10 20:30 /usr/bin/qemu-system-x86_64 -name instance-379a -S -machine pc-i440fx-trusty,accel=kvm,usb=off -cpu Opteron_G4,+perfctr_nb,+perfctr_core,+topoext,+nodeid_msr,+lwp,+wdt,+skinit,+ibs,+osvw,+cr8legacy,+extapic,+cmp_legacy,+fxsr_opt,+mmxext,+osxsave,+monitor,+ht,+vme -m 4096 -realtime mlock=off -smp 1,sockets=1,cores=1,threads=1 -uuid 90bebf98-cc44-4b10-9c19-18bc545e4674 -smbios type=1,manufacturer=OpenStack Foundation,product=OpenStack Nova,version=2014.2.1-a153-g68554dc-trusty,serial=534d4349-0002-5290-2500-529025005ccf,uuid=90bebf98-cc44-4b10-9c19-18bc545e4674 -no-user-config -nodefaults -chardev socket,id=charmonitor,path=/var/lib/libvirt/qemu/instance-379a.monitor,server,nowait -mon chardev=charmonitor,id=monitor,mode=control -rtc base=utc,driftfix=slew -global kvm-pit.lost_tick_policy=discard -no-hpet -no-shutdown -boot strict=on -device piix3-usb-uhci,id=usb,bus=pci.0,addr=0x1.0x2 -drive file=/var/lib/nova/in stances/90bebf98-cc44-4b10-9c19-18bc545e4674/disk,if=none,id=drive-virtio-disk0,format=raw,cache=none -device virtio-blk-pci,scsi=off,bus=pci.0,addr=0x4,drive=drive-virtio-disk0,id=virtio-disk0,bootindex=1 -drive file=/var/lib/nova/instances/90bebf98-cc44-4b10-9c19-18bc545e4674/disk.local,if=none,id=drive-virtio-disk1,format=raw,cache=none -device
[Bug 1494602] [NEW] qemu-system-x86 nested virtualisation is broken on AMD system
Public bug reported: I am reporting this bug against qemu-system-x86=1:2.2+dfsg-5expubuntu9.3~cloud0 in the Ubuntu cloud archive. # lsb_release -rd Description:Ubuntu 14.04.3 LTS Release:14.04 # apt-cache policy qemu-system-x86 qemu-system-x86: Installed: 1:2.3+dfsg-5ubuntu4~cloud0 Candidate: 1:2.3+dfsg-5ubuntu4~cloud0 What is happening: Version 1:2.2+dfsg-5expubuntu9.3~cloud0 of qemu-system and qemu-system-x86_64 seems to be dropping the svm (AMD nested virtualization) flag from virtual machines, despite it being specified in the CPU type. So nested virtualisation has stoppped working. What I expect to happen: svm CPU flag to be passed through to guests. Version 1:2.3+dfsg-5ubuntu4~cloud0 also drops the svm flag. Version 2.0.0+dfsg-2ubuntu1.18 passes the CPU flag through fine. This has been tested with libvirt-bin version 1.2.12-0ubuntu14. The processor is Version: AMD Opteron(TM) Processor 6238. # cat /sys/module/kvm_amd/parameters/nested 1 # modinfo kvm_amd | grep nested parm: nested:int The qemu command line includes the following cpu argument:: -cpu Opteron_G4,+perfctr_nb,+perfctr_core,+topoext,+nodeid_msr,+lwp,+wdt,+skinit,+ibs,+osvw,+cr8legacy,+extapic,+c mp_legacy,+fxsr_opt,+mmxext,+osxsave,+monitor,+ht,+vme ** Affects: qemu (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to qemu in Ubuntu. https://bugs.launchpad.net/bugs/1494602 Title: qemu-system-x86 nested virtualisation is broken on AMD system To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu/+bug/1494602/+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 1384503] Re: rsync fails on large files with compression
I just found this report myself. I've been experiencing the problem for a while but had to rule out other causes. This is a pretty serious bug in an LTS release. -- 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/1384503 Title: rsync fails on large files with compression To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rsync/+bug/1384503/+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 1446658] Re: lxc-test-apparmor fails on aarch64
This is no longer happening on stock kernels. ** Changed in: lxc (Ubuntu) Status: New = Invalid -- 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/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+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 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
** Also affects: irqbalance (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+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 1469214] Re: HP ProLiant m400 Server crashes with unhandled level 3 translation fault
Following Ming's identification of an irqbalance patch that fixes this issue, I'm marking the Affected status on linux (Ubuntu) as being invalid. ** Changed in: linux (Ubuntu Trusty) Status: New = Invalid ** Changed in: linux (Ubuntu Utopic) Status: New = Invalid ** Changed in: linux (Ubuntu Vivid) Status: New = Invalid ** Changed in: linux (Ubuntu Wily) Status: Triaged = Invalid ** Changed in: irqbalance (Ubuntu Vivid) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to irqbalance in Ubuntu. https://bugs.launchpad.net/bugs/1469214 Title: HP ProLiant m400 Server crashes with unhandled level 3 translation fault To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/irqbalance/+bug/1469214/+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 1467552] package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
One more thing that I think might be important. /repo was a symlink itself to a mounted VMWare Fusion OS X host shared folder. /repo - /mnt/hgfs/andrew/projects/PROJNAME and I am now wondering if that shared folder disconnected during the upgrade, thus the php.ini links were severed. I apologize for this oversight. I believe the shared folder feature is implemented as a kernel module. Andrew On Jun 23, 2015, at 7:06 AM, Robie Basak 1467...@bugs.launchpad.net wrote: Thank you for your report. What is /repo/config/etc/php.ini please? Is it something you have created and symlinked from /etc/php? Do you have multiple symlinks pointing to the same location? Once you've replied, please change the bug status back to New. ** Changed in: php5 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1467552 Title: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 Status in php5 package in Ubuntu: Incomplete Bug description: OUTPUT at command prompt just before error. It was working on php5 and I just told it to keep my php.ini file. After saying keep my php.ini, the below was outputted. ucfr: Attempt from package libapache2-mod-php5 to take /repo/config/etc/php.ini away from package php5-cli ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): subprocess installed post-installation script returned error exit status 4 Setting up ubuntu-standard (1.327) ... dpkg: dependency problems prevent configuration of php5: php5 depends on libapache2-mod-php5 (= 5.5.12+dfsg-2ubuntu4.4~) | libapache2-mod-php5filter (= 5.5.12+dfsg-2ubuntu4.4~) | php5-cgi (= 5.5.12+dfsg-2ubuntu4.4~) | php5-fpm (= 5.5.12+dfsg-2ubuntu4.4~); however: Package libapache2-mod-php5 is not configured yet. Package libapache2-mod-php5filter is not installed. Package php5-cgi is not installed. Package php5-fpm is not installed. dpkg: error processing package php5 (--configure): dependency problems - leaving unconfigured Setting up plymouth (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) No apport report written because the error message indicates its a followup error from a previous failure. Setting up upstart (1.13.2-0ubuntu2) ... Setting up friendly-recovery (0.2.26) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.16.0-41-generic Found initrd image: /boot/initrd.img-3.16.0-41-generic Found linux image: /boot/vmlinuz-3.13.0-43-generic Found initrd image: /boot/initrd.img-3.13.0-43-generic Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done Setting up ubuntu-minimal (1.327) ... Setting up plymouth-theme-ubuntu-text (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) Processing triggers for dbus (1.8.8-1ubuntu2.1) ... Setting up libpam-systemd:amd64 (208-8ubuntu8.2) ... Removing obsolete conffile /etc/init/systemd-logind.conf ... Setting up policykit-1 (0.105-4ubuntu2.14.10.1) ... Processing triggers for libc-bin (2.19-10ubuntu2.3) ... Processing triggers for ca-certificates (20141019ubuntu0.14.10.1) ... Updating certificates in /etc/ssl/certs... 17 added, 8 removed; done. Running hooks in /etc/ca-certificates/update.ddone. Processing triggers for initramfs-tools (0.103ubuntu8) ... update-initramfs: Generating /boot/initrd.img-3.16.0-41-generic Errors were encountered while processing: libapache2-mod-php5 php5 Error in function: A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1467552 Title: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe
Re: [Bug 1467552] package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
BTW, I can’t login. I use a password manager so I know the password and username are correct. After clicking login I get a page that says “Bad Request”. That seems like an error in the backend rather than an authentication error. Because of this, I can’t change the status of the report. Andrew chernow On Jun 23, 2015, at 7:06 AM, Robie Basak 1467...@bugs.launchpad.net wrote: Thank you for your report. What is /repo/config/etc/php.ini please? Is it something you have created and symlinked from /etc/php? Do you have multiple symlinks pointing to the same location? Once you've replied, please change the bug status back to New. ** Changed in: php5 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1467552 Title: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 Status in php5 package in Ubuntu: Incomplete Bug description: OUTPUT at command prompt just before error. It was working on php5 and I just told it to keep my php.ini file. After saying keep my php.ini, the below was outputted. ucfr: Attempt from package libapache2-mod-php5 to take /repo/config/etc/php.ini away from package php5-cli ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): subprocess installed post-installation script returned error exit status 4 Setting up ubuntu-standard (1.327) ... dpkg: dependency problems prevent configuration of php5: php5 depends on libapache2-mod-php5 (= 5.5.12+dfsg-2ubuntu4.4~) | libapache2-mod-php5filter (= 5.5.12+dfsg-2ubuntu4.4~) | php5-cgi (= 5.5.12+dfsg-2ubuntu4.4~) | php5-fpm (= 5.5.12+dfsg-2ubuntu4.4~); however: Package libapache2-mod-php5 is not configured yet. Package libapache2-mod-php5filter is not installed. Package php5-cgi is not installed. Package php5-fpm is not installed. dpkg: error processing package php5 (--configure): dependency problems - leaving unconfigured Setting up plymouth (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) No apport report written because the error message indicates its a followup error from a previous failure. Setting up upstart (1.13.2-0ubuntu2) ... Setting up friendly-recovery (0.2.26) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.16.0-41-generic Found initrd image: /boot/initrd.img-3.16.0-41-generic Found linux image: /boot/vmlinuz-3.13.0-43-generic Found initrd image: /boot/initrd.img-3.13.0-43-generic Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done Setting up ubuntu-minimal (1.327) ... Setting up plymouth-theme-ubuntu-text (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) Processing triggers for dbus (1.8.8-1ubuntu2.1) ... Setting up libpam-systemd:amd64 (208-8ubuntu8.2) ... Removing obsolete conffile /etc/init/systemd-logind.conf ... Setting up policykit-1 (0.105-4ubuntu2.14.10.1) ... Processing triggers for libc-bin (2.19-10ubuntu2.3) ... Processing triggers for ca-certificates (20141019ubuntu0.14.10.1) ... Updating certificates in /etc/ssl/certs... 17 added, 8 removed; done. Running hooks in /etc/ca-certificates/update.ddone. Processing triggers for initramfs-tools (0.103ubuntu8) ... update-initramfs: Generating /boot/initrd.img-3.16.0-41-generic Errors were encountered while processing: libapache2-mod-php5 php5 Error in function: A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1467552 Title: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+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 1467552] package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
/repo/config/etc/php.ini is a custom ini that is linked to /etc/php5 apache2 and cli folders. The same file linked in both places since Apache virtual hosts override ini directives via php_value. I'm guessing I should of removed those links before attempting the upgrade. After the upgrade, Apache and php was kind of screwed up until I purged them completely from the system and installed them again via apt-get install (which installed the 14.10 versions of apache and php properly). Now everything seems to work just fine. I was asked whether I wanted to keep both ini files and I said yes keep them. On the second one it displayed that error. I can’t be 100% sure but I believe the system is fully operational and upgraded properly. Thankfully for my sake, this was a test VM specifically created to try out the upgrade from 14.04 = 14.10. Andrew On Jun 23, 2015, at 7:06 AM, Robie Basak 1467...@bugs.launchpad.net wrote: Thank you for your report. What is /repo/config/etc/php.ini please? Is it something you have created and symlinked from /etc/php? Do you have multiple symlinks pointing to the same location? Once you've replied, please change the bug status back to New. ** Changed in: php5 (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1467552 Title: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 Status in php5 package in Ubuntu: Incomplete Bug description: OUTPUT at command prompt just before error. It was working on php5 and I just told it to keep my php.ini file. After saying keep my php.ini, the below was outputted. ucfr: Attempt from package libapache2-mod-php5 to take /repo/config/etc/php.ini away from package php5-cli ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): subprocess installed post-installation script returned error exit status 4 Setting up ubuntu-standard (1.327) ... dpkg: dependency problems prevent configuration of php5: php5 depends on libapache2-mod-php5 (= 5.5.12+dfsg-2ubuntu4.4~) | libapache2-mod-php5filter (= 5.5.12+dfsg-2ubuntu4.4~) | php5-cgi (= 5.5.12+dfsg-2ubuntu4.4~) | php5-fpm (= 5.5.12+dfsg-2ubuntu4.4~); however: Package libapache2-mod-php5 is not configured yet. Package libapache2-mod-php5filter is not installed. Package php5-cgi is not installed. Package php5-fpm is not installed. dpkg: error processing package php5 (--configure): dependency problems - leaving unconfigured Setting up plymouth (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) No apport report written because the error message indicates its a followup error from a previous failure. Setting up upstart (1.13.2-0ubuntu2) ... Setting up friendly-recovery (0.2.26) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.16.0-41-generic Found initrd image: /boot/initrd.img-3.16.0-41-generic Found linux image: /boot/vmlinuz-3.13.0-43-generic Found initrd image: /boot/initrd.img-3.13.0-43-generic Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done Setting up ubuntu-minimal (1.327) ... Setting up plymouth-theme-ubuntu-text (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) Processing triggers for dbus (1.8.8-1ubuntu2.1) ... Setting up libpam-systemd:amd64 (208-8ubuntu8.2) ... Removing obsolete conffile /etc/init/systemd-logind.conf ... Setting up policykit-1 (0.105-4ubuntu2.14.10.1) ... Processing triggers for libc-bin (2.19-10ubuntu2.3) ... Processing triggers for ca-certificates (20141019ubuntu0.14.10.1) ... Updating certificates in /etc/ssl/certs... 17 added, 8 removed; done. Running hooks in /etc/ca-certificates/update.ddone. Processing triggers for initramfs-tools (0.103ubuntu8) ... update-initramfs: Generating /boot/initrd.img-3.16.0-41-generic Errors were encountered while processing: libapache2-mod-php5 php5 Error in function: A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which
[Bug 1467552] Re: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
** Attachment added: apt.log https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+attachment/4418603/+files/apt.log ** Description changed: - Since .I am only allowed to upload a single file, but the upgrade asked - me to send two files: apt.log and main.log, I am pasting apt.log at the - bottom of this section - OUTPUT at command prompt: + OUTPUT at command prompt just before error. It was working on php5 and I just told it to keep my php.ini file. After saying keep my php.ini, the below was outputted. - ucfr: Attempt from package libapache2-mod-php5 to take /repo/config/etc/php.ini away from package php5-cli + ucfr: Attempt from package libapache2-mod-php5 to take /repo/config/etc/php.ini away from package php5-cli ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): - subprocess installed post-installation script returned error exit status 4 + subprocess installed post-installation script returned error exit status 4 Setting up ubuntu-standard (1.327) ... dpkg: dependency problems prevent configuration of php5: - php5 depends on libapache2-mod-php5 (= 5.5.12+dfsg-2ubuntu4.4~) | libapache2-mod-php5filter (= 5.5.12+dfsg-2ubuntu4.4~) | php5-cgi (= 5.5.12+dfsg-2ubuntu4.4~) | php5-fpm (= 5.5.12+dfsg-2ubuntu4.4~); however: - Package libapache2-mod-php5 is not configured yet. - Package libapache2-mod-php5filter is not installed. - Package php5-cgi is not installed. - Package php5-fpm is not installed. + php5 depends on libapache2-mod-php5 (= 5.5.12+dfsg-2ubuntu4.4~) | libapache2-mod-php5filter (= 5.5.12+dfsg-2ubuntu4.4~) | php5-cgi (= 5.5.12+dfsg-2ubuntu4.4~) | php5-fpm (= 5.5.12+dfsg-2ubuntu4.4~); however: + Package libapache2-mod-php5 is not configured yet. + Package libapache2-mod-php5filter is not installed. + Package php5-cgi is not installed. + Package php5-fpm is not installed. dpkg: error processing package php5 (--configure): - dependency problems - leaving unconfigured + dependency problems - leaving unconfigured Setting up plymouth (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) No apport report written because the error message indicates its a followup error from a previous failure. - Setting up upstart (1.13.2-0ubuntu2) ... + Setting up upstart (1.13.2-0ubuntu2) ... Setting up friendly-recovery (0.2.26) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.16.0-41-generic Found initrd image: /boot/initrd.img-3.16.0-41-generic Found linux image: /boot/vmlinuz-3.13.0-43-generic Found initrd image: /boot/initrd.img-3.13.0-43-generic Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done Setting up ubuntu-minimal (1.327) ... Setting up plymouth-theme-ubuntu-text (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) Processing triggers for dbus (1.8.8-1ubuntu2.1) ... Setting up libpam-systemd:amd64 (208-8ubuntu8.2) ... Removing obsolete conffile /etc/init/systemd-logind.conf ... Setting up policykit-1 (0.105-4ubuntu2.14.10.1) ... Processing triggers for libc-bin (2.19-10ubuntu2.3) ... Processing triggers for ca-certificates (20141019ubuntu0.14.10.1) ... Updating certificates in /etc/ssl/certs... 17 added, 8 removed; done. Running hooks in /etc/ca-certificates/update.ddone. Processing triggers for initramfs-tools (0.103ubuntu8) ... update-initramfs: Generating /boot/initrd.img-3.16.0-41-generic Errors were encountered while processing: - libapache2-mod-php5 - php5 - Error in function: + libapache2-mod-php5 + php5 + Error in function: + A fatal error occurred - A fatal error occurred - - Please report this as a bug and include the files - /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in - your report. The upgrade has aborted. - Your original sources.list was saved in - /etc/apt/sources.list.distUpgrade. + Please report this as a bug and include the files + /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in + your report. The upgrade has aborted. + Your original sources.list was saved in + /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) - - - - apt.log - - Log time: 2015-06-22 10:06:43.384289 - Log time: 2015-06-22 10:06:52.362093 - Log time: 2015-06-22 10:08:00.584588 - MarkInstall linux-headers-generic [ amd64 ] 3.13.0.43.50 - 3.16.0.41.41 ( devel ) FU=0 - Installing linux-headers-3.16.0-41-generic as Depends of linux-headers-generic - MarkInstall
[Bug 1467552] [NEW] package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4
Public bug reported: OUTPUT at command prompt just before error. It was working on php5 and I just told it to keep my php.ini file. After saying keep my php.ini, the below was outputted. ucfr: Attempt from package libapache2-mod-php5 to take /repo/config/etc/php.ini away from package php5-cli ucfr: Aborting. dpkg: error processing package libapache2-mod-php5 (--configure): subprocess installed post-installation script returned error exit status 4 Setting up ubuntu-standard (1.327) ... dpkg: dependency problems prevent configuration of php5: php5 depends on libapache2-mod-php5 (= 5.5.12+dfsg-2ubuntu4.4~) | libapache2-mod-php5filter (= 5.5.12+dfsg-2ubuntu4.4~) | php5-cgi (= 5.5.12+dfsg-2ubuntu4.4~) | php5-fpm (= 5.5.12+dfsg-2ubuntu4.4~); however: Package libapache2-mod-php5 is not configured yet. Package libapache2-mod-php5filter is not installed. Package php5-cgi is not installed. Package php5-fpm is not installed. dpkg: error processing package php5 (--configure): dependency problems - leaving unconfigured Setting up plymouth (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) No apport report written because the error message indicates its a followup error from a previous failure. Setting up upstart (1.13.2-0ubuntu2) ... Setting up friendly-recovery (0.2.26) ... Generating grub configuration file ... Found linux image: /boot/vmlinuz-3.16.0-41-generic Found initrd image: /boot/initrd.img-3.16.0-41-generic Found linux image: /boot/vmlinuz-3.13.0-43-generic Found initrd image: /boot/initrd.img-3.13.0-43-generic Found linux image: /boot/vmlinuz-3.13.0-24-generic Found initrd image: /boot/initrd.img-3.13.0-24-generic Found memtest86+ image: /memtest86+.elf Found memtest86+ image: /memtest86+.bin done Setting up ubuntu-minimal (1.327) ... Setting up plymouth-theme-ubuntu-text (0.9.0-0ubuntu7) ... update-initramfs: deferring update (trigger activated) Processing triggers for dbus (1.8.8-1ubuntu2.1) ... Setting up libpam-systemd:amd64 (208-8ubuntu8.2) ... Removing obsolete conffile /etc/init/systemd-logind.conf ... Setting up policykit-1 (0.105-4ubuntu2.14.10.1) ... Processing triggers for libc-bin (2.19-10ubuntu2.3) ... Processing triggers for ca-certificates (20141019ubuntu0.14.10.1) ... Updating certificates in /etc/ssl/certs... 17 added, 8 removed; done. Running hooks in /etc/ca-certificates/update.ddone. Processing triggers for initramfs-tools (0.103ubuntu8) ... update-initramfs: Generating /boot/initrd.img-3.16.0-41-generic Errors were encountered while processing: libapache2-mod-php5 php5 Error in function: A fatal error occurred Please report this as a bug and include the files /var/log/dist-upgrade/main.log and /var/log/dist-upgrade/apt.log in your report. The upgrade has aborted. Your original sources.list was saved in /etc/apt/sources.list.distUpgrade. SystemError: E:Sub-process /usr/bin/dpkg returned an error code (1) ** Affects: php5 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package dist-upgrade need-duplicate-check utopic ** Attachment added: main.log https://bugs.launchpad.net/bugs/1467552/+attachment/4418590/+files/main.log -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1467552 Title: package libapache2-mod-php5 5.5.12+dfsg-2ubuntu4.4 failed to install/upgrade: subprocess installed post-installation script returned error exit status 4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1467552/+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 1446658] RelatedPackageVersions.txt
apport information ** Attachment added: RelatedPackageVersions.txt https://bugs.launchpad.net/bugs/1446658/+attachment/4380593/+files/RelatedPackageVersions.txt -- 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/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+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 1446658] Dependencies.txt
apport information ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/1446658/+attachment/4380592/+files/Dependencies.txt -- 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/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+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 1446658] lxc.default.txt
apport information ** Attachment added: lxc.default.txt https://bugs.launchpad.net/bugs/1446658/+attachment/4380595/+files/lxc.default.txt -- 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/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+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 1446658] lxc-net.default.txt
apport information ** Attachment added: lxc-net.default.txt https://bugs.launchpad.net/bugs/1446658/+attachment/4380594/+files/lxc-net.default.txt -- 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/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+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 1446658] [NEW] lxc-test-apparmor fails on aarch64
Public bug reported: Running lxc-test-apparmor fails on aarch64 (arm64) systems. The following files which are listed in files_to_deny[] in src/tests/aa.c: /sys/kernel/uevent_helper /proc/sys/kernel/sysrq are not denied, but should be. Perhaps I should be changing the apparmor profile for lxc before running the tests (but that's just a guess). I'm invoking the tests as: # for i in /usr/bin/lxc-test-* ; do $i || touch /tmp/$(basename $i).failed; done which results in the following failures: lxc-test-apparmor.failed lxc-test-autostart.failed lxc-test-containertests.failed lxc-test-unpriv.failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.19.2 aarch64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 Date: Tue Apr 21 13:17:28 2015 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx --- ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 DistroRelease: Ubuntu 14.04 KernLog: Package: lxc 1.0.7-0ubuntu0.1 PackageArchitecture: arm64 ProcCmdline: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait ProcEnviron: TERM=screen-256color PATH=(custom, no user) XDG_RUNTIME_DIR=set LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Tags: trusty uec-images Uname: Linux 3.19.2 aarch64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: kvm libvirtd _MarkForUpload: True defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx lxcsyslog: ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: apparmor apport-bug apport-collected arm64 trusty uec-images ** Tags added: apport-collected ** Description changed: Running lxc-test-apparmor fails on aarch64 (arm64) systems. The following files which are listed in files_to_deny[] in src/tests/aa.c: /sys/kernel/uevent_helper /proc/sys/kernel/sysrq are not denied, but should be. Perhaps I should be changing the apparmor profile for lxc before running the tests (but that's just a guess). I'm invoking the tests as: # for i in /usr/bin/lxc-test-* ; do $i || touch /tmp/$(basename $i).failed; done which results in the following failures: lxc-test-apparmor.failed lxc-test-autostart.failed lxc-test-containertests.failed lxc-test-unpriv.failed ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: lxc 1.0.7-0ubuntu0.1 ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' Uname: Linux 3.19.2 aarch64 ApportVersion: 2.14.1-0ubuntu3.7 Architecture: arm64 Date: Tue Apr 21 13:17:28 2015 ProcEnviron: TERM=screen-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) defaults.conf: lxc.network.type = veth lxc.network.link = lxcbr0 lxc.network.flags = up lxc.network.hwaddr = 00:16:3e:xx:xx:xx + --- + ApportVersion: 2.14.1-0ubuntu3.7 + Architecture: arm64 + DistroRelease: Ubuntu 14.04 + KernLog: + + Package: lxc 1.0.7-0ubuntu0.1 + PackageArchitecture: arm64 + ProcCmdline: console=ttyS0,115200n8 root=/dev/sda1 rw rootwait + ProcEnviron: + TERM=screen-256color + PATH=(custom, no user) + XDG_RUNTIME_DIR=set + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Error: [Errno 2] No such file or directory: '/proc/version_signature' + Tags: trusty uec-images + Uname: Linux 3.19.2 aarch64 + UpgradeStatus: No upgrade log present (probably fresh install) + UserGroups: kvm libvirtd + _MarkForUpload: True + defaults.conf: + lxc.network.type = veth + lxc.network.link = lxcbr0 + lxc.network.flags = up + lxc.network.hwaddr = 00:16:3e:xx:xx:xx + lxcsyslog: -- 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/1446658 Title: lxc-test-apparmor fails on aarch64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1446658/+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 910962] Re: installArchives() failed: dpkg: unrecoverable fatal error, aborting: syntax error: unknown group 'postdrop' in statoverride file Error in function: SystemError: E:Sub-process /usr/bin
I was bitten by this too. In my case, it's because I installed postfix within a chroot that I was using schroot to enter, but postfix wasn't installed in the real root. Each time I'd enter the chroot, /etc/group would be copied from the real root into the chroot, losing the 'postdrop' group created by dpkg-reconfigure. Solution: create the 'postdrop' group in the real root too, and ensure it has the same GID. -- 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/910962 Title: installArchives() failed: dpkg: unrecoverable fatal error, aborting: syntax error: unknown group 'postdrop' in statoverride file Error in function: SystemError: E:Sub-process /usr/bin/dpkg returned an error code (2) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/910962/+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 1236299] Re: ssh-agent env variables not set when not using Bourne shell
This appears to be fixed, at least in 1:6.6p1-2ubuntu2 -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1236299 Title: ssh-agent env variables not set when not using Bourne shell To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1236299/+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 1349433] Re: AppArmor breaks seccomp @ Apache mpm-itk
I'm not clear on what the issue with mailman is but if removing the LimitUIDRange option from your Apache config solves it then it's probably expected behaviour when calling a setuid root executable (Exim?). -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1349433 Title: AppArmor breaks seccomp @ Apache mpm-itk To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1349433/+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
Systemd support is currently under development, primarily to support CentOS: http://reviews.vapour.ws/r/671/ -- 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 1409639] Re: juju needs to support systemd for = vivid
(I should have added: but will support Ubuntu, with a couple of minor adjustments) -- 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 1257186] Re: memory leakage messages (no talloc stackframe)
I'm using netatalk as well, and this bug was causing /run/samba/gencache_notrans.tdb to grow to several hundred MB until /run was out of space. According to tdbtool the database itself was basically empty, but it was still taking up disk even after a repack. Disabling the module with pam-auth-update looks to have fixed the problem. -- 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/1257186 Title: memory leakage messages (no talloc stackframe) To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 1381967] Re: mongodb shell crash on arm64
Mongodb ARM64 support explanation from Michael Hudson-Doyle. 1) MongoDB uses JS for two things: i) The 'mongo' shell that people use for interactive use and admin tasks etc. This is perhaps not used so much in production, but it's something that most people use when first learning about mongo, e.g. it's the very first command in the getting started doc: http://docs.mongodb.org/manual/tutorial/getting-started/ ii) A few server side scripting functions -- writing queries in js and the map/reduce stuff. These are considered a bit esoteric and most people probably don't actually use them but of course some do. 2) MongoDB 2.4 (the version in trusty) ships with two javascript engines: spidermonkey and v8. There is some license incompatibility with spidermonkey such that mongo said we'd be breaking the law if we distributed binaries built with it. The version of v8 that is used by mongodb 2.4 does not work on arm64. 3) MongoDB 2.6 removed the spidermonkey js engine. 4) Soon after 2.6 was released, mongodb did the work to add another js engine: one for a version of v8 that does work on arm64. 5) Unfortunately, this version of v8 handles OOM by calling abort() -- which is not a problem for the shell really but a very bad thing for the server side scripting functions, as a single query using too much RAM shouldn't cause the database daemon to abort. 6) MongoDB 2.6 is the version in utopic. For some reason, it is built for arm64 but with scripting disabled, which means that the shell just segfaults on startup. This is clearly not ideal. 7) I built packages in a PPA: https://launchpad.net/~mongodb-arm64/+archive/ubuntu/ppa that backport the support for the newer v8 js engine (and because this newer v8 version isn't packaged yet, it has the new version of v8 in a 20 megabyte distro patch). Many thanks Michael for such a clear explanation. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+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 1377308] Re: booting cloud image without initramfs broken
** Tags added: hs-arm64-maas-juju -- 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/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+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 1316579] Re: --upload-tools doesn't work with bootstrap on armhf machine managed by maas
I'm pretty sure this is fixed in 1.21-alpha1. Can someone with an ARM machine please test it? -- 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/1316579 Title: --upload-tools doesn't work with bootstrap on armhf machine managed by maas To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1316579/+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 1381967] Re: mongodb shell crash on arm64
Many thanks to Michael, Raghu and Robie for helping to clarify. Marking this bug as invalid... ** Changed in: mongodb (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+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 1381967] Re: mongodb shell crash on arm64
Michael, many thanks for your comment. Could you confirm that we should be using juju-mongodb (https://launchpad.net/ubuntu/+source/juju-mongodb) on ARM64 for the time being? ISTR that juju-mongodb has omitted the libv8 engine, and associated functionality. Thanks again, Andy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+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 1381967] Re: mongodb shell crash on arm64
Thanks Robie, so for ARM64 platforms we should be using MongoDb, but just avoiding the shell and any scripting functions (in order to avoid invoking libv8). Is that correct? Thanks again, Andy. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mongodb in Ubuntu. https://bugs.launchpad.net/bugs/1381967 Title: mongodb shell crash on arm64 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mongodb/+bug/1381967/+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 1377308] Re: booting cloud image without initramfs broken
** Tags added: hs-moonshot -- 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/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+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 1377308] Re: booting cloud image without initramfs broken
** Tags removed: hs-moonshot ** Tags added: hs-moonshot-maas-juju -- 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/1377308 Title: booting cloud image without initramfs broken To manage notifications about this bug go to: https://bugs.launchpad.net/cloud-init/+bug/1377308/+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 1349433] Re: AppArmor breaks seccomp @ Apache mpm-itk
** Changed in: mailman (Ubuntu) Status: Confirmed = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1349433 Title: AppArmor breaks seccomp @ Apache mpm-itk To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1349433/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
@danieru: what network interfaces show up? is the primary network interface called something other than eth0? If so, you'd need to set the network-bridge attribute in environments.yaml. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1359227] [NEW] package apache2 2.4.7-1-ubuntu4.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Public bug reported: Trying to do in-place upgrade from 12.04.5 to 14.04.1 with some apache2, ruby, puppet and foreman packages installed. Looks like the problem packages were apache2 and apache2-mpm-worker. ProblemType: Package DistroRelease: Ubuntu 14.04 Package: apache2 2.4.7-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-34.60~precise1-generic 3.13.11.4 Uname: Linux 3.13.0-34-generic x86_64 Apache2ConfdDirListing: False Apache2Modules: Error: command ['/usr/sbin/apachectl', '-D DUMP_MODULES'] failed with exit code 1: apache2: Syntax error on line 140 of /etc/apache2/apache2.conf: Could not open configuration file /etc/apache2/mods-enabled/version.load: No such file or directory Action '-D DUMP_MODULES' failed. The Apache error log may have more information. ApportVersion: 2.14.1-0ubuntu3.3 Architecture: amd64 Date: Wed Aug 20 08:56:44 2014 DuplicateSignature: package:apache2:2.4.7-1ubuntu4.1:ErrorMessage: subprocess installed post-installation script returned error exit status 1 ErrorMessage: ErrorMessage: subprocess installed post-installation script returned error exit status 1 InstallationDate: Installed on 2012-08-14 (735 days ago) InstallationMedia: Ubuntu-Server 12.04 LTS Precise Pangolin - Release amd64 (20120424.1) SourcePackage: apache2 Title: package apache2 2.4.7-1ubuntu4.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 UpgradeStatus: Upgraded to trusty on 2014-08-20 (0 days ago) modified.conffile..etc.apache2.mods.available.actions.load: [deleted] modified.conffile..etc.apache2.mods.available.authn.anon.load: [deleted] modified.conffile..etc.apache2.mods.available.authn.dbd.load: [deleted] modified.conffile..etc.apache2.mods.available.authn.dbm.load: [deleted] modified.conffile..etc.apache2.mods.available.authnz.ldap.load: [deleted] modified.conffile..etc.apache2.mods.available.authz.owner.load: [deleted] modified.conffile..etc.apache2.mods.available.cache.load: [deleted] modified.conffile..etc.apache2.mods.available.cgi.load: [deleted] modified.conffile..etc.apache2.mods.available.charset.lite.load: [deleted] modified.conffile..etc.apache2.mods.available.dav.fs.load: [modified] modified.conffile..etc.apache2.mods.available.dav.lock.load: [deleted] modified.conffile..etc.apache2.mods.available.dbd.load: [deleted] modified.conffile..etc.apache2.mods.available.dump.io.load: [deleted] modified.conffile..etc.apache2.mods.available.expires.load: [deleted] modified.conffile..etc.apache2.mods.available.ext.filter.load: [deleted] modified.conffile..etc.apache2.mods.available.file.cache.load: [deleted] modified.conffile..etc.apache2.mods.available.filter.load: [deleted] modified.conffile..etc.apache2.mods.available.info.load: [deleted] modified.conffile..etc.apache2.mods.available.ldap.load: [deleted] modified.conffile..etc.apache2.mods.available.log.forensic.load: [deleted] modified.conffile..etc.apache2.mods.available.mime.magic.load: [deleted] modified.conffile..etc.apache2.mods.available.proxy.ajp.load: [deleted] modified.conffile..etc.apache2.mods.available.proxy.connect.load: [deleted] modified.conffile..etc.apache2.mods.available.proxy.ftp.load: [deleted] modified.conffile..etc.apache2.mods.available.proxy.http.load: [deleted] modified.conffile..etc.apache2.mods.available.proxy.load: [deleted] modified.conffile..etc.apache2.mods.available.proxy.scgi.load: [deleted] modified.conffile..etc.apache2.mods.available.rewrite.load: [deleted] modified.conffile..etc.apache2.mods.available.speling.load: [deleted] modified.conffile..etc.apache2.mods.available.status.load: [deleted] modified.conffile..etc.apache2.mods.available.substitute.load: [deleted] modified.conffile..etc.apache2.mods.available.suexec.load: [deleted] modified.conffile..etc.apache2.mods.available.unique.id.load: [deleted] modified.conffile..etc.apache2.mods.available.userdir.load: [deleted] modified.conffile..etc.apache2.mods.available.usertrack.load: [deleted] modified.conffile..etc.apache2.mods.available.vhost.alias.load: [deleted] mtime.conffile..etc.apache2.mods.available.dav.fs.load: 2014-08-19T14:45:11.119605 ** Affects: apache2 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package trusty ** Attachment added: /var/log/dist-upgrade/apt.log https://bugs.launchpad.net/bugs/1359227/+attachment/4182491/+files/apt.log -- 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/1359227 Title: package apache2 2.4.7-1-ubuntu4.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1359227/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at:
[Bug 1359227] Re: package apache2 2.4.7-1-ubuntu4.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
** Attachment added: /var/log/dist-upgrade/main.log https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1359227/+attachment/4182505/+files/main.log -- 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/1359227 Title: package apache2 2.4.7-1-ubuntu4.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1359227/+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 1318192] Re: 14.04 host can not ssh to a Cisco router
*** This bug is a duplicate of bug 1287222 *** https://bugs.launchpad.net/bugs/1287222 The bug filed against the Cisco ssh client is CSCuo76464 - its fix resolves the issue. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1318192 Title: 14.04 host can not ssh to a Cisco router To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1318192/+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 1349433] Re: AppArmor breaks seccomp @ Apache mpm-itk
Note that the 'Operation not permitted' error in the original demonstration is desired behaviour- when this does /not/ happen the seccomp filter is not working as intended. It's not clear to me what problem you're see'ing but it /could/ be an affect of the seccomp filter in mpm-itk (governed by the LimitUIDRange setting) if for instance mailman is trying to run Exim which is setuid root. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mailman in Ubuntu. https://bugs.launchpad.net/bugs/1349433 Title: AppArmor breaks seccomp @ Apache mpm-itk To manage notifications about this bug go to: https://bugs.launchpad.net/apparmor/+bug/1349433/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
** No longer affects: juju-core/1.20 -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Sorry, I was thinking that lp:1337091 was released already. We will look at getting it into 1.20.2. If you set the kernel parameter via MAAS [0] prior to first boot, then I would concur that it's probably not going to help. If, however, you modified GRUB after it came up and rebooted, I think that would not have helped due to the network configuration actions only happening on first boot. [0] http://maas.ubuntu.com/docs/kernel-options.html -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
** Also affects: juju-core/1.20 Importance: Undecided Status: New ** Changed in: juju-core/1.20 Milestone: None = 1.20.2 ** Changed in: juju-core/1.20 Importance: Undecided = High ** Changed in: juju-core/1.20 Status: New = Triaged -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
Rick, Sorry for the frustration. It is certainly not unreasonable to expect 14.04 to be working. br0 is only brought up on first boot, so rebooting would not have triggered that part of cloud-config again. I believe we are looking at back-porting Juju 1.20.2 (the next stable release) into 14.04. There are some issues relating to Mongo replica sets in Juju 1.20.1 that we're working on, but it should be stable enough to try out. Would you please see if 1.20.1 makes any difference for you? -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1334337] [NEW] Regression: php5-fpm's socket should be accessible by www-data by default
Public bug reported: The recent security update to php5 broke common configurations for php5-fpm. From IRC: asomething mdeslaur, did you see jdub's comment in LP: #1307027? ubottu Launchpad bug 1307027 in php5 (Ubuntu) php5-fpm: Possible privilege escalation due to insecure default permissions of sockets [Undecided,Fix released] https://launchpad.net/bugs/1307027 asomething I'm seeing the same thing. I seeing the same thing. Even on a fresh install I need to go edit /etc/php5/fpm/pool.d/www.conf to get php5-fpm working mdeslaur asomething: yes, you need to either relax permissions, or configure it with the account whatever you're accessing it is using * roadmr has quit (Quit: Good night) mdeslaur asomething: whatever procedure you followed to configure integration between your web server and php-fpm needs to be modified asomething hmm... ok. are you saying there is no secure default that will work out of the box? I can handle that, but it seems to break most documentation on the web mdeslaur we could make it default to www-data perhaps...not sure that would cover all the use cases asomething that seems to be the most common, but maybe I'm just not aware of other uses mdeslaur if someone can file a bug, and attach a debdiff, I'll sponsor it for an SRU assuming the SRU team considers it an appropriate change mdeslaur asomething: actually, just file a bug, and I'll push it out as a regression fix asomething ok, will do mdeslaur asomething: thanks infinity mdeslaur: Yeah, that's a perfectly reasonable fix. All webservers in Debian/Ubuntu are meant to run as www-data, so that would cover the common case. infinity mdeslaur: People with weird setups are on their own, but they already knew that. mdeslaur infinity: ok, will do, thanks ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: php5-fpm 5.5.9+dfsg-1ubuntu4.1 ProcVersionSignature: Ubuntu 3.13.0-29.53-generic 3.13.11.2 Uname: Linux 3.13.0-29-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3.2 Architecture: amd64 CurrentDesktop: Unity Date: Wed Jun 25 11:34:20 2014 InstallationDate: Installed on 2014-04-08 (78 days ago) InstallationMedia: Ubuntu 14.04 LTS Trusty Tahr - Daily amd64 (20140408) SourcePackage: php5 UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: php5 (Ubuntu) Importance: Undecided Status: Fix Released ** Affects: php5 (Ubuntu Saucy) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Affects: php5 (Ubuntu Trusty) Importance: Undecided Assignee: Marc Deslauriers (mdeslaur) Status: Confirmed ** Affects: php5 (Ubuntu Utopic) Importance: Undecided Status: Fix Released ** Tags: amd64 apport-bug trusty -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to php5 in Ubuntu. https://bugs.launchpad.net/bugs/1334337 Title: Regression: php5-fpm's socket should be accessible by www-data by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1334337/+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 1250007] Re: Bootstrapping azure causes memory to fill
** Changed in: juju-core Status: In Progress = Fix Committed ** Changed in: juju-core Milestone: next-stable = 1.19.4 -- 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/1250007 Title: Bootstrapping azure causes memory to fill To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1250007/+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 1250007] Re: Bootstrapping azure causes memory to fill
** Changed in: juju-core Status: Triaged = In Progress ** Changed in: juju-core Assignee: (unassigned) = Andrew Wilkins (axwalk) -- 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/1250007 Title: Bootstrapping azure causes memory to fill To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1250007/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
So, my nodes don't have eth0, but p1p1, if that makes any difference. This is most likely the key; the MAAS provider code assumes it's dealing with eth0. Thanks for the information. -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1329917] [NEW] Sync python-django-piston 0.2.3-2 (main) from Debian unstable (main)
Public bug reported: Please sync python-django-piston 0.2.3-2 (main) from Debian unstable (main) Explanation of the Ubuntu delta and why it can be dropped: All Ubuntu changes have been applied in Debian. Changelog entries since current utopic version 0.2.3-1ubuntu5: python-django-piston (0.2.3-2) unstable; urgency=low * Team upload. [ Jakub Wilk ] * Use canonical URIs for Vcs-* fields. * Remove DM-Upload-Allowed; it's no longer used by the archive software. [ Christophe Siraut ] * Enable django 1.4 compatibility. (Closes: #686171) - 02-correct-httpresponse.patch: Correctly use '_base_content_is_iter' or '_is_string' depending on the Django version - 03-django1.4-support.patch: Add support for Django 1.4. * Use dh_python2 * Bump standards version to 3.9.5 without further change * Convert copyright to machine-readable format 1.0 * Add repack script, remove lintian-overrides [ Andrew Starr-Bochicchio ] * Cherry-pick patches from Ubuntu and upstream for Django 1.5 and 1.6 compatability: - 04-json-compat-django1.5.patch: Use json instead of simplejson for Django 1.5. (LP: #1184219) - 05-compat-django1.5-httpresponsewrapper.patch: Compatibility with Django 1.5 for HttpResponseWrapper. (LP: #1185012) - 06-django1.6-wsgirequest-compat.patch: Compatibility with Django 1.6 for WSGIRequest. (LP: #1256957) -- Andrew Starr-Bochicchio a...@debian.org Sat, 31 May 2014 14:43:42 -0400 ** Affects: python-django-piston (Ubuntu) Importance: Wishlist Status: New ** Changed in: python-django-piston (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-django-piston in Ubuntu. https://bugs.launchpad.net/bugs/1329917 Title: Sync python-django-piston 0.2.3-2 (main) from Debian unstable (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django-piston/+bug/1329917/+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 1328683] Re: Bad file descriptor on reboot
Mmm, not sure how this got tagged for lxc package and I don't know how to fix that. :-/ ** Package changed: lxc (Ubuntu) = ubuntu -- 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/1328683 Title: Bad file descriptor on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1328683/+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 1328683] [NEW] Bad file descriptor on reboot
Public bug reported: This is a fresh install of 14.04 LTS Server on VMware ESXi 5.1 or 5.5, I get the same symptom on both servers. I installed with OpenSSH and LAMP packages. After the install, the server reboots and comes up OK. I login, immediately type sudo reboot now and it begins stopping services. After Stopping System V runlevel compatibility [OK] I get [38.342187] init: Error while reading from descriptor: Bad file descriptor. Then it kicks me back to a prompt. ** Affects: ubuntu Importance: Undecided Status: New ** Description changed: This is a fresh install of 14.04 LTS Server on VMware ESXi 5.1 or 5.5, I get the same symptom on both servers. - I installed with OpenSSH and LAMP packages. After the install, the server reboots and comes up OK. I login, immediately type sudo reboot now and it begins stopping services. After Stopping System V runlevel compatibility [OK] I get + I installed with OpenSSH and LAMP packages. After the install, the server reboots and comes up OK. I login, immediately type sudo reboot now and it begins stopping services. After Stopping System V runlevel compatibility [OK] I get [38.342187] init: Error while reading from descriptor: Bad file descriptor. Then it kicks me back to a prompt. -- 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/1328683 Title: Bad file descriptor on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+bug/1328683/+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 1287222] Re: openssh-client 6.5 regression bug with certain servers
I've filed the bug CSCuo76464 to get this fixed on the cisco side. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/1287222 Title: openssh-client 6.5 regression bug with certain servers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1287222/+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 997927] Re: NM reports VPN service 'openvpn' disappeared
I am having a similar problem on Ubuntu-14.04. However, at one point, I was able to connect to my vpn with 14.04. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to openvpn in Ubuntu. https://bugs.launchpad.net/bugs/997927 Title: NM reports VPN service 'openvpn' disappeared To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openvpn/+bug/997927/+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 1323929] [NEW] Sync python-django 1.6.5-1 (main) from Debian sid (main)
Public bug reported: Please sync python-django 1.6.5-1 (main) from Debian sid (main) Explanation of the Ubuntu delta and why it can be dropped: All Ubuntu patches are backports from upstream. This release contains them all. Changelog entries since current utopic version 1.6.1-2ubuntu0.3: python-django (1.6.5-1) unstable; urgency=high * New upstream security release. - Caches may be allowed to store and serve private data (CVE-2014-1418) - Malformed URLs from user input incorrectly validated * Drop partial_functions_reverse.patch (merged upstream). -- Raphaël Hertzog hert...@debian.org Wed, 14 May 2014 22:49:59 +0200 python-django (1.6.3-2) unstable; urgency=high * Fix regression of reverse() and partial views. (LP: #1311433) Thanks Preston Timmons. -- Luke Faraone lfara...@debian.org Tue, 22 Apr 2014 20:44:18 -0700 python-django (1.6.3-1) unstable; urgency=high * New upstream security release. - Unexpected code execution using ``reverse()`` - CVE-2014-0472 - Caching of anonymous pages could reveal CSRF token - CVE-2014-0473 - MySQL typecasting could result in unexpected matches - CVE-2014-0474 * Drop patches 07_translation_encoding_fix and ticket21869.diff; merged upstream -- Luke Faraone lfara...@debian.org Mon, 21 Apr 2014 16:47:14 -0700 ** Affects: python-django (Ubuntu) Importance: Wishlist Status: New ** Changed in: python-django (Ubuntu) Importance: Undecided = Wishlist -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to python-django in Ubuntu. https://bugs.launchpad.net/bugs/1323929 Title: Sync python-django 1.6.5-1 (main) from Debian sid (main) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/python-django/+bug/1323929/+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 1058760] Re: unmatched entries for dovecot login
Just chiming in, the patch worked for me as well on Ubuntu 12.04.4 with Logwatch 7.4.0 and Dovecot 2.0.19. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to logwatch in Ubuntu. https://bugs.launchpad.net/bugs/1058760 Title: unmatched entries for dovecot login To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1058760/+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 1316272] Re: juju destroy-environment =256 nodes fails
** Changed in: juju-core Assignee: (unassigned) = Andrew Wilkins (axwalk) ** Changed in: juju-core Status: Triaged = In Progress -- 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/1316272 Title: juju destroy-environment =256 nodes fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1316272/+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 1316272] Re: juju destroy-environment =256 nodes fails
** Branch linked: lp:~axwalk/juju-core/lp1260171-stopinstances-ids -- 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/1316272 Title: juju destroy-environment =256 nodes fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1316272/+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 1316272] Re: juju destroy-environment =256 nodes fails
Sadly I do not have a 256+ node MAAS to test with. I'm going to mark this as Fix Committed; please let me know if you still have issues. ** Changed in: juju-core Status: In Progress = Fix Committed -- 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/1316272 Title: juju destroy-environment =256 nodes fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1316272/+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 1316272] Re: juju destroy-environment =256 nodes fails
We already do POST when stopping instances. The problem is likely that we first have to map instance IDs to instances so we can stop them (this is dumb and needs to change; see lp:1260171). -- 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/1316272 Title: juju destroy-environment =256 nodes fails To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1316272/+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 1318192] [NEW] 14.04 host can not ssh to a Cisco router
Public bug reported: I can not connect from a freshly installed 14.04 box to a Cisco CSR1000V. 12.04 connects with no issues. Debugging this, the symptoms are identical to this bug report: https://bugzilla.redhat.com/show_bug.cgi?id=1026430 see the logs below (hostnames, addresses, and usernames below are edited). Failing attempt (the default settings): $ ssh -vvv username@router.example OpenSSH_6.6, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to router.example [2001:db8::1] port 22. debug1: Connection established. debug1: SELinux support disabled debug1: identity file /home/ubuntu/.ssh/id_rsa type -1 debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1 debug1: identity file /home/ubuntu/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_ed25519 type -1 debug1: identity file /home/ubuntu/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6p1 Ubuntu-2ubuntu1 debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,arcfour256,arcfour128,aes128-...@openssh.com,aes256-...@openssh.com,chacha20-poly1...@openssh.com,aes128-cbc,3des-cbc,blowfish-cbc,cast128-cbc,aes192-cbc,aes256-cbc,arcfour,rijndael-...@lysator.liu.se debug2: kex_parse_kexinit: hmac-md5-...@openssh.com,hmac-sha1-...@openssh.com,umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-sha1,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96 debug2: kex_parse_kexinit: hmac-md5-...@openssh.com,hmac-sha1-...@openssh.com,umac-64-...@openssh.com,umac-128-...@openssh.com,hmac-sha2-256-...@openssh.com,hmac-sha2-512-...@openssh.com,hmac-ripemd160-...@openssh.com,hmac-sha1-96-...@openssh.com,hmac-md5-96-...@openssh.com,hmac-md5,hmac-sha1,umac...@openssh.com,umac-...@openssh.com,hmac-sha2-256,hmac-sha2-512,hmac-ripemd160,hmac-ripemd...@openssh.com,hmac-sha1-96,hmac-md5-96debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: none,z...@openssh.com,zlib debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: kex_parse_kexinit: diffie-hellman-group-exchange-sha1,diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 debug2: kex_parse_kexinit: ssh-rsa debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc debug2: kex_parse_kexinit: aes128-ctr,aes192-ctr,aes256-ctr,aes128-cbc,3des-cbc,aes192-cbc,aes256-cbc debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96 debug2: kex_parse_kexinit: hmac-sha1,hmac-sha1-96 debug2: kex_parse_kexinit: none debug2: kex_parse_kexinit: none debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: debug2: kex_parse_kexinit: first_kex_follows 0 debug2: kex_parse_kexinit: reserved 0 debug2: mac_setup: setup hmac-sha1 debug1: kex: server-client aes128-ctr hmac-sha1 none debug2: mac_setup: setup hmac-sha1 debug1: kex: client-server aes128-ctr hmac-sha1 none debug1: SSH2_MSG_KEX_DH_GEX_REQUEST(102476808192) sent debug1: expecting SSH2_MSG_KEX_DH_GEX_GROUP Connection closed by 2001:db8::1 Working attempt: $ ssh -vvv -o KexAlgorithms=diffie-hellman-group14-sha1,diffie-hellman-group1-sha1 username@router.example OpenSSH_6.6, OpenSSL 1.0.1f 6 Jan 2014 debug1: Reading configuration data /etc/ssh/ssh_config debug1: /etc/ssh/ssh_config line 19: Applying options for * debug2: ssh_connect: needpriv 0 debug1: Connecting to router.example [2001:db8::1] port 22. debug1: Connection established. debug1: identity file /home/ubuntu/.ssh/id_rsa type -1 debug1: identity file /home/ubuntu/.ssh/id_rsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa type -1 debug1: identity file /home/ubuntu/.ssh/id_dsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_ecdsa type -1 debug1: identity file /home/ubuntu/.ssh/id_ecdsa-cert type -1 debug1: identity file /home/ubuntu/.ssh/id_ed25519 type -1 debug1: identity file /home/ubuntu/.ssh/id_ed25519-cert type -1 debug1: Enabling compatibility mode for protocol 2.0 debug1: Local version string SSH-2.0-OpenSSH_6.6p1 Ubuntu-2ubuntu1 debug1: Remote protocol version 1.99, remote software version Cisco-1.25 debug1: no match: Cisco-1.25 debug2: fd 3 setting O_NONBLOCK debug3: load_hostkeys: loading entries for host router.example from file /home/ubuntu/.ssh/known_hosts debug3: load_hostkeys: found key type RSA in file /home/ubuntu/.ssh/known_hosts:1 debug3: load_hostkeys:
[Bug 1313785] Re: Can't SSH with juju ssh command to EC2 instance.
** Changed in: juju-core Status: In Progress = Fix Committed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with juju ssh command to EC2 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1313785/+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 1313785] Re: Can't SSH with juju ssh command to EC2 instance.
** Changed in: juju-core Status: Triaged = In Progress ** Changed in: juju-core Assignee: (unassigned) = Andrew Wilkins (axwalk) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with juju ssh command to EC2 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1313785/+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 1313785] Re: Can't SSH with juju ssh command to EC2 instance.
Thanks, I hadn't noticed the version difference. I can also reproduce the issue with a 1.18.2 server. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with juju ssh command to EC2 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1313785/+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 1313785] Re: Can't SSH with juju ssh command to EC2 instance.
** Branch linked: lp:~axwalk/juju-core/lp1313785-ssh-useproxy -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with juju ssh command to EC2 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1313785/+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 1316720] Re: We should increase time to live for messages and queues for max value in mcollective
** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** No longer affects: qemu-kvm (Ubuntu) -- 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/1316720 Title: We should increase time to live for messages and queues for max value in mcollective To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1316720/+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 1316812] Re: ubuntu qemu-kvm package attempts to start a service and fails
** Also affects: qemu-kvm (Ubuntu) Importance: Undecided Status: New ** Attachment added: apt-cache show qemu-kvm https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1316812/+attachment/4106762/+files/apt-cache%20show%20qemu-kvm -- 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/1316812 Title: ubuntu qemu-kvm package attempts to start a service and fails To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1316812/+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 1316812] Re: ubuntu qemu-kvm package attempts to start a service and fails
** Description changed: Iso 172, 180, 183 Ubuntu fails to deploy because qemu-kvm fails to install because its init service wont start. init fails due to - cat /etc/init/qemu-kvm.conf + cat /etc/init/qemu-kvm.conf ... pre-start script - # Silently exit if the package isn't installed anymore - if [ ! -e /usr/bin/kvm ]; then - exit 0 - fi - [ -r /etc/default/qemu-kvm ] . /etc/default/qemu-kvm - # Load the appropriate module, respecting blacklists - if grep -qs ^flags.* vmx /proc/cpuinfo; then - modprobe -b kvm_intel $KVM_NESTED || true - chown root:kvm /dev/kvm - chmod 0660 /dev/kvm - elif grep -qs ^flags.* svm /proc/cpuinfo; then - modprobe -b kvm_amd || true - chown root:kvm /dev/kvm - chmod 0660 /dev/kvm - fi - ... + # Silently exit if the package isn't installed anymore + if [ ! -e /usr/bin/kvm ]; then + exit 0 + fi + [ -r /etc/default/qemu-kvm ] . /etc/default/qemu-kvm + # Load the appropriate module, respecting blacklists + if grep -qs ^flags.* vmx /proc/cpuinfo; then + modprobe -b kvm_intel $KVM_NESTED || true + chown root:kvm /dev/kvm + chmod 0660 /dev/kvm + elif grep -qs ^flags.* svm /proc/cpuinfo; then + modprobe -b kvm_amd || true + chown root:kvm /dev/kvm + chmod 0660 /dev/kvm + fi + ... On guests that have parent hosts that support kvm_nested - /proc/cpuinfo will contain 'svm' or 'vmx' however because we are already a guest, /dev/kvm might not create, running modprobe on kvm_amd or kvm_intell will fail, then chmod will fail because /dev/kvm still doesn't exist. This causes init to fail + /proc/cpuinfo will contain 'svm' or 'vmx' however because we are already a guest, /dev/kvm might not create, running modprobe on kvm_amd or kvm_intel will fail, then chmod will fail because /dev/kvm still doesn't exist. This causes init to fail + + root@node-1:/etc/init# modprobe kvm + root@node-1:/etc/init# modprobe kvm_amd + FATAL: Error inserting kvm_amd (/lib/modules/3.11.0-18-generic/kernel/arch/x86/kvm/kvm-amd.ko): Operation not supported + root@node-1:/etc/init# ls -l /dev/kvm + ls: cannot access /dev/kvm: No such file or directory we should probably change the first test from /usr/bin/kvm to /dev/kvm like in Debian SID case $1 in - start|restart|force-reload) + start|restart|force-reload) - [ ! -e /dev/kvm ] || exit 0 # nothing to do + [ ! -e /dev/kvm ] || exit 0 # nothing to do -- 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/1316812 Title: ubuntu qemu-kvm package attempts to start a service and fails To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1316812/+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 1316812] Re: ubuntu qemu-kvm package attempts to start a service and fails
** Description changed: Iso 172, 180, 183 - Ubuntu fails to deploy because qemu-kvm fails to install because its - init service wont start. + Ubuntu (guest) 12.04.04 qemu-kvm fails to install because upstart wont + pass. + + root@node-2:~# apt-get install -f + Reading package lists... Done + Building dependency tree + Reading state information... Done + 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. + 3 not fully installed or removed. + After this operation, 0 B of additional disk space will be used. + Setting up qemu-kvm (1.2.0+noroms-0ubuntu7.12.10) ... + start: Job failed to start + invoke-rc.d: initscript qemu-kvm, action start failed. + dpkg: error processing qemu-kvm (--configure): + subprocess installed post-installation script returned error exit status 1 + + expected result: qemu-kvm should install and start anyways even if + acceleration can't be loaded. + + grep ^flags.* svm /proc/cpuinfo + flags : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 syscall nx mmxext fxsr_opt pdpe1gb lm 3dnowext 3dnow rep_good nopl extd_apicid pni cx16 popcnt hypervisor cmp_legacy svm cr8_legacy abm sse4a misalignsse 3dnowprefetch osvw + + root@node-1:/etc/init# modprobe kvm + root@node-1:/etc/init# modprobe kvm_amd + FATAL: Error inserting kvm_amd (/lib/modules/3.11.0-18-generic/kernel/arch/x86/kvm/kvm-amd.ko): Operation not supported + root@node-1:/etc/init# ls -l /dev/kvm + ls: cannot access /dev/kvm: No such file or directory + + dmesg: + [10925.939670] has_svm: can't execute cpuid_800a + [10925.939677] kvm: no hardware support + init fails due to cat /etc/init/qemu-kvm.conf ... pre-start script # Silently exit if the package isn't installed anymore if [ ! -e /usr/bin/kvm ]; then exit 0 fi [ -r /etc/default/qemu-kvm ] . /etc/default/qemu-kvm # Load the appropriate module, respecting blacklists if grep -qs ^flags.* vmx /proc/cpuinfo; then modprobe -b kvm_intel $KVM_NESTED || true chown root:kvm /dev/kvm chmod 0660 /dev/kvm elif grep -qs ^flags.* svm /proc/cpuinfo; then modprobe -b kvm_amd || true chown root:kvm /dev/kvm chmod 0660 /dev/kvm fi - ... + ... - On guests that have parent hosts that support kvm_nested - /proc/cpuinfo will contain 'svm' or 'vmx' however because we are already a guest, /dev/kvm might not create, running modprobe on kvm_amd or kvm_intel will fail, then chmod will fail because /dev/kvm still doesn't exist. This causes init to fail + It appears that guest might have been passed bad CPU flags and qemu-kvm + in host might not be allowing kvm acceleration to load. It appears that + similar results have been noted in Debian upstream, where they are + testing for -e /dev/kvm before attempting to load more acceleration - root@node-1:/etc/init# modprobe kvm - root@node-1:/etc/init# modprobe kvm_amd - FATAL: Error inserting kvm_amd (/lib/modules/3.11.0-18-generic/kernel/arch/x86/kvm/kvm-amd.ko): Operation not supported - root@node-1:/etc/init# ls -l /dev/kvm - ls: cannot access /dev/kvm: No such file or directory - - we should probably change the first test from /usr/bin/kvm to /dev/kvm - like in Debian SID + in Debian SID case $1 in start|restart|force-reload) [ ! -e /dev/kvm ] || exit 0 # nothing to do -- 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/1316812 Title: ubuntu qemu-kvm package attempts to start a service and fails To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1316812/+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 1316812] Re: ubuntu qemu-kvm package attempts to start a service and fails
** Changed in: fuel Status: Confirmed = Triaged -- 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/1316812 Title: ubuntu qemu-kvm package attempts to start a service and fails To manage notifications about this bug go to: https://bugs.launchpad.net/fuel/+bug/1316812/+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 1313785] Re: Can't SSH with juju ssh command to EC2 instance.
I am not able to reproduce this. juju ssh will now ssh to machine 0's public address directly, and then proxy through that to machine 0's internal address. This is to support environments where machines do not have unique public addresses (i.e. with load balancing). Can you please ssh to the machine directly and then check whether you can resolve ip-172-31-21-242.us-west-2.compute.internal. If that does not resolve, that would indicate a problem with EC2. If it *does* resolve, then please try juju ssh again with --debug and attach the output. ** Changed in: juju-core Status: Triaged = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju in Ubuntu. https://bugs.launchpad.net/bugs/1313785 Title: Can't SSH with juju ssh command to EC2 instance. To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1313785/+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 1312936] Re: Post-installation script fails
On Mon, Apr 28, 2014 at 4:57 AM, James Page james.p...@ubuntu.com wrote: How much memory does you installation have? The default innodb buffer pool size increased in 5.6 and I'm wondering if this is the issue you are hitting? That sounds like it might be it. This is on a 512MB VPS. I'll try to reproduce on something larger. Thanks! -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-5.6 in Ubuntu. https://bugs.launchpad.net/bugs/1312936 Title: Post-installation script fails To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-5.6/+bug/1312936/+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 1032633] Re: Keystone's token table grows unconditionally when using SQL backend.
A CLI command is an interesting stopgap, but on a heavily utilized OpenStack installation with automated tools operating against OpenStack, this has a high manual maintenance cost. Surely there is some better default that lies in the middle ground between keeping tokens for ever and ever and requiring a manual removal of tokens? As a reference point, I wasn't even aware this was an issue, until one of our test deployments of grizzly using a limited IO system started acting horribly (30 second response times). After tracing the problem from nova to keystone to mysql, I found a 442,000 row token table with 440,000 expired tokens. I went and checked our havana test on a somewhat beefier system and found 1M rows. This issue is a timebomb for any production OS install. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1032633 Title: Keystone's token table grows unconditionally when using SQL backend. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1032633/+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 1032633] Re: Keystone's token table grows unconditionally when using SQL backend.
That seems reasonable. I would suggest adding that as a step to the OpenStack setup documentation. No one has infinite database space, eventually all used OpenStack installations will suffer unless this is done. Regardless of what component (or person) has to complete the task, they'll need to be aware of it. I would prefer to see some kind of automatically expire old tokens configuration option so that the maintenance of keystone stays in keystone - whether that be implemented as a expire-on-access query or cron-derived mechanism, but re-implementing cron is not great and a purge tagged on to other operations could cause a slowdown on those operations. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to keystone in Ubuntu. https://bugs.launchpad.net/bugs/1032633 Title: Keystone's token table grows unconditionally when using SQL backend. To manage notifications about this bug go to: https://bugs.launchpad.net/keystone/+bug/1032633/+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 1296912] Re: python-qpid-python package does not exist
** Also affects: heat (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heat in Ubuntu. https://bugs.launchpad.net/bugs/1296912 Title: python-qpid-python package does not exist To manage notifications about this bug go to: https://bugs.launchpad.net/neutron/+bug/1296912/+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 1296912] Re: python-qpid-python package does not exist
** No longer affects: neutron ** Summary changed: - python-qpid-python package does not exist + python-qpid-python package does not exist in precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to heat in Ubuntu. https://bugs.launchpad.net/bugs/1296912 Title: python-qpid-python package does not exist in precise To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/heat/+bug/1296912/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
** Changed in: juju-core Assignee: Roger Peppe (rogpeppe) = Andrew Wilkins (axwalk) ** Changed in: juju-core Status: Triaged = In Progress -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1248283] Re: juju userdata should not restart networking
** Changed in: juju-core Status: Triaged = In Progress ** Changed in: juju-core Assignee: (unassigned) = Andrew Wilkins (axwalk) ** Changed in: juju-core Milestone: 1.18.0 = 1.17.6 -- 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/1248283 Title: juju userdata should not restart networking To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1271144] Re: br0 not brought up by cloud-init script with MAAS provider
** Branch linked: lp:~axwalk/juju-core/lp1271144-maas-bridge-utils ** Changed in: juju-core Status: In Progress = Fix Committed -- 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/1271144 Title: br0 not brought up by cloud-init script with MAAS provider To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1271144/+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 1248283] Re: juju userdata should not restart networking
** Branch linked: lp:~axwalk/juju-core/lp1271144-maas-bridge-utils ** Changed in: juju-core Status: In Progress = Fix Committed -- 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/1248283 Title: juju userdata should not restart networking To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1248283/+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 1284127] Re: juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client
This only affects 1.17.2 and 1.17.3 interaction, so we can just close it. There was a change introduced in 1.17.2 to add an image-stream config attribute, which was previously specific to the Azure provider. The config default (omit) was invalid, though, causing the bug lp:1277636. We fixed this in 1.17.3 by changing the default to match what it was for Azure (empty string). If you try to mix 1.17.2 and 1.17.3, you'll get this complaint. 1.17.3 has set image-stream to , and the 1.17.2 client doesn't like that. -- 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/1284127 Title: juju deploy fails against juju-core 1.17.3 environment with 1.17.2 client To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1284127/+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 1257186] Re: memory leakage messages
** Bug watch added: Samba Bugzilla #8449 https://bugzilla.samba.org/show_bug.cgi?id=8449 ** Also affects: samba via https://bugzilla.samba.org/show_bug.cgi?id=8449 Importance: Unknown Status: Unknown -- 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/1257186 Title: memory leakage messages To manage notifications about this bug go to: https://bugs.launchpad.net/samba/+bug/1257186/+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 1264815] Re: nova-compute can't be setting up during install on trusty
Great! Many thanks Chuck :-) -- 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/1264815 Title: nova-compute can't be setting up during install on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1264815/+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 1265443] Re: nona on trusty: valueError exception
Does this patch need to be cherrypicked from the upstream project into the Ubuntu archive? -- 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/1265443 Title: nona on trusty: valueError exception To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1265443/+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 1264815] Re: nova-compute can't be setting up during install on trusty
The workaround that's been identified is to download and install python- webob_1.2.3. -- 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/1264815 Title: nova-compute can't be setting up during install on trusty To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1264815/+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
