Writes to current log file update the last modified timestamp of 6 day old log file.

Q & ACategory: QuestionsWrites to current log file update the last modified timestamp of 6 day old log file.
Jeff asked 7 months ago

Nearly every time syslog-ng writes to the current log file, it touches the log file from 6 days prior. It is not writing any data into the old log files, just updating their last modified timestamp.
Screenshot of log files
I’m not 100% sure why it stopped updating the last modified timestamp of the files from the 26th and 27th just before noon the last two days, but I think that may just be coincidence. I restarted the syslog-ng service and the VMware host’s syslog service around that time the last two days and that may have stopped the touching of old files. That being said, I restarted the services again this morning, and it is still happening.
We are currently capturing logs from 24 VMware hosts. Each host’s log files are stored in their own directory with a new file each day. This only happens to the log files from one host. All of the host names are very similar (group1-esx01…08, group2-esx01…08, group3-esx01…08), so it doesn’t seem like a filtering issue explains why it only happens to the logs located in one folder.
We use the default syslog-ng.conf file and put our configurations in a single file located in the conf.d directory. That file looks like this:
#Global network listener
source s_network {

#Dir for each host, file for each day.
destination d_vmware {

#Only get data from machines who's hostname starts with the prefixes of the various blade groups.
filter f_vmware {
    host("group1-esx*" type(glob)) or
    host("group2-esx*" type(glob)) or
    host("group3-esx*" type(glob));

#From global listener to VMware dest
log {

Thanks for your time.