1101860737 Q * tchan uranium.oftc.net arion.oftc.net
1101860737 Q * brc uranium.oftc.net arion.oftc.net
1101860737 Q * UFOczek uranium.oftc.net arion.oftc.net
1101860737 Q * eyck uranium.oftc.net arion.oftc.net
1101860805 J * tchan tchan@c-24-13-81-164.client.comcast.net
1101860805 J * brc bruce@201008090252.user.veloxzone.com.br
1101860805 J * UFOczek ufoczek@hood.openbug.net
1101860805 J * eyck eyck@81.219.64.71
1101862692 Q * brc uranium.oftc.net arion.oftc.net
1101862692 Q * tchan uranium.oftc.net arion.oftc.net
1101862692 Q * eyck uranium.oftc.net arion.oftc.net
1101862692 Q * UFOczek uranium.oftc.net arion.oftc.net
1101862763 J * tchan tchan@c-24-13-81-164.client.comcast.net
1101862763 J * brc bruce@201008090252.user.veloxzone.com.br
1101862763 J * UFOczek ufoczek@hood.openbug.net
1101862763 J * eyck eyck@81.219.64.71
1101863340 Q * tchan Remote host closed the connection
1101865291 J * dsanta santa@c68.190.156.105.roc.mn.charter.com
1101866051 J * tchan tchan@c-24-13-81-164.client.comcast.net
1101866850 Q * tchan Ping timeout: 480 seconds
1101866863 J * tchan tchan@c-24-13-81-164.client.comcast.net
1101876568 J * _no_x vps@c150153.adsl.hansenet.de
1101876670 Q * no_x Ping timeout: 480 seconds
1101883931 J * anonymous-coward nwalsh@shaggy.internode.com.au
1101886365 Q * sannes Read error: Connection reset by peer
1101887483 J * BWare bware@212.26.196.41
1101888594 N * Bertl_zZ Bertl
1101888604 M * Bertl morning folks!
1101889210 M * Bertl okay, back later ...
1101889215 N * Bertl Bertl_oO
1101893330 J * sannes ace@home.skarby.no
1101893597 J * rs rs@ice.aspic.com
1101893607 M * rs hi dudes
1101893961 N * Val_away Val
1101893967 M * Val hi
1101893973 M * Val chand : here ?
1101895850 N * Bertl_oO Bertl
1101895861 M * Bertl greetings folks!
1101896504 M * lilo hey Bertl 
1101896523 M * Bertl hey lilo, how are you?
1101896674 M * Zoiah Bertl: hiho :)
1101896769 M * Bertl hey Zoiah! everything fine?
1101896792 M * Zoiah Bertl: not really, I really need to migrate to the new configuration style because the brokenness of the legacy-support is getting on my nerves. :)
1101896815 M * Bertl sorry about that, but maybe you can fix that easily yourself?
1101896833 M * Bertl IIRC, we pretty much tracked it down ...
1101896834 M * Zoiah I also just noticed the vserver-stat doesn't show the name of the vserver if they're legacy.
1101896839 M * Zoiah Ahh, I missed that. :)
1101896850 M * Bertl let me check the logs ... sec
1101896866 M * Zoiah I saw the hunting in the logs, but missed the catch. :)
1101896916 M * Loki|muh_ i like the new configuration layout :)
1101896958 M * Bertl http://irc.13thfloor.at/LOG/LOG_2004-11-23.txt
1101897003 M * Bertl 1101212338 M * Doener that leaves caps unchanged if initpid was already set, with 2.4 + stable tools
1101897033 M * Bertl (and of course the lines before)
1101897090 M * Bertl Zoiah: so as I see it you have two options: a) you remove the security check from the kernel, everything should work fine ...
1101897110 M * Bertl or b) lower the caps (or the relevant cap that is) _after_ the second call ...
1101897127 N * Doener_zZz Doener
1101897136 M * Doener morning!
1101897137 M * Bertl morning Doener!
1101897188 M * Zoiah I think changing the utils is a bit less scary than changing the kernel. :)
1101897227 J * Duckx duckx@195.75.27.158
1101897248 M * Bertl Zoiah: depends on the perspective :)
1101897256 M * Zoiah Bertl: true. :)
1101897257 M * Bertl welcome Duckx!
1101897666 N * _no_x no_x
1101898090 M * Bertl wb no_x!
1101898103 M * no_x thanks bertl
1101898297 M * Zoiah The evil code is confusing me. :)
1101898319 M * Doener Zoiah: want some evil quick fix?
1101898327 M * Zoiah Doener: sir, yes, sir. :)
1101898906 M * Loki|muh_ ensc: could you mention in the flowerpage, that hostname and domainname are deprecated in favour of uts/nodename and uts/domainname?
1101898945 M * Doener Zoiah: http://doener.homeip.net/doener/vserver/evil-Zoiah-fix.diff
1101898995 M * Zoiah Hmm... :)
1101898995 M * Doener i expect no security problems, since it only restores 1.9.2 behaviour for that single syscall
1101899030 Q * TheSeer Ping timeout: 480 seconds
1101899042 J * TheSeer theseer@border.office.salesemotion.net
1101899346 M * Duckx Hy Bertl
1101899355 M * Duckx Me is fighting with my suse )
1101899417 M * Loki|muh_ it is funny like hell? ;)
1101899502 M * Bertl last known good SuSE (for me) was 6.3
1101899640 M * no_x Bertl: was my last too , but can´t remember it beeing good ... switching to mandrake all probs where gone (:
1101899742 M * Loki|muh_ for me it was switching to debian ;)
1101899883 M * Bertl no_x: didn't know Mandrake at that time ...
1101899911 M * Bertl switched over to debian, was lost, moved to redhat ... then Mandrake ...
1101899969 M * no_x hehe so it is proofed to be good having such much different  distros  *g*
1101900043 M * no_x I droped Mandrake when woody released (was it 8.2 mandrake ??)
1101902234 M * Bertl okay, off for lunch now ... back later ...
1101902238 N * Bertl Bertl_oO
1101902264 J * DaGucci mragucci@pD95F2854.dip.t-dialin.net
1101902275 M * DaGucci hi @all
1101902371 M * DaGucci just a simple question: my vservers (stable-branch) don't mount the mountpoints I specified in /etc/fstab. Is there another way to mount them at boottime (maybe I missed something)?
1101903257 M * BWare try a bind mount from the vserver startup script
1101903552 Q * DaGucci Quit: Lost terminal
1101903976 J * axu_ axu@62.116.66.2
1101903980 M * axu_ hi :)
1101904010 M * axu_ bertl: thanks i think that fixed it :) ...by now i should have understood ulimit :(
1101904094 N * Bertl_oO Bertl
1101904123 M * axu_ is tehre tool to do a lsof -i on all context ?
1101904148 M * Bertl hi axu_! not that I know of
1101904150 M * axu_ i am searching for a vserver the binds to a port it shouldnt
1101904164 M * axu_ Bertl: well, then, some work for me :)
1101904164 M * daniel_hozac wouldn't chcontext --xid 1 lsof -i work?
1101904164 M * Bertl but you could try with chcontext --ctx 1 lsof 
1101904265 M * axu_ looks nice :)
1101904540 M * axu_ wie legt ma nochmal nen 2. rootuser an ?
1101904547 M * axu_ sorry, wrong # ;)
1101904556 M * Bertl np
1101904792 M * Psy0rz when i try to connect to my vserver, i endup connecting the real server
1101904808 M * Psy0rz services within the vserver say they can't bind to the port 
1101904814 M * Loki|muh_ Psy0rz: tell your host sshd to bind to only one ip
1101904819 M * Psy0rz ooh
1101904820 M * Psy0rz ah
1101904824 M * Loki|muh_ same with the other services ;)
1101904825 M * Psy0rz doh!
1101904878 M * Psy0rz thx
1101904885 M * Psy0rz it
1101904888 M * Loki|muh_ np :)
1101904890 M * Psy0rz it's all logical and clean :)
1101905227 M * axu_ hmm, strange, found no process in no context that ocupies officialip:443 but trying to start a apache-ssl gives me a "Address already in use: make_sock: could not bind to address officialip port 443"
1101905245 M * axu_ i check it again :)
1101905638 M * axu_ typical axu mistake :) 
1101907044 M * Bertl hmm ... seems I got disconnected ...
1101907272 M * axu_ welcome back :)
1101907412 M * Bertl tx, everything resolved as it looks ...
1101907930 J * [HvD] Miranda@chello212017106212.graz.surfer.at
1101907942 M * Bertl welcome [HvD]!
1101907945 M * [HvD] ^hi
1101907962 M * [HvD] any idea what this is: 
1101907963 M * [HvD] write(2, "telnet: connect to address 10.49"..., 56telnet: connect to address 10.49.3.12: Invalid argument
1101907970 M * [HvD] connect(3, {sa_family=AF_INET, sin_port=htons(25), sin_addr=inet_addr("10.49.3.12")}, 16) = -1 EINVAL (Invalid argument)
1101907995 M * Bertl 2.6 kernel?
1101908004 M * [HvD] removed policy routing, interface alias is setup ok, vserver-alpha utils, 2.6.9-vs1.9.3
1101908065 M * [HvD] vserver is rh9
1101908072 M * [HvD] debian seems to work fine .. *duck*
1101908089 M * [HvD] 10.49.3.12 is the alias setup for vserver .. 
1101908116 M * Bertl you are trying to telnet to yourself?
1101908119 M * [HvD] yep
1101908136 M * Bertl could you upload the complete strace of that somewhere?
1101908149 M * [HvD] but even outside the vserver it does not work (Debian master)
1101908159 M * [HvD] must be a config problem huh .. 
1101908205 M * [HvD] can email strace output .
1101908216 M * Bertl hmm, let's start with something simpler first
1101908224 M * Bertl what about tracepath to that address?
1101908241 M * [HvD] from where
1101908246 M * Bertl from the host
1101908261 M * [HvD] btw ..from another host it looks fine ..
1101908291 M * [HvD]  1:  send failed
1101908293 M * [HvD] mhh ..
1101908299 M * [HvD] this is really strange ..
1101908312 M * Bertl looks like some security stuff in the way?
1101908316 M * Bertl check your iptables
1101908329 M * [HvD] no rules 
1101908445 M * Bertl hmm .. okay send me the strace (-fF of both)
1101908474 M * [HvD] mhh i think there is some routing problem .. but all looks fine ..
1101908498 M * Bertl attach the 'ip route ls' output too
1101908964 M * [HvD] on the way ..
1101909030 M * Bertl bad news ... see your email ;)
1101910684 Q * ntrs_ Read error: Connection reset by peer
1101913402 J * tchan___ tchan@c-24-13-81-164.client.comcast.net
1101913510 Q * tchan Ping timeout: 480 seconds
1101914629 N * tchan___ tchan
1101914639 M * Bertl wb tchan!
1101914653 M * tchan hi Bertl
1101914805 Q * infowolfe Ping timeout: 480 seconds
1101915512 J * shuri shuri@dsl.speedline209.226.electronicbox.net
1101916140 Q * shuri Remote host closed the connection
1101918715 Q * grecea Read error: Connection reset by peer
1101918767 J * grecea grecea@h-195-22-237-74.mdl.net
1101918774 M * Bertl wb grecea!
1101919206 M * axu_ bye folks :) by bertl
1101919209 P * axu_ Client exiting
1101920937 J * infowolfe infowolfe@infowolfe.vps.xhcl.net
1101920946 M * infowolfe Bertl: i have something for you
1101920978 M * Bertl yeah? an early christmas present?
1101920988 M * Bertl welcome btw!
1101920991 M * infowolfe sadly, a kernel panic
1101921007 M * infowolfe i'll have a link shortly, have to rotate the pic first
1101921131 M * Bertl program instruction counter?
1101921548 M * infowolfe http://gallery.xhcl.net/main.php/view/foto_20_.jpg
1101921550 M * infowolfe there's the pic
1101921554 M * infowolfe picture
1101921555 M * infowolfe lol
1101921557 M * infowolfe sorry
1101921734 M * infowolfe Bertl: not sure if that would help you any, not sure how exactly it was produced, but the machine died unexpectedly after 3 weeks uptime...
1101921767 M * Bertl hmm, ever encountered one which died expectedly?
1101921775 M * infowolfe lol, of course i have
1101921789 M * infowolfe do_brk... do_mremap, umm... yes... i have
1101921790 M * infowolfe lol
1101921798 M * Bertl okay, you will be happy to hear that this issue has been fixed in 2.4.10 ;)
1101921808 M * infowolfe huh?
1101921836 M * infowolfe 2.6.10?
1101921850 M * Bertl 2.6.10-rc2 that is
1101921863 M * infowolfe what was the problem?
1101921882 M * Bertl let me see if I can dig up the relevant info from lkml ...
1101921913 M * infowolfe thanks
1101921933 M * infowolfe i'd really like to know what caused it so i can decide if i should wait until 2.6.10 is released.
1101921939 Q * Duckx Quit: Leaving
1101922022 M * Bertl rs: you around?
1101922157 M * infowolfe Bertl: skb_linearize?
1101922159 M * Bertl infowolfe: http://www.spinics.net/lists/linux-net/msg11490.html
1101922187 A * infowolfe was reading the -rc2 changelog
1101922214 M * Bertl well, rs and I where looking for the 'fix' part, but we could not find it ... 
1101922232 M * Bertl nevertheless Herbert Xu confirmed that it has been fixed in 2.6.10-rc2
1101922337 M * infowolfe so basically it's like an overflow
1101922357 M * infowolfe of the tcp stack? as soon as the counters are full the kernel punts an Oops?
1101922359 M * Bertl infowolfe: if you have the kernel source tree (with the compiled vmlinux) you could use addr2line -e vmlinux on the
1101922380 M * Bertl eip address (being c033ba4f)
1101922422 M * Bertl btw, whos galery is that?
1101922443 M * rs re
1101922448 M * Bertl wb rs!
1101922451 M * infowolfe what would be the proper way to input c033ba4f
1101922457 M * infowolfe Bertl: it's one of mine
1101922461 M * Bertl addr2line -e vmlinux c033ba4f
1101922463 M * infowolfe it's gallery2 cvs
1101922491 M * infowolfe [root@machine linux-2.6.9-vs1.9.3]# addr2line -e vmlinux c033ba4f
1101922491 M * infowolfe ??:0
1101922501 M * Bertl no debug info compiled in ...
1101922512 M * Bertl you could change just that option and recompile ...
1101922512 Q * sannes Read error: Connection reset by peer
1101922516 M * rs Bertl: you were looking for me?
1101922526 M * Bertl yep, see http://www.spinics.net/lists/linux-net/msg11490.html
1101922531 M * infowolfe alright, brb
1101922587 M * Bertl rs: wasn't that the one we where looking for?
1101922644 M * rs I don't think so
1101922664 M * Bertl okay, then sorry for disturbing you ...
1101922673 M * rs but maybe
1101922681 M * rs the panic wasn't the same one
1101922723 M * Bertl the stack backtrace isn't really relevant
1101922737 M * Bertl it happens somewhere when the retransmit kicks in
1101922761 Q * Loki|muh_ Ping timeout: 480 seconds
1101922762 M * rs http://lkml.org/lkml/2004/11/18/95
1101922831 M * rs do you think it's the same one ?
1101922864 M * Bertl hmm .. no, you are right ... let me check the other oopses ...
1101922941 J * Loki|muh loki@satanix.de
1101923254 M * infowolfe rs: your link doesn't look as close to what i experienced as the one that Bertl gave me
1101923517 M * infowolfe Bertl: should i just bite the bullet and go with .10-rc2-vs1.9.3?
1101923541 M * rs infowolfe: yeah I think so too
1101923841 M * infowolfe rs: do you suggest a .10-rc2-vs1.9.3 for now?
1101923848 Q * Hollow Remote host closed the connection
1101923854 M * rs for production purpose ?
1101923858 M * infowolfe yes.
1101923864 M * rs not really
1101923872 M * rs I only got this error (mine) once
1101923881 M * rs never got it again
1101923900 M * rs maybe .10-rc2 add more bugs than it fix :)
1101923909 M * infowolfe so do you think i can hold off until .10-stable?
1101923929 M * rs in my point of view, yes
1101923941 M * rs 2.6.9 is stable enough for me so far
1101923943 J * Hollow bene@home.xnull.de
1101924226 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101924299 Q * Hollow Remote host closed the connection
1101924329 M * infowolfe addr2line -e vmlinux c033ba4f
1101924329 M * infowolfe net/ipv4/tcp_input.c:2045
1101924335 J * Hollow bene@home.xnull.de
1101924426 P * laberwaber2333 
1101924432 Q * tchan Read error: Connection reset by peer
1101924433 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101924729 P * rollingthunder43 
1101924738 J * tchan tchan@c-24-13-81-164.client.comcast.net
1101924789 M * infowolfe rs, i think the problem with it only matters when you're doing a LOT of heavy traffic
1101924814 M * infowolfe the occasional burst we do isn't big enought of fill up the stack for a while...
1101925657 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101925690 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101925704 J * redLED redled@d51A4EFA7.kabel.telenet.be
1101925716 M * redLED howdy #vserver
1101925912 P * rollingthunder43 
1101925947 P * laberwaber2333 
1101926385 Q * redLED Read error: Connection reset by peer
1101926536 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101926753 Q * rollingthunder43 Quit: 
1101927255 J * redLED redled@d51A4EFA7.kabel.telenet.be
1101928102 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101928313 P * rollingthunder43 
1101928401 M * Bertl  well, so much for reliable routing ...
1101928415 M * Bertl okay, back later ...
1101928421 N * Bertl Bertl_oO
1101928694 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101928780 Q * infowolfe Remote host closed the connection
1101929068 P * laberwaber2333 
1101929671 J * sannes ace@home.skarby.no
1101929900 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101929963 M * rs cya
1101929967 Q * rs Quit: home
1101930044 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101930059 Q * sannes Read error: Connection reset by peer
1101930082 Q * rollingthunder43 Quit: 
1101930102 Q * laberwaber2333 Quit: 
1101930147 Q * Hollow Quit: Leaving
1101930370 Q * ndim Ping timeout: 480 seconds
1101930581 M * redLED what is the latest patch version for 2.6.9 which works
1101930683 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101930689 J * ndim U2FsdGVkX1@helena.bawue.de
1101930737 M * redLED i tried http://vserver.13thfloor.at/Experimental/patch-2.6.9-vs1.9.3.7.diff
1101930740 M * redLED but it won't compile
1101930899 Q * laberwaber2333 Quit: 
1101930924 M * Loki|muh the vs1.9.3 does
1101930939 M * Loki|muh in development
1101931828 J * ntrs ntrs@SP2-24.207.228.55.charter-stl.com
1101932054 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101932237 Q * laberwaber2333 Quit: 
1101932282 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101932431 P * laberwaber2333 
1101932437 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101932819 P * rollingthunder43 
1101933076 J * Fibbs chris@p83.129.202.58.tisdip.tiscali.de
1101933079 M * Fibbs Hi all
1101933411 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101933456 Q * laberwaber2333 Quit: Leaving
1101933519 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101933529 Q * rollingthunder43 Quit: Leaving
1101934185 J * Hollow bene@home.xnull.de
1101934990 Q * brc Ping timeout: 480 seconds
1101936624 M * Doener redLED: got the error message at hand?
1101936698 M * redLED not anymore, something in procfs
1101936709 M * redLED building the 1.9.3 from the webpage now
1101937806 J * brc bruce@201008071179.user.veloxzone.com.br
1101937939 J * mef mef@targe.CS.Princeton.EDU
1101937947 Q * mef Quit: 
1101940330 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101940337 J * rollingthunder43 laberwabe@pD955E5BD.dip.t-dialin.net
1101940418 P * laberwaber2333 
1101940419 J * DuckMaster Duck@dyn-83-154-130-187.ppp.tiscali.fr
1101940561 P * rollingthunder43 
1101940838 Q * DuckKing Ping timeout: 480 seconds
1101941410 J * laberwaber2333 laberwabe@pD955E5BD.dip.t-dialin.net
1101941617 P * laberwaber2333 
1101942689 Q * [HvD] Ping timeout: 480 seconds
1101944179 N * Bertl_oO Bertl
1101944190 M * Bertl evening folks!
1101944252 M * Doener evening Bertl!
1101944270 M * Bertl hey Doener! everything fine?
1101944395 Q * redLED Quit: Leaving
1101944411 M * Doener yeah, brain's working again. But i guess the stuff i learned for yesterdays' exam already left my memory again ;)
1101944489 M * Bertl well, happens sometimes ...
1101944517 M * matti Yeppp... :/
1101944909 J * nosy nosy@pD9E72AE1.dip.t-dialin.net
1101944915 M * Bertl welcome nosy!
1101944921 M * nosy hello Bertl
1101944930 M * nosy read about you in the docs ;)
1101944940 M * nosy i have a little question
1101944940 M * Bertl ah, I'm in the docs?
1101944967 M * nosy suppose *uhm*...wait
1101945072 M * nosy Bertl: chroot-barrier
1101945073 M * nosy DebianVserverVirtualHosting
1101945077 M * nosy those
1101945100 M * Bertl hmm, what do they say about me there?
1101945120 M * nosy Bertl: do you have any idea how i can prevent users from binding any service to INADDR_ANY?
1101945138 M * nosy Bertl: something like thanks
1101945165 M * Bertl hmm, define users, and elaborate on your setup, please
1101945227 M * nosy Bertl: nothing special but the written name is memorizable
1101945278 M * nosy Bertl: user in the context of vservers is someone who only has root access to one of the vservers not the real server
1101945325 M * Bertl okay, and why should she not bind services to INADDR_ANY?
1101945349 M * nosy Bertl: because then nobody else can use the port
1101945352 M * nosy like ssh
1101945374 M * Bertl on that vserver, yes .. but on a different one, no ...
1101945407 M * Bertl and I guess here we come to the 'elaborate on your setup' part ...
1101945474 M * nosy Bertl: ok, cool, didnt try until now. In fact if i bind my ssh server on the main host to INADDR_ANY i cannot start another one on a vserver because the main server ssh is bound there so i thought it might be the same for all vservers on the system
1101945483 M * nosy Bertl: will try now
1101945510 M * Bertl that is correct, that is why you 'restrict' your sshd on the host to a single ip (usually)