SABnzbd Forums

Hi

I"m running into a problem in which when my indexer, Mylar3, send NZB file to the queue, the file in the /config/admin/future directory has permissions set as such it cannot be read.

16-Apr-2024 6:29:14 - ERROR :: mylar.historycheck.268 : AUTO-COMPLETE-NZB : Cannot find nzb SABnzbd_nzo_3c9uw0td in the queue. Was it removed?
today at 6:29:19 AM16-Apr-202422:29:19 - WARNING :: mylar.cdh_monitor.3412 : AUTO-COMPLETE-NZB : NZB seems to have been removed from queue: SABnzbd_nzo_3c9uw0td

I find this file, SABnzbd_nzo_3c9uw0td in the /config/admin/future directory, but its permissions are very locked down. THere is an item to be fetche in the queue created,. but it just sits there and times out. And in the logs its shows the file cannot be found.

Any ideas? Both are in docker containers from LSIO.

Third party apps such as mylar don't read internal files directly, but talk to sabnzbd via an API. As such, strict permissions on these files aren't an issue, provided sabnzbd itself has sufficient access.

Your actual problem is whatever causes the timeout. Take a look at the (debug) logging of sabnzbd, and see if there's a clue as to what is going on with the fetching part.

Hello,

It seems like you're encountering permission issues with files created by Mylar3 in the /config/admin/future directory when sent to the SABnzbd queue. The error messages indicate that the NZB file cannot be read from the queue, likely due to restrictive permissions set on the file.

Verify the permissions set on the NZB file (SABnzbd_nzo_3c9uw0td) in the /config/admin/future directory. Ensure that the file permissions allow the SABnzbd application to read the file. You may need to adjust the permissions to make the file readable by the application.

Since both Mylar3 and SABnzbd are running within Docker containers from LSIO, ensure that the permissions within the containers are correctly configured. Check the user/group settings within the Docker containers to ensure that they have appropriate access to the directories and files they need to operate on.

If you're using Docker volumes to persist data, ensure that the volume mounts are correctly configured with appropriate permissions. Misconfigured volume mounts can lead to permission issues within Docker containers.

Check the logs of both Mylar3 and SABnzbd for any additional error messages or warnings that could provide further insights into the issue. Look for any specific error messages related to file permissions or access issues.

How can we avoid these AI bots?