-
-
Notifications
You must be signed in to change notification settings - Fork 65
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disabling Log Shipping Functionality #54
Comments
Can you try |
In the meantime I've also pushed |
The extra "/' is a |
Heya, Both with new image + container_enable_scheduling:
Just something I picked up whilst looking at the logs! Core functionality is still working as expected which is good!
Happy to help test whatever needed. |
OK! I'm taking a day off today but I will look into this. I had a client request big changes to my base images and it seems I have a few kinks to work out. Overall functionality of the image should not be affected are you have noticed, I just need to untangle some of the technical debt I've added. |
No worries man! Zero rush on this, as I said, base functionality works as intended, this was just something that was picked up by chance, and realistically shouldn't make any massive impact. More an FYI rather than anything else! Have a good day off! |
Summary
today at 06:49:42 /var/run/s6/etc/cont-init.d/05-logging: line 11: /assets/cron//logrotate: No such file or directory
today at 06:49:42 2021-08-09-06:49:42 [NOTICE] ** [logging] Disabling Log Shipping Functionality
Steps to reproduce
Start container, see logs.
What is the expected correct behavior?
For log rotate to work.
Relevant logs and/or screenshots
Environment
Docker, latest
Possible fixes
Looks like line 11 has an errant "/" (/assets/cron//logrotate)
The text was updated successfully, but these errors were encountered: