Page 1 of 1

Problem with Categories and question about ADMIN folder

Posted: May 27th, 2013, 3:52 am
by bbaraniec
Hello,

Let's start with question. I remember you have told me Shypike that ADMIN folder privileges will be changed so anyone can delete it. If the job fails and I can delete folder only from web interface.
For some reason, some of the jobs even after deleting are leaving only _ADMIN_ folder which I can't access and I need to ssh to my box.

Second issue I run yesterday are Categories. Below you will find a list of my Categories. In most cases I don't use manual download. My main source of downloads are SickBeard and CouchPotato.
I have finally updated my old 0.7.1 to the latest 0.7.12. I run SAB on ReadyNAS Pro (x64 some variation of Debian).
So just after update SickBeard picked up few tv shows and send them to SAB, and hour later I still haven't received information that it has completed. When I checked my downloads I have noticed that they aren't unpacked.
Sometimes Categories were working sometimes not. By not working I mean that tv shows, movies etc. were assigned to proper category but processing was still on download only.
I tried restart, editing and saving categories. The success ratio was 50%. What finally helped me (it's working so far) was deleting last category and adding it again.

I should also mention that during SAB update I have kept config and admin folder.

Image

Re: Problem with Categories and question about ADMIN folder

Posted: May 28th, 2013, 1:33 am
by shypike
The admin folder is "private" and will remain so.
On most systems it isn't available from a remote location any way.
Aren't you confusing it with "incomplete"?

I don't recognize any of the Category behaviour that you describe.
Since you already fixed it, tracking down what happened isn't possible any more.

Re: Problem with Categories and question about ADMIN folder

Posted: May 28th, 2013, 4:24 am
by bbaraniec
Yes I'm taking about ADMIN folder in incompleted downloads.

Re: Problem with Categories and question about ADMIN folder

Posted: May 28th, 2013, 1:00 pm
by shypike
That's the __ADMIN__ folder inside a job folder in the "incomplete" folder.
So you're telling me that when removing jobs with SABnzbd's web interface, sometimes the __ADMIN__ folder remains?
If so, that has nothing to do with access rights.

Re: Problem with Categories and question about ADMIN folder

Posted: June 11th, 2013, 3:14 am
by bbaraniec
Yesterday I had to restart SAB, after restart I was facing again problems with categories. SAB is picking up correct category, but pp is only download. Removing, adding category didn't helped.
After few restarts everything working again but I'm really puzzled what's going on. I'm running latest version on ReadyNas Pro (that's some kind of debian).
Additionally I have noticed that when I remove active job sometimes it's not being removed from drive and I can't delete them via Samba share.

Re: Problem with Categories and question about ADMIN folder

Posted: June 11th, 2013, 11:14 am
by bbaraniec
I have found how silly I am, they were orphaned jobs. That's sorted but still need help with categories please.

Re: Problem with Categories and question about ADMIN folder

Posted: June 11th, 2013, 12:12 pm
by shypike
Be aware that SABnzbd will only use its category-defined attributes
when a program like SickBeard and CouchPotato do not override there attributes.
I'm almost sure that at least SickBeard does this.

Re: Problem with Categories and question about ADMIN folder

Posted: June 11th, 2013, 1:51 pm
by bbaraniec
I know that but I was sending the nzbs from one of the newznab providers using the SABnzbd integration.

Re: Problem with Categories and question about ADMIN folder

Posted: June 11th, 2013, 5:28 pm
by shypike
So they're sending their api-url through SABnzbd's URL.
That may contain overrides as well.
Set logging to Debug (Status page) and check what's being sent.

Re: Problem with Categories and question about ADMIN folder

Posted: June 12th, 2013, 3:53 am
by bbaraniec
I will do that but it's working ok right now and it will be until I restard SAB. Maybe if I get lucky after restart it will be working again, maybe not. Maybe I will need to restart SAB 2 or 3 times to get it fixed again.