1379982748 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:c1e7:ae42:43ce:f43d 1379983232 Q * thierryp Ping timeout: 480 seconds 1379986378 J * thierryp ~thierry@home.parmentelat.net 1379986864 Q * thierryp Ping timeout: 480 seconds 1379990010 J * thierryp ~thierry@home.parmentelat.net 1379990495 Q * thierryp Ping timeout: 480 seconds 1379992614 M * Bertl_oO off to bed now ... have a good one everyone! 1379992619 N * Bertl_oO Bertl_zZ 1379993640 J * thierryp ~thierry@home.parmentelat.net 1379994125 Q * thierryp Ping timeout: 480 seconds 1379997274 J * thierryp ~thierry@home.parmentelat.net 1379997756 Q * thierryp Ping timeout: 480 seconds 1380000901 J * thierryp ~thierry@home.parmentelat.net 1380001384 Q * thierryp Ping timeout: 480 seconds 1380002547 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:b457:f324:fa26:72ef 1380004389 J * Ghislain ~aqueos@adsl1.aqueos.com 1380005243 Q * thierryp Remote host closed the connection 1380006064 J * beng_ ~BenG@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com 1380006421 Q * mnemoc Remote host closed the connection 1380006426 J * mnemoc ~amery@geeks.cl 1380006515 M * Ghislain hello there 1380006571 M * Ghislain i wanted to know what do you think is the best way to investigate a context that is stalled ? For exemple when one context run out of memory and locks itself down we cannot enter or launch any command in this context 1380006592 M * Ghislain so is there another way to look at it wituout being lock also by the cgroup policy ? 1380007331 M * daniel_hozac vps? 1380007839 J * alpha_one_x86 ~kvirc@190.186.23.251 1380007929 J * thierryp ~thierry@zebra.inria.fr 1380008220 J * thierryp_ ~thierry@zebra.inria.fr 1380008220 Q * thierryp Read error: Connection reset by peer 1380010043 M * Ghislain yes a vps is stuck by cgtroup policy ( read memory limits) or any ressource 1380010058 M * Ghislain then i cannot enter the context 1380010063 M * Ghislain oh you mean vps the command 1380010192 M * Ghislain yes i used it to recover doing 1380010192 M * Ghislain vps auxw | grep myguest | grep apache | awk '{ print $2 }'| xargs -I% vkill -c myguest -- % 1380010340 Q * daniel_hozac Ping timeout: 480 seconds 1380010363 M * Ghislain i wonder if there is a way to do a vlsof :) 1380010399 M * Ghislain ohhh stupid of me chcontext --silent --ctx 1 lsof -p 32290 1380010432 M * Ghislain humm no it fail with permission denied :) 1380010733 J * daniel_hozac ~daniel@h149n2-spaa-a12.ias.bredband.telia.com 1380012551 M * Jb_boin Ghislain, root@bdeo1:~# lsof |wc -l 1380012551 M * Jb_boin 3862 1380012551 M * Jb_boin root@bdeo1:~# chcontext --xid 19004 lsof|wc -l 1380012551 M * Jb_boin 1047 1380012580 M * Jb_boin the solution might be that i run this at boot : setattr --watch /proc/vmstat 1380012639 M * Jb_boin and btw : root@bdeo1:~# chcontext --xid 1 lsof|wc -l 1380012639 M * Jb_boin 140051 1380012754 M * Ghislain yes but it do not list the files , for me i have only a list of permission denied 1380012810 M * Ghislain and you cannot use chcontext in other than one i think when the vps is stuck 1380012901 P * alpha_one_x86 No matter how dark the night, somehow the Sun rises once again 1380012926 M * Jb_boin well, i dont have a stuck VServer atm so i cant tell you but on the ones that are not locked i can see the files in use on the vserver with this command 1380012944 M * Jb_boin Ghislain, that also might come in handy if you host VPSes : http://paste.debian.net/45552/ 1380012971 M * Jb_boin a script i made some itme a go to print the bandwith used by each VServers for a duration 1380012986 M * Jb_boin time ago* 1380013096 M * Ghislain oh thanks for sharing, will have a look :) 1380013598 M * Jb_boin it was usefull when a vps was flooding or getting flooded but iftop on the context1 is also pretty nice as long as you put all the vps hostnames on the /etc/hosts of the host system 1380016542 J * Walex ~Walex@cl-203.lon-02.gb.sixxs.net 1380019526 N * Bertl_zZ Bertl 1380019532 M * Bertl morning folks! 1380019923 A * Walex waves 1380020100 Q * ircuser-1 Read error: Operation timed out 1380021376 Q * Wonka Quit: Stromzählertausch... 1380021539 Q * Aiken Remote host closed the connection 1380022937 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1380023473 Q * beng_ Quit: I Leave 1380025011 Q * Walex 1380025015 N * l0kit Guest179 1380025023 J * l0kit ~1oxT@0001b54e.user.oftc.net 1380025415 Q * Guest179 Ping timeout: 480 seconds 1380027814 J * BenG_ ~bengreen@bmex-gw.bristolwireless.net 1380027947 J * Wonka produziert@chaos.in-kiel.de 1380038394 Q * BenG_ Quit: I Leave 1380038897 M * AlexanderS whats wrong with my vserver if i could add addresses to interfaces from within the guest? (NET_ADMIN is not set) the ips are not visible inside the guest but they get added to the interface on the host... 1380039719 M * Bertl a lot seems to be wrong 1380039727 M * Bertl what kernel/patch/util-vserver version? 1380039886 M * AlexanderS vserver-info: http://p.animux.de/8RfAM9Nkwqi.html 1380040039 M * Bertl okay, check with vattribute --get and nattribute --get what flags/caps your guest actually has 1380040122 M * AlexanderS http://p.animux.de/B2rUqNsHFV.html 1380040144 Q * thierryp_ Remote host closed the connection 1380040301 M * Bertl well, you have quite a number of capabilities set 1380040934 M * AlexanderS but I never set them... 1380041045 M * Bertl I presume that is util-vserver enabling them (by default) 1380041069 M * Bertl how do you add ips? 1380041086 M * Bertl i.e. what are the commands you tried? 1380041106 M * AlexanderS currently it is possible to use "ip a a dev eth0" in the guest 1380041273 M * Bertl should result in EPERM on a proper isolation 1380041328 M * Bertl just tried with a recent kernel and it works fine there 1380041342 M * Bertl it could be a bug in the beng kernel/patch 1380041349 M * AlexanderS i have another server with squeeze there it also works fine... 1380041401 M * Bertl works fine means it is not allowed to do that? 1380041466 M * AlexanderS yes 1380041483 M * AlexanderS i'll just try to update the beng kernel... 1380041612 M * Bertl okay, let me know how that goes 1380041871 M * Jb_boin never had this kind of issue on 3.2 beng kernels 1380043844 M * AlexanderS the newer 3.2 kernel does not change anything, but using the 3.10 beng kernel ip returns EPERM as expected... 1380043891 M * Bertl so I presume something is broken in the 3.2 branch 1380043923 M * Bertl you might want to send an email to beng with the collected information 1380043933 M * Bertl (should be easy to test for him) 1380043972 M * AlexanderS yes, i will do 1380044080 M * Bertl thanks! 1380048298 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg 1380050515 J * alpha_one_x86 ~kvirc@190.186.23.7 1380051482 J * Aiken ~Aiken@2001:44b8:2168:1000:21f:d0ff:fed6:d63f 1380052859 Q * hijacker_ Quit: Leaving 1380053133 J * bonbons ~bonbons@2001:a18:20f:4601:c0c0:b294:cddb:2f30 1380055280 Q * bonbons Quit: Leaving 1380061597 Q * alpha_one_x86 Ping timeout: 480 seconds 1380061952 Q * disposable Ping timeout: 480 seconds 1380062219 J * alpha_one_x86 ~kvirc@190.186.23.56 1380065404 Q * Ghislain Quit: Leaving.