You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes it happens that the droplet-agent update script fails with an error. This is reported by cron, but without any detail about the nature of the error (only "exited with return code 1"), yet we are not able to find this detail in the droplet-agent.update.log file because this file is overwritten by the script every time it runs.
If there was a one-time error in the middle of the night, even though it may have solved in the subsequent runs, it would still be useful to know the reason of the error.
So my proposal is to have the update script append to the log file instead of overwriting it every time.
Moreover, I would like to propose to review the scripts so that timestamps are written in the log file as well, this is important for troubleshooting.
Than you!
The text was updated successfully, but these errors were encountered:
Sometimes it happens that the droplet-agent update script fails with an error. This is reported by cron, but without any detail about the nature of the error (only "exited with return code 1"), yet we are not able to find this detail in the
droplet-agent.update.log
file because this file is overwritten by the script every time it runs.If there was a one-time error in the middle of the night, even though it may have solved in the subsequent runs, it would still be useful to know the reason of the error.
So my proposal is to have the update script append to the log file instead of overwriting it every time.
Moreover, I would like to propose to review the scripts so that timestamps are written in the log file as well, this is important for troubleshooting.
Than you!
The text was updated successfully, but these errors were encountered: