Question about logging file error

[eremika0000]

I got this in the cmd while scanning files, does this mean the file was not properly scanned?

DEBUG: dvr_scan video_joiner.read(): End of current video, loading next: C:\Users\eremi\Downloads\DVR\1761426244839.mp4
Detected: 116 | Progress: 40%|█████████████▏ | 1306074/3261852 [5:48:13<9:27:09, 57.47 frames/s]--- Logging error ---
Traceback (most recent call last):
File "logging[handlers.py](http://handlers.py/)", line 74, in emit
File "logging[handlers.py](http://handlers.py/)", line 179, in doRollover
File "logging[handlers.py](http://handlers.py/)", line 115, in rotate
PermissionError: [WinError 32] The process cannot access the file because it is being used by another process: 'C:\Users\eremi\AppData\Local\DVR-Scan\Logs\dvr-scan-app.log' -> 'C:\Users\eremi\AppData\Local\DVR-Scan\Logs\dvr-scan-app.log.1'
Call stack:

[Breakthrough]

What version of DVR-Scan are you running? This was an issue in v1.7 when you run multiple instances of DVR-Scan at once, but it should be fixed in v1.8+. Can you confirm if you're still running an older version, and if so, updating to a newer one fixes it?

This error doesn't affect scanning, but it does mean log messages won't be stored in your logfile correctly.

(Context: This was fixed in #227.)

[eremika0000]

I haven't updated in a few months so I believe I am using 1.7, I'll go update it soon. Are you able to tell me if this means it wasn't properly scanned and I'd have to rescan those files that were mentioned by the cmd

…

On Wed, Oct 29, 2025, 6:49 PM Brandon Castellano ***@***.***> wrote: What version of DVR-Scan are you running? This was an issue in v1.7 but should be fixed in v1.8+. Can you confirm if you're still running an older version? (Context: This was fixed in #227 <#227>.) — Reply to this email directly, view it on GitHub <#247 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNWWLHDVO3JR7CBP4ATDDOL32FG7ZAVCNFSM6AAAAACKQFT2KKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOBSGEYDMMY> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[Breakthrough]

The file should still have been scanned. There could still have been errors during scanning, but they would still show up in the command output. If you did not see any, you can assume it was scanned correctly.

You can safely ignore this particular log message. It only affects writing the log messages out to disk, the program should run fine otherwise.

[eremika0000]

Ok thanks

…

On Wed, Oct 29, 2025, 6:55 PM Brandon Castellano ***@***.***> wrote: The file should still have been scanned. There could still have been errors during scanning, but they would still show up in the command output. As long as you did not see any other errors during scanning, you can safely ignore this particular log message. It only affects writing the log messages out to disk, the program should run fine otherwise. — Reply to this email directly, view it on GitHub <#247 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/BNWWLHBGXU3HNXGU6LYM4OL32FHXXAVCNFSM6AAAAACKQFT2KKVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTIOBSGEYDQNY> . You are receiving this because you authored the thread.Message ID: ***@***.***>