It was always going to be a full day today. Weeks with Melbourne travel in them are always a little more hectic than any others to begin with.
One of the last meetings of my day was with a counterpart in the business. I’ve extended the concept of employee one-on-ones out to the business as well. We are after all trying to meet business needs, and the best way to keep in-the-loop in that regard is to have regular conversations.
It’s always good to catch up.
When I got back to my desk there was a message indicating the Wiki system was having some issues. Quick click. No, no dice for me either.
Login to the VM. Restart service. No dice.
Upgrade OS. Upgrade Wiki. Restart service. No dice.
This was really not the last thing I wanted to deal with for the day. One hour before my gym class starts. Login, cancel, sulk.
Have you ever tried to read and comprehend a Tomcat/Java log file full of warnings?
No, neither had I. I had no idea what I was looking for.
I looked at it two times without much luck.
Third time was luckier though.
I noticed that the most verbose messages were detailing database connection issues. Surely not? Why now? What has changed?
To keep a long story short. It turned out that the database the system was relying on had never been properly noted. The database had been handed from one team to another. Other team was consolidating, and didn’t realise the database server was being used for anything else any more. Database server gets turned off.
A quick fix.
Alas, 15 minutes too late to get me to the gym in time.
Saturday will be my next exercise now.