1327450103 Q * derjohn_mob Ping timeout: 480 seconds
1327450888 J * clopez ~clopez@82.25.60.213.dynamic.mundo-r.com
1327451703 Q * ryker Quit: ryker
1327453152 Q * dowdle 
1327460548 Q * hparker Quit: I've fallen off the 'net and can't get up
1327465031 Q * clopez Ping timeout: 480 seconds
1327469770 J * sannes ~ace@cm-84.209.106.118.getinternet.no
1327470754 J * Marbug ~Marbug@83.101.67.3
1327471532 J * fisted_ ~fisted@xdsl-87-78-17-160.netcologne.de
1327471613 Q * fisted Ping timeout: 480 seconds
1327472907 M * Bertl off to bed now .. have a good one everyone!
1327472912 N * Bertl Bertl_zZ
1327473877 J * derjohn_mob ~aj@d074099.adsl.hansenet.de
1327475612 Q * Marbug Ping timeout: 480 seconds
1327475987 Q * fback Ping timeout: 480 seconds
1327476418 Q * derjohn_mob Ping timeout: 480 seconds
1327476514 J * fback fback@2a02:2780:9000:50::2
1327476688 J * ghislain ~AQUEOS@adsl2.aqueos.com
1327478634 J * petzsch ~markus@dslb-088-075-122-206.pools.arcor-ip.net
1327478650 J * derjohn_mob ~aj@87.253.171.208
1327479632 Q * petzsch Quit: Leaving.
1327481026 J * kir ~kir@swsoft-msk-nat.sw.ru
1327481116 P * kir 
1327481783 Q * ensc|w Remote host closed the connection
1327481792 J * ensc|w ~ensc@www.sigma-chemnitz.de
1327483328 Q * fisted_ Ping timeout: 480 seconds
1327483462 J * fisted ~fisted@xdsl-87-78-17-160.netcologne.de
1327487439 J * clopez ~clopez@155.99.117.91.static.mundo-r.com
1327488919 J * Marbug ~Marbug@83.101.67.3
1327489073 J * petzsch ~markus@dslb-088-075-122-206.pools.arcor-ip.net
1327493163 Q * petzsch Quit: Leaving.
1327493521 Q * DLange Quit: a reboot a day keeps the doctor away
1327493691 J * DLange ~DLange@dlange.user.oftc.net
1327494707 Q * Aiken Remote host closed the connection
1327496694 Q * padde Remote host closed the connection
1327496735 J * padde ~padde@patrick-nagel.net
1327497221 J * ryker ~jalberts@c-67-176-243-86.hsd1.in.comcast.net
1327501883 J * gucki ~gucki@80-218-125-247.dclient.hispeed.ch
1327504353 J * dowdle ~dowdle@scott.coe.montana.edu
1327504877 N * ensc Guest466
1327504887 J * ensc ~irc-ensc@p54ADFCF1.dip.t-dialin.net
1327505296 Q * Guest466 Ping timeout: 480 seconds
1327506360 Q * ryker resistance.oftc.net larich.oftc.net
1327506360 Q * PowerKe resistance.oftc.net larich.oftc.net
1327506360 Q * pexapor resistance.oftc.net larich.oftc.net
1327506360 Q * imcsk8 resistance.oftc.net larich.oftc.net
1327506416 J * pexapor ~rj@tdream.lly.earlham.edu
1327506694 J * PowerKe ~tom@94-226-105-186.access.telenet.be
1327507426 J * ryker ~jalberts@c-67-176-243-86.hsd1.in.comcast.net
1327507536 Q * quasisane Quit: leaving
1327507723 J * quasisane ~sanep@c-24-218-184-186.hsd1.nh.comcast.net
1327509741 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1327510124 N * Bertl_zZ Bertl
1327510128 M * Bertl morning folks!
1327511410 J * bonbons ~bonbons@2001:960:7ab:0:869:7d37:45d9:e42c
1327513410 Q * gucki Remote host closed the connection
1327513542 J * petzsch ~markus@dslb-088-075-122-206.pools.arcor-ip.net
1327514090 Q * ryker Remote host closed the connection
1327514105 J * ryker ~jalberts@CF3840C2.endinfosys.com
1327514476 J * imcsk8 ~ichavero@148.229.1.11
1327514703 Q * mcp Remote host closed the connection
1327514946 Q * petzsch Quit: Leaving.
1327515695 J * mcp ~mcp@wolk-project.de
1327516205 J * trapni ~trapni@h1969975.stratoserver.net
1327516240 M * trapni hey. does anyone know the *proper* way to build a new Ubuntu guest?
1327516404 M * clopez trapni: http://linux-vserver.org/Installing_Ubuntu_on_Debian
1327516772 Q * derjohn_mob Ping timeout: 480 seconds
1327517203 M * trapni clopez: yeah, I kind of followed these guides, but I cannot actually start it then http://pastie.org/3251504 :)
1327517228 M * trapni I posted you the pastie of the error message (and how I bootstrapped the ubuntu container)
1327517413 M * trapni has anyone an idea of what the error message is actually telling me?
1327517488 M * Bertl the message tells you that your util-vserver is quite outdated for the kernel you are using
1327517515 M * trapni oh!
1327517628 M * trapni that error message isn't really *that* self-explanary. in fact, it didn't even mention the "kernel" or "version" word :)
1327517699 M * Bertl it's hard to code in such a way, that future changes to the API will be recognized by the toolchain
1327517854 M * Bertl what the message is correctly telling you is the following:
1327517885 M * Bertl util-vserver called a syscall command (vc_set_sched()) which isn't implemented in your kernel
1327517930 M * Bertl the reason could be either that the kernel is way too old, but that case would be caught by util-vserver when the API is probed
1327517965 M * Bertl or, alternatively, the function was removed from the kernel, because it got replaced by something incompatible, like in this case, cgroups
1327518018 M * Bertl back then, when your util-vserver version was written, this could not have been anticipated, thus no message explaining that a future kernel will not work properly :)
1327518080 J * fisted_ ~fisted@xdsl-87-78-12-178.netcologne.de
1327518130 M * trapni Bertl: that worked. many thanks :)
1327518198 Q * fisted Ping timeout: 480 seconds
1327518215 M * Bertl you're welcome!
1327518379 N * ryker Guest494
1327518379 J * ryker ~jalberts@c-67-176-243-86.hsd1.in.comcast.net
1327518778 Q * Guest494 Ping timeout: 480 seconds
1327520782 Q * clopez Ping timeout: 480 seconds
1327520942 J * pluto pluto@carme.pld-linux.org
1327521284 M * pluto Bertl: do you need more info from my oopsing vserver/autofs? i have a next short service window tomorrow moring...
1327523546 M * Bertl I'll try to recreate the issue here as well, please try to enable the lock proving as well, and upload the output somewhere (pastebin or so)
1327523686 J * petzsch ~markus@dslb-092-078-158-068.pools.arcor-ip.net
1327524063 M * pluto Bertl: iirc the lockdep only reports a false-positive in autofs4 -> http://pastebin.com/yVxeAHEv
1327524211 Q * puck Quit: Coyote finally caught me
1327524352 J * puck ~puck@leibniz.catalyst.net.nz
1327524395 M * Bertl hmm, but it is autofs4 which causes your issues, right?
1327524607 M * pluto Bertl: http://us.generation-nt.com/answer/lockdep-splat-autofs-2-6-39-rc2-help-202915172.html#203012622
1327524632 M * pluto Bertl: this is a still-not-fixed-annotation :)
1327524700 M * pluto Bertl: https://bugzilla.kernel.org/show_bug.cgi?id=33242
1327527070 Q * neofutur Quit: leaving
1327527281 J * neofutur ~neofutur@xena.ww7.be
1327528579 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1327528800 P * pluto sleeping-mode.
1327529550 Q * mcp Remote host closed the connection
1327529568 J * mcp ~mcp@wolk-project.de
1327529707 Q * ghislain Quit: Leaving.
1327529865 M * ryker i'm using cgroups for my servers.  usually the util-vserver mounts /dev/cgroup for me, but I've noticed hosts sometimes end up not having it mounted after a host reboot
1327529886 M * ryker should I just put it in /etc/fstab on the host and not rely on utli-vserver to mount it?
1327530014 M * Bertl no, you should rather ensure that the util-vserver scripts are executed at startup
1327530038 Q * bonbons Quit: Leaving
1327530047 M * ryker it is in startup and the status shows running, but /dev/cgroup isn't mounted sometimes
1327530056 M * Bertl if creating the cgroup mount fails (i.e. they are executed) then there is another problem daniel_hozac might look into
1327530060 M * ryker if i stop and start util-vserver, it mounts it properly
1327530071 M * Bertl what util-vserver version?
1327530242 M * ryker sry, just a sec
1327530258 M * ryker util-vserver-0.30.216-0.pre2937
1327530307 M * ryker I know there is a newer version available, but I don't think this release is too old
1327530416 M * ryker and of course you know the kernel we are currently using ;)
1327530497 M * ryker Bertl: i know where I can find a newer release of util-vserver, but I don't know where there's a changelog at to see if this is a known bug that was fixed.  Do you know if there is a changelog somewhere?
1327530574 M * ryker i'm tempted to just add the cgroup mounting to my /etc/fstab.  I had that before, but later removed it when I noticed util-vserver was mounting it for me.  I don't recall any errors by util-vserver if it was already mounted.
1327530645 M * Bertl my suggestion would be to simply update to pre3004
1327530733 M * Bertl you have to check with daniel_hozac regarding changelog and/or this specific issue, but I remember something similar
1327530785 M * ryker Bertl: ok.  will do.  Any idea if I *must* restart all of the guests after I upgrade util-vserver or is it safe to just do it later?
1327530825 M * Bertl should be perfectly safe to not restart at all
1327530876 M * Bertl of course, it is advised to do a supervised restart (at some point), to know everything is coming up as expected
1327530906 M * ryker ok, that's what I was hoping. :)
1327530918 M * ryker Bertl: got a sec to look at this?  http://pastebin.com/KwbvHi9z
1327530927 M * ryker this was in my hosts message log after a guest restarted
1327530941 M * ryker it caused the other guests to lose network connectivity
1327530957 M * ryker but this is the same host (and guests) that didn't have /dev/cgroup mounted
1327530980 M * ryker I assume/hope the restart problem and kernel message is related.
1327530999 M * Bertl 2.6.38-rc6 ... a lot was fixed since then, mainline and Linux-VServer wise
1327531051 M * ryker i don't even understand what the kernel message is and if it's bad or just a warning about something
1327531064 M * ryker do you have any idea?
1327531072 M * Bertl it is a warning (as it says in capital letters :)
1327531091 M * ryker LOL, yes indeed it does :)
1327531097 M * Bertl it basically means that something happened which wasn't supposed to happen
1327531161 M * Bertl could be harmless, could be a potential issue, I'd rather say this is the result of a network interface losing a large part of its configuration than the cause for similar
1327531200 M * Bertl when the guests are actively using the assigned IPs, and the IPs suddenly go away, the kernel becomes a little confused
1327531228 M * ryker well, that would explain what happened to my guests then.  I guess they lost their network configuration for some reason.
1327531250 M * ryker 4 guests, 1 guest was rebooted, the other 3 lost connectivity
1327531260 M * Bertl yes, and that is the point you should focus on, i.e. why did they lose their addresses
1327531274 M * Bertl and most likely the answer is simple and already covered in the FAQ
1327531282 M * ryker could it have anything to do with cgroups not being mounted?
1327531289 M * ryker i didn't think network used cgroups
1327531296 M * Bertl i.e. you do not promote secondaries and one guest holds a primary
1327531313 M * Bertl not really cgroup related I guess
1327531330 M * Bertl is the system up and running right now?
1327531359 M * ryker yes it is.  I stopped all of the guests.  restarted util-vserver, which mounted /dev/cgroup, and then started the guests.
1327531362 M * ryker all seems well now
1327531381 M * Bertl what does 'ip a l' report in regard of 'secondaries'?
1327531387 M * Bertl (on the host)
1327531450 M * Bertl i.e. is one guest IP listed _without_ the 'secondary' flag?
1327531483 M * ryker yes, it is actually.  one of them is
1327531503 M * Bertl and what does: 'sysctl -a | grep promote' report?
1327531517 M * Bertl disabled for the interface the guest is on?
1327531542 M * ryker http://pastebin.com/4kRBF2c6
1327531562 M * ryker yes, disabled for all
1327531576 M * ryker i've never heard of that flag before
1327531584 M * Bertl so, when you restart that specific guest, all other guests will lose their connectivity
1327531593 M * Bertl that's how mainline designed it to work
1327531638 M * ryker wow, that's not good
1327531659 M * Bertl and my guess is, that once that happens, the warnings you have seen will reappear :)
1327531681 M * ryker so this is expected behavior?  how can I fix it?
1327531694 M * Bertl anyway, as I said, that's an FAQ, and can be simply avoided by enabling the promote_secondaries
1327531788 M * Bertl and yes, from the mainline PoV this is expected (and desired) behaviour
1327531863 M * ryker so i need to read the faq to figure out how to fix this?
1327531878 M * ryker ie. it's in the faq?  thx. i never noticed that.
1327531898 M * Bertl not necessarily, sysctl -w net.ipv4.conf.all.promote_secondaries=1 should fix it
1327531925 M * Bertl of course, setting the net.ipv4.conf.default.promote_secondaries isn't such a bad idea either
1327531941 M * Bertl both can be done in the host's sysctl config
1327532222 M * ryker is there any reason I wouldn't want promote_secondaries to be the default?
1327532235 M * ryker I don't even know what it actually means.  I guess I should google and read
1327532301 M * Bertl it means that if the primary goes down (that's the IP without the secondary flag) a new primary is found among the remaining secondaries instead of taking all of them down as well
1327532335 M * Bertl besides that, there is no other effect of that sysctl flag
1327532394 M * ryker ok.  thank you very much for your help.
1327532454 M * Bertl you're welcome!
1327532604 Q * Marbug Ping timeout: 480 seconds
1327532616 Q * petzsch Quit: Leaving.
1327532986 J * NightMonkey ~NightMonk@nightmonkey.user.oftc.net
1327533013 M * NightMonkey Hi all. Is Upstart in guests supported at present (ala CentOS6/Ubuntu)?
1327533098 M * ryker NightMonkey: there's info in the wiki about upstart here: http://linux-vserver.org/Upstart_issues
1327533139 M * ryker i know i had upstart working fine in an ubuntu guest a while back, but 99.9% of my guests are centos 5 right now
1327533187 J * petzsch ~markus@dslb-092-078-158-068.pools.arcor-ip.net
1327533209 M * NightMonkey Ah, thanks ryker.
1327533225 M * ryker Bertl: sorry, I'm continuing to think about this secondary issue in my head. :)   so…. all guests IP's should be indicated as secondaries in 'ip a l' ? 
1327533267 M * Bertl if you don't want to enable promote_secondaries then better yes
1327533282 M * Bertl but with promote_secondaries enabled it doesn't matter
1327533295 M * NightMonkey Hrm, presently, the setup looks a bit brittle, at least from the wiki page. But I can give it a shot.
1327533519 Q * petzsch Quit: Leaving.
1327534997 M * daniel_hozac NightMonkey: last time i tried it, it was fine.
1327535002 M * daniel_hozac (on RHEL6)
1327535784 Q * BobR_zZ Remote host closed the connection
1327535809 Q * sid3windr Remote host closed the connection
1327535810 J * sid3windr luser@bastard-operator.from-hell.be
1327535824 Q * Bertl Remote host closed the connection