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.

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

Sporadic issues applying category and subsequent actions #1908

Open
DarrenPIngram opened this issue May 30, 2021 · 9 comments
Open

Sporadic issues applying category and subsequent actions #1908

DarrenPIngram opened this issue May 30, 2021 · 9 comments
Labels

Comments

@DarrenPIngram
Copy link

For a while (several versions, including current beta/RC) I've been experiencing issues with the bulk application of labels for items set to download. I've put off reporting this as I was of the opinion it must be "user error" but I am less sure now.

The issue only happens sporadically to make matters more strange (Mac OS 10.15.7 version).

Situation: set SAB to "pause", "read feed" and items in an indexer's queue download. Select the "multiple items" icon and "select all" items in the right-hand side. Then select the download category type to "bulk" (a custom made item)" and then press the "multiple items" icon again to close the option. All items are shown to have the "bulk" category.

Bulk is set to download items to a different directory than the default (the other categories are also set to the same default directory).

Select "play" to start the download.

Situation: Items go to the default/standard category directory and NOT the "bulk" defined directory.

On a couple of occasions, it seems to have applied the changes to PART of the entire download queue, leading me to wonder if some "rewrite" function doesn't fully apply.

Would the logging show the rewriting of categories and subsequent filing in the right/wrong directory? If so what level and I can try and recreate with a future job.

@Safihre
Copy link
Member

Safihre commented May 30, 2021

Strange! But indeed, we would need Debug logging.
If you could enable that and then after it happens again share the logs here or through pastebin.
And mention which job changed category.

@DarrenPIngram
Copy link
Author

The GUI log gets overwritten very quickly. Are older logs saved and rotated? If so, where might they be stored?

@Safihre
Copy link
Member

Safihre commented May 30, 2021

In your Admin directory: https://sabnzbd.org/wiki/advanced/directory-setup

@DarrenPIngram

This comment has been minimized.

@DarrenPIngram
Copy link
Author

DarrenPIngram commented Jun 4, 2021

OK. I have now got the incident (it has happened several times since I last wrote) replicated whilst I was in front of the computer and able to grab the log file. I had a small amount of data being transferred so I could be 100% sure I had "marked all" to map the "bulk" tag in line with my earlier submission. I had began to wonder if the problem happened when the number of files was such that it spread over more than one "page". It was not the case on this occasion.

I had six files queued to download. As of the log file's submission one was correctly sent to the "bulk" (mapped) directory whereas another file has been stored (wrongly) in the default directory.

The log file, even with it expunging information, contains some sensitive information. Is there a way I can share a Dropbox link privately to the developer/those who can help interpret the problem?

@Safihre
Copy link
Member

Safihre commented Jun 4, 2021

Send it to safihre@sabnzbd.org

@DarrenPIngram
Copy link
Author

Thanks. I will do that!

@Safihre
Copy link
Member

Safihre commented Jun 5, 2021

I found the problem based on your log:
When we fetch a NZB from an URL we create a placeholder-job, which is replaced fully with a new job when the NZB is fetched and parsed.
At the moment the raw-NZB-data is received and we start parsing is when we copy the attributes (like the category) from the placeholder-job.
In this case, you changed the category exactly during the ~20 seconds that SABnzbd was parsing the raw-NZB-data. So your changed to the placeholder-job is not applied to the real job.

@DarrenPIngram
Copy link
Author

Thank you for the response and investigation. Is this something you can fix to stop the undesired behaviour? If so, what might be the approximate timeline (I already install the beta versions when provided).

As additional information, if I "send" items to SAB via NZBHydra I've (so far) not experienced the problem. I don't know the communications mechanism that may be extant, but with heavy usage of NZBHydra in any case I've either been very lucky, or the "problem" is different as not to affect me through that means.

@Safihre Safihre added the Bug label Jun 6, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants