[Bug 1053424] Re: rabbitmq-server-2.7.1-0ubuntu4 discards log output
Hi Emile, thanks for taking the time to file this bug report and help us make Ubuntu better. I can confirm that this package does not seem to log the vital things coming from rabbitmq-server's stdout and/or stderr. ** Changed in: rabbitmq-server (Ubuntu) Status: New = Confirmed ** Changed in: rabbitmq-server (Ubuntu) Importance: Undecided = High -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to rabbitmq-server in Ubuntu. https://bugs.launchpad.net/bugs/1053424 Title: rabbitmq-server-2.7.1-0ubuntu4 discards log output To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/1053424/+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 1053414] Re: smbd crashed when trying to connect from Ubuntu
James Yes, with stock kernel I've not encountered that issue, but then we should be aware of that for the lts-quantal-backport kernel, but I'm not sure where to file that... -- 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/1053414 Title: smbd crashed when trying to connect from Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/1053414/+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 1061277] Re: ssh ignores ssh_config
Thank you for taking the time to report this bug and helping to make Ubuntu better. Indeed it should generate an error on startup if you get that wrong, and it does for me: With openssh-client 1:5.9p1-5ubuntu1: $ ssh localhost /etc/ssh/ssh_config: line 54: Bad configuration option: AllowUsers /etc/ssh/ssh_config: terminating, 1 bad configuration options Marking this as Incomplete for now. If you can provide accurate reproduction steps then please add them to this bug and change the status back to New. I'm also marking as Importance: Low as it affects unusual end-user configurations only, as per the bug importance guidelines. This is unlikely to get fixed in Ubuntu without it being fixed upstream first, so if you'd like to see it fixed it would be best to file a bug upstream once you have detailed steps to reproduce. ** Changed in: openssh (Ubuntu) Status: New = Incomplete ** Changed in: openssh (Ubuntu) Importance: Undecided = Low ** Summary changed: - ssh ignores ssh_config + ssh ignores invalid configuration directives in ssh_config -- 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/1061277 Title: ssh ignores invalid configuration directives in ssh_config To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/1061277/+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 879710] Re: ubuntu-vm-builder crashes when trying to umount tmp directory.
This bug duplicates https://bugs.launchpad.net/vmbuilder/+bug/966439 . The workaround is to add --removepkg=cron to the vmbuilder command line. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vm-builder in Ubuntu. https://bugs.launchpad.net/bugs/879710 Title: ubuntu-vm-builder crashes when trying to umount tmp directory. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vm-builder/+bug/879710/+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 1063175] Re: mysql 5.1.66 update
i will do it myself, all i need is a tutorial how to compile from source or how can i apply a patch into current version ... thanks in advance -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to mysql-dfsg-5.1 in Ubuntu. https://bugs.launchpad.net/bugs/1063175 Title: mysql 5.1.66 update To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mysql-dfsg-5.1/+bug/1063175/+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 1065883] Re: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder
** Changed in: nova Assignee: (unassigned) = James Page (james-page) ** Changed in: nova Status: New = In Progress -- 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/1065883 Title: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065883/+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 1065883] Re: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder
This bug was fixed in the package nova - 2012.2-0ubuntu5 --- nova (2012.2-0ubuntu5) quantal-proposed; urgency=low [ Adam Gandelman ] * Move management of /var/lib/nova/volumes from nova-common to nova-volume. Ensure it has proper permissions. (LP: #1065320) * debian/patches/avoid_setuptools_git_dependency.patch: Remove setuptools_git from tools/pip-requires to avoid it being automatically added to python-nova's runtime dependencies. (LP: #1059907) [ Chuck Short ] * debian/patches/rbd-security.patch: Support override of ceph rbd user and secret in nova-compute. (LP: #1065883) * debian/patches/ubuntu/fix-libvirt-firewall-slowdown.patch: Fix refreshing of security groups in libvirt not to block on RPC calls. (LP: #1062314) * debian/patches/ubuntu/fix-ec2-volume-id-mappings.patch: Read deleted snapshot and volume id mappings. (LP: #1065785) -- Chuck Short zul...@ubuntu.com Fri, 12 Oct 2012 12:35:01 -0500 ** Changed in: nova (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065883 Title: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065883/+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 1065785] Re: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade
This bug was fixed in the package nova - 2012.2-0ubuntu5 --- nova (2012.2-0ubuntu5) quantal-proposed; urgency=low [ Adam Gandelman ] * Move management of /var/lib/nova/volumes from nova-common to nova-volume. Ensure it has proper permissions. (LP: #1065320) * debian/patches/avoid_setuptools_git_dependency.patch: Remove setuptools_git from tools/pip-requires to avoid it being automatically added to python-nova's runtime dependencies. (LP: #1059907) [ Chuck Short ] * debian/patches/rbd-security.patch: Support override of ceph rbd user and secret in nova-compute. (LP: #1065883) * debian/patches/ubuntu/fix-libvirt-firewall-slowdown.patch: Fix refreshing of security groups in libvirt not to block on RPC calls. (LP: #1062314) * debian/patches/ubuntu/fix-ec2-volume-id-mappings.patch: Read deleted snapshot and volume id mappings. (LP: #1065785) -- Chuck Short zul...@ubuntu.com Fri, 12 Oct 2012 12:35:01 -0500 ** Changed in: nova (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065785 Title: volume and snapshot IDs do not correctly map to UUIDs after folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1065785/+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 1065320] Re: /var/lib/nova/volumes is owned by root after Folsom upgrade
This bug was fixed in the package nova - 2012.2-0ubuntu5 --- nova (2012.2-0ubuntu5) quantal-proposed; urgency=low [ Adam Gandelman ] * Move management of /var/lib/nova/volumes from nova-common to nova-volume. Ensure it has proper permissions. (LP: #1065320) * debian/patches/avoid_setuptools_git_dependency.patch: Remove setuptools_git from tools/pip-requires to avoid it being automatically added to python-nova's runtime dependencies. (LP: #1059907) [ Chuck Short ] * debian/patches/rbd-security.patch: Support override of ceph rbd user and secret in nova-compute. (LP: #1065883) * debian/patches/ubuntu/fix-libvirt-firewall-slowdown.patch: Fix refreshing of security groups in libvirt not to block on RPC calls. (LP: #1062314) * debian/patches/ubuntu/fix-ec2-volume-id-mappings.patch: Read deleted snapshot and volume id mappings. (LP: #1065785) -- Chuck Short zul...@ubuntu.com Fri, 12 Oct 2012 12:35:01 -0500 ** Changed in: nova (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1065320 Title: /var/lib/nova/volumes is owned by root after Folsom upgrade To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1065320/+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 1062314] Re: do_refresh_security_group_rules in nova.virt.firewall is very slow
This bug was fixed in the package nova - 2012.2-0ubuntu5 --- nova (2012.2-0ubuntu5) quantal-proposed; urgency=low [ Adam Gandelman ] * Move management of /var/lib/nova/volumes from nova-common to nova-volume. Ensure it has proper permissions. (LP: #1065320) * debian/patches/avoid_setuptools_git_dependency.patch: Remove setuptools_git from tools/pip-requires to avoid it being automatically added to python-nova's runtime dependencies. (LP: #1059907) [ Chuck Short ] * debian/patches/rbd-security.patch: Support override of ceph rbd user and secret in nova-compute. (LP: #1065883) * debian/patches/ubuntu/fix-libvirt-firewall-slowdown.patch: Fix refreshing of security groups in libvirt not to block on RPC calls. (LP: #1062314) * debian/patches/ubuntu/fix-ec2-volume-id-mappings.patch: Read deleted snapshot and volume id mappings. (LP: #1065785) -- Chuck Short zul...@ubuntu.com Fri, 12 Oct 2012 12:35:01 -0500 ** Changed in: nova (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1062314 Title: do_refresh_security_group_rules in nova.virt.firewall is very slow To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1062314/+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 1059907] Re: python-nova depends on python-setuptools-git?
This bug was fixed in the package nova - 2012.2-0ubuntu5 --- nova (2012.2-0ubuntu5) quantal-proposed; urgency=low [ Adam Gandelman ] * Move management of /var/lib/nova/volumes from nova-common to nova-volume. Ensure it has proper permissions. (LP: #1065320) * debian/patches/avoid_setuptools_git_dependency.patch: Remove setuptools_git from tools/pip-requires to avoid it being automatically added to python-nova's runtime dependencies. (LP: #1059907) [ Chuck Short ] * debian/patches/rbd-security.patch: Support override of ceph rbd user and secret in nova-compute. (LP: #1065883) * debian/patches/ubuntu/fix-libvirt-firewall-slowdown.patch: Fix refreshing of security groups in libvirt not to block on RPC calls. (LP: #1062314) * debian/patches/ubuntu/fix-ec2-volume-id-mappings.patch: Read deleted snapshot and volume id mappings. (LP: #1065785) -- Chuck Short zul...@ubuntu.com Fri, 12 Oct 2012 12:35:01 -0500 ** Changed in: nova (Ubuntu) Status: Confirmed = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nova in Ubuntu. https://bugs.launchpad.net/bugs/1059907 Title: python-nova depends on python-setuptools-git? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nova/+bug/1059907/+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 1066570] Re: should build-depend on librbd-dev
Thank you for taking the time to report this bug and helping to make Ubuntu better. I can't reproduce a build failure in a Debian sid chroot using sbuild. Looking at debian/control, I see librbd-dev listed as a Build-Depends on line 22. This is with 1.2.0+noroms-0ubuntu2 pulled from Quantal just now. Note that the bzr packaging branch is currently out of date. Since we have a mismatch somewhere I'll attach the debian/changelog and debian/control that I'm looking at. What am I missing? -- 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/1066570 Title: should build-depend on librbd-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+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 1066570] Re: should build-depend on librbd-dev
** Attachment added: control https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+attachment/3398777/+files/control -- 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/1066570 Title: should build-depend on librbd-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+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 1066570] Re: should build-depend on librbd-dev
** Attachment added: changelog https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+attachment/3398778/+files/changelog ** Changed in: qemu-kvm (Ubuntu) Status: New = Incomplete -- 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/1066570 Title: should build-depend on librbd-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+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 1060184] Re: puppet client init script pid file error
Thank you for taking the time to report this bug and helping to make Ubuntu better. I have not managed to reproduce this on Precise using puppet 2.7.11-1ubuntu2.1. When I start puppet using /etc/init.d/puppet start, I get /var/run/puppet/agent.pid. When I stop it using /etc/init.d/puppet stop, the process seems to terminate correctly although the pidfile remains. This does not seem to cause a problem starting puppet again though; the pidfile gets updated as expected. /etc/init.d/puppet restart appears to work fine, too. Marking this bug as Incomplete for now. If you are still having problems, please post exact steps to reproduce, including exact commands used, and then change the status back to New. ** Changed in: puppet (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1060184 Title: puppet client init script pid file error To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 1066834] [NEW] LevelForFileTypesDetection=0 produces unexpected results
Public bug reported: When setting LevelForFileTypesDetection=0 in the Awstats config file, Awstats starts to count every hit as a page load, ie the number of Hits and Pages in the Awstats report is identical. In other words, the Pages statistics becomes meaningless. This was not happening with older versions of Awstats, there must have been a change in version 7.0. While this may not be a bug, it would be good if it's documented somewhere that LevelForFileTypesDetection must be set to 2 even if you turn ShowFileTypesStats off. Currently the documentation only says that leaving LevelForFileTypesDetection=2 reduces Awstats speed by 1%, so users who don't use/need the file types report might be tempted to turn it off. ** Affects: awstats (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1066834 Title: LevelForFileTypesDetection=0 produces unexpected results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1066834/+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 1065714] Re: vsftpd 2.3.5 needs allow_writeable_chroot option
Thank you for taking the time to report this bug and helping to make Ubuntu better. In order to keep stable releases stable, updates after release are only considered under specific circumstances. Details of the process and of the criteria required are listed here: https://wiki.ubuntu.com/StableReleaseUpdates#When I understand that this makes it difficult for users of the LTS release to have writeable chroots, but now that the LTS is released and the fix doesn't meet the above criteria, I don't think this will change for 12.04. But note that the stable release updates team makes the decision on this by following the above policy and not me. If you'd like a newer version of vsftpd to be made generally available for users who do want to use the allow_writeable_chroot option, then the backports repository is an appropriate venue for this. With a backport, users who want the feature could just add the backports repository and install vsftpd from there. You can find out more about backports and how to request one here: https://wiki.ubuntu.com/UbuntuBackports However, you can generally only backport after the development release of Ubuntu contains the version requested. I see that Debian unstable has vsftpd 3.0.2-1 now, and Ubuntu should merge this in a month or two, after the imminent release of Quantal. So a backport would take at least that long since we are in final freeze at the moment. I appreciate the difficulty this causes and I regret that this can't be resolved sooner or just by updating the LTS. But I hope you understand that the LTS can only be kept stable if it is not modified to add features to minimise the risk of regressions. Marking this bug as Invalid, as the request was to backport a feature to an existing release, which would violate SRU policy. I'm not sure that we need a bug to track the merge of vsftpd from Debian sid, as this will happen in due course anyway. But once the next development release contains vsftpd 3 for the feature you need, please do go ahead and follow the backports procedure and file a backports bug against the Precise Backports project if you want to go down that route. ** Changed in: vsftpd (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to vsftpd in Ubuntu. https://bugs.launchpad.net/bugs/1065714 Title: vsftpd 2.3.5 needs allow_writeable_chroot option To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/vsftpd/+bug/1065714/+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 1060184] Re: puppet client init script pid file error
After a clean install i type
#apt-get install puppet
following which i change the line in /etc/default/puppet from START=no to
START=yes
then i join the puppet client to my puppet server using
#puppetd --server servername --waitforcert 60 --test
on the client side and
#puppetca --sign servername
on the server side
then the following session can occur:
root@testserv1:~# pgrep puppet
root@testserv1:~# dpkg -s puppet
Package: puppet
Status: install ok installed
Priority: optional
Section: admin
Installed-Size: 336
Maintainer: Ubuntu Developers ubuntu-devel-disc...@lists.ubuntu.com
Architecture: all
Version: 2.7.11-1ubuntu2.1
Depends: puppet-common (= 2.7.11-1ubuntu2.1), ruby1.8
Pre-Depends: dpkg (= 1.15.7.2)
Recommends: rdoc
Suggests: puppet-el, vim-puppet, etckeeper
Conffiles:
/etc/init.d/puppet 05404948b351469e8d56ac080f5d92fe
/etc/default/puppet 9e5a0cf174ccff1af10342297b8b1bdb
Description: Centralized configuration management - agent startup and
compatibility scripts
This package contains the startup script and compatbility scripts for the
puppet agent, which is the process responsible for configuring the local node.
.
Puppet lets you centrally manage every important aspect of your system
using a cross-platform specification language that manages all the
separate elements normally aggregated in different files, like users,
cron jobs, and hosts, along with obviously discrete elements like
packages, services, and files.
.
Puppet's simple declarative specification language provides powerful
classing abilities for drawing out the similarities between hosts while
allowing them to be as specific as necessary, and it handles dependency
and prerequisite relationships between objects clearly and explicitly.
Homepage: http://projects.puppetlabs.com/projects/puppet
Original-Maintainer: Puppet Package Maintainers
pkg-puppet-de...@lists.alioth.debian.org
root@testserv1:~# uname -a
Linux testserv1 3.2.0-31-generic #50-Ubuntu SMP Fri Sep 7 16:16:45 UTC 2012
x86_64 x86_64 x86_64 GNU/Linux
root@testserv1:~# cat /etc/lsb-release
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION=Ubuntu 12.04.1 LTS
root@testserv1:~# /etc/init.d/puppet start
* Starting puppet agent
...done.
root@testserv1:~# pgrep puppet
8459
root@testserv1:~# /etc/init.d/puppet stop
* Stopping puppet agent
...done.
root@testserv1:~# pgrep puppet
8459
root@testserv1:~# /etc/init.d/puppet start
* Starting puppet agent
...done.
root@testserv1:~# pgrep puppet
8459
8941
root@testserv1:~# /etc/init.d/puppet stop
* Stopping puppet agent
...done.
root@testserv1:~# pgrep puppet
8459
8941
root@testserv1:~# /etc/init.d/puppet start
* Starting puppet agent
...done.
root@testserv1:~# pgrep puppet
8459
8941
9395
root@testserv1:~# pkill puppet
root@testserv1:~# pgrep puppet
9395
root@testserv1:~# pkill puppet
root@testserv1:~# pgrep puppet
root@testserv1:~# exit
as you can see, the /etc/init.d/puppet stop appears to have no effect - puppet
processes remain running after it is called.
the reason appears to be because the /etc/init.d/puppet file contains the line:
PIDFILE=/var/run/puppet/${NAME}.pid
I assume in this case ${NAME} resolves to puppet
therefore when it is attempting to stop puppet it searches for
/var/run/puppet/puppet.pid but the agent creates
/var/run/puppet/agent.pid
Simply changing the line in the /etc/init.d/puppet file from ${NAME}
to agent should (and does) solve the problem
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 1065883] Re: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder
** Changed in: cinder (Ubuntu) Status: New = Invalid -- 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/1065883 Title: ceph rbd username and secret should be configured in nova-compute, not passed from nova-volume/cinder To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065883/+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 1066570] Re: should build-depend on librbd-dev
Alright, my fault. Shame on me. On Mon, Oct 15, 2012 at 8:02 AM, Robie Basak 1066...@bugs.launchpad.netwrote: ** Attachment added: changelog https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+attachment/3398778/+files/changelog ** Changed in: qemu-kvm (Ubuntu) Status: New = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/1066570 Title: should build-depend on librbd-dev Status in “qemu-kvm” package in Ubuntu: Incomplete Bug description: I could only compile it after installing librbd-dev. Otherwise could only get the following: error: rbd/librbd.h: No such file or directory lsb_release -rd: Description: Debian GNU/Linux testing (wheezy) Release: testing (yes, i'm building it in debian) qemu-kvm version: 1.2.0+noroms-0ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+subscriptions -- []'s Rodrigo *Powered by carbohydrates * -- 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/1066570 Title: should build-depend on librbd-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+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 1060184] Re: puppet client init script pid file error
On Mon, Oct 15, 2012 at 12:44:16PM -, Matthew Malkin wrote:
I assume in this case ${NAME} resolves to puppet
${NAME} is set directly in the init script, two lines above, to agent.
Do you see this in your init script too?
Unfortunately I can't reproduce your setup exactly since I don't have
access to your puppetmaster setup. It looks like this is the only thing
that is different.
I tested the behaviour without connecting to a puppetmaster at all,
since the agent appears to happily run even if it cannot connect to one.
Can you try this, perhaps?
Are you sure that your puppet manifests aren't accidentally changing
puppet's own startup scripts or configuration in a way that is causing
this?
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 1066570] Re: should build-depend on librbd-dev
Don't worry about it, and thanks for confirming. I appreciated the detail in your report that allowed me to fail to reproduce quickly. Most reports are much more vague and take far more effort :-) ** Changed in: qemu-kvm (Ubuntu) Status: Incomplete = Invalid -- 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/1066570 Title: should build-depend on librbd-dev To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1066570/+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 1060541] Re: racoon: broken script env for IPv6
** Also affects: ipsec-tools (Ubuntu Lucid) Importance: Undecided Status: New ** Also affects: ipsec-tools (Ubuntu Hardy) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1060541 Title: racoon: broken script env for IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/1060541/+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 1060541] Re: racoon: broken script env for IPv6
Added (via hggdh - thank you!) bug tasks for Lucid and Hardy, and marking as Fix Released in the current development version, as ipsec- tools has been on 0.8 since Oneiric. ** Changed in: ipsec-tools (Ubuntu) Status: New = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ipsec-tools in Ubuntu. https://bugs.launchpad.net/bugs/1060541 Title: racoon: broken script env for IPv6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ipsec-tools/+bug/1060541/+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 1060184] Re: puppet client init script pid file error
Matthew Malkin 1060...@bugs.launchpad.net writes:
the reason appears to be because the /etc/init.d/puppet file contains the
line:
PIDFILE=/var/run/puppet/${NAME}.pid
I assume in this case ${NAME} resolves to puppet
[...]
Simply changing the line in the /etc/init.d/puppet file from ${NAME}
to agent should (and does) solve the problem
There is no need to assume, that is set explicitly in the init script.
What does the command 'grep ^NAME /etc/init.d/puppet' give as output in
your case?
In the debian packaging, it was set to puppetd in 0.25.5-1, but
changed to agent in 2.6.0-1. For the ubuntu packaging, it may be
different.
Your bug report mentions a newer version, could you check if you have
the init script that came with the package, or if it is changed, or an
older version is kept when upgrading? An md5sum /etc/init.d/puppet may
also help, if they differ.
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 1065589] Re: initctl list shows 11974 instances of network-interface-security after two days of uptime
** Also affects: linux (Ubuntu) Importance: Undecided Status: New -- 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/1065589 Title: initctl list shows 11974 instances of network-interface-security after two days of uptime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/+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 919451] Re: PHP CGI arbitrary code execution vulnerability
** Visibility changed to: Public -- 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/919451 Title: PHP CGI arbitrary code execution vulnerability To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/919451/+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 1065589] Missing required logs.
This bug is missing log files that will aid in diagnosing the problem. From a terminal window please run: apport-collect 1065589 and then change the status of the bug to 'Confirmed'. If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'. This change has been made by an automated script, maintained by the Ubuntu Kernel Team. ** Changed in: linux (Ubuntu) Status: New = Incomplete -- 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/1065589 Title: initctl list shows 11974 instances of network-interface-security after two days of uptime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/+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 1066916] [NEW] package tftpd-hpa 5.2-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127
Public bug reported: E: tftpd-hpa: el subproceso instalado el script post-installation devolvió el código de salida de error 127 ProblemType: Package DistroRelease: Ubuntu 12.04 Package: tftpd-hpa 5.2-1ubuntu1 ProcVersionSignature: Ubuntu 3.2.0-31.50-generic 3.2.28 Uname: Linux 3.2.0-31-generic i686 ApportVersion: 2.0.1-0ubuntu13 Architecture: i386 Date: Mon Oct 15 09:55:49 2012 ErrorMessage: el subproceso instalado el script post-installation devolvió el código de salida de error 127 InstallationMedia: Ubuntu 10.10 Maverick Meerkat - Release i386 (20101007) SourcePackage: tftp-hpa Title: package tftpd-hpa 5.2-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 UpgradeStatus: Upgraded to precise on 2012-04-28 (169 days ago) ** Affects: tftp-hpa (Ubuntu) Importance: Undecided Status: New ** Tags: apport-package i386 precise -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to tftp-hpa in Ubuntu. https://bugs.launchpad.net/bugs/1066916 Title: package tftpd-hpa 5.2-1ubuntu1 failed to install/upgrade: el subproceso instalado el script post-installation devolvió el código de salida de error 127 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tftp-hpa/+bug/1066916/+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 1066834] Re: LevelForFileTypesDetection=0 produces unexpected results
** Changed in: awstats (Ubuntu) Importance: Undecided = Medium -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to awstats in Ubuntu. https://bugs.launchpad.net/bugs/1066834 Title: LevelForFileTypesDetection=0 produces unexpected results To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/awstats/+bug/1066834/+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 1060238] Re: unmatched entries for sshd
** Changed in: logwatch (Ubuntu) Importance: Undecided = Medium -- 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/1060238 Title: unmatched entries for sshd To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/logwatch/+bug/1060238/+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 1065589] Re: initctl list shows 11974 instances of network-interface-security after two days of uptime
I'm running ltp against my proposed patch, and will send it to netdev (per the email thread) later today. ** Tags added: bot-stop-nagging ** Changed in: linux (Ubuntu) Status: Incomplete = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1065589 Title: initctl list shows 11974 instances of network-interface-security after two days of uptime To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1065589/+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 1066421] Re: fresh MAAS install from ISO fails when opening the MAAS URL
*** This bug is a duplicate of bug 1065763 *** https://bugs.launchpad.net/bugs/1065763 ** This bug is no longer a duplicate of bug 1066556 MAAS installed via d-i/tasksel: fails when opening the browser to /MAAS ** This bug has been marked a duplicate of bug 1065763 UI URL displays 200 Error page after CD install -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1066421 Title: fresh MAAS install from ISO fails when opening the MAAS URL To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066421/+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 1065763] Re: UI URL displays 200 Error page after CD install
** Changed in: maas (Ubuntu) Importance: High = Critical -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1065763 Title: UI URL displays 200 Error page after CD install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1065763/+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 1065763] Re: UI URL displays 200 Error page after CD install
This bug has been reported on the Ubuntu ISO testing tracker. A list of all reports related to this bug can be found here: http://iso.qa.ubuntu.com/qatracker/reports/bugs/1065763 ** Tags added: iso-testing -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1065763 Title: UI URL displays 200 Error page after CD install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1065763/+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 1060184] Re: puppet client init script pid file error
Strange
Unfortunately I didn't keep the instance of the VM I just got those
results above from.
Having just recreated the VM (always from a snapshot of 12.04.1 before
first boot but after installation) following the same steps and before I
connected it to the puppetmaster i tested and it worked just fine as you
said. After connecting to the puppetmaster it continued to work just
fine.
I had created an puppetmaster entry for puppet's init script, but only
after i discovered the problem initially and only to solve that problem.
I have tested with that entry enabled and disabled so it appears to make
no difference. Indeed the only difference between the two files is one
(the one installed by the puppetmaster) has
PIDFILE=/var/run/puppet/agent.pid and the other (before puppetmaster
changed it) had /var/run/puppet/${NAME}.pid (difference tracked with
mercurial)
So i'm now a bit confused as to how this could have happened, but it
doesn't appear to be a bug as I originally thought.
This is how events have progressed:
2012-10-02:
- on new physical server: - detected problem
- installed copy of 12.04.1 server on virtualbox for testing
- took snapshot before first boot
- detected same problem on VM after installation - discovered it had to do with
name of pid file
- reported bug
2012-10-15
- saw response
- rolled VM back to snapshot above
- installed puppet and produced output as seen above in my previous reply
(recorded with screen and then manually tidied)
- saw response
- rolled VM back to snapshot above
- installed puppet without joining to puppetmaster - no problem
- joined to puppetmaster having commented out the entry that affects
/etc/init.d/puppet - no problem
- uncommented entry - /etc/init.d/puppet changed - no problem
In conclusion
I don't know what was causing the problem initially but whatever it was appears
to have gone away. Unless an update for puppet has been released between 2nd
and 15th then I can't understand how come it now works, but it does so I shan't
complain.
I am sorry - It seems I've been wasting your time.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 1066935] [NEW] named.conf.rndc.maas is insecure by default
Public bug reported: After default installation the following permissions are applied: -rw-r--r-- 1 maas root 193 Oct 15 14:37 /etc/bind/maas/named.conf.rndc.maas This makes the bind communication key readable to all users of the system ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: maas-dns 0.1+bzr1264+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Mon Oct 15 17:10:58 2012 InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release i386 (20121014) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1066935 Title: named.conf.rndc.maas is insecure by default To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066935/+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 1066929] [NEW] duplicate entry added to named.conf.local on each package reconfigure
Public bug reported: Running dpkg-reconfigure maas-dns breaks the current dns config Observation seems to indicate that each reconfigure appends the following line to /etc/bind/named.conf.local include /etc/bind/maas/named.conf.maas; This causes bind to choke and output confusing messages about multiple definitions of the master zone ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: maas-dns 0.1+bzr1264+dfsg-0ubuntu1 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic i686 ApportVersion: 2.6.1-0ubuntu3 Architecture: i386 Date: Mon Oct 15 17:04:52 2012 InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release i386 (20121014) PackageArchitecture: all ProcEnviron: LANGUAGE=en_US:en TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: maas UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: maas (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 quantal -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1066929 Title: duplicate entry added to named.conf.local on each package reconfigure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066929/+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 1060404] Re: update-grub runs and fails in containers
** Branch linked: lp:ubuntu/lxc -- 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/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+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 1066938] [NEW] maas-dns changes default bind rndc key and breaks initscripts
Public bug reported:
The default install of maas-dns creates the following file
/etc/bind/maas/rndc.conf.maas
Among it are the following two bind9 configuration sections:
key rndc-maas-key {
algorithm hmac-md5;
secret (edited away);
};
options {
default-key rndc-maas-key;
default-server 127.0.0.1;
default-port 954;
};
This breaks init scripts (sudo service bind9 restart) as they use the
key called rndc-key. I would suggest that maas explicitly provide the
key that it wishes to use whenever it interacts with bind9 so that
defaults don't have to change
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: maas-dns 0.1+bzr1264+dfsg-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu3
Architecture: i386
Date: Mon Oct 15 17:15:31 2012
InstallationMedia: Ubuntu-Server 12.10 Quantal Quetzal - Release i386
(20121014)
PackageArchitecture: all
ProcEnviron:
LANGUAGE=en_US:en
TERM=xterm-256color
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: maas
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: maas (Ubuntu)
Importance: Undecided
Status: New
** Tags: apport-bug i386 quantal
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to maas in Ubuntu.
https://bugs.launchpad.net/bugs/1066938
Title:
maas-dns changes default bind rndc key and breaks initscripts
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066938/+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 1066935] Re: named.conf.rndc.maas is insecure by default
setup_rndc() (in src/provisioningserver/dns/config.py) should be fixed to write the file with the appropriate permissions. ** Package changed: maas (Ubuntu) = maas ** Changed in: maas Importance: Undecided = High ** Changed in: maas Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1066935 Title: named.conf.rndc.maas is insecure by default To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066935/+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 1066942] [NEW] cps_ plugin autodetection is broken
Public bug reported:
Summary: Please apply https://github.com/munin-
monitoring/munin/commit/3281ce622bbd5dbf2c0ac5be8c951cb9a488e47a to the
munin-node package.
I'm using these packages:
ii munin-common 1.4.6-3ubuntu3.1 network-wide
graphing framework (common)
ii munin-node 1.4.6-3ubuntu3.1 network-wide
graphing framework (node)
On 12.04.1 (precise).
The problem is with the cps_ plugin. It suggests the following plugins:
# /usr/share/munin/plugins/cps_ suggest
cps_1.1.1.1_21
cps_1.1.1.1_80
cps_1.1.1.1_873
cps_2.2.2.2_21
cps_2.2.2.2_80
cps_2.2.2.2_873
When these get created by munin-node-configure I end up with the
following:
# ls -la /etc/munin/plugins/cps_cps_212.219.56.18*
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_1.1.1.1_21 -
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_1.1.1.1_80 -
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_1.1.1.1_873
- /usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Oct 15 16:26 /etc/munin/plugins/cps_cps_2.2.2.2_21 -
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Aug 18 18:37 /etc/munin/plugins/cps_cps_2.2.2.2_80 -
/usr/share/munin/plugins/cps_
lrwxrwxrwx 1 root root 29 Oct 15 16:26 /etc/munin/plugins/cps_cps_2.2.2.2_873
- /usr/share/munin/plugins/cps_
The code in cps_ parses $0:
unless ($0 =~ /cps(?:_([^_]+)|)_(.+)\s*$/) {
die Could not parse name $0.\n;
}
my $vip = $1;
my $port = $2;
As you can see, the cps_cps_ should be cps_. It's doubling this up which
breaks the regex and therefore breaks the plugin.
The fix is quite simple:
--- cps_.orig 2012-10-15 16:14:14.580595524 +0100
+++ cps_2012-10-15 16:14:25.092431645 +0100
@@ -103,7 +103,7 @@
foreach my $vip (sort keys %{$ipvs}) {
foreach my $port (sort keys %{$ipvs-{$vip}}) {
- print cps_${vip}_$port\n;
+ print ${vip}_$port\n;
}
}
exit 0;
This creates the plugins with a single cps_ at the start and then
everything works as expected.
The fix can also be seen upstream here:
https://github.com/munin-
monitoring/munin/commit/3281ce622bbd5dbf2c0ac5be8c951cb9a488e47a
It'd be great if this fix could be applied.
** Affects: munin (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to munin in Ubuntu.
https://bugs.launchpad.net/bugs/1066942
Title:
cps_ plugin autodetection is broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/munin/+bug/1066942/+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 1066938] Re: maas-dns changes default bind rndc key and breaks initscripts
I would suggest that maas explicitly provide the key that it wishes to use whenever it interacts with bind9 so that defaults don't have to change Looks like a very good idea to me. ** Package changed: maas (Ubuntu) = maas ** Changed in: maas Importance: Undecided = Critical ** Changed in: maas Status: New = Triaged -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1066938 Title: maas-dns changes default bind rndc key and breaks initscripts To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1066938/+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 1065763] Re: UI URL displays 200 Error page after CD install
** Changed in: maas (Ubuntu) Status: Confirmed = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1065763 Title: UI URL displays 200 Error page after CD install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1065763/+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 1066929] Re: duplicate entry added to named.conf.local on each package reconfigure
I see two ways to fix this: - we can fix this in the packaging and avoid adding the entry in /etc/bind/named.conf.local if it's already there or - we can fix the 'get_named_conf' command so that it won't include the snippet if it's already there. Maybe we could use write_custom_config_section (src/provisioningserver/utils.py) but I wonder if we can manage the upgrade properly. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1066929 Title: duplicate entry added to named.conf.local on each package reconfigure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066929/+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 1066929] Re: duplicate entry added to named.conf.local on each package reconfigure
** Changed in: maas (Ubuntu) Assignee: (unassigned) = Gavin Panella (allenap) ** Changed in: maas (Ubuntu) Status: New = In Progress -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1066929 Title: duplicate entry added to named.conf.local on each package reconfigure To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1066929/+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
[Blueprint servercloud-r-default-swap-disk-size-calculation] Review swap disk size allocation policies
Blueprint changed by Dmitrijs Ledkovs: Whiteboard changed: Documentation and limitations of partman-auto-recipes in their current implementation: http://bazaar.launchpad.net/~vcs-imports/debian-installer/master/view/head:/doc/devel/partman-auto-recipe.txt + + Laney, managed to reproduce this with desktop install as well with + matching amounts of RAM HDD (which is not uncommon for high-memory + + SSD combos). The minimal size encoded in partman-auto was too small and + swap took most of space failing the install completely. User Stories: Risks: Test Plans: Release Note: -- Review swap disk size allocation policies https://blueprints.launchpad.net/ubuntu/+spec/servercloud-r-default-swap-disk-size-calculation -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1029889] Re: LVM Based KVM VM taking 100% CPU on first start and hangs.
** Also affects: lvm2 (Ubuntu) Importance: Undecided Status: New -- 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/1029889 Title: LVM Based KVM VM taking 100% CPU on first start and hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1029889/+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 1029889] Re: LVM Based KVM VM taking 100% CPU on first start and hangs.
@Lewdmole, Looking at your vg and lvdisplay output, it looks like you should have plenty of space for vm5. -- 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/1029889 Title: LVM Based KVM VM taking 100% CPU on first start and hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1029889/+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 1029889] Re: LVM Based KVM VM taking 100% CPU on first start and hangs.
@Lewdmole, Looking at your vg and lvdisplay output, it looks like you should have plenty of space for vm5. -- 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/1029889 Title: LVM Based KVM VM taking 100% CPU on first start and hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1029889/+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 1029889] Re: LVM Based KVM VM taking 100% CPU on first start and hangs.
Isn't this duplicate of bug 1012946 ? Can you please try parted from precise-proposed as per instructions in: https://bugs.launchpad.net/ubuntu/+source/parted/+bug/1012946/comments/11 and comment here or on the bug 1012946. -- 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/1029889 Title: LVM Based KVM VM taking 100% CPU on first start and hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1029889/+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 1060184] Re: puppet client init script pid file error
Matthew Malkin 1060...@bugs.launchpad.net writes:
Indeed the only difference between the two files is one (the one
installed by the puppetmaster) has PIDFILE=/var/run/puppet/agent.pid
and the other (before puppetmaster changed it) had
/var/run/puppet/${NAME}.pid (difference tracked with mercurial)
After setting NAME in /etc/init.d/puppet, the file /etc/default/puppet
is sourced, so a NAME=puppet in /etc/default/puppet could give the
reported behaviour. Apart from that, I'm out of ideas.
Anyhow, thanks for a very thorough report, even if the source of the bug
was not found. :)
--
Stig Sandbeck Mathisen
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to puppet in Ubuntu.
https://bugs.launchpad.net/bugs/1060184
Title:
puppet client init script pid file error
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1060184/+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 997978] Re: KVM images lose connectivity with bridged network
I got the same issue, but my host OS is RHEL 6.3 (2.6.32-220.el6.x86_64), the qemu-kvm version is 0.12.1.2 , and my guest base image is Ubuntu 12.4 LTS. My problem is: After I enable the libvirt_use_virtio_for_bridges = true in the nova.conf, the new instance can not get ip address and the gateway can not be added in the router table. The router table like this: --before enable virtio ~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 172.17.33.8 0.0.0.0 UG10000 eth0 172.17.32.0 0.0.0.0 255.255.252.0 U 0 00 eth0 --after enable virtio ~$ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric RefUse Iface 0.0.0.0 172.17.32.1 0.0.0.0 UG10000 eth0 172.17.32.0 0.0.0.0 255.255.252.0 U 0 00 eth0 Here is the dnsmasq process on my host server: root 32034 32033 0 Oct12 ?00:00:00 /usr/sbin/dnsmasq --strict-order --bind-interfaces --conf-file= --domain=novalocal --pid-file=/var/lib/nova/networks/nova-br100.pid --listen-address=172.17.33.8 --except-interface=lo --dhcp-range=172.17.33.3,static,120s --dhcp-lease-max=256 --dhcp-hostsfile=/var/lib/nova/networks/nova-br100.conf --dhcp-script=/usr/bin/nova-dhcpbridge --leasefile-ro Soren, Your solution are only for ubuntu host and should install the ppa on the host machine, right? Is there any solution or workaround for RHEL? -- 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/997978 Title: KVM images lose connectivity with bridged network To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/997978/+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 1067029] [NEW] lxc-start fails on 'lxc-create -t ubuntu-cloud' container
Public bug reported:
$ name=precise-cloud-amd64-source
$ sudo lxc-create -t ubuntu-cloud -n $name -- \
--release=precise --arch=amd64 \
--tarball $cached/$tarball
$ sudo lxc-start -n precise-cloud-amd64-source
lxc-start: No such file or directory - failed to mount a new instance of
'/dev/pts'
lxc-start: failed to setup the new pts instance
lxc-start: failed to setup the container
lxc-start: invalid sequence number 1. expected 2
lxc-start: failed to spawn 'precise-cloud-amd64-source'
Previously, I thought I coudl fix the situation with the following, but that
seems not to have worked.
$ rootd=/var/lib/lxc/$name/rootfs
$ sudo cp -a /dev/{console,urandom,random,tty[1234]} $rootd/dev
$ sudo mkdir $rootd/dev/pts
ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: lxc 0.7.5-3ubuntu63
ProcVersionSignature: User Name 3.2.0-31.50-virtual 3.2.28
Uname: Linux 3.2.0-31-virtual x86_64
ApportVersion: 2.0.1-0ubuntu13
Architecture: amd64
Date: Mon Oct 15 19:17:34 2012
Ec2AMI: ami-015b
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.small
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
ProcEnviron:
TERM=screen
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: lxc
UpgradeStatus: No upgrade log present (probably fresh install)
** Affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug ec2-images precise
--
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/1067029
Title:
lxc-start fails on 'lxc-create -t ubuntu-cloud' container
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1067029/+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 1065702] Re: After folsom upgrade, instances can no longer access existing volumes.
** Changed in: cinder Assignee: (unassigned) = John Griffith (john-griffith) ** Changed in: nova Assignee: (unassigned) = John Griffith (john-griffith) -- 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/1065702 Title: After folsom upgrade, instances can no longer access existing volumes. To manage notifications about this bug go to: https://bugs.launchpad.net/cinder/+bug/1065702/+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 1065763] Re: UI URL displays 200 Error page after CD install
This bug was fixed in the package maas - 0.1+bzr1264+dfsg-0ubuntu2 --- maas (0.1+bzr1264+dfsg-0ubuntu2) quantal; urgency=low * Fix MAAS not working after CD/preseed install (LP: #1065763) - debian/extras/maas-region-celeryd: Add wrapper to run celery from the upstart job. - debian/extras/maas-region-controller.maas-region-celery.upstart: Create rabbitmq user if it does not exists. * debian/control: Remove unneeded deps on python-txtftp for some binary pkgs. * debian/maas-region-controller.postinst: Minor fix referencing variable. -- Andres Rodriguez andres...@ubuntu.com Thu, 11 Oct 2012 17:38:08 -0400 ** Changed in: maas (Ubuntu) Status: In Progress = Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1065763 Title: UI URL displays 200 Error page after CD install To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/maas/+bug/1065763/+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 1067029] Re: lxc-start fails on 'lxc-create -t ubuntu-cloud' container
** Changed in: lxc (Ubuntu) Importance: Undecided = High -- 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/1067029 Title: lxc-start fails on 'lxc-create -t ubuntu-cloud' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1067029/+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 1029889] Re: LVM Based KVM VM taking 100% CPU on first start and hangs.
Ok will give it a try and post on bug bug 1012946. -- 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/1029889 Title: LVM Based KVM VM taking 100% CPU on first start and hangs. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libvirt/+bug/1029889/+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 1067029] Re: lxc-start fails on 'lxc-create -t ubuntu-cloud' container
*** This bug is a duplicate of bug 1060404 *** https://bugs.launchpad.net/bugs/1060404 Thanks for reporting this bug. This is due to the same problem as bug 1060404. The workaround is the same as the solution - add a devtmpfs entry to /var/lib/lxc/$name/fstab. The solution is queued for acceptance to precise-proposed. ** This bug has been marked a duplicate of bug 1060404 update-grub runs and fails in containers -- 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/1067029 Title: lxc-start fails on 'lxc-create -t ubuntu-cloud' container To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1067029/+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 1060404] Re: update-grub runs and fails in containers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: grub2 (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+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 1060404] Re: update-grub runs and fails in containers
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: upstart (Ubuntu Precise) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to lxc in Ubuntu. https://bugs.launchpad.net/bugs/1060404 Title: update-grub runs and fails in containers To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1060404/+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 97513] Re: Squid requires restart after Network Manager made connection to network
I am on precice 12.04 LTS and the problem is still there... below is part of the log from cache.log 2012/10/15 23:39:38| Starting Squid Cache version 3.1.19 for i686-pc-linux-gnu... 2012/10/15 23:39:38| Process ID 1170 2012/10/15 23:39:38| With 65535 file descriptors available 2012/10/15 23:39:38| Initializing IP Cache... 2012/10/15 23:39:38| DNS Socket created at [::], FD 5 2012/10/15 23:39:38| DNS Socket created at 0.0.0.0, FD 6 2012/10/15 23:39:38| Warning: Could not find any nameservers. Trying to use localhost 2012/10/15 23:39:38| Please check your /etc/resolv.conf file 2012/10/15 23:39:38| or use the 'dns_nameservers' option in squid.conf -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to squid in Ubuntu. https://bugs.launchpad.net/bugs/97513 Title: Squid requires restart after Network Manager made connection to network To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/squid/+bug/97513/+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 1041829] Re: package bacula-director-mysql 5.2.5-0ubuntu6.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
I have the same problem. Has anyone found a solution? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1041829 Title: package bacula-director-mysql 5.2.5-0ubuntu6.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/bacula/+bug/1041829/+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 1065628] Re: pci device not reset (passthrough)
Thanks for submitting this bug. Is there any way you could test this with either the quantal package, or with upstream qemu version 1.2? ** Changed in: qemu-kvm (Ubuntu) Importance: Undecided = Medium ** Changed in: qemu-kvm (Ubuntu) Status: New = Incomplete -- 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/1065628 Title: pci device not reset (passthrough) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1065628/+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 1041829] Re: package bacula-director-mysql 5.2.5-0ubuntu6.1 failed to install/upgrade: ErrorMessage: subprocess installed post-installation script returned error exit status 1
Ok, the answer is stupid. When asked whether to update or not the database, say no :P -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to bacula in Ubuntu. https://bugs.launchpad.net/bugs/1041829 Title: package bacula-director-mysql 5.2.5-0ubuntu6.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/bacula/+bug/1041829/+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
[Blueprint servercloud-q-juju-charm-best-practices] Juju Charm Best practices
Blueprint changed by Mark Mims: Work items changed: Work items: [jorge] Pick better example charms, flagbearer charms.: DONE [jorge] Choose a single place for presenting flagbearer charms (charm browser?): TODO [jorge] Move rules and charm best practices into juju/docs.: DONE [jorge] Add Maintainer field information to documentation. (thanks clint!): DONE [jorge] Reach out to maintainers to get their maintainer field filled out.: DONE [jorge] Add docs work items to patch pilot!: DONE [jorge] pull file bug or join the doc team from other projects: TODO [jorge] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing: DONE [imbrandon] Reach out to maintainers to get their maintainer filled out.: DONE [imbrandon] Put Doc instructions in the docs: http://askubuntu.com/q/52063 : TODO - [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: TODO + [mark-mims] (and individual maintainers!) clean up existing charms wrt best practices: DONE [clint-fewbar] Comment and add links to docs in 'charm create' templates: POSTPONED [clint-fewbar] juju in Debian! NOW!: DONE [clint-fewbar] determine most likely maintainers based on bzr logs: DONE [clint-fewbar] fix doc repos wrt (trunk, go, docs): DONE [marcoceppi] tag:juju review on AU and SE network: DONE [hazmat] incorporate output of charm proof into charm browser: DONE [hazmat] clear out trunk docs for juju: DONE [imbrandon] Clarify documentention on what to expect when your using LXC and EC2. Cost, wait time, what you see, logs, downloading. You should expect this to download 300 megs, etc. Here's a table of look here troubleshooting your LXC thing.: TODO [hazmat] make juju report on initial lxc image downloads ?: TODO [clint-fewbar] make juju lxc use lxc networking instead of libvirt networking ?: INPROGRESS -- Juju Charm Best practices https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-best-practices -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1067101] [NEW] processes terminated with status (N) on lxc-start
Public bug reported: lxc-start -n name on quantal complains about following processes terminated during container start (it gets started fine though). Using template 'ubuntu' provided by lxc package. root@ip-10-63-1-192:~# lxc-start -n p1 4init: ureadahead main process (5) terminated with status 5 4init: udev-fallback-graphics main process (43) terminated with status 1 4init: console-font main process (57) terminated with status 1 4init: setvtrgb main process (71) terminated with status 1 4init: plymouth main process (6) killed by ABRT signal 4init: plymouth-splash main process (70) terminated with status 2 4init: console-setup main process (113) terminated with status 1 4init: plymouth-log main process (125) terminated with status 1 30udevd[148]: starting version 175 4init: setvtrgb main process (274) terminated with status 1 4init: plymouth-stop pre-start process (272) terminated with status 1 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lxc 0.8.0~rc1-4ubuntu37 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 15 21:49:36 2012 Ec2AMI: ami-73c3c307 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: m1.small Ec2Kernel: aki-62695816 Ec2Ramdisk: unavailable ProcEnviron: LC_CTYPE=en_GB.UTF-8 TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: lxc (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apparmor apport-bug ec2-images quantal third-party-packages ** Description changed: - lxc-start -n name complains about following processes terminated on - container start (it gets started though). + lxc-start -n name on quantal complains about following processes + terminated during container start (it gets started fine though). Using template 'ubuntu' provided by lxc package. root@ip-10-63-1-192:~# lxc-start -n p1 4init: ureadahead main process (5) terminated with status 5 4init: udev-fallback-graphics main process (43) terminated with status 1 4init: console-font main process (57) terminated with status 1 4init: setvtrgb main process (71) terminated with status 1 4init: plymouth main process (6) killed by ABRT signal 4init: plymouth-splash main process (70) terminated with status 2 4init: console-setup main process (113) terminated with status 1 4init: plymouth-log main process (125) terminated with status 1 30udevd[148]: starting version 175 4init: setvtrgb main process (274) terminated with status 1 4init: plymouth-stop pre-start process (272) terminated with status 1 ProblemType: Bug DistroRelease: Ubuntu 12.10 Package: lxc 0.8.0~rc1-4ubuntu37 ProcVersionSignature: Ubuntu 3.5.0-17.28-generic 3.5.5 Uname: Linux 3.5.0-17-generic x86_64 ApportVersion: 2.6.1-0ubuntu3 Architecture: amd64 Date: Mon Oct 15 21:49:36 2012 Ec2AMI: ami-73c3c307 Ec2AMIManifest: (unknown) Ec2AvailabilityZone: eu-west-1b Ec2InstanceType: m1.small Ec2Kernel: aki-62695816 Ec2Ramdisk: unavailable ProcEnviron: - LC_CTYPE=en_GB.UTF-8 - TERM=xterm-256color - PATH=(custom, no user) - LANG=en_US.UTF-8 - SHELL=/bin/bash + LC_CTYPE=en_GB.UTF-8 + TERM=xterm-256color + PATH=(custom, no user) + LANG=en_US.UTF-8 + SHELL=/bin/bash SourcePackage: lxc UpgradeStatus: No upgrade log present (probably fresh install) -- 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/1067101 Title: processes terminated with status (N) on lxc-start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1067101/+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 1067101] Re: processes terminated with status (N) on lxc-start
Thanks for taking the time to report this. This is not a bug in lxc. Rather they are upstart (init) messages which previously were not shown due to a bug in container setup. ** 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/1067101 Title: processes terminated with status (N) on lxc-start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1067101/+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 1066084] Re: Permissions mangled when creating rootfs from cloud images
Thanks, the fix has been pulled into the source tree, but will have to wait for quantal-proposed and r to open up. -- 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/1066084 Title: Permissions mangled when creating rootfs from cloud images To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lxc/+bug/1066084/+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
[Blueprint servercloud-q-juju-charm-unit-tests] Juju Charm Unit Tests
Blueprint changed by Mark Mims: Work items changed: Work items: documentation for unit tests: INPROGRESS - write examples of unit tests on flag-bearing charms: INPROGRESS + write examples of unit tests on flag-bearing charms (example charm): DONE [jimbaker] make 'jitsu run-tests' aware of error codes (Jitsu watch): INPROGRESS [jimbaker] improve charmtester logging information: DONE [hazmat] charm proof testing: DONE - keep everything green: INPROGRESS - [mark-mims] make charmtester easier to use one-off by anyone: INPROGRESS + keep everything green (ongoing task): DONE + [mark-mims] make charmtester easier to use one-off by anyone: DONE [mark-mims] make charmtester whitelist: DONE extend charm tools to help generate tests: POSTPONED run charmtester against maas environment: TODO -- Juju Charm Unit Tests https://blueprints.launchpad.net/ubuntu/+spec/servercloud-q-juju-charm-unit-tests -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1056072] Re: php5-dev missing mysqlnd header files
** Changed in: php5 (Debian) Status: Unknown = New -- 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/1056072 Title: php5-dev missing mysqlnd header files To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/1056072/+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 1065775] Re: dbus and avahi-daemon not started after package install
** Also affects: maas (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to maas in Ubuntu. https://bugs.launchpad.net/bugs/1065775 Title: dbus and avahi-daemon not started after package install To manage notifications about this bug go to: https://bugs.launchpad.net/maas/+bug/1065775/+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 811518] Re: SAMBA cannot browse Workgroups, name resolve order
This bug affected me, Windows shared worked fine, then they stopped working, and this fixed it. I tried launching an exe in Mono, and then started installing wine right before my shares stopped working. Ubuntu 12.04 amd64 to Windows 8 x64 -- 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/811518 Title: SAMBA cannot browse Workgroups, name resolve order To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/samba/+bug/811518/+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 1043292] Re: Hung agent processes
Might also be bug #995719. Can you try remove process_name.rb ? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to puppet in Ubuntu. https://bugs.launchpad.net/bugs/1043292 Title: Hung agent processes To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1043292/+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 978281] Re: apache2 crashed with SIGABRT in raise()
[Expired for php5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: php5 (Ubuntu) Status: Incomplete = Expired -- 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/978281 Title: apache2 crashed with SIGABRT in raise() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/978281/+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 938804] Re: apache2 crashed with SIGSEGV in prefill_from_oparray()
[Expired for php5 (Ubuntu) because there has been no activity for 60 days.] ** Changed in: php5 (Ubuntu) Status: Incomplete = Expired -- 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/938804 Title: apache2 crashed with SIGSEGV in prefill_from_oparray() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/php5/+bug/938804/+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
