Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[MR MISTER]

...114 seconds. Fickin asthmatic server.

[MR MISTER]

And..why is my username showing twice

[Andy H]

Page created in 25.668 seconds with 12 queries.

I guess it's a bit poorly then 

[AndyRoid]

Page created in 0.045 seconds with 18 queries.

Guess it's woken up now 

[dbug]

Yep same here - was like watching paint dry, other sites/forums working at normal speed - but seems ok now

[TheBoy]

Yeah, that ongoing problem reared its head around 2:30 and 4pm this afternoon, as before, no clues as to why.

I hate spending money on the offchance it will fix it 

[Steve B]

Yeah, that ongoing problem reared its head around 2:30 and 4pm this afternoon, as before, no clues as to why.

I hate spending money on the offchance it will fix it 

You have caught that from your mate tunnie 

[TheBoy]

Yeah, that ongoing problem reared its head around 2:30 and 4pm this afternoon, as before, no clues as to why.

I hate spending money on the offchance it will fix it 

You have caught that from your mate tunnie 

Trouble is, its quite large sums (£100s) on an offchance it may resolve it. Or about £1500 that I know will resolve it.

[Andy H]

Yeah, that ongoing problem reared its head around 2:30 and 4pm this afternoon, as before, no clues as to why.

I hate spending money on the offchance it will fix it 

No clues at all?

[TheBoy]

Yeah, that ongoing problem reared its head around 2:30 and 4pm this afternoon, as before, no clues as to why.

I hate spending money on the offchance it will fix it 

No clues at all?

Nope. I was watching it do it on Saturday. Everthing running smoothly, then all of a sudden, disk latency jumping up to over 100ms for ages. Disk throughput at the time was peaking at approx 25MBps, which is fairly low.

Array diags found no hardware errors with controller, or no preemtive failure signs on the disks.

No clues in logs of hypervisor or VMs, only that processes are aborting due to disks not responding.

[TheBoy]

Should add, at 4pm today, latency jumped to 200-225ms but fell to normal sub 10ms levels after about 3 mins, which was a short enough time for everything to recover.

[Andy H]

I have no experience of hardware raid or VMs therefore I am probably way off the mark but
1. does the VM have a way of capping the disc transfer rate of each virtual machine?
2. could you be the target of a DNS attack ?

[TheBoy]

I have no experience of hardware raid or VMs therefore I am probably way off the mark but
1. does the VM have a way of capping the disc transfer rate of each virtual machine?
2. could you be the target of a DNS attack ?

1) Not capping, but prioritising. All VMs have same priority to the disks, thus one VM shouldn't easily be able to bring down others.
2) The only DNS available to the Internet is an authoritive one, not caching one, thus doesn't allow recursive lookups, thus DNS/Reflection type attacks are less successful. Said DNS server is not seeing increased traffic, and easily fits all zones in RAM, so not touching the disks much. DNS/Reflection attacks are more to swallow bandwidth rather than server resources.

Been looking for eveidence of any attacks, not found anything so far...

[Andy H]

I have no experience of hardware raid or VMs therefore I am probably way off the mark but
1. does the VM have a way of capping the disc transfer rate of each virtual machine?
2. could you be the target of a DNS attack ?

Oops, been a long crappy weekend visiting the sick
What I meant to ask was: could you be the target of a DoS attack?........... (which you answered anyway )

[Andy H]

I have no experience of hardware raid or VMs therefore I am probably way off the mark but
1. does the VM have a way of capping the disc transfer rate of each virtual machine?
2. could you be the target of a DNS attack ?

1) Not capping, but prioritising. All VMs have same priority to the disks, thus one VM shouldn't easily be able to bring down others.
2) The only DNS available to the Internet is an authoritive one, not caching one, thus doesn't allow recursive lookups, thus DNS/Reflection type attacks are less successful. Said DNS server is not seeing increased traffic, and easily fits all zones in RAM, so not touching the disks much. DNS/Reflection attacks are more to swallow bandwidth rather than server resources.

Been looking for eveidence of any attacks, not found anything so far...

I wonder if there is some 'undocumented feature' that trys to be helpful (when you aren't expecting it)