[Bug 947617] Re: After update, lxc does not start
Serge, This container I created with oneiric with the lxc-sshd template. It worked there reasonably well (only needed to add a default route, which is missing). I've compared (visually) what oneiric created for mounting and what precise would have created. It seems there is only 1 difference. Oneiric did not include a mount for /proc, which precise does add. To me this looks like a regression after upgrading from oneiric. -- 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/947617 Title: After update, lxc does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/947617/+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 947617] Re: After update, lxc does not start
For me this seems not fixed. ii apparmor 2.7.102-0ubuntu3 User-space parser utility for AppArmor ii lxc 0.7.5-3ubuntu56 Linux containers userspace tools root@kira:~# lxc-start -n jake lxc-start: failed to mount rootfs lxc-start: failed to setup rootfs for 'jake' lxc-start: failed to setup the container lxc-start: invalid sequence number 1. expected 2 lxc-start: failed to spawn 'jake' And in dmesg [92690.144338] type=1400 audit(1339010096.655:40): apparmor=DENIED operation=mount info=failed type match error=-13 parent=3406 profile=/usr/bin/lxc-start name=/var/tmp/lxc/jake/ pid=3429 comm=lxc-start srcname=/var/lib/lxc/jake/rootfs/ flags=rw, rbind I have not yet tried the workaround from comment 4, but will try that shortly. -- 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/947617 Title: After update, lxc does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/947617/+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 947617] Re: After update, lxc does not start
After the workaround, my container is running. -- 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/947617 Title: After update, lxc does not start To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/apparmor/+bug/947617/+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 278712] [NEW] 3.2.3 and qemu: could not init smb messaging context
Public bug reported: Binary package hint: samba I've got win2k in a qemu vm and I'm using '-smb' with my home directory. When I try to reach that network drive, smbd crashes. The log is below. And w2k reports that the network path was not found. Smbd reports that it is dumping core in /var/log/samba/cores/smbd, but nothing shows up there. So there might be two bugs here, one being that it crashes, as in the log below. The second being that there is no coredump. Note that I 'chgrp adm /var/*/samba' and 'chmod g+rw /var/*/samba' to be able to run samba as a regular user. This is because of bug 50385. This is intrepid, uptodate to today, 5-oct-2008, it is 2:3.2.3-1ubuntu2. And this is a x86_64 install. If there's something else you'd like me to do, just ask. It is very easy to reproduce. This is all that is logged for the whole run in /var/log/samba/smbd.log: [2008/10/05 19:30:12, 0] smbd/server.c:main(1213) smbd version 3.2.3 started. Copyright Andrew Tridgell and the Samba Team 1992-2008 [2008/10/05 19:30:12, 0] lib/messages_local.c:messaging_tdb_init(96) ERROR: Failed to initialise messages database: Permission denied [2008/10/05 19:30:12, 0] lib/messages.c:messaging_init(204) messaging_tdb_init failed: NT_STATUS_ACCESS_DENIED [2008/10/05 19:30:12, 0] lib/util.c:smb_panic(1663) PANIC (pid 15018): Could not init smbd messaging context [2008/10/05 19:30:12, 0] lib/util.c:log_stack_trace(1767) BACKTRACE: 6 stack frames: #0 /usr/sbin/smbd(log_stack_trace+0x1c) [0x7f526f56ec5d] #1 /usr/sbin/smbd(smb_panic+0x5b) [0x7f526f56ed6b] #2 /usr/sbin/smbd(smbd_messaging_context+0x3f) [0x7f526f42d4d7] #3 /usr/sbin/smbd(main+0x68d) [0x7f526f42de8a] #4 /lib/libc.so.6(__libc_start_main+0xe6) [0x7f526c0a0466] #5 /usr/sbin/smbd [0x7f526f42cd89] [2008/10/05 19:30:12, 0] lib/fault.c:dump_core(201) dumping core in /var/log/samba/cores/smbd ** Affects: samba (Ubuntu) Importance: Undecided Status: New -- 3.2.3 and qemu: could not init smb messaging context https://bugs.launchpad.net/bugs/278712 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 278712] Re: 3.2.3 and qemu: could not init smb messaging context
Please note that there's a simple 'chmod g+rw /var/run/samba/message.tbd' fixes the access denied and thus prevents the whole stacktrace. But I just thought that I should report it anyways. -- 3.2.3 and qemu: could not init smb messaging context https://bugs.launchpad.net/bugs/278712 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 50385] Re: samba can't be launched by a normal user (qemu related)
After the workaround I did, samba started and was usable from a w2k in qemu. (I did start chmodding only one file and manually starting smbd and then it complained about another one and then another one...) I don't know what's incomplete about this bug and I can confirm that it still exists with hardy packages: qemu 0.9.1-1ubuntu1, samba 3.0.28a- 1ubuntu4. ** Changed in: qemu (Ubuntu) Status: Incomplete = Confirmed -- samba can't be launched by a normal user (qemu related) https://bugs.launchpad.net/bugs/50385 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 50385] Re: samba can't be launched by a normal user (qemu related)
Me too. As a really ugly workaround I thought about this... (1) disable samba to run as daemon (add 'exit' in /etc/default/samba) (2) sudo chmod a+rw /var/run/samba/*.tdb /var/lib/samba/*.tdb This totally ruins the samba security, I expect. That's why I disabled samba to start as a daemon. -- samba can't be launched by a normal user (qemu related) https://bugs.launchpad.net/bugs/50385 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
