[Bug 1557345] Re: xenial juju 1.25.3 unable to deploy to lxc containers
** Tags added: cross-team-kanban landscape -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to juju-core in Ubuntu. https://bugs.launchpad.net/bugs/1557345 Title: xenial juju 1.25.3 unable to deploy to lxc containers To manage notifications about this bug go to: https://bugs.launchpad.net/juju-core/+bug/1557345/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1490727] Re: "Invalid IPC credentials" after corosync, pacemaker service restarts
** Changed in: landscape/cisco-odl Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to pacemaker in Ubuntu. https://bugs.launchpad.net/bugs/1490727 Title: "Invalid IPC credentials" after corosync, pacemaker service restarts To manage notifications about this bug go to: https://bugs.launchpad.net/landscape/+bug/1490727/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382632] Re: Insecure key file permissions
I don't think the ordering of the package installs are important. They run the same command. The problem seem to be that the code that creates the secret key doesn't create it with the right permissions. The current code in horizon/utils/secret_key.py does this: old_umask = os.umask(0o177) # Use '0600' file permissions with open(key_file, 'w') as f: f.write(key) os.umask(old_umask) That doesn't work on the systems we're installing to. It works if I change the code to: with open(key_file, 'w') as f: os.chmod(key_file, 0o600) f.write(key) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1382632/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382632] Re: Insecure key file permissions when running under LXC
The system where we saw this bug uses file system ACLs, with defauls, and thus the umask is ignored: ubuntu@juju-machine-0-lxc-5:/var/lib/openstack-dashboard$ getfacl . # file: . # owner: root # group: root user::rwx group::r-x other::r-x default:user::rwx default:group::r-x default:other::r-x -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1382632 Title: Insecure key file permissions when running under LXC To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1382632/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1382632] Re: Insecure key file permissions
To clarify, I see the same behavior on bare metal, deploying machines with MAAS using the fast-path installer, so it's not LXC-specific. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to horizon in Ubuntu. https://bugs.launchpad.net/bugs/1382632 Title: Insecure key file permissions To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/horizon/+bug/1382632/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 670289] Re: Laptop won't shut down with rabbitmq running
To add further to Thomas' observations, after disconnecting NM, the beginning of my /etc/hosts file look like this: 192.168.60.104|_ixia|___# Added by NetworkManager 127.0.0.1|__localhost.localdomain|__localhost ::1|ixia|___localhost6.localdomain6|localhost6 127.0.1.1|__ixia If I comment out the first line (192.168.60.104), rabbitmq-multi status and stop_all work as expected. Could it be that NetworkManager should remove the added line in /etc/hosts when it disconnects from a network? -- 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/670289 Title: Laptop won't shut down with rabbitmq running -- Ubuntu-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 670289] Re: Laptop won't shut down with rabbitmq running
On Thu, Dec 16, 2010 at 08:12:49AM -, Thomas Herve wrote: Since Maverick, NetworkManager seems to do some weird trick with /etc/hosts, making the local hostname unresolvable at some points. At least when it doesn't start, I get a can't resolve hostname error in startup_err, which could map with what Björn is saying, where the hostname can't be found at shutdown (presumably after NM did his job on a laptop). Right, this seems to be the issue somehow. I can reproduce the issue without shutting down the laptop, if I disconnect any network that NetworkManager is connected to. If NM isn't connected to anything, rabbit-multi status says that rab...@ixia is not_running and rabbitmq-multi stop_all hangs while trying to stop rab...@ixia. Björn: do you have anything in shutdown_err by any chance? No, nothing. -- Björn Tillenius | https://launchpad.net/~bjornt -- 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/670289 Title: Laptop won't shut down with rabbitmq running -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 670289] Re: Laptop won't shut down with rabbitmq running
FWIW, an ugly workaround to this bug is to place a file in /etc/rc0.d and /etc/rc6.d that removes the line NetworkManager added before rabbitmq is shut down. I'm attaching the file I'm using to do that. ** Attachment added: K19remove-nm-from-hosts https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/670289/+attachment/1767484/+files/K19remove-nm-from-hosts -- 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/670289 Title: Laptop won't shut down with rabbitmq running -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 670289] Re: Laptop won't shut down with rabbitmq running
Clint, when shutting down, the console doesn't show much. It shows killing apache, a few other things, and then it stalls when trying to shut down rabbitmq. I.e, it doesn't get any further, so sendsigs doesn't get executed. It's the 'rabbitmq-multi stop_all' that hangs. Seems it's waiting forever for the node to shut down. I'm attaching shutdown_log. Also, I modified the init.d script to log what 'rabbitmq-multi status' says, and it says: Status of all running nodes... Node 'rab...@ixia' with Pid 3743: not_running done. -- 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/670289 Title: Laptop won't shut down with rabbitmq running -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 670289] Re: Laptop won't shut down with rabbitmq running
** Attachment added: shutdown_log https://bugs.launchpad.net/ubuntu/+source/rabbitmq-server/+bug/670289/+attachment/1767403/+files/shutdown_log -- 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/670289 Title: Laptop won't shut down with rabbitmq running -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
