wildcard for *.log files in generated directories #4822
Replies: 4 comments 2 replies
-
It seems to be a permission issue but I don't understand why, syslog-ng is run by user root: |
Beta Was this translation helpful? Give feedback.
-
You might have AppArmor or SELinux enabled, which limit syslog-ng to specific directories. Also, I have some distant memories, that capabilities support can prevent you from reading other user's files. The --no-caps parameter takes care of that. Or a combination of the two... |
Beta Was this translation helpful? Give feedback.
-
Hello czanik, I stopped AppArmor but it did not change anything. |
Beta Was this translation helpful? Give feedback.
-
I literally just submitted a PR to improve that ugly error message. You need to increase the max-files() option. Which limits the number of log files. The default limit is 100 files |
Beta Was this translation helpful? Give feedback.
-
Hello everyone,
I'm having an issue with syslog-ng version 4.6.0-1 on Ubuntu 22.04. I'm trying to use the wildcard-file source to detect new log files in newly generated directories, but it doesn't seem to be working as expected. Here's the configuration I'm using:
source s_src {
wildcard-file(
base-dir("/home/user/ROS2/data/live_sensor_logs/")
filename-pattern("*.log")
flags(no-parse)
recursive(yes)
follow-freq(1)
);
};
The wildcard-file source is not detecting new log files in newly generated directories. Any ideas on how to fix this?
Thanks in advance for your help!
Beta Was this translation helpful? Give feedback.
All reactions