tfabris
commented
5 years ago I looked at this some, and it's a stumper. It's not the usual expected thing of needing to exit from a sub-function in Bash. I honestly didn't expect this line to get hit at all.
The line comes after the "exit 0" inside the For-Next loop where it is testing the network.
Possibilities:
- Maybe "Exit" doesn't break out of for-next loops? There is some indications here that maybe it doesn't. https://stackoverflow.com/q/17810562/3621748
- But if that were true, then I would expect there to be more instances of me seeing this exact error message. Every time there is a network problem, I should have seen this error message, and I haven't.
- Maybe this happened when I updated the script file, and it was a line-alignment problem with the already-executing script? I do indeed see that I made a checkin on 2019-09-29 at 2:49pm PDT, which was a Sunday where I might be home that afternoon, and so I might have committed the code and copied it directly into production at that time. The commit did indeed change the number of lines in the file by a small amount. So in theory this could be the root cause.
I'm going to chalk it up to that latter thing for now, and keep an eye out for it.
I saw this in the log:
Error System 2019-09-29 14:54:15 SYSTEM CrowCam Controller - Unexpected program behavior. This program was expected to have exited before this line was reached.