1380850775 Q * Ghislain Quit: Leaving. 1380850989 J * Ghislain ~aqueos@adsl1.aqueos.com 1380851107 Q * Ghislain 1380852515 N * l0kit Guest1260 1380852521 J * l0kit ~1oxT@0001b54e.user.oftc.net 1380852721 Q * Guest1260 Ping timeout: 480 seconds 1380853676 M * user-K In running the tests after initial setup shown here, http://linux-vserver.org/Installation_on_Linux_2.6, if I have not compiled into the kernel support for xfs, reiser, or jfs filesystems, it would be normal to expect those three parts of testing to fail, would it not? Specifically, this test, for instance: "testfs.sh -l -t -D /dev/loop0". 1380853760 M * user-K It seems to me that this result would not represent a problem. Is that not so? 1380853855 M * user-K I mean, so long as the rest of the test was positive, accounting for the file systems I have compiled for. 1380861607 M * user-K it's been great chatting with all of you 1380861614 M * user-K exit 1380861628 Q * user-K Quit: leaving 1380868581 J * Ghislain ~aqueos@adsl1.aqueos.com 1380870614 Q * ncopa Quit: Leaving 1380870621 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:49df:45ab:e62a:9201 1380870909 J * ncopa ~test@3.203.202.84.customer.cdi.no 1380873451 M * Ghislain hello, from a crude test it seems that sysinfo call is not virtualized where /proc/uptime is. I noticed it because uptime command works but monitoring systems do not report the guest one but the host one 1380873481 M * Ghislain here zabbix agent is reporting the uptime of the host not of the guest it runs in 1380874449 M * daniel_hozac what kernel and patch? 1380874816 M * Ghislain Kernel: 3.4.63-vs2.3.3.9 1380875523 J * beng_ ~BenG@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com 1380876054 M * Ghislain i am doing some test to see why zabbix return the host uptime 1380876238 M * Ghislain http://paste.linux-vserver.org/25357 1380876670 N * Bertl_zZ Bertl 1380876675 M * Bertl morning folks! 1380877139 M * Bertl Ghislain: thanks! will look into it 1380877144 M * Bertl off for now ... bbl 1380877148 N * Bertl Bertl_oO 1380878743 Q * rawplayer Ping timeout: 480 seconds 1380881247 J * alpha_one_x86 ~kvirc@190.186.23.54 1380881307 M * alpha_one_x86 Hello, I have patch to show into the guest only the cpu, memory, hdd IO consumed by the guest, somebody is interrested? 1380881372 M * alpha_one_x86 Bertl: If I have only 'too many arguments to function' and the patch is open and public, can you fix quickly and freely this error? 1380881393 M * alpha_one_x86 Because I have adapted the patch to 3.10 1380881679 M * Bertl_oO sure, we are always interested in contributions ... upload the patch somewhere and paste the url, we'll look into it ASAP 1380884035 Q * ircuser-1 Read error: Operation timed out 1380886891 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net 1380889600 Q * Guy- Ping timeout: 480 seconds 1380889612 J * Guy- ~korn@elan.rulez.org 1380889712 M * Ghislain bertl: woot created my first c program to test that, yeah t'was a cut and paste but nevertheless it was one :) 1380890319 Q * BlackPanx Quit: KVIrc 4.1.1 Equilibrium http://www.kvirc.net/ 1380893036 Q * Ghislain Ping timeout: 480 seconds 1380896075 J * Ghislain ~aqueos@adsl1.aqueos.com 1380896165 Q * Ghislain Read error: Connection reset by peer 1380896379 J * Ghislain ~aqueos@adsl1.aqueos.com 1380901045 J * user-K ~username@pool-71-170-154-175.dllstx.fios.verizon.net 1380901830 M * user-K This page, http://linux-vserver.org/Downloads, has a link to "vserver tools project homepage", which I am reading. One of the points made on its site, in section 4.10, mentions problems that may arise, and one of them in particular, I am seeing on a vserver installation of mine, which I just made and am now getting set up. 1380901904 M * user-K It mentioned the problem where some services of the main server binding to address 0.0.0.0, and I can see this happening with sshd in my case. 1380902025 M * user-K It also stated that one way around this issue would be to make use of the provided services, for example, "v_sshd". However, I do not see any file with this name on my system. Is the information still relevant on that site? 1380902144 M * user-K Or should I make use of this alternative also mentioned on that site: "/sbin/chbind --ip eth0 /etc/rc.d/init.d/sshd start". 1380902223 P * alpha_one_x86 No matter how dark the night, somehow the Sun rises once again 1380902461 M * Bertl_oO the v_sshd is one of the 'older' runlevel scripts, which basically does the chbind for you 1380902481 M * Bertl_oO in general, for many services using chbind is a good idea, but for ssh it usually is not 1380902526 M * Bertl_oO this is mainly because usually you do administration via ssh, and it would be counter productive if you ssh into a restricted (chbind) environment to administrate contexts 1380902570 M * Bertl_oO for ssh (and many services) running on the host, the best solution is to configure the service (ssh, ...) to only bind host only IPs instead of * 1380902674 M * Bertl_oO user-K: note that v_sshd is still present in util-vserver-legacy-0.30.216-0.pre3038 1380902677 M * user-K Well then, I should be able to do that easily enough with sshd_config settings. That is what you mean? 1380902687 M * Bertl_oO yep, precisely 1380902705 M * Bertl_oO just adjust the Listen directive to match host IP(s) 1380902722 M * user-K yes, thank you. 1380902726 M * Bertl_oO you're welcome! 1380903251 Q * beng_ Quit: I Leave 1380904450 J * beng_ ~BenG@cpc35-aztw23-2-0-cust207.18-1.cable.virginmedia.com 1380904702 Q * thierryp Remote host closed the connection 1380905752 J * Walex ~Walex@cl-203.lon-02.gb.sixxs.net 1380905985 Q * beng_ Quit: I Leave 1380908915 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:dd4c:f6af:b59a:588d 1380909399 Q * thierryp Ping timeout: 480 seconds 1380909437 M * Bertl_oO off for a nap ... bbl 1380909442 N * Bertl_oO Bertl_zZ 1380909518 Q * eyck Remote host closed the connection 1380910509 J * eyck ~eyck@nat08.nowanet.pl 1380912940 Q * Walex 1380914522 J * hijacker_ ~hijacker@cable-84-43-134-121.mnet.bg 1380914537 Q * hijacker_ 1380915358 J * bonbons ~bonbons@2001:a18:20f:4601:40e8:bb8e:92a2:a2e3 1380921248 M * user-K Using "vserver vs-name enter" while trying to enter a vs for the first time, I got this response:" 'vserver ... suexec' is supported for running vservers only; aborting..." 1380921305 M * user-K Any ideas what that is about? Any pointers to making it right would be welcome. 1380922848 Q * cuba33ci Read error: Connection reset by peer 1380922946 J * cuba33ci ~cuba33ci@114-25-196-143.dynamic.hinet.net 1380923450 M * Aiken user-K, do you have anything running in the vserver ie cron sshd 1380924766 M * user-K Aiken, no apparently not. :) I mean, that is the problem. I successfully created the new vserver, but I was prevented when I tried entering it. What am I missing. Should I not be able to simply enter a shell without specifying any process? 1380924879 M * user-K running vserver-stat indicates that only context 0 is up. 1380925039 M * Aiken the guest is stopping after being started because there is nothing running in it 1380925078 M * Aiken I have my template starting sshd so there is a process to run when a new guest starts 1380925183 M * user-K Ah, I see. I have to explicitly start a process, any process, that would remain running, else the server shuts down immediately and I cannot enter it? 1380925258 M * Aiken yes 1380925274 M * user-K My bad! 1380925403 M * Aiken I can not remember if there is a way to run a command in a guest without a full start, vserver name exec cmd only works for on a running guest 1380925631 M * user-K I think I was mistakenly expecting a server to stay up indefinitely after starting it with the capability of, say, allowing me to enter a shell, from which to execute commands for other processes and maintenance, etc., until I explicitly shut it down. 1380925632 M * Aiken user-K, used this to get a shell in a vserver where all services were disabled so it would not vserver hoppy start --rescue bash 1380925733 M * Aiken hoppy is my test image and this got me a shell I could use even though so services were enabled to keep it running 1380926156 M * user-K I suppose cron might be a process that would keep it up too? 1380926431 M * Aiken yes 1380926556 M * user-K You know, I was expecting a certain amount of minimal service activity to be created automatically when I created the vs, which would then initialize when I started it. I think now that must not be what happens. IOW, I now have to build everything into it pretty much. That's fine with me too. 1380927982 M * user-K Aiken, there must be a way. I mean, how could you have gotten into your guest if you had not used a command to start a process after creating it? 1380930247 M * Aiken what I said at 27 past the hour is what I used to get into a guest with no services -> vserver hoppy start --rescue bash 1380930278 M * Aiken I had disabled all services in hoppy to test this and that got me a shell in it 1380930406 M * user-K and with that rescue shell you were able to get a service configured to start at boot-up? 1380930601 M * user-K nice, move. 1380930837 M * user-K thank goodness for rescue mode. Still, seems like a less stressful means would have been mentioned more prominently. If it is pointed out, I am missing it for sure. 1380930858 M * Aiken it gave me a shell that allowed me to set up some services 1380930865 M * Aiken it also has networking 1380931003 M * Aiken I am out of here 1380931048 M * user-K take care, Aiken. Thank you for the help today