1362789283 Q * clopez Ping timeout: 480 seconds 1362789872 J * clopez ~clopez@137.Red-80-59-166.staticIP.rima-tde.net 1362791334 Q * bonbons Quit: Leaving 1362802164 Q * clopez Ping timeout: 480 seconds 1362812614 Q * Romster Remote host closed the connection 1362813362 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1362814535 Q * Romster Quit: Geeks shall inherit properties and methods of object earth. 1362814594 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1362814659 Q * Romster Remote host closed the connection 1362814727 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1362815612 Q * Romster Quit: Geeks shall inherit properties and methods of object earth. 1362815678 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1362815737 Q * Romster Remote host closed the connection 1362816769 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1362817927 Q * Romster Remote host closed the connection 1362818259 N * Bertl_zZ Bertl 1362818267 M * Bertl morning folks! 1362818569 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1362819742 J * _WildPikachu_ ~nkukard@196-210-205-18.dynamic.isadsl.co.za 1362819889 Q * nkukard_ Ping timeout: 480 seconds 1362823054 J * bonbons ~bonbons@2001:a18:20a:1601:8856:f3f7:adc:72ee 1362824356 Q * bonbons Remote host closed the connection 1362824661 J * bonbons ~bonbons@2001:a18:20a:1601:8856:f3f7:adc:72ee 1362826983 J * nkukard_ ~nkukard@196-210-204-27.dynamic.isadsl.co.za 1362827129 Q * _WildPikachu_ Ping timeout: 480 seconds 1362829113 J * Ghislain ~aqueos@adsl1.aqueos.com 1362829692 Q * Ghislain Quit: Leaving. 1362832194 Q * ircuser-1 Ping timeout: 480 seconds 1362832800 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net 1362832891 Q * Seattle 1362832966 J * Seattle 18224ae4@ircip1.mibbit.com 1362833134 M * Seattle Hi All - am trying to start/stop all vservers with one command, am trying "vsomething" and getting error code 127. Q: is "vsomething" a reasonable way to do this? If so, think am just having trouble with syntax. Trying "vsomething stop * --all". Suggestions? 1362833454 M * Seattle PS all vservers have /apps/init/mark with a value of default 1362835556 M * Jb_boin you could try to do '*' instead of * 1362835578 Q * Seattle Quit: http://www.mibbit.com ajax IRC Client 1362835606 J * seattle 18224ae4@ircip2.mibbit.com 1362835638 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1362835667 M * seattle Sorry - was in process of rebooting when got message! Could you repeat? Looking for command syntax to restart all vservers.. 1362835826 M * seattle And assume "vsomething" is a reasonable place to start 1362835977 M * Jb_boin you could try to do '*' instead of * 1362836039 M * Jb_boin i never used vsomething so i cant assure you its the solution to your problem but using * as an argument on a command line will replace your * by a list of the files present in the directory you are on while executing the command 1362836292 M * seattle Thanks - tried, but get same error. Vsomething --help shows: vsomething --help Usage: /usr/sbin/vsomething [--quiet|-q] [--debug] [--] * [--all] -- + Execute * foreach vserver. 1362836326 M * seattle Error I'm getting is stop: operating on vserver * /usr/sbin/vsomething: line 120: stop: command not found stop failed on vserver '*' with errorcode 127 which in effect repeats for each vserver 5 (have 5 or so running on test machine) 1362836613 M * seattle PS yesterday Bertl said "there is a runlevel script to start guests having a 'default' mark"...each of the vservers here have that I think (in apps/init/mark)....just not sure what level script he may have meant... 1362838743 M * daniel_hozac /etc/init.d/vservers-default 1362838855 M * seattle Thanks Daniel(!) - can you suggest a command for that - is it just "etc/init.d/vservers-default"? 1362838896 M * daniel_hozac like every service script it accepts stop, start, restart, etc arguments. 1362838906 M * seattle Thanks! 1362839213 M * seattle PS sorry for nobishness....don't have a "vservers-default" script in /etc/init.d.....have a "util-server"..so if issue "/etc/init.d/util-vserver stop" that works!!! Should I have a "vservers-default" too? 1362839307 M * daniel_hozac yes. 1362839389 M * seattle OH...am using Debian 6....did I miss how to create "vservers-default" in instructions (i.e., should this get created during original vserver install, or do you set it up manually)? 1362839551 M * daniel_hozac it is installed by make install of util-vserver. 1362839694 M * seattle stumped...seem to have util-vserver but apparently "etc/init.d/vservers-default" didn't get created....vservers seem to be running OK...can I get by without this or issue a command to generate it? 1362839716 M * daniel_hozac did you install the Debian package? 1362839754 M * seattle PS - am using Squeeze, so didn't compile from stratch... 1362839776 M * seattle Yes (using debian package) 1362840702 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg 1362840992 M * seattle Hoping to ask another....want to use pacemaker/drbd for vserver failover. Have got things working so data areas for vservers fail over succesfully...next step is to try actually to get vsrvers to fail over. Q: will we need some symlinks from the /etc/vservers and /var/lib/vservers areas? 1362841670 M * daniel_hozac i don't know, have you set them up as mount points for drbd? 1362841737 M * seattle If I understand, yes. I.e., have a mount point /Vservers. In there create LV for each vserver. Map that LV as backing device to drbd. Then create pacemaker config. 1362841782 M * seattle So I can see how the vserver data would "fail over", but it's unclear to me how the 2nd machine would know where the vserver data are... 1362841972 M * seattle PS would think this might be true of ssh keys as well (we would want to be able to ssh to the vservers on the fail over server) 1362842083 M * Jb_boin if you are using default standard debian packages, i would strongly recommand you to switch to the beng packages 1362842265 M * seattle Sorry, what are beng packages? 1362842788 J * Ghislain ~aqueos@adsl1.aqueos.com 1362843049 M * Jb_boin http://repo.psand.net/info/ 1362847797 M * seattle Another one...this may be hard to answer....just set up a new guest on a "new build" test box....use script to build guests that has worked for months..., but not now. Guest not starting at boot, and no network connectivity....when manually start, get "Error an inet prefix is expected rather than 192.168.1.301/24 1362849150 M * Jb_boin in the /etc/vservers/XXX/interface/X/ you should have a file prefix with the prefix and a file ip with the ip 1362849154 M * Jb_boin is that what you got? 1362850031 M * seattle yes - prefix 24 and ip 192.168.1.301 and dev eth0....going to delete vserver, maybe start all over....suspect this is because of something with pacemaker/drbd (that's the main thing that's different)...including our host and hostname syntax is slightly different....arrrrrrrrr 1362852050 Q * seattle Quit: http://www.mibbit.com ajax IRC Client 1362855207 J * clopez ~clopez@137.Red-80-59-166.staticIP.rima-tde.net 1362857709 Q * Walex 1362860069 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net 1362860131 Q * Seattle 1362861369 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net 1362861398 Q * clopez Ping timeout: 480 seconds 1362861576 M * Seattle Hi All - am working on failover solution for vserver (debian 6; drbd; pacemaker). Adding guest for the first time on this particular set of test systems. Getting an error that is new on me...."Error: an inet prefix is expected rather than "192.168.1.285/24"." My guess is this has something to do with hosts or host name....for guest, "interfaces/0/dev" is eth0, ip is 192.168.1.285, and... 1362861578 M * Seattle ...prefix is 24. Assume this is something simple, but am stuck. 1362861618 M * Seattle PS - /apps/init/mark is "default", but vserver is not starting after boot either 1362861718 M * Seattle PPS if do ifconfig inside of guest, only get lo (loopback I think) address, no IP. On working vserver examples on another machine, get the IP here. 1362861940 J * clopez ~clopez@137.Red-80-59-166.staticIP.rima-tde.net 1362862112 M * daniel_hozac 192.168.1.285 is not a valid IP address. 1362862160 M * Seattle Thanks Daniel .... dumb question, but why not? Wanted it outside of DHCP.... 1362862194 M * daniel_hozac because 285 is greater than 255. 1362862204 M * Seattle ah....!!!!!!!!!!!!!!!!!!!!!!!!!! thanks! 1362862211 M * Seattle bye for now... 1362862479 Q * Seattle Remote host closed the connection 1362862693 Q * clopez Read error: Operation timed out 1362863581 J * clopez ~clopez@21.102.11.37.dynamic.jazztel.es 1362863733 Q * Romster Read error: No route to host 1362864152 J * kolorafa ~irc@ave103.neoplus.adsl.tpnet.pl 1362864321 M * kolorafa Sorry guys that i only join when i have problem, and thanks for your support. I have a problem with loopback: CONFIG_VSERVER_AUTO_LBACK=y, i see 127.0.0.1 address in guest, I can bind to it, but when i try to connect i got Connection refused, firewall clean, using custom build 3.7.9-vs2.3.5.6, vserver 0.30.216-pre3038-squeeze0.2 1362864394 M * kolorafa and it looks like it binds 127 globaly, because after vserver upgrade i got error on some vservers because they could not bind to 0.0.0.0:80 (probably because of localhost / already bind on another) 1362864530 M * daniel_hozac do you also have CONFIG_VSERVER_AUTO_SINGLE? 1362864658 M * kolorafa yes 1362864696 M * kolorafa CONFIG_VSERVER_AUTO_LBACK=y 1362864696 M * kolorafa CONFIG_VSERVER_AUTO_SINGLE=y 1362864696 M * kolorafa CONFIG_VSERVER_COWBL=y 1362864696 M * kolorafa # CONFIG_VSERVER_VTIME is not set 1362864696 M * kolorafa # CONFIG_VSERVER_DEVICE is not set 1362864698 M * kolorafa CONFIG_VSERVER_PROC_SECURE=y 1362864698 M * kolorafa ... 1362864806 M * daniel_hozac you'll want that disabled. 1362864821 M * daniel_hozac either for that guest specifically, or disabling it in the kernel. 1362864855 M * kolorafa what exactly single stands for? 1362864869 M * daniel_hozac it's an optimization for guests with just a single IP. 1362864882 M * kolorafa O_o after 4 trys it somehow allows me to connect, i did bind to localhost 2 times and after second it connected 1362864883 M * daniel_hozac binds to 0.0.0.0 will actually bind to the guest's IP address. 1362865151 M * kolorafa tanks 1362865157 M * kolorafa thanks 1362866108 J * Seattle ~chatzilla@c-24-34-74-228.hsd1.ma.comcast.net 1362866161 M * Seattle Just a quick "big huge thanks" to Daniel....having invalid IP was embarrassing, but thanks so much for suggestion and getting me unstuck! 1362866701 J * wmp ~wmp@2001:41d0:1:8616::1 1362867316 J * Romster ~romster@202.168.100.149.dynamic.rev.eftel.com 1362868876 Q * Seattle Remote host closed the connection 1362869000 Q * clopez Ping timeout: 480 seconds 1362869073 Q * hijacker_ Quit: Leaving 1362871923 Q * Ghislain Quit: Leaving.