No disk space when running as a service
Posted: July 25th, 2011, 2:44 am
Version: 0.6.5
OS: Windows 7 (NAS runs on some Linux flavor)
Install-type: Windows Installer
Skin (if applicable): Plush
Firewall Software: ESET 4
Are you using IPV6? No
Is the issue reproducible? Yes
When running SABnzbd as a service it says that my destination folder has 0.0GB free, even though it is actually well over 80GB. downloads fail because of this with an error saying that the destination folder could not be created. When running SABnzbd "normally" (through the start menu), the Free Space is shown correctly, and downloads succeed. Also, retrying downloads that have failed with this error succeed.
I first thought that maybe because the service starts while Windows is starting, the networked folder (my destination folder is a folder on my NAS) is not available yet. But the problem also occurs when I start the service manually after accessing the remote folder (e.g. through windows explorer).
Has anyone seen a similar issue, and is there a way to solve it?
OS: Windows 7 (NAS runs on some Linux flavor)
Install-type: Windows Installer
Skin (if applicable): Plush
Firewall Software: ESET 4
Are you using IPV6? No
Is the issue reproducible? Yes
When running SABnzbd as a service it says that my destination folder has 0.0GB free, even though it is actually well over 80GB. downloads fail because of this with an error saying that the destination folder could not be created. When running SABnzbd "normally" (through the start menu), the Free Space is shown correctly, and downloads succeed. Also, retrying downloads that have failed with this error succeed.
I first thought that maybe because the service starts while Windows is starting, the networked folder (my destination folder is a folder on my NAS) is not available yet. But the problem also occurs when I start the service manually after accessing the remote folder (e.g. through windows explorer).
Has anyone seen a similar issue, and is there a way to solve it?