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
Many scripts run by cron, such as so-rule-update and so-elasticsearch-indices-delete, overwrite their logfile on each run, so a history of what the script has done is lost. Changing the redirect from '>' to '>>' means historical runs will remain in the logfile. Furthermore, the bash-ism '&>>' redirects for stdout and stderr, eliminating the need for the separate '2>&1'.
Note: this does not address retention and rotation of these logfiles. With them growing in size after this patch, they could get large quickly if not rotated regularly.
The text was updated successfully, but these errors were encountered:
Are the elasticsearch and idstools patch still useful? I haven't found where logs from so-elasticsearch-indices-delete-delete or logs from so-rule-update are saved.
I can resubmit a PR with just those two commits if you'd like, but I'm not sure even that would log anything for so-elasticsearch-indices-delete-delete.
Many scripts run by cron, such as so-rule-update and so-elasticsearch-indices-delete, overwrite their logfile on each run, so a history of what the script has done is lost. Changing the redirect from '>' to '>>' means historical runs will remain in the logfile. Furthermore, the bash-ism '&>>' redirects for stdout and stderr, eliminating the need for the separate '2>&1'.
See #12943 for proposed fix.
Note: this does not address retention and rotation of these logfiles. With them growing in size after this patch, they could get large quickly if not rotated regularly.
The text was updated successfully, but these errors were encountered: