While rotating log file gives EPERM: operation not permitted, stat error about rotating-file-stream HOT 7 CLOSED

Hi @ankityadav1 ,

I can't say if the error depends on the problem I can see, but for sure your options are so strange:

    maxSize: '5M',
    size: '5M',

this means "please rotating-file-stream, rotate my log file every 5MB and do not allow more than 5MB for all the rotated files".

I suggest to remove (or increase the value of) maxSize.

Please let me know if this cleaning action solves your problem, if yes you discovered a strange bug.

Thank you,
iCC

from rotating-file-stream.

Hi iCC,

Thanks for responding.
My requirement is to compress the rotated log files and the existing log files are mostly larger in size.
Hence the code says maxSize 5MB and for the new log files, I want rotating-file-stream to generate slog files of 5MB max.
And it works!!
It compresses the log files after rotation and its hardly few bytes after that.

Lastly I tried your suggestion and removed maxSize option but still facing the same issue.

Do you want me to paste any more of my code here?
It seems this is a bug.

from rotating-file-stream.

No thanks, no other code is required, @ankityadav1 . If possible could you please cut/paste the stack trace of the EPERM error?

BTW, are you sure you have full write access on LOG_PATH ?

Thank you

from rotating-file-stream.

Yes I have full access to the folder.
Here you go!
The below screenshot is when I try to open the log file after the EPERM error:

And this screenshot refers to the ERR_STREAM_DESTROYED message after the log file rotation occurs and my code tries to push data to the log file:

from rotating-file-stream.

Hi @ankityadav1 ,

thank you but there are not the info I need: the first screenshot gives no info while the stack trace of the ERR_STREAM_DESTROIED is irrelevant.

I need the stack trace of the EPERM error. The output of this code should contain the info I need.

stream.on('error', err =>
  console.log('RFS error -->', err)
)

from rotating-file-stream.

The error has no stack trace.
It is just:
EPERM: operation not permitted, open error '{path to log file/file.log}'

from rotating-file-stream.

I'm sorry @ankityadav1 , but I'm not able to reproduce (so to investigate) the error.
If you could share with me a minimal reproducible example I can try to investigate it.

from rotating-file-stream.