With Unomaly 3.3.8, we've made changes to where the configuration for syslog-ng is stored. Most users will not need to bother with this change, but in case you have custom configuration for syslog-ng you will need to take action to when upgrading to Unomaly 3.3.8.
In older versions of Unomaly, the syslog-ng config is stored in /etc/syslog-ng/ on the host that runs Unomaly. In 3.3.8 and later, the config is stored in a persistent docker volume, and will not be accessible from the host file system any more.
After upgrading to 3.3.8, syslog-ng will start up with default config - your existing syslog-ng config on disk will not be touched. You will need to insert that config into the docker volume.
- Inspect the config running in the syslog-ng container:
docker run --net=host --rm -i -v=syslogng:/etc/syslog-ng busybox head /etc/syslog-ng/syslog-ng.conf
- List config files for the container. Your changes will most likely be to files in /etc/syslog-ng/conf.d/
docker run --net=host --rm -i -v=syslogng:/etc/syslog-ng busybox find /etc/syslog-ng
- Move your existing config to the container volume.
unomaly stop docker cp /etc/syslog-ng/syslog-ng.conf syslogng:/etc/syslog-ng/ docker cp /etc/syslog-ng/conf.d/* syslogng:/etc/syslog-ng/conf.d/ unomaly start