18 Days Of Troubleshooting
I never thought I'd be blogging on a technical website. But here I am, taking that new step towards a change this new year.
I'd not call what follows a purely technical account, but is definitely related to my work and my work is definitely technical.
The last 18 days I was actively pursuing a small problem that surfaced at work. Normally, it is something that people (including me) would brush over considering it not worth spending time on. After all, who would want to troubleshoot a small script that becomes unresponsive after giving the desired output? Moreover, there was no attached benefit in resolving the same either.
I started posting in forums and searching for pointers on Google. People were quite generous with their feed-backs, I must say, and I began to gain clarity into the problem. There were times when it didn't look all that promising, but I'd will myself to push-on. Definitely, it paid the price.
Coming to the problem (some were posted on LQ and some on LinkedIn), it was as simple as a light-weight in-house script not behaving the way it should. To compound the irritability, it was working perfectly in test environment.
So, the general inclination was to blame the difference in the environment. Easier said.
That being so it was more irritating as I knew we had a problem, but no visibility into it to trace. That's when suggestions in the forums started clearing the way. Using truss, lsof, etc. kind of zeroed in on the problem.
And in the end it was the difference in the sudo version that was the villain.
To summarize, learned a few things on the journey and that was definitely the up-side.
I'd not call what follows a purely technical account, but is definitely related to my work and my work is definitely technical.
The last 18 days I was actively pursuing a small problem that surfaced at work. Normally, it is something that people (including me) would brush over considering it not worth spending time on. After all, who would want to troubleshoot a small script that becomes unresponsive after giving the desired output? Moreover, there was no attached benefit in resolving the same either.
I started posting in forums and searching for pointers on Google. People were quite generous with their feed-backs, I must say, and I began to gain clarity into the problem. There were times when it didn't look all that promising, but I'd will myself to push-on. Definitely, it paid the price.
Coming to the problem (some were posted on LQ and some on LinkedIn), it was as simple as a light-weight in-house script not behaving the way it should. To compound the irritability, it was working perfectly in test environment.
So, the general inclination was to blame the difference in the environment. Easier said.
That being so it was more irritating as I knew we had a problem, but no visibility into it to trace. That's when suggestions in the forums started clearing the way. Using truss, lsof, etc. kind of zeroed in on the problem.
And in the end it was the difference in the sudo version that was the villain.
To summarize, learned a few things on the journey and that was definitely the up-side.
Total Comments 1
Comments
-
Mufy,
Glad to hear you were able to resolve your issue. Seems as if we learn so much when things "Don't Work" then when things work as advertised.
I wish you continued sucess in 2011.
All the best,
IanPosted 01-03-2011 at 02:05 PM by ichase