Error when logrotate and compressed a log file being tailed

Hi @iccicci ,

I have my stream config as follow: { interval: '10s', compress: (source, dest) => 'cat ${source} | gzip -c9 > ${dest}.gz', maxFiles: 3 }

I was monitoring the log file with tail -F, when it comes to the rotation time, it did not generate the .gz file and the writing stream was stopped

I have received the error message as follow: { [Error: EPERM: operation not permitted, stat 'C:\git\***\log\access.log'] errno: -4048, code: 'EPERM', syscall: 'stat', path: 'C:\\git\\***\\log\\access.log' }

Error [ERR_STREAM_DESTROYED]: Cannot call write after a stream was destroyed at doWrite (_stream_writable.js:411:19) at writeOrBuffer (_stream_writable.js:399:5) at RotatingFileStream.Writable.write (_stream_writable.js:299:11)

[iccicci]

Hi @FelixChow ,

first of all, which version of the package are you using?

From the error reported it’s clear we are facing a permissions problem. Looking at the filename it seems to be the not rotated filename while the reported problem is about rotation; this makes me think you have right privileges on that file. What I don’t know is tail behavior under Windows. Could it be the root cause of the problem? Do you have the same experience without the tail command in execution?

As last (but this is not related with your problem), in your compressor function you are adding ".gz" at the destination file and you are using history (maxFiles: 3); the package remembers the destination file it generates, it can’t know you are adding that extension; so history won’t work as expected. If you want to add an extension to the filename it’s better to use a filename generator function doing that and keep untouched the destination file name in the compressor function.

Please let me know, iCC

[yi]

I have just experienced the same issue, and found that is causes by race condition of workers. When deployed with pm2, the application has no master, and all cluster workers are writing to the same file path, which conflicts with each other.

To solve this problem, I added a leader election to workers to make sure only one worker can rotate the log file. I hope this rts module could provide manually start/stop rotation.