2 ms·
So the "engineering teams" couldn't tail /var/log/FPRSA-R.log and see the cause of the halt? I've had servers and software that I had never, ever used before s
by johnklos 3y ago
So the "engineering teams" couldn't tail /var/log/FPRSA-R.log and see the cause of the halt?
I've had servers and software that I had never, ever used before stop working, and it took a lot less than four hours to figure out what went wrong. I've even dealt with situations where bad data caused a primary and secondary to both stop working, and I've had to learn how to back out that data and restart things.
Sure, hindsight is easy, but when you have two different systems halt while processing the same data, the list of possible causes shrinks tremendously.
The lack of competence in the "engineering teams" tells us lots about how horribly these supposedly critical systems are managed.
- slingnow 3y agoDamn, if only you had been there to instantly save the day by just running that simple command!
- johnklos 3y agoNo. That's silly. The logs would've / should've just shown that the program halted because it was confused about data. The actual commands to fix would've been quite different.
- seabass-labrax 3y agoYou're assuming that there is in fact a /var/log/FPRSA-R.log to tail - it would not at all surprise me if a system this old is still writing its logs to a 5.25 inch floppy in Prestwick or Swanwick^1. ^1: they closed the West Drayton centre about twenty years ago; I don't imagine they moved their old IBM 9020D too, if they still had it by then. My comment is nonetheless only slightly exaggerated ;)