-
Notifications
You must be signed in to change notification settings - Fork 48
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
Log file in PowerShell version #183
Comments
DBRepair.log should be in the same folder as the databases. As for what you'll see, most minor issues in the DB are silently repaired without logging as part of the "auto" process. The "Check Databases" will report all errors which will cause PMS to have operational issues (malformed / corrupted databases messages in logs). Constraint errors (major DB corruption) will be reported even in "IGNORE" mode. This is intentional. Index errors are minor. These only impact performance. They are corrected as part of the reindex phase (phase 3 of 'auto') |
Sorry I will close it now!
Best Regards,
Mike
From: Kevan Ferrara ***@***.***>
Sent: Sunday, January 26, 2025 9:16 AM
To: ChuckPa/PlexDBRepair ***@***.***>
Cc: Mike Prachar ***@***.***>; Mention ***@***.***>
Subject: Re: [ChuckPa/PlexDBRepair] Log file in PowerShell version (Issue #183)
Hello - I recently used the PowerShell version and it worked perfectly. I would love to know more about what it found but I cannot locate dbrepair.log anywhere.
@mprachar<https://github.com/mprachar> have you seen @ChuckPa<https://github.com/ChuckPa> reply and been able to find and review the log(s)? Your request for assistance is still open.
—
Reply to this email directly, view it on GitHub<#183 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AFOEDLGO6E7QY5W3GTWWAYT2MUX5XAVCNFSM6AAAAABVQWJ57KVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDMMJUGU2TIMJYG4>.
You are receiving this because you were mentioned.Message ID: ***@***.******@***.***>>
|
Hello - I recently used the PowerShell version and it worked perfectly. I would love to know more about what it found but I cannot locate dbrepair.log anywhere.
The text was updated successfully, but these errors were encountered: