Problems with autoProcessTV.cfg

Get help with all aspects of SABnzbd
Forum rules
Help us help you:
  • Are you using the latest stable version of SABnzbd? Downloads page.
  • Tell us what system you run SABnzbd on.
  • Adhere to the forum rules.
  • Do you experience problems during downloading?
    Check your connection in Status and Interface settings window.
    Use Test Server in Config > Servers.
    We will probably ask you to do a test using only basic settings.
  • Do you experience problems during repair or unpacking?
    Enable +Debug logging in the Status and Interface settings window and share the relevant parts of the log here using [ code ] sections.
Post Reply
kl1k
Release Testers
Release Testers
Posts: 30
Joined: November 1st, 2009, 3:21 pm

Problems with autoProcessTV.cfg

Post by kl1k »

Used to have SAB running with Sickbeard and have recently converted to Sickrage.

Not sure if this is a SAB or a SR issue.

SAB downloads the file but there is a issue with post processing. The download is not being moved to the tv series server.

On SAB:

Code: Select all

Loading config from /usr/local/sickbeard/autoProcessTV/autoProcessTV.cfg

Opening URL: http://localhost:8082/home/postprocess/processEpisode?nzbName=Mr.Robot.S01E05.720p.HDTV.x264-KILLERS.nzb&quiet=1&dir=%2Fvar%2Fsabnzbd%2FDownloads%2Fcomplete%2FMr.Robot.S01E05.720p.HDTV.x264-KILLERS

<!DOCTYPE html>
<html>
<head>
<meta charset="utf-8">
<meta http-equiv="X-UA-Compatible" content="IE=edge">
<meta name="viewport" content="width=device-width">

<!-- These values come from css/dark.css and css/light.css -->
<meta name="theme-color" content="#15528F">

<title>SickRage - BRANCH:[master] - Login</title>

<!--[if lt IE 9]>
<script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
<script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
<![endif]-->

<link rel="shortcut icon" href="/images/ico/favicon.ico">
<link rel="icon" sizes="16x16 32x32 64x64" href="/images/ico/favicon.ico">
<link rel="icon" type="image/png" sizes="196x196" href="/images/ico/favicon-196.png">
<link rel="icon" type="image/png" sizes="160x160" href="/images/ico/favicon-160.png">
<link rel="icon" type="image/png" sizes="96x96" href="/images/ico/favicon-96.png">
<link rel="icon" type="image/png" sizes="64x64" href="/images/ico/favicon-64.png">
<link rel="icon" type="image/png" sizes="32x32" href="/images/ico/favicon-32.png">
<link rel="icon" type="image/png" sizes="16x16" href="/images/ico/favicon-16.png">
<link rel="apple-touch-icon" sizes="152x152" href="/images/ico/favicon-152.png">
<link rel="apple-touch-icon" sizes="144x144" href="/images/ico/favicon-144.png">
<link rel="apple-touch-icon" sizes="120x120" href="/images/ico/favicon-120.png">
<link rel="apple-touch-icon" sizes="114x114" href="/images/ico/favicon-114.png">
<link rel="apple-touch-icon" sizes="76x76" href="/images/ico/favicon-76.png">
<link rel="apple-touch-icon" sizes="72x72" href="/images/ico/favicon-72.png">
<link rel="apple-touch-icon" href="/images/ico/favicon-57.png">
<meta name="msapplication-TileColor" content="#FFFFFF">
<meta name="msapplication-TileImage" content="/images/ico/favicon-144.png">
<meta name="msapplication-config" content="/css/browserconfig.xml">

<link rel="stylesheet" type="text/css" href="/css/lib/bootstrap.css?14024"/>
<link rel="stylesheet" type="text/css" href="/css/browser.css?14024" />
<link rel="stylesheet" type="text/css" href="/css/lib/jquery-ui-1.10.4.custom.css?14024" />
<link rel="stylesheet" type="text/css" href="/css/lib/jquery.qtip-2.2.1.min.css?14024"/>
<link rel="stylesheet" type="text/css" href="/css/style.css?14024"/>
<link rel="stylesheet" type="text/css" href="/css/dark.css?14024" />


<script type="text/javascript" src="/js/lib/jquery-1.11.2.min.js?14024"></script>
<script type="text/javascript" src="/js/lib/bootstrap.min.js?14024"></script>
<script type="text/javascript" src="/js/lib/bootstrap-hover-dropdown.min.js?14024"></script>
<script type="text/javascript" src="/js/lib/jquery-ui-1.10.4.custom.min.js?14024"></script>
</head>

<body>
<nav class="navbar navbar-default navbar-fixed-top" role="navigation">
<div class="container-fluid">
<div class="navbar-header">
<button type="button" class="navbar-toggle collapsed" data-toggle="collapse" data-target="#bs-example-navbar-collapse-1">
<span class="sr-only">Toggle navigation</span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
<span class="icon-bar"></span>
</button>
<a class="navbar-brand" href="/home/" title="SickRage"><img alt="SickRage" src="/images/sickrage.png" style="height: 50px;" class="img-responsive pull-left" /></a>
</div>

</div><!-- /.navbar-collapse -->
</div><!-- /.container-fluid -->
</nav>




<div id="contentWrapper">
<div id="content">

<div class="login">
<form action="" method="post">
<h1>SickRage</h1>
<div class="ctrlHolder"><input class="inlay" name="username" type="text" placeholder="Username" autocomplete="off" /></div>
<div class="ctrlHolder"><input class="inlay" name="password" type="password" placeholder="Password" autocomplete="off" /></div>
<div class="ctrlHolder">
<label class="remember_me" title="for 30 days"><input class="inlay" id="remember_me" name="remember_me" type="checkbox" value="1" checked="checked" /> Remember me</label>
<input class="button" name="submit" type="submit" value="Login" />
</div>
</form>
</div>

           

The autoProcessTV file has the correct info in - the port is correct and username/password correct.

Code: Select all

[SickBeard]
host=localhost
port=8082
username=xxxxxxxxx
password=xxxxxxx
web_root=
ssl=0
Any ideas what going wrong? I've checked the permissions on the cfg file and thats not a issue.
User avatar
shypike
Administrator
Administrator
Posts: 19774
Joined: January 18th, 2008, 12:49 pm

Re: Problems with autoProcessTV.cfg

Post by shypike »

This is a Sickbeard problem.
SABnzbd starts the script, but somehow it cannot communicate with the mothership.
kl1k
Release Testers
Release Testers
Posts: 30
Joined: November 1st, 2009, 3:21 pm

Re: Problems with autoProcessTV.cfg

Post by kl1k »

Thanks - will look into SR logs/forum

Think I fixed the issue - looks like it was a permissions issue on the file after all. Set to 777 and its now post processing :)
Post Reply