-
Notifications
You must be signed in to change notification settings - Fork 2
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
Rsyslogd fails to start in staging #37
Comments
Debug log:
|
The solution to this can be found in this issue discussion. Adding I'll try to figure out some resonable number to set here. The documentation is here Ideally, we should add a volume for the syslog configs in the docker compose env, so things like these could be edited. And/or make it configurable as a template on build. |
I guess another possible way to fix this would be to use This is really outside my expertise tbh, comments are welcome. |
Confirmed as fixed in staging with the |
After some fixes, I've gotten rsyslogd working nicely on this image in dev. However, when attempting to deploy
sodar-docker-compose
in staging, I get the following:I'm not yet sure if this is a problem within the image, the Docker Compose environment or our Ansible playbook, but opening the issue here for starters.
I'm guessing it should be somehow environment related, but the only "moving part" I can think of are the logging volume mounts, so I probably better start with verifying those. Also I need to see what kind of workarounds others have proposed online regarding this error.
The text was updated successfully, but these errors were encountered: