Hello,
I am currently using OPNsense 21.1.7_1-amd64.
A few weeks ago I migrated the LAN of my OPNsense box from 192.168.31.0/24 to 192.168.11.0/24, thereby dropping the remote syslog server 192.168.31.2. Though, syslog-ng still tries to connect to 192.168.31.2. Since I did not find any trace of this setting in the GUI, I browsed through the config files and found /usr/logal/etc/syslog-ng.conf.d/legacy-remote.conf dated Apr 24 2020 still containing the entry.
Can I safely delete both legacy.conf and legacy-remote.conf in that directory? Is this a leftover from a previous update?
Kind regards
Boris
Export your conf file and grep for 31.2. If it's not there, it's not part of the configuration.
System, Configuration, Backups
Bart...
It may be related to this: https://github.com/opnsense/core/issues/4121
I had to do something similar when OPNsense moved to logging targets...that was quite a while back.
Quote from: bartjsmit on July 05, 2021, 10:14:31 AM
Export your conf file and grep for 31.2. If it's not there, it's not part of the configuration.
Thanks, Bart, that´s a remarkable trick!
Indeed, the rsyslog host is not in the configuration.
I moved the legacy* files away and rebooted. It worked, no more complaints about the non-existant syslog remote host.
Quote from: gpb on July 05, 2021, 04:21:18 PM
It may be related to this: https://github.com/opnsense/core/issues/4121
I had to do something similar when OPNsense moved to logging targets...that was quite a while back.
Yes, looks like an related or even the same issue.