Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Care package issues [win10] #231

Closed
professionaltart opened this issue Mar 28, 2020 · 1 comment
Closed

Care package issues [win10] #231

professionaltart opened this issue Mar 28, 2020 · 1 comment
Assignees
@evilhero
Labels
bug Something isn't working pending testing

Comments

@professionaltart
Copy link

Describe the bug
Click on Care Package button. ISError 500 ensues.

image

Logs

28-Mar-2020 13:52:24 - INFO    :: mylar.toggleVerbose.4055 : CP Server Thread-11 : Verbose (DEBUG) logging is enabled
28-Mar-2020 13:52:24 - DEBUG   :: mylar.toggleVerbose.4056 : CP Server Thread-11 : If you can read this message, debug logging is now working
28-Mar-2020 13:52:24 - INFO    :: mylar.toggleVerbose.4059 : CP Server Thread-11 : config file has been loaded from: c:\ProgramData\mylar3\config.ini
28-Mar-2020 13:52:28 - INFO    :: mylar.clearLogs.4037 : CP Server Thread-3 : Web logs cleared
28-Mar-2020 13:52:34 - DEBUG   :: mylar.cleaned_config.229 : CP Server Thread-10 : Configuration cleaned of keys/passwords and written to temporary location.
28-Mar-2020 13:52:34 - DEBUG   :: mylar.panicbutton.270 : CP Server Thread-10 : analyzing C:\ProgramData\mylar3\logs\mylar.log
28-Mar-2020 13:52:34 - DEBUG   :: mylar.panicbutton.287 : CP Server Thread-10 : removed 11621 keys from C:\ProgramData\mylar3\logs\mylar.log
28-Mar-2020 13:54:41 - DEBUG   :: mylar.dbUpdate.84 : ThreadPoolExecutor-0_0 : Refresh sequence set to fire every 5 minutes for 7 day(s)

Environment

  • OS: Windows, Version 10.0.18363.720
  • Branch / commit: Version: 830e0bf (python3-dev)

Additional information
\mylar3\logs contains logs (obvs) but probably shouldn't contain:
MylarRunningEnvironment.txt
clean_config.ini
\mylar3\logs\carepackage also contains mylar.log
500 ISError also means carepackage.zip sits there and doesn't get pushed to download from the server.

Unsure if this is related to #151 which was closed - that was running on a *nix box, not Windows.
evilhero added a commit that referenced this issue Mar 28, 2020
@evilhero
FIX:(#231) Carepackage fails to perform cleanup of temporary files an…
b11a01a 
…d causes an error on Windows systems due to locked files
barbequesauce pushed a commit that referenced this issue Mar 28, 2020
@evilhero @barbequesauce
FIX:(#231) Carepackage fails to perform cleanup of temporary files an…
1b92664 
…d causes an error on Windows systems due to locked files
@barbequesauce barbequesauce added bug Something isn't working pending testing labels Mar 28, 2020
@professionaltart
Copy link
Author

Pulled and tested. Confirmed working again.
carepackage.zip created and downloaded. Log files tidied up.
mylar3\logs now contains .log files and carepackage.zip

barbequesauce added a commit that referenced this issue Apr 8, 2020
@evilhero @barbequesauce
python3-dev merge (#245)
68122e6 
* FIX: default sort order not in descending order on history page

* fix history default sort order

* patch for carepackage to ensure removal of multiple keyed items on a single log entry

* FIX: forgot the file option

* FIX: fix for telegram notifs failing due to max retries exceeded, which would then lock the pp-queue

* FIX: fix for DDL download breaking for some series

* FIX: fix for simultaneous searches firing off when done using different search methods

* FIX:(#225) If git wasn't in environment path, would accept failed output as a valid response and attempt to use that as commit/branch information

* FIX: fix for incorrect error reference when encountering an SQlite error trap

* FIX(#229) API response was not being handled properly by cherrypy

* FIX:(#231) Carepackage fails to perform cleanup of temporary files and causes an error on Windows systems due to locked files

* Fix crash if Mylar sees book that's a symlink to a nonexistant file

* optional config.ini choice to use either [CVDBxxxx] or [Issue ID xxxxxx] (the default) in the notes field when metatagging.

* FIX: provider_order would not respect ini settings (would tend to reorder based on code priority vs ini priority)

Co-authored-by: Barbeque Sauce <saucebarbeque@hotmail.com>
Co-authored-by: Bran Tyslerx <btx@mxyzptlk.net>
barbequesauce added a commit that referenced this issue Apr 23, 2020
@evilhero @barbequesauce
@eroth312 @ajslater @mylar3
Dev branch merge (#265)
9eefa84 
* FIX: default sort order not in descending order on history page

* fix history default sort order

* patch for carepackage to ensure removal of multiple keyed items on a single log entry

* FIX: forgot the file option

* FIX: fix for telegram notifs failing due to max retries exceeded, which would then lock the pp-queue

* FIX: fix for DDL download breaking for some series

* FIX: fix for simultaneous searches firing off when done using different search methods

* FIX:(#225) If git wasn't in environment path, would accept failed output as a valid response and attempt to use that as commit/branch information

* FIX: fix for incorrect error reference when encountering an SQlite error trap

* FIX(#229) API response was not being handled properly by cherrypy

* FIX:(#231) Carepackage fails to perform cleanup of temporary files and causes an error on Windows systems due to locked files

* Fix crash if Mylar sees book that's a symlink to a nonexistant file

* optional config.ini choice to use either [CVDBxxxx] or [Issue ID xxxxxx] (the default) in the notes field when metatagging.

* FIX: provider_order would not respect ini settings (would tend to reorder based on code priority vs ini priority)

* fix popup javascript error in importresults datatables due to extraneous html

* Performance Tuning - speed up weekly pull check which was locking database

* fix typo in search which would cause a traceback

* removed logging line that captured data

* update carepackage to ensure complete removal

* Eliminate endless loop in sabnzb queue (#251)

* Eliminate endless loop in nzb queue

* Eliminate double for loop & ensure we use the correct nzb id based on downloader configuration

* Handle paused sab queue by throwing a warning

* fix a crash

Co-authored-by: Barbeque Sauce <saucebarbeque@hotmail.com>
Co-authored-by: Bran Tyslerx <btx@mxyzptlk.net>
Co-authored-by: Evan Roth <evan.roth@gmail.com>
Co-authored-by: AJ Slater <aj@slater.net>
Co-authored-by: mylar3 <59849447+mylar3@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@evilhero evilhero

Labels
bug Something isn't working pending testing
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@evilhero @barbequesauce @professionaltart