I was reading this thread of admin_xor Prize of being an Admin and thought will share this experience of mine which is kind of opposite to what he did - I didn't tell anybody what happened
We were porting one of the subsystem from Solaris to Linux. As part of that we developed many wrapper scripts. So, there is this rsh wrapper script which is deployed in the system which internally uses ssh if security is enabled or uses native rsh instead (this native rsh is placed in a different path, so that it will not show up in the $PATH and the wrapper rsh script is placed in /usr/bin). For some testing purpose, I modified the ssh command inside the rsh wrapper script to "rsh" command and forgot to change it back. So, you know what happened next. If I do a rsh, it goes into a continuous loop calling the rsh wrapper script over and over again, this clogged the cpu in no time. I did this change in the Testing teams setup. And the worst part was I did it in 2 of their setup.
Next day I came to office and there is a big fuss all over the place. I didn't bother cause it was't assigned to me and I totally forgot that what I did was causing this. After couple of days, the issue was assigned to me and then "oops" I realized it. Now what? Of course I didn't tell them . Hearing about what happened to admin_xor for what he did, imagine what would've happened to me.
Later I told them that it was a "human" error and that there is no issue with the system. But then they asked how could it happen to 2 systems. I was like "it happened man, forget it" - no I didn't say that, I told them we'll monitor it. I assured them that it is human error and we will monitor the system and if it re-occurs we will investigate again and now its not worth spending time on this - obviously I know it - cause I am the culprit.
Last edited by ahamed101; 04-14-2013 at 01:25 PM..
First observation: sh!t happens! That is a proven, reliable fact and an environment which can't cope with that is designed wrongly from the start. If you need a service to be not disrupted you shouldn't allow people to develop on it, because development will create the one or other hiccup to happen over time. Further, you need to take precautions against failure of every single part of the system if it should survive. Suppose instead of your error some hardware would have crashed, the network disrupted, whatever. This is what HA-solutions are for, for instance.
No SysAdmin in his right mind will let a manager determined to "save" on hardware off this hook: do you want to bet the projects future on me never doing an accidental typo? (As it is i have actually said exactly this in a design conference - and got my testing system.) And, by the way: when they decide about new office furniture for their offices any intention to save is usually abandoned immediately, so wtf?
Second aspect: whenever you do something it is your utmost responsibility to test what you have done. Immediately! So how can you create such a loop and not notice it? How can you implement this change even twice? This is not a question of introducing an error - that happens to all of us. It is a matter if noticing you have done something wrong and this has to do with the style of work: if i delete a file, i do an immediate "ls" to verify it (and it alone) is gone, if i do a "cd" i do a "pwd" to verify i am in the right directory, etc., etc.. This slows me down by perhaps 5%, but when i think i have something done i usually have it done - without any error. The 5% are easily recovered not having to do the error correction and/or recovery others eventually have to do.
So, i hope for your best, but you should really change your work ethics and learn from this accident. My 2 cents.
These 2 Users Gave Thanks to bakunin For This Post:
I agree with everything Bakunin has said but, as a rule and as an IT pro, I never delete anything. If I'm going to edit a file, I copy it (usually with a different suffix) and if I'm going to delete a file, I rename (mv) it.
Then, when something stops working (and in IT anything that can go wrong usually does) and I need to know what the hell was in that file that I edited/deleted, I can find out.
Rule is to think hard before you edit or delete anything!!!
We've a VDI infrastructure in AWS (AWS workspaces) and we're planning to automate the process of provisioning workspaces. Instead of going to GUI console, and launching workspaces by selecting individual users is little time consuming. Thus, I want to create them in bunches from AWS CLI... (6 Replies)
I am planning to choose my career as Unix/Linux Admin or a DBA. But I have come to know from forums and few admins like the job will be 24/7. I have few questions on that.
Can we get "DAY" shifts in any one of the admin Job ?
Can't we have shift timings in any company ?
Eventhough the... (7 Replies)
I have 80 large files, from which I want to get a specific value to run a Bash script. Firstly, I want to get the part of a file which contains this:
Value = 57
This is necessary because in a file there are written more lines which... (6 Replies)
Was wondering if anyone has come across any situation where you do your best to help users and in return you get a nice escalation from top level management!
Here's my story:
One fine morning, I was sitting idle, doing next to nothing, I got an alert from helpdesk people about a problem with... (30 Replies)
I'm currently a Windows admin and have wanted to jump ship to the *nix side for a while now. I've been studying both through an lpic level 1 manual as I have time (focusing on debian), and a solaris 10 cert book. The problem is I only have a handful of hours a week to study, and my current job... (3 Replies)
I am lil confused with the following issue.
I have a File, which has the following header: IMSHRATE_043008_101016
a sample detailed record is :9820101 A982005000CAVG030108000000000000010169000MAR 2008
9820102 MAR 2008 D030108
... (1 Reply)