up_the_irons: still doing orders?
au: starting soon
Escable: if it's just teamspeak, you could easily get away with a $10 vps
up_the_irons: ok :)
up_the_irons: for the whois records on the IP, do you have a privacy option?
au: ARIN policy states I can put "Private Customer" for name and "Private Residence" for the address, but the city,state,postal code, and country must be disclosed
ok cool
hmmmm I wonder if NZ DNC have a similar rule for domains
looks like no
done :)
mattx86: do you have larger than a /30 IP block?
up_the_irons: nah, I picked the free /30
mattx86: then i'll have to expand your existing /30 to a /29 ($5 per month).  we don't give out multiple /30's
oh ok
hm.. let me think about it for moment
ok, yeah, that's fine
ok
will my current IP on the existing vps change?
not that it matters
if ARIN needs my info, I'd prefer to be listed as private
up_the_irons: It would be cool for our accounts to have a "SWIP privacy" checkbox which sets the SWIP info to the "Private Customer/Private Residence" values without having to muck about with temporary account info changes.
mattx86: what's your current IP? i'll see if there is space above it (usually there is, since we use rfc 3531 allocation method)
pilgrimd: send that to support@arpnetworks.com and i'll put it in the suggestion box
up_the_irons: pm'ed
mattx86: yes, there is space
ah, cool
mattx86: you'll want to change your subnet mask from 255.255.255.252 to 255.255.255.248 on your existing vps once i send you the 2nd one
up_the_irons: ok
up_the_irons: thanks again garry
mattx86: np!
hmm
heya. my host at arp just rebooted for no apparent reason... anything going on?
host in questions is river.styx.org
I'm getting some failed pings too
do you know which kvm you're on?
RandalSchwartz: no clue
ww: what is your vnc host?
ww: that'll be your kvm host
oh yeah, my nagios is going nuts
starting about 10 minutes ago
kvr13
21 packets transmitted, 21 packets received, 0.0% packet loss
for both v4 and v6 on my vps, on kvr14
so something is odd
came back up pretty much immediately... but
15:33  up 8 mins, 0 users, load averages: 0,00 0,11 0,08
I need to chat with Garry about how he's monitoring these things
he uses nagios... ;-)
no - I mean to what depth
because I definitely have hiccups across all my boxes at once, weirdly
like the box can't even ping itself
nagios is .. finicky .. wrt helper timing
nagios -> exec -> helper .. if helper doesn't do its thing within a short period of time, it presumes failure
yeah, but I get correlating ad hoc tests that
I've had real hardware scenarios (swapping, busy server, etc) cause false positives to the point that I gave up using nagios altogether.
not sayin there isn't something to this, but a host not being able to ping itself islikely more that the disk io and/or cpu didn't churn the helper app fast enough to satisfy nagios rather than the box actually not being able to ping itself
well - let's just pretend I didn't say nagios
things seem to break
but spooky.  like unable to ping self
you can login and run ping manually I bet it works every time
I suspect the virtual network interface is marginal
maybe under stress or something
I'm just sayin nagios needs a 'helper timed out' notification rather than 'ALERT WE HAD FAILURE TO PING' notification
the box pinging an IP on its ethernet nic would be the local os processing the packets, nothing to do with kvm pretending to be ethernet hardware
therefore a failure to ping the local IP can only be a timeout failure due to io or cpu being 'otherwise busy' .. or a firewall on the local box failure, I trust the 2nd not to be the case
as I said, other indicators too.
please stop fixating. :)
a kvm host chewing cpu or disk whether via another vps or native app is most likely the reason for your nagios alerts. just my $.02 anyway.
yeah, I fixated. moving on .. ;-)
I used to have really weird ICMP problems on a Verio VPS, but I suspect that was more due to the way they do virtualized FreeBSD with their own jail implementation
is the ssh serial console running at 9600 bps?
probably is :)
anyone know what to do when my VNC session to the console will output just fine (bootup/reboot), but sometimes will not accept/display input?
perhaps I should throttle my upload(s) at the moment
yep, its 9600.
ah n/m, it was an issue of specifying which console(s) to use, I think.  works now on both VNC and SSH
just realized I was using tightvnc 1.3.10.. really old stuff.  no wonder it was so slow ;)
mattx86: that's weird, because in the software world, usually newer means slower
true