Regression with symlinks in Linux
I originally asked about symlinks in a thread https://nxlog.co/community-forum/t/1518-wildcard-paths-not-working-with-symlinks, but was told that symlinks just didn't work. Pity. But I had a working config which worked around the issue. I'll reproduce the file structure here:
/opt/tomcat-onesite/bin
| /logs
| /etc....
|-/tomcat-anothersite/bin
| /logs
| /etc....
|-/tomcat-somewhereelse/bin
| /logs
| /etc....
|-/tomcat-etc...
|-/tomcat-logs/onesite -> /opt/tomcat-onesite/logs
/anothersite -> /opt/tomcat-anothersite/logs
/somewhereelse -> /opt/tomcat-somewhereelse/logs
/etc ....Now, with nxlog-ce-2.9.x or 2.10.x, I could define a path of /opt/tomcat-logs/* and nxlog would start. It wouldn't read any symlinks under it but it would start. Now with any of the 3.x series, nxlog won't even start if there is a symlink directly in /opt/tomcat-logs. I can sort of get by with /opt/tomcat-logs/*/* in that particular case but it doesn't help with another part of the set of the setup where there are valid files in the equivalent or /opt/tomcat-logs at the same time. How or where can I report bugs or regressions?
Hi Nick,
NXLog CE is a community driven project, bugs can be flagged at: https://gitlab.com/nxlog-public/nxlog-ce/-/issues
I am wondering if you could work around the issue by excluding the Dir containing symlinks and then adding a second Input module to read specifically from your log files FILE ‘/opt/tomcat-logs/*.log’
<Input in1>
Module im_file
FILE '/opt/tomcat-*/*'
Exclude ‘/opt/tomcat-logs/*’
Recursive TRUE
</Input>
<Input in2>
Module im_file
FILE ‘/opt/tomcat-logs/*.log’
</Input>
Cheers,
Konstantinos
