Monday

[sobrique]

It's monday.
I was working yesterday:
I moved around a few network switches so our labs had more performance
This included a crash course in cisco configuration, but it worked fine.
I moved a SGI origin. (And had to reseat cables and system boards)
Helped a workmate with a problem on the NT domain (sheah, as if I have any clue about that).
All successful, and checke out ok.
Just prior to leaving, tidied up the computer room (my boss dislikes cables strewn everywhere.

Came in this morning.
Labs network was down, and they were upset.
After a spot of headbanging, checking configs etc. we noticed that there was no signal down the fiber.
Yep, when tidying, I managed to shut the door on the fiber, and it didn't work no more. Doh.

SGI license manager didn't come up properly. That was sorted easily enough.

The NT domain problem is getting worse. Some moronMSCE has created a 'site' domain called 'domain'. This is, apparently, really stuffing up our WINS database replicas. We're still sorting it, and it's looking like drastic measures are needed - WINS is 'masterless' so a stuffed replica replicates to all of them. If you clear one, it replicates back again. So we're going to have to take 'em down, one by one, and clear them _all_ before starting up again.

Sigh.

And I've had an archive request - an engineer needing $IMPORTANT FILE that we archived. I've been searching semi-frantically for it, because it wasn't on our archive or backup.
There's a reason for that. After we did the "Well, $OTHER FILE was a previous revision, and so I might be able to take that and update it", I restored that one, and went trolling through our optical disk library (it's big, badly indexed, and horrible). I was vaguely panicing, because ... well engineering get very upset when we 'lose' drawings. 30 year contracts, large amounts of money, that kind of thing.

Well, it turns out it had never existed in the first place. (ARGH!)

And now i've got a new 60Gb VMWare virtual machine to create. As soon as possible, because the guy is going to switzerland tomorrow lunchtime.

I can't believe it's only 11:45 on monday. Really I can't.

Comments

[eithnepdb.livejournal.com]

I love when people used reserved words as names.

I once had a developer name a variable in a db "date" - which of course completely stuffed the processing....

[sobrique.livejournal.com]

Oh it gets better. The major problem we're having is that we have _two_ domains called 'domain' within the company. One is in china, and one is in eastleigh.

And it was never a problem before, because there was a static mapping, and firewalls protected that static mapping from reaching the rest of the empire.

Now of course, we're implementing 'Active Directory' (which is a new swear word around here). So the firewalls were changed to allow some windows communication. Which stuffed everything up.

[eithnepdb.livejournal.com]

Oh you know one of the most idiotic things about the .NET /Active Directory schema is the the idea of local dlls.

wtf....

So now you can have multiple copies of the same dll in any directory structure - try keeping all of them up to date.

ARGH!

[sobrique.livejournal.com]

Thankfully, I'm still getting away with "Sorry, mate, I'm just a Unix Admin".

Of course, that's starting to get me evil glares from workmates, particularly when the latest AD crisis kicks off...

[eithnepdb.livejournal.com]

As a programmer it worries me to no end - under the old architecture you had one of each dll and registered it so there was an entry in the registry. That way when you called it the OS knew where to look for it.

Now its completely up for grabs.

GAH!

[jorune.livejournal.com]

Dll hell, tedious, obnoxious, loathsome. It is one of the astounding mysteries of the IT world, Microsoft has shedloads of really talented people and they manage to produce awful nastiness like this.

[eithnepdb.livejournal.com]

Well its even worse when you're working on a project with other developers - they keep dropping the same dll (different versions) into different locations so the code isn't working against the same one all the time.

[xarrion.livejournal.com]

'Tis the season, it seems.

Have a read of todays NS - at least you're not alone :)

http://www.newscientist.com/news/news.jsp?id=ns99996706

[jorune.livejournal.com]

Support work, some days it's lovely, other days are just pain without an end in sight. I hope you managed to solve your problems.