Statuses

2004-08-22 23:26:00
Didn’t see that one coming
I found a bug in my anti-scrambler software after Jason called to inform me of a connection problem.

There is a chance equal to the percentage of packetloss that the ping will not return and cause the DSL modem to reset prematurely. The bug can be reproduced when pinging against a host where there is packet loss between you and the host. Since there are a small number of people (only Meredith and mmself) using the anti-scrambler I will write the fix later this week.

2004-08-13 09:17:00
System Alert
Update: Storm calmed. Everything back to normal.

Lightning storm near our West Coast servers. I’m getting additional backup battery systems ready to run but hopefully we won’t need them. If we lose power we can stay up no longer than 2 hours. 

Update @ 11:12 PDT: we are experiencing frequent power spikes. UPS systems are holding.
Update @ 11:27 PDT: on a plus side I am enjoying the rain. |:-)
Update @ 12:03 PDT: Spotted Firefighters patrolling our streets after some massive lightning strikes. Most of the storm has passed. Power spikes occuring less frequently.
Update @ 12:37 PDT: Storm has calmed. Power spikes have ceased. All systems normal.

2004-08-07 21:44:00
Beta One

DSL modem anti-scrambler is here! Jointly developed by b3n.org (software) and killer-server (hardware).

Operation: cron job calls script every minute. Script sends ping to router. If ping returned assume everything is fine and abort. If ping not returned assume DSL modem is down. Activate pin one on parallel port which is connected to the box. The pin triggers a relay switch which cuts power to the outlets for five seconds resetting the DSL modem. Program repeats until ping is returned.

2004-07-30 08:42:00
It’s SysAdmin Day!
Oh thank you White Mike. ::sniff:: You brought tears of joy to me eyes. |:_-) 

From: Michael Johnson <[censored]@domlev.us>
User-Agent: Mozilla Thunderbird 0.7.2
To: Benjamin Bryan <[censored]@b3n.org>
Subject: Happy SysAdmin Day

Happy SysAdmin day!

2004-07-26 18:51:00
Update: Power restored. All services normal. Monitoring for abnormalities.

—- old report —-
SYSTEM ALERT: POWER FAILURE. ON BATTERY.
We have experienced a power failure. Downtime imminent. See log for status:

~16:30. Power failure.

~17:20. Power failure reported to sysadmin (me).

~17:30. Non-critical servers powered down. Power saving status enabled. Connection tested: link good.

18:01. Primary UPS reports it can run for another 15 minutes. Re-routing all critical systems to Secondary UPS.

18:02. Secondary UPS overloads and fails without warning (The blasted Best Buy salesman told me it would work)!! All power re-routed to Primary UPS. Making procedure for blind shut-down.

18:06. Primary UPS is critical.

18:13. Primary UPS fails. Falcon goes down hard.

18:14. Silence…

18:35. Power LED activated. Systems booting. Checking disks. Power up success!

18:37. Link restored.

18:41. All services running.

Uptime Report: 230 days 23 hours and 8 minutes. Three days short of previous uptime record!! Arg!

2004-07-22 11:30:00
Can you say it right?

Here are a few computer terms I hear mispronounced by professors and professionals: 

GIF – Macintosh artists typically say GIF with a hard g but the correct pronounciation is with a soft g like JIFF.

MySQL – Windows SQL admins commonly say MySequel. But the correct way to say MySQL is My ess que el.

PNG – just say ping

Linux – Many professors at csusb use a long i… “line-ix” …Linus Torvalds, the inventer uses a short i… “lennix.”

Gnome – often people forget the g. the correct pronounciation: guh-nome