-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ace.log locked #284
Comments
Thanks for the report. This is problematic indeed. We could either make try to figure out if the permission can be somehow reset, or else use a uniquely named log file as you suggest. |
Developer notes:
|
Main code reference: ace/packages/ace-logger/src/index.js Lines 49 to 58 in 72047a2
Note that we would have to capture stream termination (final flush) using the private ace/packages/ace-logger/src/index.js Lines 11 to 38 in 72047a2
https://github.com/winstonjs/winston-daily-rotate-file/blob/6f60117cd3fd9e5cee1d8a4a8f494df3bd4e270a/daily-rotate-file.js#L80-L94 See the reason for this hack: |
Problem with "log rotate" Winston transport plugin ( |
Related (identical?) issue: #286 (comment) |
@danielweck this issue comes from wrong process killing when tentatively trying to stop the node.js freeze (see issue #286). |
Please provide the following details if possible or relevant:
ace -v
command).node -v
command).--verbose
option).After a crash of node.exe, the ace.log file in the folder ...\Daisy Ace\Log\ace.log is locked.
All future run of ace fails with permission error :
Throw er ; // Unhandled ‘error’ event
Error : EPERM : operation not pemitted, stat ‘C:\Users\VerifEpub\AppData\Local\Daisy Ace\Log\ace.log’
Would it be possible to give this ace.log a unique name per activation, so that next executions of ace are not locked ?
The text was updated successfully, but these errors were encountered: