1461651497 J * Ghislain ~aqueos@adsl1.aqueos.com 1461655391 Q * derjohn_mobi Ping timeout: 480 seconds 1461656388 M * Bertl_oO off to bed now ... have a good one everyone! 1461656394 N * Bertl_oO Bertl_zZ 1461656982 J * derjohn_mobi ~aj@fw.gkh-setu.de 1461657028 Q * padde Remote host closed the connection 1461657094 J * padde ~padde@patrick-nagel.net 1461657666 J * nikolay ~Nikolay@HOST.255.3.ixos.de 1461661982 J * kimegede ~kimegede@77.66.3.165 1461662061 M * kimegede Hi, can I have a host running an different OS version than the guest? (Host Debian 6.0, Guest 8.2) 1461662522 M * kimegede Getting "Failed to read /proc/cmdline. Ignoring: No such file or directory" 1461663320 M * CcxCZ kimegede: distribution version doesn't mean much. You can run the guest iff the userspace is compatible with the kernel version/features. Kernel is what's shared between the guests, userspace is all theirs. 1461663376 M * kimegede Thanks, but how do I know if the kernel version is ok? Can I somehow test that? 1461663480 M * CcxCZ Probably look up which kernel versions the libc supports. 1461663853 M * kimegede So I shall `uname -r` to see the kernel the host is using? (2.6.32-5-vserver-amd64) and then look up if that one can be used proper with Debian Jessie - is that what you mean? 1461663876 M * kimegede The guest is actually up running - but cron doesn 1461663913 M * CcxCZ Yes, that's what I meant. 1461664011 M * kimegede doesn't* work - and getting the /proc/cmdline error after upgrading the guest from Debian 6 -> Debian 8. 1461664035 M * kimegede I found this one: https://archive.debian.net/squeeze/linux-image-2.6.32-5-vserver-amd64 it seems like this is "squeenze" support? 1461664280 M * CcxCZ I'm lost when it comes to Debian version numbers. 1461664341 M * kimegede Okay that's fair, I just upgraded Debian - but I fear if I need to upgrade the host as well, right now - as it's having 6 other vservers on it running the older Debian version. 1461664707 M * CcxCZ Having not so ancient kernel is generally advisable. FWIR there were quite a few important security fixes since then. 1461664830 M * CcxCZ You probably want to update the util-vserver too. The behaviour you are seeing might be bug in that which was resolved long time ago. 1461665835 M * gnarface of course, it could also just be a feature not compiled in to your host's existing kernel too 1461665848 M * gnarface (in theory) 1461665877 M * gnarface that's probably worth checking because you wouldn't want to go through all the trouble of compiling a newer kernel only to find that its still missing the option 1461665924 M * gnarface hmm. 2.6.32 sounds pretty old for jessie though 1461665944 M * gnarface upgrading very likely required, just not necessarily 1461666920 M * kimegede I will love to get it upgraded as it's so old - but I also fear 5 other vservers will break if I'm doing that. 1461667187 M * kimegede gnarface: It seems to be the cron there isn't doing anything. That's currently the only problem I'm seeing. 1461667253 M * gnarface kimegede: oddly, i had a similar problem in wheezy. just reinstalling the cron package after the guest was started fixed it 1461667283 M * kimegede I have tried that as well. (apt-get install --reinstall cron) 1461667295 M * gnarface eh, it was worth a try 1461667313 M * kimegede https://gist.github.com/kimegede/5b3dd1468c2956422d0aadb1fef7ff8e 1461667358 M * gnarface although, just an fyi debian support also told me that skipping a release during upgrades is generally considered suicide 1461667390 M * gnarface following the rules, you should have upgraded from debian 6 to debian 7 first, before upgrading to debian 8 1461667412 M * kimegede I did upgrade like that! 1461667431 M * gnarface oh. well i was just throwing that out there because you didn't specify 1461667452 M * gnarface the error does seem like a kernel version or config related issue 1461667485 M * kimegede Can it be any of the `bcapabilities` or `ccapabilities` preventing this? 1461667515 M * gnarface uh, sorry the answer to that is beyond my level of expertise 1461667528 M * gnarface maybe? 1461667602 M * gnarface kimegede: you looked through the tips on the FAQ right? 1461667628 M * gnarface kimegede: i see bcapabilities mentioned amongst the things to check 1461667656 M * gnarface kimegede: http://linux-vserver.org/Frequently_Asked_Questions#Cron_is_not_working_on_my_guest_system_.28which_is_Debian.29._How_can_I_fix_it.3F 1461667877 M * kimegede Thanks gnarface, I did actuall look there. Have done the first 2 steps. Will look again on step 3 & 4. 1461668084 M * kimegede As I understand it step 3 & 4 is only if you want to limit it right? 1461668678 M * gnarface that's not quite what i'm gathering about #4, which seems to be about disabling limits altogether 1461668700 M * gnarface it doesn't sound very safe 1461668946 M * kimegede It do sound a bit funky... 1461670308 M * gnarface kimegede: in a few hours the smart people will probably wake up and they should have more solid advice for you, sorry i'm out of ideas 1461670343 M * kimegede Thanks gnarface. I appreciate both yours and CcxCZ help 1461671993 N * Bertl_zZ Bertl 1461671994 M * Bertl morning folks! 1461672003 M * kimegede Morning folks 1461672022 M * kimegede Bertl :) 1461672025 M * gnarface 'morning Bertl 1461672044 M * kimegede gnarface: /var/log/syslog also tells me "Cannot make/remove an entry for the specified session". 1461672065 M * gnarface hmm 1461672079 M * kimegede That's more useful, so will Google that :) 1461673821 Q * Ghislain Ping timeout: 480 seconds 1461673890 J * Ghislain ~aqueos@adsl1.aqueos.com 1461674225 Q * Ghislain Read error: No route to host 1461676148 J * Ghislain ~aqueos@adsl1.aqueos.com 1461676163 Q * kimegede Quit: Linkinus - http://linkinus.com 1461676298 J * Ghislain1 ~aqueos@adsl1.aqueos.com 1461676322 Q * Ghislain Read error: No route to host 1461676509 J * Ghislain ~aqueos@adsl1.aqueos.com 1461676512 Q * Ghislain1 Read error: No route to host 1461676525 M * Bertl off for now ... bbl 1461676526 N * Bertl Bertl_oO 1461676730 Q * Ghislain Read error: No route to host 1461676734 J * Ghislain ~aqueos@adsl1.aqueos.com 1461676881 J * Ghislain1 ~aqueos@adsl1.aqueos.com 1461676881 Q * Ghislain Read error: Connection reset by peer 1461677185 Q * Ghislain1 Read error: No route to host 1461677238 J * Ghislain ~aqueos@adsl1.aqueos.com 1461681223 J * fstd ~fstd@xdsl-87-78-18-28.netcologne.de 1461684616 Q * AlexanderS Remote host closed the connection 1461684620 J * AlexanderS ~Alexander@home.zedat.fu-berlin.de 1461685312 M * yang Hello, (standard question) what is the problem that there is no 4.x kernel series patch yet ? 1461687452 Q * nikolay Remote host closed the connection 1461688119 M * Bertl_oO yang: the problem is that the script which updates the main page doesn't handle 4.x yet 1461688135 M * Bertl_oO i.e. look at the directory, you will find 4.x patches there 1461689019 Q * derjohn_mobi Ping timeout: 480 seconds 1461689666 M * yang ah ok 1461697341 M * Bertl_oO off for a nap, maybe back later ... 1461697342 N * Bertl_oO Bertl_zZ 1461700332 J * bonbons ~bonbons@2001:a18:225:a801:e52c:1d20:a894:cfd9 1461701714 J * Wermwud ~wermwud@69-29-150-18.stat.centurytel.net 1461703342 J * Long_yanG ~long@15255.s.time4vps.eu 1461703619 Q * bonbons Quit: Leaving 1461703700 Q * LongyanG Ping timeout: 480 seconds 1461705179 Q * Wermwud Quit: Going offline, see ya! (www.adiirc.com) 1461705786 J * derjohn_mob ~aj@p578b6aa1.dip0.t-ipconnect.de 1461706028 Q * Ghislain Quit: Leaving. 1461708137 Q * derjohn_mob Ping timeout: 480 seconds 1461715156 J * fstd_ ~fstd@xdsl-87-78-9-17.netcologne.de