1294272748 Q * hparker Quit: Quit 1294273418 M * Bertl daniel_hozac: something like this? http://vserver.13thfloor.at/ExperimentalT/delta-capcon-feat01.diff 1294273448 M * daniel_hozac yeah... 1294275532 M * Bertl okay, uploaded an rc patch for testing ... 1294275542 M * Bertl off to bed now ... have a good one everyone! 1294275548 N * Bertl Bertl_zZ 1294275833 Q * FireEgl Ping timeout: 480 seconds 1294277335 J * hparker ~hparker@2001:470:1f0f:32c:beae:c5ff:fe01:b647 1294277426 J * FireEgl ~FireEgl@173-25-19-139.client.mchsi.com 1294278625 Q * _nono_ Read error: Operation timed out 1294278825 J * _nono_ ~gomes@licencieux.ircam.fr 1294280588 Q * FireEgl Quit: Leaving... 1294281718 Q * bsingh Read error: Operation timed out 1294282310 J * bsingh ~balbir@122.172.34.105 1294283566 J * FireEgl FireEgl@2001:470:e056:8:10c6:6015:2b49:b49e 1294290155 Q * nkukard synthon.oftc.net oxygen.oftc.net 1294290155 Q * hel_ synthon.oftc.net oxygen.oftc.net 1294290155 Q * tam synthon.oftc.net oxygen.oftc.net 1294290218 J * nkukard ~nkukard@41-133-198-46.dsl.mweb.co.za 1294290218 J * hel_ ~hel@porthos.lennackers.de 1294290218 J * tam ~tam@gw.nettam.com 1294293888 Q * bsingh Ping timeout: 480 seconds 1294294997 J * harobed ~harobed@arl57-1-82-231-110-14.fbx.proxad.net 1294295619 Q * harobed Quit: Ex-Chat 1294295906 J * derjohn_foo ~aj@d074003.adsl.hansenet.de 1294296339 Q * aj__ Ping timeout: 480 seconds 1294297235 Q * nkukard Remote host closed the connection 1294297995 J * nkukard ~nkukard@196-208-246-195.dynamic-8632.isgsm.net 1294298859 Q * derjohn_foo Ping timeout: 480 seconds 1294300393 J * derjohn_foo ~aj@213.238.45.2 1294302739 J * harobed ~harobed@pda57-1-82-231-115-1.fbx.proxad.net 1294303555 J * bsingh ~balbir@122.248.161.59 1294305003 J * petzsch ~markus@dslb-092-078-232-230.pools.arcor-ip.net 1294306249 N * ensc Guest3482 1294306259 J * ensc ~irc-ensc@p5DF2FEE1.dip.t-dialin.net 1294306655 Q * Guest3482 Ping timeout: 480 seconds 1294308256 Q * ncopa Quit: Leaving 1294308332 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no 1294308444 Q * ncopa 1294308453 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no 1294310071 N * Bertl_zZ Bertl 1294310076 M * Bertl morning folks! 1294310134 M * hparker You sleep/wake cycle is as bad as mine :P 1294310265 M * fback morning Bertl :) 1294310318 M * fback hparker: that's just specific TZ he resides in, not a bad sleep/wake cycle :P 1294310371 M * hparker ahh.. But I see him come and go at lots of different hours 1294310397 M * hparker Yesterday it was like 6 hours later than this :P 1294310603 M * hparker Maybe he had a long coffee ;) 1294310645 M * Bertl :) 1294311588 M * fback hparker: google for irc logs for this channel, then grep for Bertl's timezone ;) 1294311615 M * hparker Yeah, he's a "bit" south of me iirc 1294312527 Q * harobed Ping timeout: 480 seconds 1294314326 M * Bertl off for now ... bbl 1294314330 N * Bertl Bertl_oO 1294314758 M * ard his TZ is just unstable 1294314795 Q * arekm Quit: leaving 1294314823 M * hparker Maybe it's just his clock source 1294315206 J * arekm arekm@carme.pld-linux.org 1294317489 Q * bsingh Read error: Operation timed out 1294317978 J * DreamerC ~DreamerC@122-116-181-118.HINET-IP.hinet.net 1294318913 A * arekm booted 2.6.37+vserver+tons of other stuff, no suprise so far 1294319833 N * Bertl_oO Bertl 1294319836 M * Bertl back now ... 1294320115 J * harobed ~harobed@pda57-1-82-231-115-1.fbx.proxad.net 1294322125 Q * ncopa Quit: Leaving 1294322250 J * ncopa ~ncopa@3.203.202.84.customer.cdi.no 1294324243 M * wurtel arekm: did you use the experimental vs2.3.0.37-rc1 patch for 2.6.37? 1294324719 M * arekm wurtel: yes 1294324730 M * wurtel good to know :) 1294325623 Q * nkukard Ping timeout: 480 seconds 1294327799 Q * eyck_ Read error: Connection reset by peer 1294327863 M * ser anyone using vservers on drbd? 1294327949 M * Bertl I'd say so, why, any problems? 1294328069 J * eyck ~eyck@77.79.198.68 1294328085 M * ser no, just a quick research. i would like to have linux-ha+drbd+vserver solution and i am able to deploy it but with a spare server. how to mix the setup to have two working servers where services can failover to one when one fails 1294328143 M * ser is xen which devides a phisical machine into two vservers (one main, one failover) a good idea? 1294328188 M * ser of course i am chatting about two-servers deployment and i just need the services to resist one server failure 1294328192 M * Bertl the described setup is a common case, so I guess no big problems to expect there 1294328217 M * ser Bertl: you mean two working servers in the same time? 1294328225 M * Bertl xen doesn't make much sense, if failover and host is on the same machine 1294328245 M * ser Bertl: why? if you cross them over with pairs? 1294328256 M * Bertl no point in doing so 1294328276 M * Bertl if one machine goes down, you will lose one main and one failover 1294328282 M * ser ok so it is possible to run services on both machines and failover to one? 1294328296 M * Bertl if you run both machines in active-active with separate guests on each 1294328318 M * Bertl you have the same amount of load balancing when all is fine, and the failover is similar too 1294328331 M * ser do you have a link to any such solution described? 1294328356 M * ser i mean any guide/report how to build it 1294328379 M * Bertl google should know, first hit I get is this: http://allmybrain.com/2007/10/02/using-linux-ha-for-high-availability-with-gentoo-and-linux-vserver/ 1294328392 M * ser reading, thanks 1294329803 Q * harobed Quit: Ex-Chat 1294330825 M * Bertl off for now ... bbl 1294330829 N * Bertl Bertl_oO 1294333510 J * bonbons ~bonbons@2001:960:7ab:0:2c0:9fff:fe2d:39d 1294333890 Q * derjohn_foo Ping timeout: 480 seconds 1294336603 Q * FireEgl Ping timeout: 480 seconds 1294337324 J * FireEgl ~FireEgl@173-25-19-139.client.mchsi.com 1294337610 Q * dannf Quit: Coyote finally caught me 1294337796 J * dannf ~dannf@utter.lackof.org 1294338293 Q * petzsch Quit: Leaving. 1294339067 J * petzsch ~markus@dslb-092-078-232-230.pools.arcor-ip.net 1294339640 Q * ncopa Quit: Leaving 1294340586 J * nkukard ~nkukard@41-133-198-46.dsl.mweb.co.za 1294341623 Q * mikez Ping timeout: 480 seconds 1294344605 J * derjohn_mob ~aj@d074003.adsl.hansenet.de 1294346414 J * frank 4fd5df2c@ircip1.mibbit.com 1294346768 J * hijacker_ ~hijacker@87-126-142-51.btc-net.bg 1294347203 M * frank hi all 1294347262 M * frank any chance that kernel 2.6.36.2 + patch patch-2.6.36.2-vs2.3.0.36.38.2.diff is kinda buggy? 1294347306 M * frank when doing repeatedly 'vserver xyz enter' (for about 10times in a row) I end up with an error 1294347383 M * frank I cannot reproduce this with kernel 2.6.32.1 + vs2.3.0.36.38 1294347449 M * frank erm - it should read kernel 2.6.36.1 1294347488 M * frank the exact error message (on kernel 2.6.36.2 + vs2.3.0.36.38.2) is 1294347499 M * frank vlogin: fork(): Try again 1294347554 M * frank ... and as a result the complete guest goes bananas (must stop and start the vserver again) 1294347917 M * frank ie... postfix goes bananas spitting postfix/master[21831]: warning: master_spawn: fork: Resource temporarily unavailable -- throttling and other crap in log files 1294348448 N * Bertl_oO Bertl 1294348459 M * Bertl back now ... 1294348479 M * Bertl frank: could be, somebody else reported issues with fork() resource unavailable 1294348550 M * frank aye... read something similiar in the irc logs - but wasn't sure 1294348671 M * Bertl could you try with 2.6.36.1 + vs2.3.0.36.38.2 ? 1294348683 M * Bertl (as you seem to be able to recreate the issue easily) 1294348706 M * frank can do so - but need to recompile 1294348794 M * frank I'll do so tomorrow - and will then report back here in IRC 1294348800 M * Bertl and 2.6.37 would be interesting too, if you get around 1294348843 M * frank ok =) 1294348850 M * Bertl thanks in advance! 1294348886 M * frank boss is on vacation tomorrow - I therefor hope that I've plenty of time to do some further tests =) 1294348901 M * Bertl excellent :) 1294348978 M * frank well then - see/read you tomorrow 1294348985 M * frank byebye for now! =) 1294348988 M * Bertl cya! 1294349032 Q * frank Quit: http://www.mibbit.com ajax IRC Client 1294349210 M * vasko Hi, i am experiencing the fork() issue too with 2.6.36.2-vs2.3.0.36.38.2 and right now i got a new problem -- i cannot enter a guest 1294349229 M * vasko i am getting: 'vserver ... suexec' is supported for running vservers only; aborting... 1294349243 M * Bertl and vserver-stat reports the guest as running? 1294349256 M * vasko reports it like this: 1294349259 M * vasko 1217 62 519.1M 143.7M 0m00s00 0m00s00 19h12m07 1294349262 M * vasko empty name 1294349270 M * vasko using vps i can see processes 1294349271 M * Bertl util-vserver version? 1294349299 M * vasko util-vserver: 0.30.216-pre2926; Dec 15 2010, 14:23:15 1294349320 M * Bertl for whatever reason, it seems your /var/run/vserver/ disappeared? 1294349347 M * vasko yes, it is missing there 1294349386 M * vasko other 6 guests are ok 1294349400 M * Bertl adding the info back there should fix this 1294349405 M * vasko except on of them reports strange rss value: 1294349415 M * vasko 74 28 148.5M 5.5G 0m00s00 0m00s00 10d23h29 backup4 1294349453 M * vasko ps xau reports about 30MB 1294349513 M * vasko (mysqld, postfix, bacula, cron, syslog) 1294349535 M * Bertl 30MB sounds a little low for all of those actually 1294349732 M * vasko http://pastebin.com/GYdLBua1 1294350040 Q * hijacker_ Quit: Leaving 1294350374 Q * bonbons Quit: Leaving 1294352319 J * saschagehlich ~sascha@p57931895.dip.t-dialin.net 1294352325 M * saschagehlich hey, I'm having a problem with lilo. I'm trying to boot from a vserver image, so my lilo looks like that: https://gist.github.com/03df5f2d61630724a02e - calling "lilo" also tells me that it will boot from the "Vserver" image, but after rebooting my server boots with the bzImage. any help? 1294352428 M * Bertl do folks still use lilo? anyway, did you update the on disk representation for lilo? 1294352465 M * Bertl i.e. is it the correct disk you are writing the changes to? 1294352528 M * saschagehlich yes, it's /dev/md1 1294352545 M * saschagehlich lilo tells me that it updated /dev/md1 and in my syslog I also see that it boots from /dev/md1 1294352554 M * Bertl md1 sounds wrong for lilo, it needs to be a raw device 1294352566 M * Bertl i.e. the bios won't know about md1 1294352580 M * saschagehlich okay, how can I find out which device to use? fdisk -l? 1294352594 M * Bertl what kind of raid do you use? 1294352653 M * saschagehlich raid 1 1294352658 M * saschagehlich software raid I think 1294352673 M * Bertl so you are mirroring two or more disks 1294352681 M * saschagehlich yes 1294352684 M * Bertl check which ones with /proc/mdstat 1294352722 M * saschagehlich https://gist.github.com/11f3ecc04b07d0b71d9e 1294352757 M * Bertl so sda1 and sdb1 want lilo updates 1294352770 M * Bertl most likely sda1 is the one you are currently booting from 1294352812 M * saschagehlich okay 1294352820 M * saschagehlich so I have to change the root property to /dev/sda1 then? 1294352860 M * saschagehlich now I'm getting this warning: https://gist.github.com/44b4c4a07bb95a93c431 1294352864 M * Bertl http://tldp.org/HOWTO/Boot+Root+Raid+LILO-3.html#ss3.1 1294353168 M * Bertl note that you are probably a lot better off if you use grub instead, it simplifies quite a number of things 1294353740 M * saschagehlich I tried to use grub but had the same problems there. People told me grub would not support raids 1294353892 M * Bertl you had the same problems there? i.e. so it obviously worked on your raid setup, no? 1294353905 M * Bertl (otherwise it would not boot with grub, right?) 1294354963 Q * petzsch Quit: Leaving. 1294357084 Q * derjohn_mob Ping timeout: 480 seconds 1294357760 J * derjohn_mob aj@tmo-046-8.customers.d1-online.com 1294358221 Q * saschagehlich Quit: saschagehlich 1294358239 Q * manana Remote host closed the connection