1247011426 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1247012943 J * docelic ~docelic@78.134.202.119
1247013167 J * dowdle_ ~dowdle@97-121-204-120.blng.qwest.net
1247013396 Q * dowdle Ping timeout: 480 seconds
1247015562 J * imcsk8 ~ichavero@189.155.83.205
1247016391 M * Bertl off to bed now .. have a good one everyone!
1247016397 N * Bertl Bertl_zZ
1247016450 Q * urbi Read error: Connection reset by peer
1247016567 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1247018196 Q * imcsk8 Quit: This computer has gone to sleep
1247020715 J * imcsk8 ~ichavero@189.155.83.205
1247021451 Q * dowdle_ Remote host closed the connection
1247022035 J * saulus_ ~saulus@d003070.adsl.hansenet.de
1247022442 Q * SauLus Ping timeout: 480 seconds
1247022450 N * saulus_ SauLus
1247025944 Q * imcsk8 Quit: This computer has gone to sleep
1247027170 J * balbir_ ~balbir@122.172.27.254
1247029965 J * ghislainocfs2 ~Ghislain@adsl2.aqueos.com
1247033013 J * dna ~dna@128-205-103-86.dynamic.dsl.tng.de
1247033419 M * allquixotic I'm on a quest to eliminate services that bind to 0.0.0.0:X on my host, so that the guests have maximum flexibility. The only ones left according to netstat -pant are rpcbind on 111 and rpc.statd on 44372. Do these guys have config files where I can change their listen address, or do I have to somehow hack their invocation to chbind them?
1247034101 J * gate_keeper_ ~gk@62.162.38.90
1247034325 J * ghislainocfs21 ~Ghislain@adsl2.aqueos.com
1247034395 Q * Shuro Read error: Connection reset by peer
1247034521 M * gate_keeper_ hey computer geeks, how's goin .. ?
1247034523 M * gate_keeper_ :)
1247034542 M * gate_keeper_ is someone still using util-vserver versions older then 0.30
1247034546 M * gate_keeper_ 0.27/28?
1247034557 M * gate_keeper_ i need the /usr/bin/vdlimit file ..
1247034650 Q * ghislainocfs2 Ping timeout: 480 seconds
1247034793 M * gate_keeper_ thanks in advance!
1247036450 M * _Shiva__ gate_keeper_: any chance to build it from source? http://www.13thfloor.at/~ensc/util-vserver/files/stable/
1247036492 M * gate_keeper_ _Shiva__, no luck
1247036499 M * gate_keeper_ i'm running into errors all the time
1247036563 M * _Shiva__ no doubt ;-)  the sources are 4 years plus old...
1247036579 M * _Shiva__ . o 0 ( 5 actually )
1247036669 M * _Shiva__ gate_keeper_: additionally, i think you'll need a static linked version after all and i doubt that anyone who might have a binary laying around has a static linked one
1247036741 M * _Shiva__ gate_keeper_: besides - are the utils not backward compatible?
1247036904 J * ktwilight__ ~keliew@38.168-247-81.adsl-dyn.isp.belgacom.be
1247037210 Q * ktwilight_ Ping timeout: 480 seconds
1247037212 Q * hijacker Read error: Connection reset by peer
1247037258 M * gate_keeper_ centos 5.3, gcc-4.1.2
1247037269 M * gate_keeper_ when i try to build rpm from util-vserver.spec
1247037272 M * gate_keeper_ it says
1247037273 M * gate_keeper_ error: Legacy syntax is unsupported: copyright
1247037279 M * gate_keeper_ error: line 8: Unknown tag: Copyright:	GPL
1247037301 M * gate_keeper_ i've tried also with replacement of Copyright with Licence ..but no success
1247037358 M * gate_keeper_ rpmbuild is 4.4 ver.
1247038259 M * _Shiva__ sorry - no clue with wierd package managers :-)
1247038662 J * davidkarban ~david@193.85.217.71
1247039240 M * gate_keeper_ :)
1247040076 J * BWare ~itsme@ip-80-113-1-198.ip.prioritytelecom.net
1247040511 Q * pmenier_off Quit: Konversation terminated!
1247041360 J * Pazzo ~ugelt@reserved-225136.rol.raiffeisen.net
1247041397 J * BenG ~bengreen@94-169-110-10.cable.ubr22.aztw.blueyonder.co.uk
1247041587 J * pmenier ~pme@LNeuilly-152-22-8-5.w193-251.abo.wanadoo.fr
1247041742 Q * ktwilight__ Read error: Connection reset by peer
1247041780 J * ktwilight__ ~keliew@156.7-241-81.adsl-dyn.isp.belgacom.be
1247042185 M * daniel_hozac gate_keeper_: why aren't you using 0.30.216-preX?
1247042851 Q * BenG Quit: I Leave
1247043263 J * eyck N1FXINA3@nat06.nowanet.pl
1247044040 Q * cehteh Ping timeout: 480 seconds
1247045144 J * friendly ~friendly@ppp118-208-140-89.lns10.mel4.internode.on.net
1247045144 Q * allquixotic Read error: Connection reset by peer
1247045216 J * allquixotic ~sean@pool-70-17-238-89.balt.east.verizon.net
1247045385 Q * eyck Read error: No route to host
1247045632 J * eyck JIafEf0c@nat06.nowanet.pl
1247046056 J * esa bip@62.123.67.214
1247046126 Q * friendly Read error: Connection reset by peer
1247046206 Q * kir Read error: Connection reset by peer
1247046217 M * allquixotic Hmm, weird... I have two distinct sshd instances running on different IPs (one for host, one for guest).... the host is indeed _only_ listening on the host IP and not the guest IP... I'm able to update the passwd for root and regular users in the guest... but when trying to ssh into the guest, after I enter my password the server closes the connection. My shell is set to /bin/bash which exists and is executable, so I'm not sure
1247046217 M * allquixotic  why it just gives up.
1247046532 M * daniel_hozac what do the logs say?
1247046541 Q * esa Ping timeout: 480 seconds
1247046593 J * esa bip@62.123.79.222
1247046684 M * BWare is the user locked 
1247046686 M * BWare ?
1247046708 M * allquixotic BWare: I did a usermod -U on them, so they should be unlocked
1247046740 M * allquixotic daniel_hozac: I found this interesting stuff in /var/log/secure, which is repeated each time I try to ssh in, so this must be related to the problem. But it's fairly cryptic: http://pastebin.com/m4de2b57e
1247046774 M * daniel_hozac so, remove pam_loginuid from /etc/pam.d/sshd
1247046801 M * BWare :)
1247046883 M * allquixotic daniel_hozac: Interesting solution - it works!!
1247046924 M * allquixotic I hope I just didn't make my system extremely insecure... but it looks like PAM will still check your password so I guess that's good enough
1247046947 M * allquixotic it's a guest with low-value info anyway, probably more secure than doing that on my host
1247046993 M * BWare or just skip pam altogether if you don't need something fancy
1247047000 M * daniel_hozac unless you're using kernel auditing or SELinux, you won't know the difference.
1247047011 M * BWare closes another potential security hole 
1247047046 M * allquixotic ah, I disabled SELinux because it was conflicting with vserver somehow. I was getting selinux errors when trying to run passwd inside a guest.
1247047069 J * kir ~kir@swsoft-msk-nat.sw.ru
1247047973 J * thierryp ~thierry@zanzibar.inria.fr
1247048031 J * mxs_ mxs@p4FCCAB3E.dip.t-dialin.net
1247048252 Q * eyck Read error: Connection reset by peer
1247048332 Q * mxs Ping timeout: 480 seconds
1247050664 M * Val micah: bug "sshd[...] error writing /proc/self/oom_adj: Permission denied" #506949 & #507006 is not fixed for lenny (linux-image-2.6.26-2-vserver-amd64 2.6.26-17, util-vserver 0.30.216~r2772-6)
1247050998 Q * _are_ Quit: bbl
1247051541 M * Hollow_ daniel_hozac: i'm running the latest snapshot of util-vserver (2841), and cannot enter guests anymore (# vserver serv1 enter
1247051544 M * Hollow_ vcontext: pivot_root(): Invalid argument
1247051545 M * Hollow_ any hints?
1247051558 N * Hollow_ Hollow
1247051914 M * Hollow daniel_hozac: i found something in the irc logs, so basically, pivot_root is broken, and i shouldn't use the current snapshot
1247051917 M * Hollow ?
1247052149 Q * thierryp Quit: ciao folks
1247053119 N * Bertl_zZ Bertl
1247053214 M * _Shiva__ Hollow: what's your current `uname -r`? 
1247053279 M * Bertl morning folks!
1247053292 M * fback morning Bertl!
1247053308 M * _Shiva__ Hollow: i remember having this when running some 2.6.27 or 2.6.28 kernel using the latets tools... rebooting into a 2.6.29.x solved it..
1247053398 M * Bertl allquixotic: it doesn't conflict, but it needs to be setup properly to handle guests (i.e. the default setup a distro might provide is usually not sufficient :)
1247053478 M * _Shiva__ ("some 2.6.27 or 2.6.28" meaning: not a recent patchlevel regarding Kernel + vserver-patch .. like having an uptime for about 140 days..)
1247053511 M * fback Bertl: I'm preparing to upgrade some important server here, is 2.6.27 still suggested, as this will be long-maintained kernel version?
1247053544 M * allquixotic Bertl: I'm not knowledgable on the internals of the process used to build new vservers (e.g. from yum), but if it is scriptable, it might be worthwhile for someone who has time (maybe even me) to figure out certain things that should be touched in the guest environment to make the guest's filesystem state more amenable to running as a vserver guest. We could then script this during the build process on a per-distro, per-version
1247053544 M * allquixotic  basis, to eliminate user headache
1247053684 M * allquixotic Bertl: We would have some kind of extensible functionality that "knows" certain things about Distro X, Release Y are broken as a guest from the start, and clean up these issues as we discover them. Tripping on them by accident is only fun if I can prevent the same happening to the next guy. :)
1247053958 N * allquixotic allquix_brb
1247054185 M * Hollow _Shiva__: 2.6.28-vs2.3.0.36.4-gentoo
1247054240 M * Hollow _Shiva__: i see, thanks for the info
1247054265 J * doener ~doener@i59F5AC52.versanet.de
1247054366 M * _Shiva__ Hollow: try (your own ;-) =sys-kernel/vserver-sources-2.3.0.36.14 *g*
1247054382 M * _Shiva__ 2.3.0.36.14 is 2.6.29 based?
1247054598 M * _Shiva__ Hollow: hmm .. =sys-kernel/gentoo-sources is stable @2.6.29-r5 ... so maybe vserver-sources shoulg go stable (or at least testing keyworded) w/i the 2.6.29.x, too? rather than 2.6.28?
1247054899 M * micah Val: thats is a ssh bug
1247054944 M * micah Val: either upgrade to the ssh package in testing or edit /etc/default/ssh and change SSHD_OOM_ADJUST=-17 to be "unset SSHD_OOM_ADJUST=-17"
1247055208 M * _Shiva__ Hollow: iirc this patch fixes the issue and was added to vs2.3.0.36.9 : http://vserver.13thfloor.at/ExperimentalT/delta-pivot-fix01.diff
1247055228 M * _Shiva__ Hollow: so it really might be your vs2.3.0.36.*4*
1247056113 J * ktwilight_ ~keliew@91.178.155.239
1247056310 Q * pmenier Ping timeout: 480 seconds
1247056511 J * docelic_ ~docelic@78.134.197.78
1247056555 Q * ktwilight__ Ping timeout: 480 seconds
1247056911 Q * docelic Ping timeout: 480 seconds
1247056922 M * Hollow _Shiva__: ok, have to test it locally, i've just hit this problem because my puppet modules keyword all util-vserver ebuilds and update them automatically, and most machines i have are 2.2.0.7 or 2.3.0.36.4 :)
1247058761 J * `6og ~kgoetz@ppp121-45-226-5.lns10.adl6.internode.on.net
1247058773 J * eyck 1mUxgtnU@nat06.nowanet.pl
1247058828 J * thierryp ~thierry@zanzibar.inria.fr
1247059839 Q * eyck Remote host closed the connection
1247059936 J * nenolod_ nenolod@petrie.dereferenced.org
1247060042 Q * nenolod_ Read error: Connection reset by peer
1247060568 J * eyck ~eyck@nat05.nowanet.pl
1247062729 J * dowdle ~dowdle@97-121-204-120.blng.qwest.net
1247062767 Q * bernroth Remote host closed the connection
1247063293 P * kir Leaving.
1247063446 Q * gate_keeper_ Ping timeout: 480 seconds
1247063836 Q * nenolod Quit: my eyes cannot compute this misery.
1247063854 J * nenolod nenolod@petrie.dereferenced.org
1247064109 J * gate_keeper_ ~gk@62.162.38.90
1247064142 J * Floops[w] ~baihu@205.214.201.176
1247064388 J * daenney_ ~daenney@daenney.net
1247064396 J * tam_ ~tam@gw.nettam.com
1247064418 Q * nenolod resistance.oftc.net weber.oftc.net
1247064418 Q * allquix_brb resistance.oftc.net weber.oftc.net
1247064418 Q * FireEgl resistance.oftc.net weber.oftc.net
1247064418 Q * Floops[w]2 resistance.oftc.net weber.oftc.net
1247064418 Q * daenney resistance.oftc.net weber.oftc.net
1247064418 Q * tam resistance.oftc.net weber.oftc.net
1247064418 Q * infowolfe resistance.oftc.net weber.oftc.net
1247064419 N * daenney_ daenney
1247064593 J * infowolfe ~infowolfe@c-76-105-242-186.hsd1.or.comcast.net
1247064722 J * nenolod nenolod@petrie.dereferenced.org
1247064722 J * allquix_brb ~sean@pool-70-17-238-89.balt.east.verizon.net
1247064722 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1247064722 J * Floops[w]2 ~baihu@205.214.201.176
1247064722 J * tam ~tam@gw.nettam.com
1247064960 Q * FireEgl Ping timeout: 480 seconds
1247064960 Q * Floops[w]2 Ping timeout: 480 seconds
1247064960 Q * tam Ping timeout: 480 seconds
1247065100 Q * nenolod Remote host closed the connection
1247065107 J * nenolod nenolod@petrie.dereferenced.org
1247065134 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1247065199 J * imcsk8 ~ichavero@189.155.83.205
1247065641 J * jpic ~jpic@chocolatpistache.com
1247065703 M * jpic hi, i've copied stuff like .bashrc to /vservers/myvps/root, and it doesn't seem to load with `vserver myvps enter`, it only loads if i do `su` once i'm in. Any idea why that happens?
1247065746 M * Bertl because 'enter' is a backdoor, and not a 'login'?
1247065903 J * cehteh ~ct@pipapo.org
1247065932 M * Bertl setup sshd in the guest, logon via ssh and your scripts will be executed as usual
1247065940 M * Bertl off for now .. bbl
1247065945 N * Bertl Bertl_oO
1247066036 Q * gate_keeper_ Remote host closed the connection
1247066130 Q * esa Quit: Coyote finally caught me
1247066614 Q * imcsk8 Quit: This computer has gone to sleep
1247067747 J * pmenier ~pme@LNeuilly-152-22-8-5.w193-251.abo.wanadoo.fr
1247068463 Q * vk5foss Read error: Connection reset by peer
1247068474 J * Kamping_Kaiser kgoetz@203.209.167.143
1247068774 M * nkukard hrmmmm, would a vserver have any problem using O_DIRECT?
1247068802 M * daniel_hozac no.
1247069249 J * derjohn_mob ~aj@c189180.adsl.hansenet.de
1247069866 Q * Kamping_Kaiser Ping timeout: 480 seconds
1247070030 J * doener_ ~doener@i59F5BF88.versanet.de
1247070131 Q * doener Ping timeout: 480 seconds
1247070134 J * Kamping_Kaiser kgoetz@203.209.167.143
1247070376 N * DoberMann[ZZZzzz] DoberMann[PullA]
1247070651 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d
1247071276 Q * thierryp Quit: ciao folks
1247071839 M * jpic oh ok, thanks
1247072098 J * jklblerf jkl@c-67-172-157-52.hsd1.co.comcast.net
1247072127 M * jklblerf hello, I am having some trouble killing two dead vcontext prcoesses. 
1247072155 M * jklblerf I try something like: vkill -s 9 --xid nameofserver 25949
1247072173 M * jklblerf but the process remains and I cannot stop/restart the vserver
1247072189 M * daniel_hozac what state are the processes in?
1247072206 M * jklblerf "D"
1247072225 M * daniel_hozac so they're stuck in kernel space. did the kernel oops?
1247072257 M * jklblerf can't tell, I'm not at the console, that may be recorded by syslog however, I will check
1247072271 M * daniel_hozac run dmesg
1247072348 N * pmenier pmenier_off
1247072368 M * jklblerf no oops, but there were some messages about "Out of Memory" problems
1247072426 M * jklblerf These seem to be related to another vserver though
1247072628 M * fback daniel_hozac: speaking of oom, oomkiller is aware of vserver causing memory "shortage" or it will kill random task?
1247072786 M * Bertl_oO jklblerf: what kernel?
1247072812 M * Bertl_oO fback: OOM killing is never random
1247072831 M * jklblerf Bertl_oO: 2.6.18-6-vserver-amd64
1247072847 M * jklblerf (debian etch)
1247072873 M * Bertl_oO so I would try with a more recent and preferably mainline kernel
1247072899 M * daniel_hozac that kernel is known to be broken in a lot of ways.
1247072925 M * jklblerf So, you're suggesting an upgrade to Lenny then, or that I build my own kernel
1247072980 M * daniel_hozac the lenny kernel isn't any better.
1247072993 M * jklblerf haha, fair enough
1247073037 M * jklblerf In the immediate situation is my only option to reboot the host to clear this up?
1247073094 M * Bertl_oO no, you can 'ignore' those processes, and start guests with a different context id
1247073127 M * jklblerf ah, so just change the context id of the guest that's broken to something different and restart it then
1247073128 M * Bertl_oO but assuming that they are stuck in a kernel operation, which will never complete, you won't be able to get rid of them
1247073160 M * Bertl_oO (without a kernel restart, that is)
1247073179 J * hparker ~hparker@2001:470:1f0f:32c:290:96ff:fe50:40fa
1247073213 M * julius (linux needs the ability to terminate kernel threads!)
1247073252 M * Bertl_oO well, after killing off all kernel threads, you'll still have those userspace processes stuck in kernel space :)
1247073292 M * morrigan daniel_hozac: thanks for fixing the util-vserver so that it builds under mandriva :)
1247073399 M * jklblerf Bertl_oO: what is the procedure for starting a guest under a different context id? 
1247073447 M * Bertl_oO you simply change the context id in the config
1247073478 M * jklblerf ah, yeah that's what I tried, then a 'vserver name start'. It simply says it's still running
1247073515 M * Bertl_oO then you have a (back) reference in /var/run/vserver*
1247073539 Q * Kamping_Kaiser Ping timeout: 480 seconds
1247073617 M * jklblerf ok, thanks - got it running again.
1247073809 J * Kamping_Kaiser kgoetz@203.209.167.143
1247074265 J * gate_keeper_ ~gk@92.53.16.197
1247074416 Q * davidkarban Quit: Ex-Chat
1247074549 J * vk5foss kgoetz@203.209.167.143
1247074571 Q * Kamping_Kaiser Read error: Connection reset by peer
1247075302 Q * derjohn_mob Remote host closed the connection
1247076679 J * imcsk8 ~ichavero@189.155.83.205
1247077273 Q * vk5foss Ping timeout: 480 seconds
1247077731 J * ktwilight__ ~keliew@202.6-241-81.adsl-dyn.isp.belgacom.be
1247077768 J * Kmos ~gothicx@kmos.user.oftc.net
1247077809 Q * Piet Remote host closed the connection
1247077856 J * Piet ~piet@659AAAZ3S.tor-irc.dnsbl.oftc.net
1247077995 J * ViRUS ~mp@p579B4880.dip.t-dialin.net
1247078156 Q * ktwilight_ Ping timeout: 480 seconds
1247078427 Q * doener_ Quit: leaving
1247078546 J * miguelzinho ~miguel@quake.ic.unicamp.br
1247079038 Q * eyck Remote host closed the connection
1247080096 J * ktwilight_ ~keliew@64.13-241-81.adsl-dyn.isp.belgacom.be
1247080460 Q * ktwilight__ Ping timeout: 480 seconds
1247080886 Q * imcsk8 Quit: This computer has gone to sleep
1247081677 J * eyck m7tOPwRr@nat06.nowanet.pl
1247082932 J * thierryp ~thierry@home.parmentelat.net
1247083235 Q * thierryp Quit: ciao folks
1247083478 M * Bertl_oO off to bed now ... have a good one everyone!
1247083483 N * Bertl_oO Bertl_zZ
1247083684 J * imcsk8 ~ichavero@148.229.1.11
1247084540 J * doener ~doener@i59F561D8.versanet.de
1247085146 Q * bonbons Quit: Leaving
1247085990 Q * hparker Quit: Read error: 104 (Peer reset by connection)
1247088631 Q * Pazzo Quit: Ex-Chat
1247090542 P * Val 
1247091064 Q * FireEgl Ping timeout: 480 seconds
1247091305 N * allquix_brb allquixotic
1247091324 N * DoberMann[PullA] DoberMann[ZZZzzz]
1247091492 M * allquixotic If I do the procedure for hashifying a guest (as described in the FAQ), does that mean that whenever I clone that guest, the clones will be COW?
1247091839 J * FireEgl FireEgl@173-16-9-10.client.mchsi.com
1247092106 Q * dna Quit: Verlassend
1247092238 Q * Kmos Quit: return unless user.signoff?
1247094266 Q * imcsk8 Quit: This computer has gone to sleep
1247094919 Q * FireEgl Ping timeout: 480 seconds
1247095406 J * Kamping_Kaiser kgoetz@203.209.167.143
1247095771 J * FireEgl FireEgl@Sebastian.Atlantica.US.TO
1247095880 Q * FireEgl 
1247096993 J * thierryp ~thierry@home.parmentelat.net
1247097051 Q * thierryp