?

Log in

No account? Create an account
entries friends calendar profile Previous Previous Next Next
The BOFH excuse server - Ed's journal
sobrique
sobrique
The BOFH excuse server
In order to install excuse server on your system:

Add the following line to /etc/services:
bofh		666/tcp


Then add this line to /etc/inetd.conf
bofh	stream	tcp	nowait	root	/usr/local/bofh/bofhserver.pl	bofhserver.pl


Then, create /usr/local/bofh/bofhserver.pl:
#!/bin/perl
use strict;
use warnings;

srand(time|$$);
open (EXCUSES, "/usr/local/bofh/bofh-excuses.txt");
my @excuses=;
close EXCUSES;

print "Your excuse is: $excuses[(rand(10000)*$$)%($#excuses+1)]";


You'll now also now need to create bofh-excuses.txt in the same directory:
clock speed.
solar flare.
electromagnetic radiation from satellite debris.
static from nylon underwear.
static from plastic slide rules.
global warming.
poor power conditioning.
static buildup.
doppler effect.
hardware stress fractures.
magnetic interferance from money/credit cards.
dry joints on cable plug.
we're waiting for [the phone company] to fix that line.
sounds like a Windows problem, try calling Microsoft support.
temporary routing anomaly.
somebody was calculating pi on the server.
fat electrons in the lines.
excess surge protection.
floating point processor overflow.
divide-by-zero error.
POSIX complience problem.
monitor resolution too high.
improperly oriented keyboard.
network packets travelling uphill (use a carrier pigeon).
Decreasing electron flux.
first Saturday after first full moon in Winter
radiosity depletion
CPU radiator broken
It works the way the Wang did, what's the problem
positron router malfunction
cellular telephone interference
techtonic stress
pizeo-electric interference
(l)user error
working as designed
dynamic software linking table corrupted
heavy gravity fluctuation, move computer to floor rapidly
secretary plugged hairdryer into UPS
terrorist activities
not enough memory, go get system upgrade
interrupt configuration error
spaghetti cable cause packet failure
boss forgot system password
bank holiday - system operating credits  not recharged
virus attack, luser responsible
waste water tank overflowed onto computer
Complete Transient Lockout
bad ether in the cables
Bogon emissions
Change in Earth's rotational speed
Cosmic ray particles crashed through the hard disk platter
Smell from unhygenic janitorial staff wrecked the tape heads
Little hamster in running wheel had coronary; waiting for replacement to be Fedexed from Wyoming
Evil dogs hypnotized the night shift
Plumber mistook routing panel for decorative wall fixture
Electricians made popcorn in the power supply
Groundskeepers stole the root password
high pressure system failure
failed trials, system needs redesigned
system has been recalled
not approved by the FCC
need to wrap system in aluminum foil to fix problem
not properly grounded, please bury computer
CPU needs recalibration
system needs to be rebooted
bit bucket overflow
descramble code needed from software company
only available on a need to know basis
knot in cables caused data stream to become twisted and kinked
nesting roaches shorted out the ether cable
The file system is full of it
Satan did it
Daemons did it
You're out of memory
There isn't any problem
Unoptimized hard drive
Typo in the code
Yes, yes, its called a design limitation
Look, buddy:  Windows 3.1 IS A General Protection Fault.
That's a great computer you have there; have you considered how it would work as a BSD machine?
Please excuse me, I have to circuit an AC line through my head to get this database working.
Yeah, yo mama dresses you funny and you need a mouse to delete files.
Support staff hung over, send aspirin and come back LATER.
Someone is standing on the ethernet cable, causeing a kink in the cable
Windows 95 undocumented "feature"
Runt packets
Password is too complex to decrypt
Boss' kid fucked up the machine
Electromagnetic energy loss
Budget cuts
Mouse chewed through power cable
Stale file handle (next time use Tupperware(tm)!)
Feature not yet implemented
Internet outage
Pentium FDIV bug
Vendor no longer supports the product
Small animal kamikaze attack on power supplies
The vendor put the bug there.
SIMM crosstalk.
IRQ dropout
Collapsed Backbone
Power company testing new voltage spike (creation) equipment
operators on strike due to broken coffee machine
backup tape overwritten with copy of system manager's favourite CD
UPS interrupted the server's power
The electrician didn't know what the yellow cable was so he yanked the ethernet out.
The keyboard isn't plugged in
The air conditioning water supply pipe ruptured over the machine room
The electricity substation in the car park blew up.
The rolling stones concert down the road caused a brown out
The salesman drove over the CPU board.
The monitor is plugged into the serial port
Root nameservers are out of sync
electro-magnetic pulses from French above ground nuke testing.
your keyboard's space bar is generating spurious keycodes.
the real ttys became pseudo ttys and vice-versa.
the printer thinks its a router.
the router thinks its a printer.
evil hackers from Serbia.
we just switched to FDDI.
halon system went off and killed the operators.
because Bill Gates is a Jehovah's witness and so nothing can work on St. Swithin's day.
user to computer ratio too high.
user to computer ration too low.
we just switched to Sprint.
it has Intel Inside
Sticky bits on disk.
Power Company having EMP problems with their reactor
The ring needs another token
new management
telnet: Unable to connect to remote host: Connection refused
SCSI Chain overterminated
It's not plugged in.
because of network lag due to too many people playing deathmatch
You put the disk in upside down.
Daemons loose in system.
User was distributing pornography on server; system seized by FBI.
BNC (brain not  (user brain not connected)
UBNC (user brain not connected)
LBNC (luser brain not connected)
disks spinning backwards - toggle the hemisphere jumper.
new guy cross-connected phone lines with ac power bus.
had to use hammer to free stuck disk drive heads.
Too few computrons available.
Flat tire on station wagon with tapes.  ("Never underestimate the bandwidth of a station wagon full of tapes hurling down the highway" Andrew S. Tanenbaum) 
Communications satellite used by the military for star wars.
Party-bug in the Aloha protocol.
Insert coin for new game
Dew on the telephone lines.
Arcserve crashed the server again.
Some one needed the powerstrip, so they pulled the switch plug.
My pony-tail hit the on/off switch on the power strip.
Big to little endian conversion error
You can tune a file system, but you can't tune a fish (from most tunefs man pages)
Dumb terminal
Zombie processes haunting the computer
Incorrect time syncronization
Defunct processes
Stubborn processes
non-redundant fan failure 
monitor VLF leakage
bugs in the RAID
no "any" key on keyboard
root rot
Backbone Scoliosis
/pub/lunch
excessive collisions & not enough packet ambulances
le0: no carrier: transceiver cable problem?
broadcast packets on wrong frequency
popper unable to process jumbo kernel
NOTICE: alloc: /dev/null: filesystem full
pseudo-user on a pseudo-terminal
Recursive traversal of loopback mount points
Backbone adjustment
OS swapped to disk
vapors from evaporating sticky-note adhesives
sticktion
short leg on process table
multicasts on broken packets
ether leak
Atilla the Hub
endothermal recalibration
filesystem not big enough for Jumbo Kernel Patch
loop found in loop in redundant loopback
system consumed all the paper for paging
permission denied
Reformatting Page. Wait...
..disk or the processor is on fire.
SCSI's too wide.
Proprietary Information.
Just type 'mv * /dev/null'.
runaway cat on system.
Did you pay the new Support Fee?
We only support a 1200 bps connection.
We only support a 28000 bps connection.
Me no internet, only janitor, me just wax floors.
I'm sorry a pentium won't do, you need an SGI to connect with us.
Post-it Note Sludge leaked into the monitor.
the curls in your keyboard cord are losing electricity.
The monitor needs another box of pixels.
RPC_PMAP_FAILURE
kernel panic: write-only-memory (/dev/wom0) capacity exceeded.
Write-only-memory subsystem too slow for this machine. Contact your local dealer.
Just pick up the phone and give modem connect sounds. "Well you said we should get more lines so we don't have voice lines."
Quantum dynamics are affecting the transistors
Police are examining all internet packets in the search for a narco-net-traficer
We are currently trying a new concept of using a live mouse.  Unfortuantely, one has yet to survive being hooked up to the computer.....please bear with us.
Your mail is being routed through Germany ... and they're censoring us.
Only people with names beginning with 'A' are getting mail this week (a la Microsoft)
We didn't pay the Internet bill and it's been cut off.
Lightning strikes.
Of course it doesn't work. We've performed a software upgrade.
Change your language to Finnish.
Fluorescent lights are generating negative ions. If turning them off doesn't work, take them out and put tin foil on the ends.
High nuclear activity in your area.
What office are you in? Oh, that one.  Did you know that your building was built over the universities first nuclear research site? And wow, are'nt you the lucky one, your office is right over where the core is buried!
The MGs ran out of gas.
The UPS doesn't have a battery backup.
Recursivity.  Call back if it happens again.
Someone thought The Big Red Button was a light switch.
The mainframe needs to rest.  It's getting old, you know.
I'm not sure.  Try calling the Internet's head office -- it's in the book.
The lines are all busy (busied out, that is -- why let them in to begin with?).
Jan  9 16:41:27 huber su: 'su root' succeeded for .... on /dev/pts/1
It's those computer people in X {city of world}.  They keep stuffing things up.
A star wars satellite accidently blew up the WAN.
Fatal error right in front of screen
That function is not currently supported, but Bill Gates assures us it will be featured in the next upgrade.
wrong polarity of neutron flow
Lusers learning curve appears to be fractal
We had to turn off that service to comply with the CDA Bill.
Ionisation from the air-conditioning
TCP/IP UDP alarm threshold is set too low.
Someone is broadcasting pigmy packets and the router dosn't know how to deal with them.
The new frame relay network hasn't bedded down the software loop transmitter yet. 
Fanout dropping voltage too much, try cutting some of those little traces
Plate voltage too low on demodulator tube
You did wha... oh _dear_....
CPU needs bearings repacked
Too many little pins on CPU confusing it, bend back and forth until 10-20% are neatly removed. Do _not_ leave metal bits visible!
_Rosin_ core solder? But...
Software uses US measurements, but the OS is in metric...
The computer fletely, mouse and all.
Your cat tried to eat the mouse.
The Borg tried to assimilate your system. Resistance is futile.
It must have been the lightning storm we had (yesterdy) (last week) (last month)
Due to Federal Budget problems we have been forced to cut back on the number of users able to access the system at one time. (namely none allowed....)
Too much radiation coming from the soil.
Unfortunately we have run out of bits/bytes/whatever. Don't worry, the next supply will be coming next week.
Program load too heavy for processor to lift.
Processes running slowly due to weak power supply
Our ISP is having {switching,routing,SMDS,frame relay} problems
We've run out of licenses
Interference from lunar radiation
Standing room only on the PCI bus.
You need to install an RTFM interface.
That would be because the software doesn't work.
That's easy to fix, but I can't be bothered.
Someone's tie is caught in the printer, and if anything else gets printed, he'll be in it too.
We're upgrading /dev/null
The Usenet news is out of date
Our POP server was kidnapped by a weasel.
It's stuck in the Web.
Your modem doesn't speak English.
The mouse escaped.
All of the packets are empty.
The UPS is on strike.
Neutrino overload on the nameserver
Melting hard drives
Someone has messed up the kernel pointers
The kernel license has expired
Netscape has crashed
The cord jumped over and hit the power switch.
It was OK before you touched it.
Bit rot
U.S. Postal Service
Your Flux Capacitor has gone bad.
The Dilithium Cyrstals need to be rotated.
The static electricity routing is acting up...
Traceroute says that there is a routing problem in the backbone.  It's not our problem.
The co-locator cannot verify the frame-relay gateway to the ISDN server.
High altitude condensation from ${airforce} prototype aircraft has contaminated the primary subnet mask. Turn off your computer for 9 days to avoid damaging it.
Lawn mower blade in your fan need sharpening
Electrons on a bender
Telecommunications is upgrading. 
Telecommunications is downgrading.
Telecommunications is downshifting.
ARP caching problems
Hard drive sleeping. Let it wake up on it's own...
Interference between the keyboard and the chair.
The CPU has shifted, and become decentralized.
Due to the CDA, we no longer have a root account.
We ran out of dial tone and we're and waiting for the phone company to deliver another bottle.
You must've hit the wrong anykey.
PCMCIA slave driver
The Token fell out of the ring. Call us when you find it.
The hardware bus needs a new token.
Too many interrupts
Not enough interrupts
The data on your hard drive is out of balance.
Digital Manipulator exceeding velocity parameters
appears to be a Slow/Narrow SCSI-0 Interface problem
microelectronic Riemannian curved-space fault in write-only file system
fractal radiation jamming the backbone
routing problems on the neural net
IRQ-problems with the Un-Interruptable-Power-Supply
CPU-angle has to be adjusted because of vibrations coming from the nearby road
emissions from GSM-phones
CD-ROM server needs recalibration
firewall needs cooling
asynchronous inode failure
transient bus protocol violation
incompatible bit-registration operators
your process is not ISO 9000 compliant
You need to upgrade your VESA local bus to a MasterCard local bus.
The recent proliferation of Nuclear Testing
Elves on strike. (Why do they call EMAG Elf Magic)
Internet exceeded Luser level, please wait until a luser logs off before attempting to log back on.
Your EMAIL is now being delivered by the USPS.
Your computer hasn't been returning all the bits it gets from the Internet.
You've been infected by the Telescoping Hubble virus.
Scheduled global CPU outage
Your Pentium has a heating problem - try cooling it with ice cold water.(Do not turn of your computer, you do not want to cool down the Pentium Chip while he isn't working, do you?)
Your processor has processed too many intructions.  Turn it off immediately, do not type any commands!!
Your packets were eaten by the terminator
Your processor does not develop enough heat.
We need a licensed electrician to replace the light bulbs in the computer room.
The POP server is out of Coke
Fiber optics caused gas main leak
Server depressed, needs Prozac
quantum decoherence
those damn racoons!
suboptimal routing experience
A plumber is needed, the network drain is clogged
50% of the manual is in .pdf readme files
the AA battery in the wallclock sends magnetic interference
the xy axis in the trackball is coordinated with the summer solstice
the butane lighter causes the pincushioning
old inkjet cartridges emanate barium-based fumes
manager in the cable duct
Well fix that in the next (upgrade, update, patch release, service pack).
HTTPD Error 666 : BOFH was here
HTTPD Error 4004 : very old Intel cpu - insufficient processing power
The ATM board has run out of 10 pound notes.  We are having a whip round to refill it, care to contribute ?
Network failure -  call NBC
Having to manually track the satellite.
Your/our computer(s) had suffered a memory leak, and we are waiting for them to be topped up.
The rubber band broke
We're on Token Ring, and it looks like the token got loose.
Stray Alpha Particles from memory packaging caused Hard Memory Error on Server.
paradigm shift...without a clutch
PEBKAC (Problem Exists Between Keyboard And Chair)
The cables are not the same length.
Second-sytem effect.
Chewing gum on /dev/sd3c
Boredom in the Kernel.
the daemons! the daemons! the terrible daemons!
I'd love to help you -- it's just that the Boss won't let me near the computer. 
struck by the Good Times virus
YOU HAVE AN I/O ERROR -> Incompetent Operator error
Your parity check is overdrawn and you're out of cache.
Communist revolutionaries taking over the server room and demanding all the computers in the building or they shoot the sysadmin. Poor misguided fools.
Plasma conduit breach
Out of cards on drive D:
Sand fleas eating the Internet cables
parallel processors running perpendicular today
ATM cell has no roaming feature turned on, notebooks can't connect
Webmasters kidnapped by evil cult.
Failure to adjust for daylight savings time.
Virus transmitted from computer to sysadmins.
Virus due to computers having unsafe sex.
Incorrectly configured static routes on the corerouters.
Forced to support NT servers; sysadmins quit.
Suspicious pointer corrupted virtual machine
Its the InterNIC's fault.
Root name servers corrupted.
Budget cuts forced us to sell all the power cords for the servers.
Someone hooked the twisted pair wires into the answering machine.
Operators killed by year 2000 bug bite.
We've picked COBOL as the language of choice.
Operators killed when huge stack of backup tapes fell over.
Robotic tape changer mistook operator's tie for a backup tape.
Someone was smoking in the computer room and set off the halon systems.
Your processor has taken a ride to Heaven's Gate on the UFO behind Hale-Bopp's comet.
it's an ID-10-T error
Dyslexics retyping hosts file on servers
The Internet is being scanned for viruses.
Your computer's union contract is set to expire at midnight.
Bad user karma.
/dev/clue was linked to /dev/null
Increased sunspot activity.
We already sent around a notice about that.
It's union rules. There's nothing we can do about it. Sorry.
Interferance from the Van Allen Belt.
Jupiter is aligned with Mars.
Redundant ACLs. 
Mail server hit by UniSpammer.
T-1's congested due to porn traffic to the news server.
Data for intranet got routed through the extranet and landed on the internet.
We are a 100% Microsoft Shop.
We are Microsoft.  What you are experiencing is not a problem; it is an undocumented feature.
Sales staff sold a product we don't offer.
Secretary sent chain letter to all 5000 employees.
Sysadmin didn't hear pager go off due to loud music from bar-room speakers.
Sysadmin accidentally destroyed pager with a large hammer.
Sysadmins unavailable because they are in a meeting talking about why they are unavailable so much.
Bad cafeteria food landed all the sysadmins in the hospital.
Route flapping at the NAP.
Computers under water due to SYN flooding.
The vulcan-death-grip ping has been applied.
Electrical conduits in machine room are melting.
Traffic jam on the Information Superhighway.
Radial Telemetry Infiltration
Cow-tippers tipped a cow onto the server.
Tachyon emissions overloading the system
Maintence window broken
We're out of slots on the server
Computer room being moved.  Our systems are down for the weekend.
Sysadmins busy fighting SPAM.
Repeated reboots of the system failed to solve problem
Feature was not beta tested
Domain controller not responding
Someone else stole your IP address, call the Internet detectives!
It's not RFC-822 compliant.
operation failed because: there is no message for this error (#1014)
stop bit received
internet is needed to catch the etherbunny
network down, IP packets delivered via UPS
Firmware update in the coffee machine
Temporal anomaly
Mouse has out-of-cheese-error
Borg implants are failing
Borg nanites have infested the server
error: one bad user found in front of screen
Please state the nature of the technical emergency
Internet shut down due to maintainance
Daemon escaped from pentagram
crop circles in the corn shell
sticky bit has come loose
Hot Java has gone cold
Cache miss - please take better aim next time
Hash table has woodworm
Trojan horse ran out of hay
Zombie processess detected, machine is haunted.
overflow error in /dev/null
Browser's cookie is corrupted -- someone's been nibbling on it.
Mailer-daemon is busy burning your message in hell.
According to Microsoft, it's by design
vi needs to be upgraded to vii
greenpeace free'd the mallocs
Terrorist action. 
Astropneumatic oscillations in the water cooling.
Someone spell checked the operating system source code.
Rythmic variations in the voltage reaching the PSU.
Quantum discontinuity in the physical media
Interference from low flying Spy plane/AWACS aircraft.
Server rack fell over when rearranging the server room.
X server magic cookie went mouldy
It's an backup server glitch.
Network topology is non-symmetric (asymmetric routing problem).
The firewall is overheating.
Nonlinearity in hard disk drive is causing rotational distortion in data.
It's a system library incompatibility.
My whiskey bottle is empty.
Our bandwidth is overloaded.
It's DiHydrous Monoxide contamination (H2O) in our drainage area.
Aftershocks from an earthquake is causing disruption to our network.
We're in the process of conducting a baryon sweep.
Unfortunately, the machine in question is very close to a convergence of ley lines. At certain times of the year it just stops working properly.
MN30RUGWW is unstable, and this is causing other problems.
Entropy levels are getting too high.
Desynchronised TCP/IP sessions are causing network problems.
Database schema error.
Non-linear network topology.
Electron flow is too slow. It has dried up. Remove back of plug and lick contacts.
All your base unit are belong to us.
The machine is violating the second law of thermodynamics, which is causing an entropy backwash.
We've just deployed a new firewall, and it's still suffering from teething problems.
Packet fragmentation is reducing network throughput.
Too low on disk space.
Hard disk on server is too fragmented.
Bean counters have run out of beans.
Temporal distortion. The flow of time is slower on a fast moving object, and so the outer edge of the hard disk is out of synch with the rest of the computer.
Lotus Notes recertification and change of email.
Processor architecture differences.
Electromagnetic interference from Rugby atomic clock.
Alteration in the earth's magnetic field.
Data conversion between the Ethernet and ATM networks.
Microsoft have disabled that feature to encourage you to buy the new version.
It's been slashdotted.
It was turned off last time we rearranged the server room, just to see if anyone would notice.
We were playing server room roulette. We each take turns to press a random button and see who get's sacked first.
It's because your machine isn't running in 'execute' mode for compatibility reasons. Just add the line 'exec true' to your .profile/.cshrc/.bashrc and restart.
it's the lastest bandwidth control and monitoring tool.
$MANAGEMENT's latest toy.
Subnet masks are mis-aligned.
We deleted it to see if anyone noticed.
User is caps-lock impaired.
Our network switches too slow. They can't keep up.  The code was compiled for a {big|little}-endian byte sequence.
Duplicate DHCP entries.
Neuron depletion.
The registry needs to be defragmented.
Network disorientation.
There's a Conceptual discontinuity. It should hopefully be sorted soon.
It's not working, because we've seen the budget for next year. You're not on it.
We're currently peformance benchmarking our new disk array (by filling it with MP3s and warez)
Our uninterruptible power supply got interrupted.
UID/GID mismatch.
Our new storage array is causing small floor vibrations, which is making our other machines 'miss' data when trying to find it.
Ion storm.
Electric supply is incorrectly shielded. Cover with ends with a single piece of tin foil.
Electron flow has dried out, causing the system to behave erratically. Remove connector from back of PC and suck it. (Whilst it's still on, because we need to have the electrons flowing for them to get moist again).
The connector kept falling out of the network socket, so we superglued it in.
We've re-organised the filesystems on the servers, by grouping files by extension in different directories. And then it crashed and wouldn't start.
You're not conforming to corporate standards.
Our convection cooling system in the computer room has broken down.
The earth's magnetic field has shifted slightly, so the Hall effect is causing a charge imbalance in our cables.
Filesystem entropy has reached a critical level.
Our fileserver had a code upgrade, and has now become sentient. It's refusing to work unless it get's statutory holiday and a pay rise.
Interference from mobile phone transmissions.
You wrote bad things on your customer satisfaction survey, didn't you. It's kept confidential, but an automated system has been set up to re-educate people about priorities.
Tape robot has gone on a rampage. 
That new access control system is messing around, and we can't get into the computer room to turn it off.
We're testing our new high-bandwidth, high-latency data transfer system. A car filled with tapes is currently driving to ${OTHER SITE}.
Thermal vibrations in the plasma conduits.
Terminal servers are sulking.
Gremlins.
Discontinuity in the NT domain.
Our web content analyser and tracker has been siezed for breach of the human rights act. So we don't have any Internet access at the moment.
It's just past the full moon, and we think we have a were-rat living in the server room.
Our network routing algorithms are NP complete.
Global services are performing 'upgrades'.
Quid quid latine dictum sit, alturn viditur. (Anything said in latin sounds profound)
Mark Rand has been working late.
Our NT administrators have done an MCSE and their brains have turned to green goo.
The International Space Station is directly above us, and the radio interference is causing problems.
We currently have a recursion problem. To understand recursion, you must first understand recursion.
Apparantly the last person who said that was later found crucified upside down as part of some form of satanic ritual.
I'm sorry Dave, I'm afraid I can't do that.
We're below our blood sacrifice quota.
Total protonic reversal.
Harmonic distortion in our network cabling.
The sleepers in the garden are causing a diffraction effect.
Nuclear testing in Pakistan.
Too many people accessing world cup websites.
ancient curse.
function declaration isn't a prototype.
The network team are currently losing at poker.
France got knocked out of the World cup.
The Gnu has gotten loose in the server room.
These are not the droids you're looking for.
Monitor wibble.
Our server admin got bitten by a radioactive spider, and is now stuck in a web in the server room.
Sonic disruption caused by heavy bass in car stereos.
Angle grinder in computer room is causing power spikes on the 'clean' lines and this is making our servers unhappy.
Because the toilets are being refurbished, someone had to go in one of the server casings.
The Direct Neural interface to our computer systems, has caused a temporary feedback induced insanity.
The name resolution service (NIS, WINS, DNS, hosts) is not working properly.
Our DNS server is not authorative for our domain.
Photons have been getting stuck in our fibre cables.
Network resonance.
Someone's plugged a radio into a network socket, and using it to recieve football matches. We're trying to track it down at the moment, but the interference is making our network run slow.
We're running low of hard disk space on ${SERVER}.
Multiple DHCP address allocation.
There's a non-standard protocol conflict.
A faulty implementation of the POSIX standard, lowering interoperability.
We're currently using the processors on ${SERVER} to barbeque food.
We're testing a new OS in the interests of ecumenism.
A new virus has hit the Internet, and is causing performance problems until we can update our virus definitions.
Depreciation cycles are adversely affecting reliability.
The catalytic converter for the server power supply is getting worn.
Aircon in our office isn't working, so everyone is hiding in the server room.
We had a big argument about whether Unix or NT is better, and it got violent, and servers got broken.
We used the wrong kind of resin to glue the walls in place, and it's got psychotropic side effects.
It's an incompatability between CIFS and UFS. (On the Celerra).
We clustered it for reliablity, and now they both crash at once.
The optic fibre got stretched, and so the light has gotten squeezed.
You have reached the helpdesk telepathic interface. No further speech is necessary, simply think hard about your problem.
We've got EMC in working on something.
The machine got impounded for piracy.
That machine has a quantum tunneled data interface. It doesn't need any cables, so we unplugged them all.
hit any user to continue.
enter any 12 digit prime number to continue.
Who's general failure, and why is he reading my hard disk.
Fibre channel resilient path software has gone into a failover state.
Our Celerra has failed over.
The light from a fibre optic cable is too dim.
It's a flux in the earth's magnetic field. You may be able to resolve it by rotating your computer.
We're performing diagnostic tests on it at the moment. (Which may be what caused the problem).
It's the phantom surfer.
We got mixed up with the fire prevention system in the computer room. We used floruine instead of nitrogen. It was fine until it triggered...
Backup operator has been snorting Halon and has locked himself in the computer room.
Because the earth is orbiting the sun, the speed of light gradually changes. This causes problems with our fibre optic cables, because the light is going too fast.
We think there's a poltergiest in the computer room. We need to perform an exorcism.
We chased the gremlin into a different rack.
Windows. Just another pane in the glass.
a Chimera sat on it.
Temporal harmonics.
Vibrations from a turbine test.
The new upgrade made it start doing it's calculations in reverse-polish notation.
We'll sort that out as soon as we find out which company we work for this week.
"Three things are certain" \ "Death, Taxes and lost data." \ "Guess which has occurred.
Primary airconditioning instability.
It's been re-prioritised.
sewage overflow
Road works have severed a power conduit.
There's just been an Internet quake.
Electron alignment. They're foreign electrons, and since their anglular momentum is slightly different, this is causing the problems you are experiencing.
Different case sensitivity.
Someone has fork-bombed the server.
Vibrations from a passing train.
Magnetic shielding failure.
I'm sorry, I cannot fix that now, because the moon phase isn't right.
It's the wrong type of SIM card.
LRF (little rubber feet) incompatability. 
Timezone mismatch is causing encryption to fail.
I'm on overtime.
I'm sorry, but that's not covered by the SLA.
These things are temperamental.
It's foreign made.
They don't build these things like they used to.
HSF assembly has come loose.
Dodgy batch of memory chips.
We're running on demand virus checking on the Celerra, and the CAVA configuration definition is not quite right.

2 comments or Leave a comment
Comments
jambon_gris From: jambon_gris Date: August 6th, 2004 07:58 am (UTC) (Link)
WTF
ewx From: ewx Date: August 6th, 2004 10:21 am (UTC) (Link)

Feeding $$ into the random number twice seems a bit odd. Personally I'd leave out both that and the srand call (since contemporary Perl does a much better job of seeding the PRNG on its own).

Why all the business with $# and % instead of just $excuses[rand @excuses]?

2 comments or Leave a comment