1455669814 Q * dustinm` Quit: Leaving
1455670215 J * dustinm` ~dustinm`@2607:5300:100:200::160d
1455670743 Q * fstd Remote host closed the connection
1455670795 J * fstd ~fstd@xdsl-81-173-186-65.netcologne.de
1455683493 Q * fstd Remote host closed the connection
1455683666 J * bzed_ ~bzed@bzed.netrep.oftc.net
1455683943 Q * bzed Ping timeout: 480 seconds
1455683947 N * bzed_ bzed
1455684134 J * fstd ~fstd@xdsl-81-173-186-65.netcologne.de
1455696028 J * Ghislain ~aqueos@adsl1.aqueos.com
1455698343 Q * aj__ Ping timeout: 480 seconds
1455698525 J * Ghislain1 ~aqueos@adsl1.aqueos.com
1455698552 J * nikolay ~Nikolay@199.91.137.248
1455698573 Q * Ghislain Read error: Connection reset by peer
1455699804 J * aj__ ~aj@fw.gkh-setu.de
1455700177 M * nikolay morning fellows
1455700252 N * Bertl_zZ Bertl
1455700264 M * Bertl morning folks!
1455700269 J * misc-- ~misc@123-243-234-69.static.tpgi.com.au
1455700291 M * misc-- hello... how can I start a command at boot from within a guest?
1455700322 M * Bertl write a runlevel script for it?
1455700373 M * misc-- ah yeah... I thought that rc.local was supposed to run at boot
1455700454 M * Bertl it really depends on the init system and how the scripts are written
1455700714 M * misc-- ahhh I remember now what happened
1455700758 M * misc-- rc.local is really delayed to run, there is something at startup causing it (the guest) to not start up as quick as it should
1455700844 M * misc-- sleep 20    is ran and then sleep 40... I think this is part of vserver if a service doesn't start properly (something to do with networking I think)
1455700991 M * Bertl probably some script needs some adjustments for a guest
1455700992 M * Ghislain1 my guest start fine and wuick, perhaps you enabled a service in a guest that cannot start and  lock it all ?
1455701007 M * Ghislain1 ..until it times out
1455701216 M * misc-- that's what I'm thinking, but every service is starting correctly... I'll compare it to some other guests
1455701318 M * misc-- looks like they're all doing it, and they all run different services. It does it before any service starts. All I get in the syslog is "Feb 17 20:25:57 talend failsafe: Failsafe of 120 seconds reached." 
1455701346 M * misc-- it's not really causing any issues, but would be interesting to know what's causing it. Seems to sleep just after the networking service, and before any other services
1455703204 M * Bertl ubuntu?
1455703808 M * Bertl in any case, most likely scripts waiting for plymouth
1455703822 M * Bertl (which should be disabled inside a guest)
1455704310 M * daniel_hozac why are you running the networking service in a guest?
1455704340 M * Bertl probably because the guest was not properly cleaned up
1455708251 J * distemper_ ~user@2001:4dd0:ff00:9484:3f2f:58c8:2997:3dd2
1455708252 Q * distemper Read error: Connection reset by peer
1455708253 N * distemper_ distemper
1455713591 Q * gamingrobot_ Remote host closed the connection
1455713789 Q * yang Quit: Free yourself with Free Software, join www.FSF.org
1455713943 Q * fstd Remote host closed the connection
1455714034 J * fstd ~fstd@xdsl-87-78-81-165.netcologne.de
1455716424 J * Gremble ~Gremble@cpc87151-aztw31-2-0-cust755.18-1.cable.virginm.net
1455716445 Q * Gremble 
1455717507 J * gamingrobot_ sid10990@id-10990.highgate.irccloud.com
1455719536 M * nikolay fellows, is it possible to run CentOS guest on non-cent/rhel host? Example: Gentoo Host + CentOS 7 guest?
1455719777 J * Gremble ~Gremble@cpc87151-aztw31-2-0-cust755.18-1.cable.virginm.net
1455720238 M * Bertl nikolay: host and guest are pretty independant
1455720274 M * Bertl so, as long as the distro you want to run "works" in a guest and with the kernel you got on the host, there is no problem to mix
1455720309 M * Bertl debian guests run fine on centos hosts and vice versa
1455720359 M * Bertl similar with gentoo, the only critical parts are init systems which don't work in a guest and kernels which are incompatible with certain distros
1455720540 M * nikolay debian guests work fine, indeed
1455720565 M * nikolay I have attempted with some centos7 and looks I cannot make it build using method yum ...
1455720587 M * nikolay I will investigate a bit more... thank you Bertl 
1455720786 M * Bertl in case all else fails, build a system in a virtual machine and then create a guest from that
1455720815 M * Bertl note that you have to get rid of systemd, as it doesn't play nice with a Linux-VServer container
1455721390 Q * aj__ Ping timeout: 480 seconds
1455722833 M * nikolay thanks
1455722840 M * nikolay the yum method fails like: 
1455722851 M * nikolay ERROR You need to update rpm to handle:
1455722852 M * nikolay rpmlib(BuiltinLuaScripts) <= 4.2.2-1 is needed by filesystem-3.2-20.el7.x86_64 ...
1455722858 M * nikolay http://pastebin.com/M8UNbUmv
1455724023 M * Bertl probably your host's rpm is too old
1455724054 M * Bertl i.e. updating the rpm binary on the host is likely to fix it
1455724428 J * aj__ ~aj@88.128.80.110
1455725062 M * nikolay sounds like a plan, updating to app-arch/rpm-4.12.0.1
1455725071 M * nikolay will report back
1455727800 Q * aj__ Ping timeout: 480 seconds
1455728743 M * Bertl off for a nap ... bbl
1455728745 N * Bertl Bertl_zZ
1455728818 J * _nikolay ~Nikolay@70.34.55.20
1455729186 Q * nikolay Ping timeout: 480 seconds
1455729581 Q * _nikolay Ping timeout: 480 seconds
1455732644 Q * Gremble Quit: I Leave
1455735707 J * yang yang@yang.netrep.oftc.net
1455735721 M * yang Hi, is there still no stable patch for the 4.x kernel series ?
1455741468 N * Bertl_zZ Bertl
1455741471 M * Bertl back now ...
1455741482 M * Bertl yang: nope
1455742169 Q * neofutur Quit: leaving
1455742219 J * neofutur neofutur@gabrielle.ww7.be
1455744596 Q * Ghislain1 Quit: Leaving.
1455745693 M * misc-- Bertl: yeah I was also suspecting plymouth but that service is disabled
1455745770 M * misc-- and regarding network services starting while booting, I don't know what I was talking about then. There should have been no networking services configured to start (except for "upstart-socket-bridge which may not even be network related). Probably right though in that there is a network service trying to start. I will check it out
1455745844 M * Bertl forget the service, most likely plymouth is hard coded into the runlevel script
1455745863 M * Bertl i.e. there will be several checks and calls to the deamon with timeouts
1455745890 M * Bertl best grep for plymouth in the rc.* scripts and see what happens if you comment out the relevant code
1455746999 J * aj__ ~aj@x590d68fa.dyn.telefonica.de
1455748498 Q * l0kit Quit: leaving
1455748520 J * l0kit ~1oxT@0001b54e.user.oftc.net
1455749104 M * misc-- ah I see, ok. I did a grep in /etc/init.d (ubuntu) but nothing turned up. In /etc/init though there is some entries. I can't look in to it at the moment but will check later. Thanks
1455749812 M * misc-- it's in /etc/init/failsafe.conf where the problem is. There are is a bunch of sleeps (20, 40, 59). It waits for plymouth to start. I don't really understand what the point of it is. I guess when plymouth is available that the failsafe gets killed at some point but because in my case plymouth doesn't start, it continues with its sleeps. I don't even need plymouth as there is no slash screen on these guests. I'll see if I can disable it
1455751099 M * misc-- ok what fixed it was..... in the vserver's /etc/init/rc-sysinit.conf, up the top there is: start on (filesystem and static-network-up) or failsafe-boot
1455751108 M * misc-- I replaced it with: start on filesystem
1455751144 M * misc-- (also removed all the /etc/init/plymouth* stuff as it's not needed). Will add this to my doco. Ahhh feels much better now, have had that niggling issue for a while
1455751211 M * misc-- I think the later ubuntu version's guests have a slightly different rc-sysinit.conf, as the older ones have a different "start on....." line
1455751227 M * misc-- which wouldn't have caused an issue before
1455752787 M * Bertl probably