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
After we rolled out the recent API Umbrella v0.7 updates to our servers a couple weeks ago (#180), it looks like the nightly log rotation on the servers has not been completing successfully. It looks like it's making an attempt to rotate the log files, but the resulting files are all 0 bytes.
Not much changed related to log rotation during the API Umbrella v0.7 upgrade, so this is a bit puzzling why it just cropped up. However, I have identified a few different issues that are likely contributing and fixed those in: NREL/api-umbrella-router@3dfa8b2 Locally, these fixes seem to resolve things. They are deployed now, but we'll have to wait until tonight's log rotation time to verify that it does in fact work.
The text was updated successfully, but these errors were encountered:
As a belated update, this was actually addressed by this tweak to the log rotation configuration: NREL/omnibus-api-umbrella@e30433d (Basically, the wildcard paths caused the logs to be rotated twice which led to all sort of oddities).
Since fixing that, all the log rotation has been happening as expected, with the exception of the dnsmasq logs. That process isn't re-opening logs, so it's still logging to the old log file locations. That should be simple to fix, I'd just like to wrap that up one last issue before marking this issue closed.
After we rolled out the recent API Umbrella v0.7 updates to our servers a couple weeks ago (#180), it looks like the nightly log rotation on the servers has not been completing successfully. It looks like it's making an attempt to rotate the log files, but the resulting files are all 0 bytes.
Not much changed related to log rotation during the API Umbrella v0.7 upgrade, so this is a bit puzzling why it just cropped up. However, I have identified a few different issues that are likely contributing and fixed those in: NREL/api-umbrella-router@3dfa8b2 Locally, these fixes seem to resolve things. They are deployed now, but we'll have to wait until tonight's log rotation time to verify that it does in fact work.
The text was updated successfully, but these errors were encountered: