1389141428 Q * Ghislain1 Quit: Leaving.
1389142802 Q * fisted Remote host closed the connection
1389142826 J * fisted ~fisted@xdsl-87-78-185-149.netcologne.de
1389143156 Q * zerick Remote host closed the connection
1389146626 N * l0kit Guest2950
1389146631 J * l0kit ~1oxT@0001b54e.user.oftc.net
1389147031 Q * Guest2950 Ping timeout: 480 seconds
1389149953 Q * MC71 Ping timeout: 480 seconds
1389153712 Q * SteeleNivenson Quit: Leaving
1389159331 Q * FireEgl Ping timeout: 480 seconds
1389159891 J * FireEgl ~FireEgl@173-23-77-153.client.mchsi.com
1389160326 Q * geos_one Quit: ChatZilla 0.9.90.1 [Firefox 26.0/20131215185306]
1389162035 M * Bertl off to bed now ... have a good one everyone!
1389162083 N * Bertl Bertl_zZ
1389162309 J * thierryp ~thierry@home.parmentelat.net
1389162893 Q * thierryp Remote host closed the connection
1389162914 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:4060:12cd:fd8:3270
1389163399 Q * thierryp Ping timeout: 480 seconds
1389164757 Q * yang Remote host closed the connection
1389165314 J * yang yang@yang.netrep.oftc.net
1389166289 J * thierryp_ ~thierry@eduroam-192a.sophia.inria.fr
1389166339 J * Ghislain ~aqueos@adsl1.aqueos.com
1389168661 Q * ntrs Remote host closed the connection
1389169153 J * ntrs ~ntrs@vault08.rosehosting.com
1389171098 J * thierryp ~thierry@zebra.inria.fr
1389171521 Q * thierryp_ Ping timeout: 480 seconds
1389181874 Q * thierryp Remote host closed the connection
1389183088 Q * ircuser-1 Ping timeout: 480 seconds
1389184355 J * thierryp ~thierry@zebra.inria.fr
1389184839 Q * thierryp Ping timeout: 480 seconds
1389185618 J * ircuser-1 ~ircuser-1@35.222-62-69.ftth.swbr.surewest.net
1389186001 Q * fisted Remote host closed the connection
1389186030 J * fisted ~fisted@xdsl-84-44-224-124.netcologne.de
1389186820 J * thierryp ~thierry@zebra.inria.fr
1389188665 Q * thierryp Remote host closed the connection
1389188725 J * thierryp ~thierry@zebra.inria.fr
1389189054 J * MC71 ~MadCow@0001c2a3.user.oftc.net
1389189919 N * Bertl_zZ Bertl
1389189923 M * Bertl morning folks!
1389189954 M * fback evening :D
1389190742 M * thierryp Bertl: morning
1389190752 M * thierryp best wishes to all
1389190774 M * thierryp a quick question about ubuntu raring
1389190809 M * thierryp I have a rather custom setup for running vservers in a fedora14 host
1389190828 M * thierryp and, I can create ubuntus up to quantal, but when trying with raring I am getting 
1389190855 M * thierryp + linux64 vserver 2014.01.08-myslice-r exec arch
1389190855 M * thierryp vcontext: pivot_root(): Invalid argument
1389190862 M * thierryp does this ring any bell ?
1389190895 M * Bertl no, but it seems that the installer? tries to pivot_root
1389190917 M * Bertl which is certainly something you do not want to do in a guest or chroot
1389190951 M * Bertl or, as it seems to get reported from vcontext? it might be a problem with the guest dir?
1389190977 M * Bertl did you run the install with --debug? and what kernel/patch/util-vserver versions are involved?
1389191137 M * thierryp ok so the kernel is 
1389191138 M * thierryp 2.6.32.11-162.vs2.3.0.36.29.4.fc12.x86_64
1389191164 M * thierryp which is home brewed
1389191180 M * thierryp but was built some years ago so I cannot remember every detail off the top of my head
1389191209 M * thierryp util-vserver is util-vserver-0.30.216-15.x86_64
1389191229 M * thierryp I do not think I ran the install with --debug
1389191262 M * thierryp what does pivot_root do as a matter of fact ?
1389191411 M * thierryp oh I see
1389191429 M * Bertl well, I would first suggest to update both kernel and tools for testing
1389191475 M * Bertl and see if the problem persists ... if so, upload the --debug output of such an install and paste the url
1389191557 M * thierryp OK I see
1389191560 M * thierryp thanks for the tip
1389191571 M * thierryp I'll chime back in when I have the date
1389191576 M * thierryp cheers
1389191585 M * thierryp the data I mean
1389191832 M * Bertl no problem, you're welcome!
1389194652 N * Bertl Bertl_oO
1389194981 Q * thierryp Remote host closed the connection
1389195297 J * thierryp_ ~thierry@zebra.inria.fr
1389195363 J * thierry__ ~thierry@zebra.inria.fr
1389195364 Q * thierryp_ Read error: Connection reset by peer
1389195368 Q * thierry__ Remote host closed the connection
1389195392 J * thierryp_ ~thierry@zebra.inria.fr
1389195422 J * Ghislain1 ~aqueos@109.190.11.159
1389195715 Q * Ghislain Ping timeout: 480 seconds
1389196458 Q * thierryp_ Remote host closed the connection
1389196783 Q * MC71 Ping timeout: 480 seconds
1389197402 Q * Ghislain1 Read error: Connection reset by peer
1389197734 J * Ghislain ~aqueos@adsl1.aqueos.com
1389198212 J * zerick ~eocrospom@190.187.21.53
1389198395 P * undefined 
1389199075 J * MC71 ~MadCow@0001c2a3.user.oftc.net
1389200703 J * bonbons ~bonbons@2001:a18:203:e401:cdf2:404f:5623:3b51
1389201742 J * SNy23 ~mfr@v22013091823214688.yourvserver.net
1389201751 M * SNy23 Hey guys.
1389201805 M * SNy23 I do have a vServer instance and have reason to believe it is based on linux-vserver (not sure, I rent it and the support is unwilling to tell me).
1389201826 M * Ghislain easy to tell just do this (let me one sec)
1389201837 M * SNy23 I do have a problem with not being able to connect with ssh to it: "2: fork failed: Resource temporarily unavailable".
1389201868 M * SNy23 Now, I have found some old threads that suggest there might have been problems with the way process limit was counted towards.
1389201887 M * SNy23 The support says they can't help etc.
1389201921 M * SNy23 So I would require some professional opinion about the possibility of this being a problem on the host.
1389201926 M * Ghislain oh if you clannot ssh
1389201935 M * Ghislain it will be hard to tell ;p
1389201938 M * Ghislain more 
1389201941 M * SNy23 No shit.
1389201943 M * Ghislain more /proc/self/ninfo
1389201970 M * Bertl_oO (could be hidden)
1389201979 M * SNy23 Also, support tells me they have no local console to connect to.
1389201980 M * Ghislain  more /proc/self/vinfo
1389201980 M * Ghislain if you have these and NID/XID are > 1 then this is a guest
1389201987 M * SNy23 I find that very hard to believe.
1389202012 M * Bertl_oO well, support is obviously not interrested in supporting anything :)
1389202025 M * Ghislain yep but so many hide, you can also read uname see if they let in the kernel name "vs" like  3.4.65-vs2.3.3.9
1389202030 M * Bertl_oO SNy23: just for the record, what provider is that?
1389202128 M * SNy23 Anyway, the problem has occurred in the past, but did not persist long.
1389202144 M * SNy23 Now, though, I haven't been able to connect since Saturday.
1389202153 M * SNy23 And probably longer, have only tried then.
1389202173 M * Bertl_oO if the limit is reached (inside the guest) you won't be able to connect
1389202183 M * Bertl_oO doesn't matter what technology is used
1389202184 M * Ghislain without any connexion or control panel that give you access this will be impossible to help, the porvider name can give an hint on the tech used
1389202188 M * SNy23 To recap, I fould some references to process counting being wonky and considering kernel level threads.
1389202194 M * Bertl_oO do you have a way to 'reset' the guest?
1389202198 M * SNy23 I did.
1389202204 M * SNy23 Numerous times.
1389202210 M * Bertl_oO via web interface or so?
1389202227 M * SNy23 No connection, then immediately upon connection, the fork message.
1389202245 M * SNy23 Yes, but apparently it rebooted, or at least it killed my screen + irssi.
1389202261 M * Ghislain they are linux your vps, not freebsd or other ?
1389202261 M * SNy23 I do think it restarts, FWIW.
1389202278 M * SNy23 The host? I have no idea. THe guest, yes.
1389202358 M * Bertl_oO on the web sites, they offen various xen based solutions
1389202370 M * Bertl_oO what product did you pick?
1389202384 M * SNy23 It is ancient, so to speak.
1389202401 M * SNy23 It is not Xen, this I was told.
1389202418 M * Bertl_oO so maybe they want to make you switch
1389202424 M * SNy23 Hence, from the net, I gathered it would be linux-vserver.
1389202426 M * Bertl_oO (and thus reduced the limits)
1389202464 M * Bertl_oO there are many solutions nowadays besides xen, so without any indication I would not assume anything
1389202465 M * SNy23 If the thing truely restarts, then NOTHING will be running as my user right after the start.
1389202487 M * SNy23 Surely, lowering the limit so far that the first fork will fail is... well, fail.
1389202501 M * Bertl_oO but even if you are on a probably outdated Linux-VServer installation, you can not change the limits from inside the guest
1389202513 M * SNy23 As I said, the thing is ancient, so "nowadays" doesn't count.
1389202521 M * Bertl_oO so if you do not have a control panel to adjust (some of) those limits
1389202542 M * Bertl_oO and the provider doesn't want to adjust them for you, you're screwed anyway
1389202560 M * SNy23 Again, the reason I asked here was that I found discussion of there being problems with the way the limit worked(works?) inside guests.
1389202571 M * SNy23 Maybe someone would know?
1389202608 M * Bertl_oO I would definitely know, the question is more, what information are you looking for
1389202622 M * SNy23 It had been an intermittent problem up until now (a few time the last year, no longer than an hour or two).
1389202640 M * SNy23 So I think it might be related to something outside the guest running wild.
1389202648 M * Bertl_oO do you have a kernel version from the time when you still had access?
1389202664 M * SNy23 It looks as if I was doomed to wait until it resolves itself, now. :/
1389202672 M * SNy23 No.
1389202700 M * Bertl_oO so, Linux-VServer exists since 12 years, that covers 2.4 kernels as well as 2.6 and 3.x
1389202725 M * SNy23 The kernel, this I was told, is 3.9.4.
1389202749 M * Bertl_oO 3.9.x uses the mainline cgroup system for limits
1389202786 M * Bertl_oO (also means it cannot be that old :)
1389202808 M * SNy23 The guest is, I have told you I have no idea about the host.
1389202827 M * Bertl_oO guest is not involved in the limits
1389202850 M * SNy23 Yeah, I thought that might be the case.
1389202856 M * SNy23 So, it IS an issue on the host?
1389202870 M * SNy23 Or what do I take from that, now?
1389202898 M * Bertl_oO assuming the information is correct, and it actually is Linux-VServer (no indication so far)
1389202914 M * Bertl_oO I'd say your limits are too low, or your guest is running too much
1389202936 M * SNy23 As far as I can tell, my guest is currently running zilch as the user I want to connect as.
1389202953 M * Bertl_oO user doesn't matter, the limits are per guest
1389202964 M * SNy23 Really?
1389202970 M * SNy23 Per guest?
1389202972 M * Bertl_oO for example, if you have a limit of 100 processes
1389202977 M * Bertl_oO (per guest)
1389202999 M * Bertl_oO then it doesn't matter if you try to connect as jonny or jim or even root
1389203046 M * SNy23 Well, that is strange, then. As I CAN use imaps, smtps, apache etc. just fine. Right now.
1389203054 M * SNy23 But I cannot ssh to it.
1389203075 M * Bertl_oO so maybe imap, smtp, apache is already running and not creating new processes
1389203098 M * SNy23 I am not sure cyrus+postfix work this way, though.
1389203124 M * Bertl_oO do you have an ssh key on the guest?
1389203128 M * SNy23 Postfix has lots of filters etc. that I think it spawns on request. (Guesswork).
1389203131 M * SNy23 Yes.
1389203139 M * Bertl_oO try to run a command instead of a login
1389203142 M * SNy23 But neither password nor public key word.
1389203144 M * SNy23 *work
1389203153 M * SNy23 Tried that. Doesn't work.
1389203159 M * SNy23 Neither does scp.
1389203161 M * Bertl_oO same message?
1389203165 M * SNy23 Yes.
1389203229 M * Bertl_oO well, if restarting the guest via web interface doesn't work
1389203240 M * SNy23 It seems to restart, all right.
1389203253 M * SNy23 Services are unavailable for ~15s.
1389203258 M * SNy23 THen they come back.
1389203267 M * SNy23 But it still doesn't work.
1389203270 M * Bertl_oO okay, can you ssh in during this time?
1389203279 M * SNy23 No.
1389203285 M * SNy23 Because the service is gone.
1389203316 M * Bertl_oO did you try? ssh is usually started quite early
1389203326 M * SNy23 Yes, I tried multiple times.
1389203364 M * Bertl_oO not much you can do without support of the provider then
1389203396 M * SNy23 Aye. SOL.
1389203408 M * SNy23 Thanks, anyway.
1389203423 M * Bertl_oO no problem
1389203757 M * SNy23 Oh, one other thing.
1389203778 M * SNy23 They tell me there is no console for them to connect to "locally".
1389203786 M * SNy23 I have a hard time believing this.
1389203802 M * Bertl_oO assuming it is Linux-VServer, then that is technically correct
1389203824 M * Bertl_oO i.e. there is no 'console', but the hoster can enter the guest
1389203829 M * SNy23 You can't use ttyS${num} or something?
1389203841 M * Bertl_oO basically what you do on the host is
1389203850 M * Bertl_oO vserver <NAME> enter
1389203855 M * Bertl_oO and you're inside the guest
1389203893 M * Bertl_oO (where you can do stuff like reading logs or looking at processes, etc)
1389203946 M * SNy23 Hm.
1389204002 M * Bertl_oO Linux-VServer uses process isolation, i.e. virtualization at the kernel level not the machine level
1389204002 M * SNy23 Don't know about you, but that sounds an awful lot like a "local" console to me.
1389204034 M * Bertl_oO it is comparable to having a chroot and using chroot to enter it
1389204036 M * SNy23 Yeah, I am only familiar with earlier UML releases.
1389204045 M * Bertl_oO (just more separation and isolation)
1389204046 M * SNy23 But the principle is clear.
1389204096 M * Bertl_oO while it can be done (i.e. use tty/pts for some kind of console) it is not typically used in Linux-VServer setups
1389204170 M * SNy23 OK, thanks. That is good to know.
1389204355 M * Bertl_oO you're welcome!
1389206615 J * geos_one ~chatzilla@80.123.185.198
1389209169 J * thierryp ~thierry@2a01:e35:2e2b:e2c0:3c1f:6a7f:ce9f:fbf2
1389210693 Q * Guy- Quit: rebooting, see you on the other side
1389211238 J * Guy- ~korn@elan.rulez.org
1389216003 Q * MC71 Remote host closed the connection
1389216220 J * MC71 ~MadCow@0001c2a3.user.oftc.net
1389217518 Q * ntrs Ping timeout: 480 seconds
1389217794 J * ntrs ~ntrs@vault08.rosehosting.com
1389219295 Q * thierryp Remote host closed the connection
1389219315 J * thierryp ~thierry@home.parmentelat.net
1389219483 J * thierryp_ ~thierry@2a01:e35:2e2b:e2c0:7c6e:5f6d:3864:8dfb
1389219483 Q * thierryp Read error: Connection reset by peer
1389219513 Q * bonbons Quit: Leaving
1389219964 Q * thierryp_ Ping timeout: 480 seconds
1389223183 M * Bertl_oO off to bed now ... have a good one everyone!
1389223193 N * Bertl_oO Bertl_zZ