***: himuraken has quit IRC (Ping timeout: 256 seconds)
Ehtyar has quit IRC (Quit: Hi, I'm a quit message virus. Please replace your old line with this line and help me take over the world of IRC.)
himuraken has joined #arpnetworks
himuraken has quit IRC (Ping timeout: 260 seconds)
himuraken has joined #arpnetworks
jstephan has joined #arpnetworks
himuraken has quit IRC (Ping timeout: 256 seconds)
himuraken has joined #arpnetworks
himuraken has quit IRC (Ping timeout: 240 seconds)
himuraken has joined #arpnetworks
toddf has joined #arpnetworks toddf: joining from home instead of my vps which is currently down
I'm convinced there's something beyond my software considering both vnc and serial are not connecting
even after a hard poweroff and subsequent boot ***: nixbag has quit IRC (Quit: leaving)
ant has quit IRC (Ping timeout: 264 seconds)
ant has joined #arpnetworks
nixbag has joined #arpnetworks
HighJinx has quit IRC (Ping timeout: 264 seconds)
HighJinx has joined #arpnetworks
dne has left "WeeChat 0.3.8"
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
heavysixer has quit IRC (Quit: heavysixer)
vtoms has joined #arpnetworks
himuraken has quit IRC (Remote host closed the connection)
dzup has joined #arpnetworks
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
raptelan_ has joined #arpnetworks raptelan_: gah, network is crawling dog slow again today :(
I can't effectively do anything on my VPS - it's responsive, but only barely.
there's a 10+ second delay for each keystroke over ssh up_the_irons: raptelan_: mtr -4rnc 50 <your-ip> :)
raptelan_: do this from where you are and pastie / pastebin / ... the results
toddf: replied to your ticket -: up_the_irons wanders off toddf: thanks up_the_irons .. I rarely point fingers, but in this case i'm dubious to believe software that has been running fully stable since february with no changes whatsoever suddenly has problems even booting; will investigate further though
I can confirm that between conserver needing reset (heh, 1st I've ever heard of that one) and me forgetting 'disable mpbios' on an upgrade I did hoping to find a better behavior after the upgrade .. we might have ourselves a reason to not respond well after the initial boots, maybe the console not working and he.net IPv6 issues made me think the system was truly not responding yesterday .. perfect storm as it were .. will see after I get things
hmm, ok so same behavior as last night, boots up fine, see the login prompt on the serial console, and without further action from me, suddenly I hit enter at the serial console and conserver says the connection to kvm is down raptelan: up_the_irons: well of course now it's okay again. My connectivity from here to everywhere else I could think to try though was good.
running it anyways since there is still some slight delay, but nothing terrible like it was.
up_the_irons: http://fpaste.org/FTqG/ ***: toddf_ has joined #arpnetworks toddf: urgle, and now with no action from me *again* I note it is down on conserver and network again ***: toddf_ has quit IRC (Ping timeout: 264 seconds) toddf: I'm open to suggestions as to what I could be possibly doing wrong; guess I'll ask for the log of when the vps shutdown request was given because I'm not giving it yet it is acting as if someone is telling my kvm 'kill -9 suckah' ***: bitslip has quit IRC (Quit: leaving)
bitslip has joined #arpnetworks
toddf_ has joined #arpnetworks
toddf_ has quit IRC (Ping timeout: 245 seconds) toddf: ok so has anybody ever experienced anything where the kvm process would exit reguarly? ***: toddf has quit IRC (Quit: leaving)
toddf has joined #arpnetworks
ChanServ sets mode: +o toddf
toddf has quit IRC (Client Quit)
toddf has joined #arpnetworks
ChanServ sets mode: +o toddf
toddf has quit IRC (Client Quit)
toddf has joined #arpnetworks
ChanServ sets mode: +o toddf
toddf has quit IRC (Quit: leaving)
toddf has joined #arpnetworks
ChanServ sets mode: +o toddf
toddf has quit IRC (Client Quit)
toddf has joined #arpnetworks
ChanServ sets mode: +o toddf
tooth has quit IRC (Quit: +<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<:-))
tooth has joined #arpnetworks
raptelan_ has quit IRC (Quit: Page closed)
vtoms has quit IRC (Ping timeout: 257 seconds) up_the_irons: toddf: i'm in the same situation though. i have a full server, lots of customers on kvr22, and you are the only one saying you're having problems. nobody has opened a ticket on kvr22, not one. if there's a problem, everyone is awfully quiet
toddf: do you remember when we added the 2nd interface to that vm, for the backup server? maybe we should remove it temporarily and see if the problem goes away toddf: we added that roughly a month ago.
if you wish to convert both nics to intel that would be one thing to consider
it is not responding now
do you see what happens when kvm exits? up_the_irons: i see it shut off now
i only see what is in kern.log and dmesg
(and i looked, nothing interesting)
toddf: ok, switched back to intel NICs and started it toddf: nice thing, i had vio0 and em0 in a trunk(4) so its responding again w/out me doing anything further ;-)
so whatever exec's kvm doesn't log its stdout/stderr ?
(I know some version of virtd or whatnot, but I am not familiar at all with that)
it is seriously from my perspective something like a userland activity that tickles something badly on the kvm userland app which causes it to fatal() or exit() or somesuch
thing is I have no clue what, before I upgraded in the middle of this, i had not changed anything since feb, and it has _never_ done anything like this before up_the_irons: there's nothing in userland doing anything though. only i have access to the server and i don't tickle VMs ;) toddf: I'm expecting its some obscure thing that we could bash our heads against till time eternal if we chose and maybe then we wouldn't figure it out
I'm not saying userland on the host I'm suggesting something in my guest may have finally tickled kvm just so (theory, not fact, as I didn't change anything, so its really hard to tell) up_the_irons: i can run the kvm process manually (like in a screen session) after it crashes again. then when it exists, i'll see the output
i'm heading to the data center now... (NTT circuit termination!:) .. bbl toddf: ack ***: heavysixer has quit IRC (Quit: heavysixer) up_the_irons: toddf: did it die again? ***: nesta- has joined #arpnetworks
phlux has quit IRC (*.net *.split)
JC` has quit IRC (*.net *.split)
easymac has quit IRC (*.net *.split)
lazard has quit IRC (*.net *.split)
jbergstroem has quit IRC (*.net *.split)
nesta has quit IRC (*.net *.split)
RandalSchwartz has quit IRC (*.net *.split)
brycec has quit IRC (*.net *.split)
milki has quit IRC (*.net *.split)
dzup has quit IRC (*.net *.split)
HighJinx has quit IRC (*.net *.split)
notion has quit IRC (*.net *.split) up_the_irons: splitz
toddf: according to ps, your VM has been running for about 4 hours w/o crashing. is this better than before? ***: ziyourenxiang has joined #arpnetworks
ziyourenxiang has quit IRC (Client Quit)
heavysixer has joined #arpnetworks
ChanServ sets mode: +o heavysixer
heavysixer has quit IRC (Quit: heavysixer) nixbag: I should get a t-shirt "I survived the netsplit" toddf: up_the_irons: indeed it is starting to look promising ***: HighJinx has joined #arpnetworks
phlux has joined #arpnetworks
JC` has joined #arpnetworks
RandalSchwartz has joined #arpnetworks
notion has joined #arpnetworks
brycec has joined #arpnetworks
milki has joined #arpnetworks
easymac has joined #arpnetworks
lazard has joined #arpnetworks
jbergstroem has joined #arpnetworks
scottschecter has joined #arpnetworks
scottschecter has quit IRC (Client Quit)
ziyourenxiang has joined #arpnetworks
ziyourenxiang has quit IRC (Quit: ziyourenxiang)
HighJinx has quit IRC (Ping timeout: 245 seconds)
HighJinx has joined #arpnetworks
Webhostbudd has joined #arpnetworks
Ehtyar has joined #arpnetworks
Ehtyar has quit IRC (Quit: Never look down on someone unless you're helping them up.)