Support Forum

I figured out my issue. Avast 2014 was preventing anything to listen on 8080 and 8081. I couldn't easily find anywhere in avast to unblock this or create an exception/exclusion so I uninstalled it and went for another antivirus.

PS..I hate windows..

Same issue here on a fresh install on Windows. Sab doesn't seem to be reporting any issues with port 8080. netstat shows nothing listening on 8080. Anything else I can check? C:\Windows\system32>netstat | grep 8080 TCP [::1]:50304 GREENBEAN:8080 SYN_SENT TCP [::1]:50305 GREENBEAN:8080 SYN_SENT 2013-...

Yep, you're correct. I noticed the same after I pasted the log contents into the json parser instead of uploading it. None of the current CP logs are producing the error. If it pops up again I'll grab fresh logs and json.

This "error" is annoying.. When I copy and paste into http://json.parser.online.fr, it parses just fine........ back to the proverbial drawing board..

I'm not sure what you're doing differently than me? I paste the entire contents into jsonlint and upload the file to json parser. I know little to nothing about json so I could be doing this all wrong. Parse error on line 71: ... "script_log": "Loading config from --------------------...

Finally remembered to send you the json.

Where can I send you the full json output? It appears it is complaining about the colon just after show details.

Example api call for history json: http://localhost:8080/api?output=json&apikey=myApiKey&limit=15&mode=history Excerpt of returned json where error lies: "show_details": "True", "script_log": "| + Codec ID: A_DTS\nVariable values: \n -> (dl_path) [arg1]...

Excellent. I agree on the default interval increase. Most movies I download are over 4GB so 5 minute polling makes more sense.

clinton hall wrote:Ruud has implemented a limit of 15. This is in the develop branch and should go to master at he next merge.

Also, in CPS settings, renamer, set Run Every (advanced option) to a greater time. This will reduce the frequency of calls.

Cool, set it to 10 minutes.

Perhaps you could add a config item to limit full history scan requests to whatever number is configured? Maybe 50-75 by default? Maybe even as little as 20? I know I don't snatch 50 at a time, others may? Perhaps it would be an advanced option? I got to thinking further about what you said about CP...

In looking at the CPS logs, it appears it does a history scan once a minute while there are items it expects sabnzbd to be downloading. By the way, you do you realize that I was able to produce the behavior via my browser right? CPS was shut down. I restarted sabnzbd, gave it about 5 minutes "i...

Yep, I've already raised the issue with CPS. I'm not sure of their plans, but will ask if they would consider a revision. I believe the purpose of this is to avoid duplicate downloads. For example, perhaps I manually added an nzb to sabnzb and then also had CPS search for the same thing in order to ...

Yep, sure "did". I have already fixed the crashing issue by purging the history. Like I said above, if I had to guess I would say I had over 500 downloads in the history. Before this issue popped up, I never purged.

I came across this issue after upgraded CouchPotatoServer to v2. It checks the queue and download history to check download status of movies it has sent to sabnzbd. I am running SABnzbd v0.7.3 on OS X 10.7.5. SABnzbd is hitting 100% cpu usage and then crashes with a segmentation fault when an api ca...