[Bug 1271000] Re: lxc-start fails with Out of memory reading cgroups
I cannot confirm the above behavior. $ sudo lxc-create -t ubuntu -n myserver -P $HOME/lxc Checking cache download in /usr/local/var/cache/lxc/trusty/rootfs-amd64 ... Copy /usr/local/var/cache/lxc/trusty/rootfs-amd64 to /home/anavarre/lxc/myserver/rootfs ... Copying rootfs to /home/username/lxc/myserver/rootfs ... Generating locales... en_US.UTF-8... done Generation complete. Creating SSH2 RSA key; this may take some time ... Creating SSH2 DSA key; this may take some time ... Creating SSH2 ECDSA key; this may take some time ... Creating SSH2 ED25519 key; this may take some time ... update-rc.d: warning: default stop runlevel arguments (0 1 6) do not match ssh Default-Stop values (none) invoke-rc.d: policy-rc.d denied execution of start. Current default time zone: 'Europe/Paris' Local time is now: Sat Mar 15 10:08:51 CET 2014. Universal Time is now: Sat Mar 15 09:08:51 UTC 2014. ## # The default user is 'ubuntu' with password 'ubuntu'! # Use the 'sudo' command to run tasks as root in the container. ## $ sudo lxc-start -n myserver lxc-start: Executing '/sbin/init' with no configuration file may crash the host As you can see above I'm running Trusty (beta 1) and it's always failing to start the container for me, no matter what flags I'm passing. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to libcgroup in Ubuntu. https://bugs.launchpad.net/bugs/1271000 Title: lxc-start fails with Out of memory reading cgroups To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libcgroup/+bug/1271000/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 993259] Re: ypbind does not start on boot
After some more testing, it's definitely a DNS issue on probably early boot stages without network. So there are two ways to workaround: 1. Only use IP addresses in /etc/yp.conf 2. Add your NIS server to /etc/hosts I am using the later one on Ubuntu 14.04. But i still don't why ypbind will skips if it can't resolve the server name, but keeps on running when it probably can't connect the server yet? And no i don't want to have static IPs in all clients as i quite trust my DHCP servers and i always prefer FQDN for network migrations. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/993259 Title: ypbind does not start on boot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nis/+bug/993259/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1012147] Re: lightdm: no graphical login for nis user
Under a standard desktop install of trusty, i don't have a /etc/lightdm/lightdm.conf. Any clues on that? -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to nis in Ubuntu. https://bugs.launchpad.net/bugs/1012147 Title: lightdm: no graphical login for nis user To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1012147/+subscriptions -- Ubuntu-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 1276766] Re: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
Steve Langasek steve.langa...@canonical.com writes: This is a bug in puppet, then; there's no reason that puppet should be trying to call 'status startpar-bridge', and the fact that it's doing so is a bug in the puppet code in question. When you run puppet resource service, puppet will enumerate _all_ services on that server (init scripts, upstart jobs, systemd services, whatnot, and then check if it is running, and if it is enabled on boot. When the operatingsystem is ubuntu, the service provider is upstart, The relevant code for handling services on ubuntu is: defaultfor :operatingsystem = :ubuntu commands :start = /sbin/start, :stop= /sbin/stop, :restart = /sbin/restart, :status_exec = /sbin/status, :initctl = /sbin/initctl Is this wrong for Ubuntu? -- 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/1276766 Title: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 781088] Re: Time is not syncronized with NTP-server
Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/781088 Title: Time is not syncronized with NTP-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/781088/+subscriptions -- Ubuntu-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 1276766] Re: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
Hi Stig, On Sat, Mar 15, 2014 at 08:19:04PM +0100, Stig Sandbeck Mathisen wrote: Steve Langasek steve.langa...@canonical.com writes: This is a bug in puppet, then; there's no reason that puppet should be trying to call 'status startpar-bridge', and the fact that it's doing so is a bug in the puppet code in question. When you run puppet resource service, puppet will enumerate _all_ services on that server (init scripts, upstart jobs, systemd services, whatnot, and then check if it is running, and if it is enabled on boot. When the operatingsystem is ubuntu, the service provider is upstart, The relevant code for handling services on ubuntu is: defaultfor :operatingsystem = :ubuntu commands :start = /sbin/start, :stop= /sbin/stop, :restart = /sbin/restart, :status_exec = /sbin/status, :initctl = /sbin/initctl Is this wrong for Ubuntu? Not being particularly familiar with puppet's internals, I don't know if the above is wrong per se. But startpar-bridge (and other jobs present on Ubuntu by default, such as network-interface and network-interface-security) are instantiated jobs; calling 'status network-interface' without specifying a network interface is not meaningful, and any errors returned from 'status' about 'unknown parameter' or 'unknown instance' should not be treated as failures by puppet. If puppet needs to get a list of all jobs running on the system, including instantiated jobs, it should use the 'initctl list' interface. -- 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/1276766 Title: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- Ubuntu-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 781088] Re: Time is not syncronized with NTP-server
Hi Charles. I'm a core dev and I run Trusty on my laptop. Still affected as of 2 months ago when I last traveled with that laptop. I will test again with the latest software and post the results soon. Excerpts from Charles Kerr's message of 2014-03-15 19:29:50 UTC: Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop ISO of the development release - Trusty Tahr. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help. ** Changed in: indicator-datetime (Ubuntu) Status: Confirmed = Incomplete -- You received this bug notification because you are subscribed to the bug report. https://bugs.launchpad.net/bugs/781088 Title: Time is not syncronized with NTP-server Status in “indicator-datetime” package in Ubuntu: Incomplete Status in “ntp” package in Ubuntu: Incomplete Bug description: 11.4 after installation there doesn't seems to be configured any communication with the nets NTP-servers, as the time isn't set correctly. using ntpdate, its possible to get the time set correctly, but this only last until next boot. 1) Default ought to be, that there is communication with NTP-server (when setting location to Denmark the NTP-server(s) ought be set to dk.pool.ntp.org) 2) When explicitly using ntpdate, it ought to result in a lasting configuration of the NTP-client. ProblemType: Bug DistroRelease: Ubuntu 11.04 Package: gnome-system-monitor 2.28.2-0ubuntu1 ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2 Uname: Linux 2.6.38-8-generic i686 Architecture: i386 Date: Wed May 11 12:53:34 2011 ExecutablePath: /usr/bin/gnome-system-monitor ProcEnviron: LANGUAGE=en_US:en LANG=en_DK.UTF-8 LC_MESSAGES=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-system-monitor UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/781088/+subscriptions -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to ntp in Ubuntu. https://bugs.launchpad.net/bugs/781088 Title: Time is not syncronized with NTP-server To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/781088/+subscriptions -- Ubuntu-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 1276766] Re: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB'
Steve Langasek steve.langa...@canonical.com writes: Not being particularly familiar with puppet's internals, I don't know if the above is wrong per se. But startpar-bridge (and other jobs present on Ubuntu by default, such as network-interface and network-interface-security) are instantiated jobs; calling 'status network-interface' without specifying a network interface is not meaningful, and any errors returned from 'status' about 'unknown parameter' or 'unknown instance' should not be treated as failures by puppet. That was what I was missing; instantiation. Thanks. :) If puppet needs to get a list of all jobs running on the system, including instantiated jobs, it should use the 'initctl list' interface. It does, but I think something is off inside puppet's guts. As far as I can see in the source (ruby code at https://github.com/puppetlabs/puppet/blob/master/lib/puppet/provider/service/upstart.rb#L47) it does initctl list, and picks the first word of each line, unless the service in question is network-interface or network-interface-security. It looks like puppet does not handle instances in a generic way, but special cases it for network-interface and network-interface-security, and then hardcoded with INTERFACE=foo and JOB=bar. It looks like the instance variable name differs between services, so if my assumption is correct, I wonder what would be the generic way of enumerating services the correct way would be to find this variable for all instanciated services. -- 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/1276766 Title: 'status startpar-bridge' fails with 'status: Unknown parameter: JOB' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1276766/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1286196] Re: puppet package ensure absent/purged causes warnings
Looks good. :-) Thanks! -- 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/1286196 Title: puppet package ensure absent/purged causes warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1286196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1286196] Re: puppet package ensure absent/purged causes warnings
** Changed in: puppet (Ubuntu) Status: Triaged = Fix Released -- 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/1286196 Title: puppet package ensure absent/purged causes warnings To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/puppet/+bug/1286196/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274247] Re: [MIR] Glusterfs
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: glusterfs (Ubuntu) Status: New = Confirmed -- 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/1274247 Title: [MIR] Glusterfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1274247/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274247] Re: [MIR] Glusterfs
Please let this make it into 14.04 -- 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/1274247 Title: [MIR] Glusterfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1274247/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1274247] Re: [MIR] Glusterfs
** Changed in: glusterfs (Ubuntu) Status: Confirmed = New -- 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/1274247 Title: [MIR] Glusterfs To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glusterfs/+bug/1274247/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
