Closed LegioN7 closed 3 months ago
Just to assist in some troubleshooting/root cause I was able to revert back to v4.5.8 and qBitrr works fine.
Hi, reason 4.5.8 is working is because that log didn't exist yet. And as you can see from the log above, you seem to have two simultaneous processes running at once. Can you test the following? Ensure all python processes you may have running are stopped temporarily, then open a terminal window in the folder where your executable is placed and run ./qbitrr
Hey Feramance, This is a fresh windows installation with only one instance of qBitrr running. I've shut down the previous .exe, and tried to run the last working version (4.6.1).
(The newer versions posted today actually don't read config files and creates a 2nd config file constantly. I can post a new issue for that.)
All Python services are shut off, and restarted via a cmd. The error pops up anyways. The actual qBitrr won't always open up if old logs are stored, and actually will crash. I can see if I can upload some examples. If I clear the old logs (delete them) and boot it gets to this part of your new logging and crashes.
If this helps my testing is done in Windows 10 (Fresh Installation).
Reverting back to the previous v4.5.8 works just fine and continues to function.
(The newer versions posted today actually don't read config files and creates a 2nd config file constantly. I can post a new issue for that.)
Just fixed this in 4.6.12. Kindly download and test again. Thank you
Any news?
Hey Feramance, The issue still persists.
Starting the old version does not provide this error. I'm not running into the config issue anymore.
The only other thing I could imagine is possibly deleting the entire folder housing qBitrr, then creating a new folder, setting the security to allow all for all users, then placing the exe, running it to generate the config file, pasting your existing config inside the newly created config file and running. If all else fails this seems more than likely a windows permission issue than a qBitrr issue. I've been testing it on windows for the past 2 weeks extensively and didn't see any issues.
And I know others who are also running on windows with no issues on the latest version
Let me see what I can do from a testing perspective.
I've done the following on a fresh windows install.
I opened a brand new folder called qBitrr2 Created an entirely new configuration and copied my old settings
I've checked to make sure no other instances are running etc.
What window permissions would be used by a script? I run it as administrator (just to test)
And even as admin it returns the permission error? I've tried to reproduce this on my Windows machine but I cannot, try as I might, replicate this issue.
One thing I could suggest is installing power toys and using the locksmith tool as admin to check if any other process is using the file when running qBitrr
Let me see what I can do this week and get back to you. It's odd it's strictly just with the log file.
At most, disable the log files in the config
For the time being I have fixed this issue by disabling that specific log. Feel free to update to the latest version.
Hey! Sorry I thought I replied. I disabled the log files and continued using it for the time being.
You can actually safely update to the latest version
It's safe to update, confirmed
Issue will be closed if there is no reply
Lets just close it and i'll re-enable logging in the next version/release.
Hello! I loaded up Qbitrr release today and now I am receiving an error with logging. This is a fresh boot of windows.