Re: [Lxc-users] Problem with: lxc.autodev=1
Thanks for your work. Am 24.04.2013 14:30, schrieb Frederic Crozat: Le lundi 22 avril 2013 à 13:57 +0200, Andreas Otto a écrit : Ok. I'll do more tests on my side. But you should open a bug report on https://bugzilla.novell.com/ against openSUSE (and assign it to me) so we don't loose it. - done For the record, I was able to duplicate the problem and found the issue. An umask call was missing. This is already fixed in 0.9.0 (see 3a32201c5a442c2732861aeee1a5f70909718b90 ) but not when I backport lxc.autodev to our package. Should be fixed in a future maintenance update on openSUSE.. -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Problem with: lxc.autodev=1
Le lundi 22 avril 2013 à 13:57 +0200, Andreas Otto a écrit : Ok. I'll do more tests on my side. But you should open a bug report on https://bugzilla.novell.com/ against openSUSE (and assign it to me) so we don't loose it. - done For the record, I was able to duplicate the problem and found the issue. An umask call was missing. This is already fixed in 0.9.0 (see 3a32201c5a442c2732861aeee1a5f70909718b90 ) but not when I backport lxc.autodev to our package. Should be fixed in a future maintenance update on openSUSE.. -- Frederic Crozat fcro...@suse.com SUSE -- Try New Relic Now We'll Send You this Cool Shirt New Relic is the only SaaS-based application performance monitoring service that delivers powerful full stack analytics. Optimize and monitor your browser, app, servers with just a few lines of code. Try New Relic and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_apr ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Problem with: lxc.autodev=1
Am 22.04.2013 10:28, schrieb Frederic Crozat: Le samedi 20 avril 2013 à 21:13 +0200, Andreas Otto a écrit : Hi all, my problem: the autodev create devices with wrong permissions: ls -ald /dev/* crw-rw 1 root tty 136, 16 Apr 20 18:34 /dev/console lrwxrwxrwx 1 root root 11 Apr 20 18:34 /dev/core - /proc/kcore lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/fd - /proc/self/fd crwxr-xr-x 1 root root 1, 7 Apr 20 18:34 /dev/full drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/hugepages prw--- 1 root root 0 Apr 20 18:34 /dev/initctl lrwxrwxrwx 1 root root 7 Apr 20 18:34 /dev/kmsg - console srw-rw-rw- 1 root root 0 Apr 20 18:34 /dev/log drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/mqueue crwxr-xr-x 1 root root 1, 3 Apr 20 18:34 /dev/null lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/ptmx - /dev/pts/ptmx drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/pts crwxr-xr-x 1 root root 1, 8 Apr 20 18:34 /dev/random drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/shm lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stderr - /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdin - /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdout - /proc/self/fd/1 crwxr-xr-x 1 root root 5, 0 Apr 20 18:34 /dev/tty crw-rw 1 root tty 136, 12 Apr 20 18:34 /dev/tty1 crw-rw 1 root tty 136, 13 Apr 20 18:34 /dev/tty2 crw-rw 1 root tty 136, 14 Apr 20 18:34 /dev/tty3 crw-rw 1 root tty 136, 15 Apr 20 18:34 /dev/tty4 crwxr-xr-x 1 root root 1, 9 Apr 20 18:34 /dev/urandom crwxr-xr-x 1 root root 1, 5 Apr 20 18:34 /dev/zero check the permissions for /dev/tty or /dev/null as example. Are you checking the permissions when the container is running or after it was run ? while it was running. it was possible to change permission in the /dev by root after but every reebot it was gond ;-) a normal user is not able to use these devices ... example: login into an non-root-user account. ssh dev01@nhi2 ... Last login: Sat Apr 20 18:34:29 2013 from linux02 Have a lot of fun... -bash: /dev/null: Permission denied -bash: /dev/null: Permission denied -bash: /dev/null: Permission denied Im using opensuse 12.3 on the host and guest. The gues is a fresh lxc container. Just to be sure: did you upgrade your system to 12.3 ? It could have an old cache for the container generation (it should be fixed these days when upgrading distro but you never know..). This is a fresh 12.3 on host and on quest ... mfg AO -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Problem with: lxc.autodev=1
Hi, as one solution I try to switch my lxc container on opensuse 12.3 back to sysvinit-init but this seems not to work eigther... # zypper --root /var/lib/lxc/nhi2/rootfs in sysvinit-init Daten des Repositories laden ... Installierte Pakete lesen ... Paketabhängigkeiten auflösen ... Problem: systemd-sysvinit-195-13.18.1.x86_64 steht in Konflikt mit namespace:otherproviders(sbin_init), angeboten von sysvinit-init-2.88+-83.2.1.x86_64 Lösung 1: Folgende Aktionen werden ausgeführt: Deinstallation von systemd-sysvinit-195-13.18.1.x86_64 Deinstallation von aaa_base-12.3-14.8.1.x86_64 Deinstallation von patterns-openSUSE-base-12.3-7.10.1.x86_64 Deinstallation von netcfg-11.5-14.1.1.noarch Deinstallation von ghostscript-fonts-std-9.06-2.1.1.noarch Deinstallation von ghostscript-fonts-other-9.06-2.1.1.noarch Deinstallation von ghostscript-9.06-4.1.1.x86_64 Deinstallation von ghostscript-x11-9.06-4.1.1.x86_64 Lösung 2: sysvinit-init-2.88+-83.2.1.x86_64 nicht installieren Wählen Sie aus den obigen Lösungen mittels Nummer oder brechen Sie a(b). [1/2/b] (b): = I think it os not an good solution to delete aaa_base .-( ## as second solution I try to don't use autodev=1 and to create the devices by hand ... but hand-made devices together with systemd ... the system immideadly crash - it seems somthig eat alle the memory :-( mfg AO Am 22.04.2013 10:28, schrieb Frederic Crozat: Le samedi 20 avril 2013 à 21:13 +0200, Andreas Otto a écrit : Hi all, my problem: the autodev create devices with wrong permissions: ls -ald /dev/* crw-rw 1 root tty 136, 16 Apr 20 18:34 /dev/console lrwxrwxrwx 1 root root 11 Apr 20 18:34 /dev/core - /proc/kcore lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/fd - /proc/self/fd crwxr-xr-x 1 root root 1, 7 Apr 20 18:34 /dev/full drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/hugepages prw--- 1 root root 0 Apr 20 18:34 /dev/initctl lrwxrwxrwx 1 root root 7 Apr 20 18:34 /dev/kmsg - console srw-rw-rw- 1 root root 0 Apr 20 18:34 /dev/log drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/mqueue crwxr-xr-x 1 root root 1, 3 Apr 20 18:34 /dev/null lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/ptmx - /dev/pts/ptmx drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/pts crwxr-xr-x 1 root root 1, 8 Apr 20 18:34 /dev/random drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/shm lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stderr - /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdin - /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdout - /proc/self/fd/1 crwxr-xr-x 1 root root 5, 0 Apr 20 18:34 /dev/tty crw-rw 1 root tty 136, 12 Apr 20 18:34 /dev/tty1 crw-rw 1 root tty 136, 13 Apr 20 18:34 /dev/tty2 crw-rw 1 root tty 136, 14 Apr 20 18:34 /dev/tty3 crw-rw 1 root tty 136, 15 Apr 20 18:34 /dev/tty4 crwxr-xr-x 1 root root 1, 9 Apr 20 18:34 /dev/urandom crwxr-xr-x 1 root root 1, 5 Apr 20 18:34 /dev/zero check the permissions for /dev/tty or /dev/null as example. Are you checking the permissions when the container is running or after it was run ? a normal user is not able to use these devices ... example: login into an non-root-user account. ssh dev01@nhi2 ... Last login: Sat Apr 20 18:34:29 2013 from linux02 Have a lot of fun... -bash: /dev/null: Permission denied -bash: /dev/null: Permission denied -bash: /dev/null: Permission denied Im using opensuse 12.3 on the host and guest. The gues is a fresh lxc container. Just to be sure: did you upgrade your system to 12.3 ? It could have an old cache for the container generation (it should be fixed these days when upgrading distro but you never know..). fresh install 12.3 host and guest -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Problem with: lxc.autodev=1
Le lundi 22 avril 2013 à 10:43 +0200, Andreas Otto a écrit : Am 22.04.2013 10:28, schrieb Frederic Crozat: Le samedi 20 avril 2013 à 21:13 +0200, Andreas Otto a écrit : Hi all, my problem: the autodev create devices with wrong permissions: ls -ald /dev/* crw-rw 1 root tty 136, 16 Apr 20 18:34 /dev/console lrwxrwxrwx 1 root root 11 Apr 20 18:34 /dev/core - /proc/kcore lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/fd - /proc/self/fd crwxr-xr-x 1 root root 1, 7 Apr 20 18:34 /dev/full drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/hugepages prw--- 1 root root 0 Apr 20 18:34 /dev/initctl lrwxrwxrwx 1 root root 7 Apr 20 18:34 /dev/kmsg - console srw-rw-rw- 1 root root 0 Apr 20 18:34 /dev/log drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/mqueue crwxr-xr-x 1 root root 1, 3 Apr 20 18:34 /dev/null lrwxrwxrwx 1 root root 13 Apr 20 18:34 /dev/ptmx - /dev/pts/ptmx drwxr-xr-x 2 root root 0 Apr 20 18:34 /dev/pts crwxr-xr-x 1 root root 1, 8 Apr 20 18:34 /dev/random drwxrwxrwt 2 root root 40 Apr 20 18:34 /dev/shm lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stderr - /proc/self/fd/2 lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdin - /proc/self/fd/0 lrwxrwxrwx 1 root root 15 Apr 20 18:34 /dev/stdout - /proc/self/fd/1 crwxr-xr-x 1 root root 5, 0 Apr 20 18:34 /dev/tty crw-rw 1 root tty 136, 12 Apr 20 18:34 /dev/tty1 crw-rw 1 root tty 136, 13 Apr 20 18:34 /dev/tty2 crw-rw 1 root tty 136, 14 Apr 20 18:34 /dev/tty3 crw-rw 1 root tty 136, 15 Apr 20 18:34 /dev/tty4 crwxr-xr-x 1 root root 1, 9 Apr 20 18:34 /dev/urandom crwxr-xr-x 1 root root 1, 5 Apr 20 18:34 /dev/zero check the permissions for /dev/tty or /dev/null as example. Are you checking the permissions when the container is running or after it was run ? while it was running. it was possible to change permission in the /dev by root after but every reebot it was gond ;-) I know :) This is because /dev is mounted as a tmpfs when running with systemd, so any change you do will be lost.. a normal user is not able to use these devices ... example: login into an non-root-user account. ssh dev01@nhi2 ... Last login: Sat Apr 20 18:34:29 2013 from linux02 Have a lot of fun... -bash: /dev/null: Permission denied -bash: /dev/null: Permission denied -bash: /dev/null: Permission denied Im using opensuse 12.3 on the host and guest. The gues is a fresh lxc container. Just to be sure: did you upgrade your system to 12.3 ? It could have an old cache for the container generation (it should be fixed these days when upgrading distro but you never know..). This is a fresh 12.3 on host and on quest ... Ok. I'll do more tests on my side. But you should open a bug report on https://bugzilla.novell.com/ against openSUSE (and assign it to me) so we don't loose it. -- Frederic Crozat fcro...@suse.com SUSE -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Problem with: lxc.autodev=1
Ok. I'll do more tests on my side. But you should open a bug report on https://bugzilla.novell.com/ against openSUSE (and assign it to me) so we don't loose it. - done -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter ___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
Re: [Lxc-users] Problem with: lxc.autodev=1
On Sat, 2013-04-20 at 22:01 +0200, Andreas Otto wrote: Hi, thanks for the fast answer, Been kind-of deeply involved in the whole systemd / audodev thing so I'm a bit sensitive to some of the bizarre nuances of systemd and various versions. You got my attention with that subject line. They (systemd) really broke far too many things far too unnecessarily (with little or no benefit from what I can discern) and then tried to tell everyone else how they should be doing things. It's been a real mess. You can probably tell, I'm not a fan of systemd at the moment. Maybe when it grows up and matures a bit more... I've got Fedora 14 (upstart - no systemd) working with and without autodev, Fedora 15 working with upstart (with systemd only after painful tweaking) and Fedora 16 not at all with systemd (major udev problems) but working on Fedora 17 with systemd following their recommendations. Problem is that their recommendations don't work for all versions of systemd. I've really given up on Fedora 15 and 16 in a container just because systemd is not stable or consistent in its behavior. if lxc version is: host# rpm -q lxc lxc-0.8.0-3.5.1.x86_64 - this is the version from opensuse 12.3 First recommendation is to get on 0.9.0. We got a lot of fixes in there so I can't tell if this was fixed or not. my 'guest' has ... guest# ps -eaf | grep systemd root 24 1 0 19:48 ?00:00:00 /usr/lib/systemd/systemd-logind message+ 28 1 0 19:48 ?00:00:00 /bin/dbus-daemon --system --address=systemd: --nofork --nopidfile --systemd-activation root955 1 0 19:48 ?00:00:00 /usr/lib/systemd/systemd-journald Any idea what version of systemd is running? I've found there are a number of versions that seem to be impossible to get to work and one versions that works you find the next version doesn't. I find this particular problem rather disturbing. I have not seen the permissions problem crop up in a systemd container with autodev enabled. What I've seen was just the opposite. This should have worked. Not sure what's causing it to be wrong, unless it's the lxc version but ever 0.8.0 worked if you had the right version of systemd. I did retest a fresh Fedora 14 (upstart) container and it works with the proper permissions in the /dev directory for both autodev settings. But that's under 0.9.0, so that would be my first check. Regards, Mike -- Michael H. Warfield (AI4NB) | (770) 985-6132 | m...@wittsend.com /\/\|=mhw=|\/\/ | (678) 463-0932 | http://www.wittsend.com/mhw/ NIC whois: MHW9 | An optimist believes we live in the best of all PGP Key: 0x674627FF| possible worlds. A pessimist is sure of it! signature.asc Description: This is a digitally signed message part -- Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter___ Lxc-users mailing list Lxc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/lxc-users
