[Deskaheh-sysadmin] My latest theory on Deskaheh problems

[john milton]

I have explored several ideas in the last week to try and figure out 
what is going "down" with Deskaheh and it's outages. The best I can come 
up with at this point is that it may be as simple as overloading it's 
internet connection. I would like to ask for comments on this, having no 
sudo access or such like it's the best I can do, here we go...

Deskaheh shares a T1 line with dissent.buffaloimc.org and the New york 
branch of the A.C.L.U., and perhaps other servers, I don't know....

 From here on i base my comments on an eyeball reading of the traffic 
graphs found here:

http://nysindy.org/mrtg

The most recent down happend at noon Saturday, which is the normal peak 
time for Deskaheh server load except for Sunday lunch, it's a sine wave 
with a daily period that peaks at mid-day american time and bottoms at 
midnight, no big surprise there.

A T1 line can carry 1.5 megabits per second.

At noon Saturday Deskaheh reports:
82.5 KBytes / second X 8 = 660 Kbits / second outbound and
17.7 KBytes / second X 8 = 142 Kbits /second inbound

at the same time dissent reports:
~= 11 KBytes / sec. X 8 =   88Kbits /second outbound and
a few say 3 kbytes/sec outbound = 24 kbits per second outbound

thats .914 megabits out of an allowable 1.5 , and makes no allowance for 
what the ACLU server or whatever else is on this line was using,

The Deskaheh sites are responding well now (midnight saturday) Test of 
Hypothosis: I would expect them to crash again at noon tomorrow when 
load ramps up.

Can we increase the resolution and logging of the traffic monitors and 
add whatever else is on the T1 to confirm or deny this?

Comments?
-- 
Peace: John Milton

Email: john at johhnmilton.ca
Web: johnmilton.ca

PGP encrypted mail is welcome, my key is here: 
http://www.hwcn.org/~aa492/security.htm