1352940173 Q * Ghislain Quit: Leaving.
1352943755 J * nkukard_ ~nkukard@dsl-246-172-193.telkomadsl.co.za
1352943824 Q * nkukard Read error: Operation timed out
1352943880 Q * clopez Ping timeout: 480 seconds
1352944521 Q * nkukard_ Ping timeout: 480 seconds
1352945006 J * nkukard_ ~nkukard@196.28.214.91
1352947433 J * fisted ~fisted@xdsl-84-44-144-2.netcologne.de
1352947951 Q * nkukard_ Read error: Operation timed out
1352951403 J * nkukard ~nkukard@196.28.222.157
1352955412 Q * nkukard Ping timeout: 480 seconds
1352958220 J * nkukard ~nkukard@41.177.102.96
1352962025 Q * ncopa Quit: Leaving
1352962033 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no
1352963116 M * Bertl off to bed now ... have a good one everyone!
1352963122 N * Bertl Bertl_zZ
1352963129 J * BenG ~bengreen@cpc29-aztw23-2-0-cust144.18-1.cable.virginmedia.com
1352963418 J * kir ~kir@swsoft-msk-nat.sw.ru
1352965432 J * derjohn_mob ~aj@87.253.171.216
1352965433 Q * tolkor Read error: Connection reset by peer
1352965451 J * tolkor ~rj@tdream.lly.earlham.edu
1352967983 J * Ghislain ~aqueos@adsl1.aqueos.com
1352971777 J * lkosewsk ~lkosewsk@2002:ae01:71dc:1234:21f:3bff:fe04:4581
1352973863 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:4ce6:f313:6df2:32af
1352973948 P * kir PING 1352973948
1352974728 J * fisted_ ~fisted@xdsl-87-78-188-29.netcologne.de
1352975134 Q * fisted Ping timeout: 480 seconds
1352975134 N * fisted_ fisted
1352977179 M * aurel42 I got a weird error last night: "root@jake:~# vserver-stat
1352977183 M * aurel42 WARNING: can not access /proc/uptime. Usually, this is caused by procfs-security.
1352977201 Q * fisted Remote host closed the connection
1352977242 M * aurel42 I rebooted with a kernel without procfs security, verified that it worked, realized some of the drawbacks of missing procfs-security, turned it back on, now the error is gone.
1352977260 J * clopez ~clopez@fanzine.igalia.com
1352977263 J * fisted ~fisted@xdsl-87-78-182-249.netcologne.de
1352977283 M * aurel42 (3.2.33-vs2.3.2.15)
1352977347 M * aurel42 I should say that I tried this on the host (jake), not on the guest. At this point, the host had one guest installed, but it wasn't running.
1352977405 M * daniel_hozac had you run vprocunhide?
1352977420 M * aurel42 Do I need to – on the *host*?
1352977428 M * daniel_hozac yes
1352977433 M * daniel_hozac that is the only place you need to
1352977439 M * daniel_hozac a guest can't control that.
1352977457 M * aurel42 But /proc isn't hidden on the host?
1352977467 M * aurel42 Well, it shouldn't be, should it?
1352977517 M * aurel42 I got the procfs error message on the *host* system when trying to run "vserver-stat".
1352977520 M * daniel_hozac it is on the spectator.
1352977525 M * daniel_hozac which is where vserver-stat runs.
1352977540 M * aurel42 Oh. Is that a separate context?
1352977556 M * daniel_hozac yes
1352977577 M * aurel42 Let me grep init.d for vprocunhide :)
1352977696 M * aurel42 daniel_hozac: thanks for explaining, I think I understand now. The init scripts handled that for me before, this time I probably installed those packages too late and so only the next reboot fixed it.
1352977713 M * daniel_hozac probably
1352977727 M * aurel42 There's actually a dedicated /etc/init.d/vprocunhide that I never noticed before.
1352977730 M * aurel42 Shame on me.
1352977743 M * aurel42 tyvm
1352978529 Q * renihs Remote host closed the connection
1352979600 Q * ircuser-1 Ping timeout: 480 seconds
1352982337 Q * Aiken Remote host closed the connection
1352983065 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net
1352985883 M * aurel42 Is there anything I need to be aware of when migrating guests from a 32bit host to a 64bit host? I moved a test system which seems to work fine, but I thought I'd ask around before migrating production systems. :)
1352985917 M * daniel_hozac as long as your 64-bit host can run 32-bit binaries, you're set.
1352985960 M * aurel42 Great, thanks
1352986707 M * BenG you've set the 'personality' of the  guest server? aurel42 ?
1352986923 Q * click Ping timeout: 480 seconds
1352987324 Q * thierryp Remote host closed the connection
1352987413 Q * fisted Quit: leaving
1352987505 J * fisted ~fisted@xdsl-87-78-182-249.netcologne.de
1352988597 N * Bertl_zZ Bertl
1352988608 M * Bertl morning folks!
1352989604 M * aurel42 BenG: didn't have to. Should I, even if it works already?
1352989622 M * daniel_hozac if you're using yum you should.
1352989643 M * aurel42 All Debian here.
1352990133 M * aurel42 Sorry for keeping you so busy today, but I have another probl^Wchallenge.
1352990187 M * aurel42 On a 2.6.36.3-vs2.3.0.36.38.4 host, I get "ls: cannot access /proc/virtual: No such file or directory" (as expected) when trying to access /proc/virtual from inside a guest.
1352990196 M * Bertl in general, it is a good idea to set the proper personality
1352990222 M * aurel42 On 3.2.33-vs2.3.2.15, I get "ls: cannot open directory /proc/virtual: Permission denied" instead.
1352990230 M * aurel42 Is that working as intended?
1352990264 M * aurel42 It breaks my puppet setup, because facter thinks the guest is a vserver_host when /proc/virtual exists.
1352990271 J * shaggy63 ~packethel@c-98-212-73-99.hsd1.in.comcast.net
1352990332 M * shaggy63 I read a pdf from 2007 about vserver.  It had a bit about guests sharing ips.  What would be the benefits of that?
1352990358 M * daniel_hozac none, NAT works better.
1352990435 M * Bertl aurel42: it is most likely the result of the changes in newer kernels and might be related to the reported issue regarding /dev/pts (will check that shortly)
1352990519 M * aurel42 Bertl: would you recommend a kernel to fall back to? If not, I'd use 2.6.36.3-vs2.3.0.36.38.4, because that one has been good to me. :)
1352990541 M * shaggy63 thanks, that is what I figured.  Also,  fixed upper bounds on RSS not being appropriate for usage scenarios for overbooking containers.
1352990731 M * Bertl aurel42: 2.6.38 was IMHO a good choice ...
1352990755 M * aurel42 And thanks again, Bertl  :)
1352990801 M * Bertl shaggy63: only scenario where sharing an IP (or IPs) between guests makes sense is when you want to do failover from inside a guest
1352990896 M * shaggy63 oh, thanks that makes perfect sense and is a nice feature
1352991220 Q * fisted Ping timeout: 480 seconds
1352991532 M * shaggy63 btw, whoever wrote that pdf called ols2007v2 did a damn good job.
1352991780 M * Bertl thanks!
1352991957 M * Bertl planetlab/princeton has done quite a lot of testing back then ... and especially Marc did a great job regarding organization and everything ...
1352991987 M * Bertl daniel_hozac: btw, have you been in contact with planetlab recently?
1352992003 M * shaggy63 I see planet lab is moving to LXC.
1352992081 M * Bertl yes, LXC is definitely the future we envision for Linux-VServer as well ... at some point, when LXC is powerful and secure enough to completely replace the Linux-VServer kernel patches, the only thing left might be a future util-vserver :)
1352992238 M * shaggy63 I run 100s of windows and linux servers.  I value stabilty over "latest and greatest"  LXC is just too new, not mature enough.  Plus hashify is a great feature.
1352992464 M * daniel_hozac Bertl: just marc every now and then
1352992614 Q * derjohn_mob Ping timeout: 480 seconds
1352992685 M * aurel42 Bertl: with 2.6.38.8-vs2.3.0.37-rc17, normality has been restored.
1352992698 M * Bertl good! :)
1352993331 J * derjohn_mob ~aj@87.253.171.200
1352994357 Q * derjohn_mob Ping timeout: 480 seconds
1352994989 J * derjohn_mob ~aj@87.253.171.216
1352995069 J * HeL_ ~HeL@46.4.254.205
1352995087 Q * quasisane resistance.oftc.net charm.oftc.net
1352995087 Q * Hunger resistance.oftc.net charm.oftc.net
1352995087 Q * HeL resistance.oftc.net charm.oftc.net
1352995087 Q * alex3 resistance.oftc.net charm.oftc.net
1352995087 Q * wurtel_ resistance.oftc.net charm.oftc.net
1352995087 Q * grobie resistance.oftc.net charm.oftc.net
1352995087 Q * MooingLemur resistance.oftc.net charm.oftc.net
1352995087 Q * nyerup resistance.oftc.net charm.oftc.net
1352995087 Q * hparker resistance.oftc.net charm.oftc.net
1352995106 J * MooingLemur ~troy@phx-pnap.pinchaser.com
1352995169 J * quasisane ~sanep@c-24-218-184-186.hsd1.nh.comcast.net
1352995169 J * Hunger hunger@proactivesec.com
1352995169 J * grobie ~grobie@tyr.schnuckelig.eu
1352995169 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647
1352995169 J * wurtel_ ~paul@gw-office.telegraaf.net
1352995169 J * nyerup irc@jespernyerup.dk
1352995170 Q * grobie Ping timeout: 480 seconds
1352995205 J * grobie ~grobie@tyr.schnuckelig.eu
1352995212 J * alex3 ~alex@v1.fob.spline.inf.fu-berlin.de
1352995366 J * fisted ~fisted@p57A5707A.dip.t-dialin.net
1352995801 M * Ghislain hello there, just checking, can we restore vroot on a live guest when /dev/* has been erased ?
1352995897 M * Bertl yes, you can simply copy it from the host 
1352995987 M * Ghislain i do a vnamespce -e guest -- cp -apf ...  but quota still fail to see the disk 
1352996030 M * Ghislain quotacheck: error (22) while opening /dev/root, dam it ! ;p
1352996050 M * Bertl :)
1352996133 Q * BenG Quit: I Leave
1352999024 J * bonbons ~bonbons@2001:960:7ab:0:b013:8ee:8e60:55e0
1352999057 M * Ghislain i hate quota !
1352999396 Q * fisted Remote host closed the connection
1353000010 M * Ghislain how would you debug a vroot issue, is there a way to have some clue ? :)
1353000031 M * Bertl well, /dev/root exists now inside the guest?
1353000056 M * Bertl what device is it? block? what major/minor?
1353001287 M * Ghislain yes i cpied /dev/vroot0 in it as /dev/root
1353001976 M * Bertl okay, is vroot0 configured properly?
1353002043 M * Bertl in case of doubt, unset and reconfigure
1353002496 J * thierryp ~thierry@LNeuilly-152-21-8-169.w193-253.abo.wanadoo.fr
1353002708 Q * Chlorek Quit: -
1353003008 Q * derjohn_mob Ping timeout: 480 seconds
1353003127 J * Chlorek chlorek@chlorek.com
1353003535 M * Ghislain i done vrsetup -r multiple time then restarted the config, i also rmmod vroot and modprobe vroot 
1353003538 M * Ghislain will try again
1353003558 M * Ghislain must have missed something
1353004494 Q * ensc|w Remote host closed the connection
1353004504 J * ensc|w ~ensc@www.sigma-chemnitz.de
1353007022 Q * thierryp Remote host closed the connection
1353007425 Q * clopez Read error: Operation timed out
1353008095 M * Bertl off for a nap .. bbl
1353008101 N * Bertl Bertl_zZ
1353010194 Q * Ghislain Quit: Leaving.
1353010225 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg
1353011997 J * fisted ~fisted@xdsl-87-78-16-108.netcologne.de
1353012343 Q * fisted Remote host closed the connection
1353012478 J * fisted ~fisted@xdsl-87-78-16-108.netcologne.de
1353012727 J * thierryp ~thierry@LNeuilly-152-21-8-169.w193-253.abo.wanadoo.fr
1353013659 Q * thierryp Remote host closed the connection
1353013852 J * thierryp ~thierry@LNeuilly-152-21-8-169.w193-253.abo.wanadoo.fr
1353013879 Q * thierryp Remote host closed the connection
1353014149 Q * hijacker_ Quit: Leaving
1353014440 M * aurel42 Since "vserver $name build" doesn't create .defaults/cachebase/$name, should I? Or is that a historical artefact?
1353014491 M * aurel42 I seem to have a dangling symlink "cache" in all my vserver dirs. No idea what I'm missing.
1353015622 N * Bertl_zZ Bertl
1353015627 M * Bertl back now ...
1353015693 M * Bertl aurel42: that's normal if you do not have set /etc/vservers/.defaults/cachebase
1353015732 M * aurel42 Oh, cachebase is set up, it points to /var/cache/vservers, which exists.
1353015772 M * aurel42 But "vserver ... build" neglects to put a cache directory for new guests there.
1353015794 M * aurel42 ...if that's how it's supposed to work.
1353015818 M * aurel42 Can I just have puppet take care of creating those directories and reap the benefits of caching?
1353016018 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f
1353016529 Q * bonbons Quit: Leaving
1353016898 J * thierryp ~thierry@LNeuilly-152-21-8-169.w193-253.abo.wanadoo.fr
1353017653 J * clopez ~clopez@242.17.60.213.dynamic.mundo-r.com
1353017776 Q * thierryp Remote host closed the connection
1353017870 Q * clopez 
1353017899 J * clopez ~clopez@242.17.60.213.dynamic.mundo-r.com
1353018598 J * thierryp ~thierry@LNeuilly-152-21-8-169.w193-253.abo.wanadoo.fr
1353018999 Q * thierryp Remote host closed the connection
1353019082 J * thierryp ~thierry@LNeuilly-152-21-8-169.w193-253.abo.wanadoo.fr
1353019886 Q * theocrite Ping timeout: 480 seconds
1353019988 Q * thierryp Remote host closed the connection
1353020195 J * thierryp ~thierry@LNeuilly-152-21-8-169.w193-253.abo.wanadoo.fr
1353020400 Q * fisted Remote host closed the connection
1353020461 J * fisted ~fisted@xdsl-84-44-146-126.netcologne.de
1353021010 J * Ghislain ~aqueos@adsl1.aqueos.com
1353021367 Q * thierryp Remote host closed the connection
1353021787 J * theocrit1 ~Hubert@kim.theocrite.org
1353022477 Q * Ghislain Quit: Leaving.
1353023067 J * derjohn_mob ~aj@d142068.adsl.hansenet.de