Page 1 of 1
Weird Beahvior with 4.1.0
Posted: November 30th, 2023, 11:48 am
by jermdog2112
Re: Weird Beahvior with 4.1.0
Posted: November 30th, 2023, 12:40 pm
by safihre
That sounds very strange. What kind of things are you downloading?
Are you sure your Sabnzbd isn't exposed to the internet and someone is messing with you?
Re: Weird Beahvior with 4.1.0
Posted: November 30th, 2023, 1:07 pm
by jermdog2112
No one is messing with me. I've been doing periodic testing to be sure. It only happens when I download items - the usual stuff, nothing crazy or large. Does anyone know how to turn off the test download? It might be related to that.
Re: Weird Beahvior with 4.1.0
Posted: November 30th, 2023, 1:28 pm
by safihre
There is no test download, only if you initiate one yourself in the Status window.
Those files are created on startup to test your folders. So clearly something is wrong, otherwise that file would be automatically removed..
Where are your download folders?
Don't you get an error on startup?
Re: Weird Beahvior with 4.1.0
Posted: November 30th, 2023, 1:54 pm
by jermdog2112
Download, incomplete and complete folders are all on the same NAS drive (Synology). SABnzbd runs from a Windows 11 machine, not on the NAS. No errors on start up. When I have time, I guess I will uninstall and reinstall SABnzbd. I guess that might be an option. I'll make sure to make a copy of my ini file for all of my connection info.
Re: Weird Beahvior with 4.1.0
Posted: December 1st, 2023, 5:37 pm
by jermdog2112
Reinstalling SABnzbd did not resolve the issue. Simply opening SABnzbd 4.1.0 is creating these files. The sab_test.txt file has the text " Some random content". The rocket file has the same exact text. The "A' file is actually ACEDO4~P as the real file name and cannot be opened.
Re: Weird Beahvior with 4.1.0
Posted: December 2nd, 2023, 2:32 am
by safihre
So what is the path to your download folders?
You should never put anything else than your complete folder on your NAS. Certainly not your Incomplete folder.
If you tried using network paths, SABNZBD will prevent you. But probably you used a mounted drive letter?
Re: Weird Beahvior with 4.1.0
Posted: April 11th, 2024, 10:04 pm
by rlaphoenix
I too had this AAAAAA.... file in my drive roughly 2 days ago with the filename:
Code: Select all
AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA20593
and it contains
Version: 4.2.3 [e7e06de]
Uptime: 2d (which coincides with it failing to remove on startup, roughly)
Config File: C:/Users/x/AppData/Local/sabnzbd/sabnzbd.ini
Parameters: "C:/Program Files/SABnzbd/SABnzbd.exe" "-b0"
Python Version: 3.12.2 (tags/v3.12.2:6abddd9, Feb 6 2024, 21:26:36) [MSC v.1937 64 bit (AMD64)] [cp1252]
OpenSSL: OpenSSL 3.0.13 30 Jan 2024
The Web UI shows a LOT of the following kinds of errors:
ERROR: 2 days ago Failed making (D:/.sab/incomplete/FileNameRedacted)
Traceback (most recent call last):
File "sabnzbd/filesystem-dot-py", line 751, in create_all_dirs
File "<frozen os>", line 225, in makedirs
PermissionError: [WinError 5] Access is denied: '////?//D://.sab//incomplete//FileNameRedacted'
However, I believe I know the issue here to some degree. D drive is a StableBit DrivePool containing an array of drives both in an Orico 5-bay external USB Bay, but also WD Elements External Drives and internal drives. The Orico bay was turned off on boot and then turned on soon after boot. I presume what happened here is StableBit DrivePool was able to store the .txt to one of the drives in a botched state, or botched trying to then remove it or when storing the NZB file data to D drive.