mirror of
https://github.com/Sonarr/Sonarr.git
synced 2024-11-22 02:32:51 +01:00
NzbDrone > Sonarr
parent
648dac527c
commit
9241869987
@ -1,6 +1,6 @@
|
||||
## URL ##
|
||||
|
||||
All API endpoints are based off of `/api` if you access drone via `http://localhost:8989` the API root would be `http://localhost:8989/api`
|
||||
All API endpoints are based off of `/api` if you access Sonarr via `http://localhost:8989` the API root would be `http://localhost:8989/api`
|
||||
|
||||
|
||||
## Authentication ##
|
||||
@ -17,7 +17,7 @@ All requests made to the api endpoint require API Key authentication using the X
|
||||
|
||||
- All dates/timestamps are ISO-8601 formatted in UTC `2014-01-27T01:30:00Z`
|
||||
- Episodes (and episode based endpoints, missing & calendar) also include the airdate in the original timezone for display purposes
|
||||
- Date parameters should be ISO-8601 UTC dates to ensure proper handling by drone
|
||||
- Date parameters should be ISO-8601 UTC dates to ensure proper handling by Sonarr
|
||||
|
||||
## Content Type ##
|
||||
|
||||
|
@ -1,7 +1,7 @@
|
||||
## POST ##
|
||||
|
||||
##### Summary #####
|
||||
Publish a new command for NzbDrone to run
|
||||
Publish a new command for Sonarr to run
|
||||
|
||||
##### Parameters ######
|
||||
|
||||
@ -82,7 +82,7 @@ Required:
|
||||
---
|
||||
|
||||
### DownloadedEpisodesScan ###
|
||||
Instruct NzbDrone to scan the DroneFactoryFolder or a folder defined by the path variable
|
||||
Instruct Sonarr to scan the DroneFactoryFolder or a folder defined by the path variable
|
||||
|
||||
##### Parameters ######
|
||||
|
||||
@ -93,7 +93,7 @@ Optional:
|
||||
---
|
||||
|
||||
### RssSync ###
|
||||
Instruct NzbDrone to perform an RSS sync with all enabled indexers
|
||||
Instruct Sonarr to perform an RSS sync with all enabled indexers
|
||||
|
||||
##### Parameters ######
|
||||
|
||||
|
@ -1,6 +1,6 @@
|
||||
# Autostart on Debian using init.d script
|
||||
|
||||
The instructions for Ubuntu/Debian did not seem to work for Debian very well, and the pid got lost whenever NzbDrone was restarted via the web-ui, so I've included a working script here init.d script here.
|
||||
The instructions for Ubuntu/Debian did not seem to work for Debian very well, and the pid got lost whenever Sonarr was restarted via the web-ui, so I've included a working script here init.d script here.
|
||||
|
||||
**Create and edit the nzbdrone init.d script**
|
||||
|
||||
@ -18,8 +18,8 @@ The instructions for Ubuntu/Debian did not seem to work for Debian very well, an
|
||||
# Should-Stop: $NetworkManager
|
||||
# Default-Start: 2 3 4 5
|
||||
# Default-Stop: 0 1 6
|
||||
# Short-Description: starts instance of NzbDrone
|
||||
# Description: starts instance of NzbDrone using start-stop-daemon
|
||||
# Short-Description: starts instance of Sonarr
|
||||
# Description: starts instance of Sonarr using start-stop-daemon
|
||||
### END INIT INFO
|
||||
|
||||
############### EDIT ME ##################
|
||||
@ -90,6 +90,6 @@ exit 0
|
||||
|
||||
sudo update-rc.d nzbdrone defaults
|
||||
|
||||
**Start NzbDrone**
|
||||
**Start Sonarr**
|
||||
|
||||
sudo service nzbdrone start
|
||||
|
@ -8,13 +8,13 @@ Using Upstart allows for more advanced features, such as start/stop and automati
|
||||
**Paste in the following code, changing the username (right click if using terminal)**
|
||||
```bash
|
||||
author "Simon Tallmyr - Nosscire"
|
||||
description "Upstart Script to run NzbDrone as a service on Ubuntu/Debian based systems, as well as others"
|
||||
description "Upstart Script to run Sonarr as a service on Ubuntu/Debian based systems, as well as others"
|
||||
|
||||
#Set username for the process. Should probably be what you use for logging in
|
||||
setuid yourusername
|
||||
|
||||
#This is the install directory. If you installed using a deb package or the NzbDrone Repository you do not need to change this
|
||||
env DIR=/opt/NzbDrone
|
||||
#This is the install directory. If you installed using a deb package or the Sonarr Repository you do not need to change this
|
||||
|
||||
setgid nogroup
|
||||
start on runlevel [2345]
|
||||
@ -29,7 +29,7 @@ exec mono --debug $DIR/NzbDrone.exe
|
||||
|
||||
Press <kbd>Ctrl</kbd>+<kbd>X</kbd> then <kbd>y</kbd> to save.
|
||||
|
||||
**Start NzbDrone**
|
||||
**Start Sonarr**
|
||||
|
||||
sudo start nzbdrone
|
||||
|
||||
@ -50,7 +50,7 @@ Press <kbd>Ctrl</kbd>+<kbd>X</kbd> then <kbd>y</kbd> to save.
|
||||
# Default-Start: 2 3 4 5
|
||||
# Default-Stop: 0 1 6
|
||||
# Short-Description: nzbdrone
|
||||
# Description: NZBDrone
|
||||
# Description: Sonarr
|
||||
### END INIT INFO
|
||||
|
||||
. /lib/lsb/init-functions
|
||||
@ -58,7 +58,7 @@ Press <kbd>Ctrl</kbd>+<kbd>X</kbd> then <kbd>y</kbd> to save.
|
||||
#set -e
|
||||
|
||||
NAME=nzbdrone
|
||||
DESC="NZBDrone"
|
||||
DESC="Sonarr"
|
||||
MONO=$(which mono)
|
||||
|
||||
DAEMON=/opt/NzbDrone/NzbDrone.exe
|
||||
@ -146,7 +146,7 @@ Note: The script by default runs as root. I suggest adding an nzbdrone user (`us
|
||||
|
||||
### Method 3: init.d script (Debian)###
|
||||
|
||||
Please see [here](https://github.com/NzbDrone/NzbDrone/wiki/Autostart-on-Debian).
|
||||
Please see [here](https://github.com/Sonarr/Sonarr/wiki/Autostart-on-Debian).
|
||||
|
||||
|
||||
### Method 4: RC.Local
|
||||
@ -154,10 +154,10 @@ Please see [here](https://github.com/NzbDrone/NzbDrone/wiki/Autostart-on-Debian)
|
||||
***
|
||||
**This Method Provided by:** protocol77
|
||||
|
||||
This Guide is to help those who would like to use linux to run NZBDrone at time of writing this there is not "Install As Service" option like with the Windows Build so this needs to be done until a better alternative is found i have personally tested it so you should have no issues if you do please post in the NZBDrone Forums (http://forums.nzbdrone.com/) and someone will try and help you.
|
||||
This Guide is to help those who would like to use linux to run Sonarr at time of writing this there is not "Install As Service" option like with the Windows Build so this needs to be done until a better alternative is found i have personally tested it so you should have no issues if you do please post in the Sonarr Forums (https://forums.sonarr.tv/) and someone will try and help you.
|
||||
|
||||
**First **
|
||||
make sure NzbDrone is installed you can go here to find out how to do that https://github.com/NzbDrone/NzbDrone/wiki/Installation
|
||||
make sure Sonarr is installed you can go here to find out how to do that https://github.com/Sonarr/Sonarr/wiki/Installation
|
||||
|
||||
Next I created a .sh or batch file to automate the process of type "sudo mono /opt/NzbDrone/NzbDrone.exe"
|
||||
Here is a link to the batch file so it saves you all from having to do this even though it was easy if you open in a text editor you will see
|
||||
@ -232,13 +232,13 @@ Typically located in /usr/lib/systemd/system/, verify before proceeding. Will d
|
||||
mv sonarr.service /usr/lib/systemd/system/
|
||||
```
|
||||
|
||||
**Add Sonarr/NzbDrone to startup**
|
||||
**Add Sonarr to startup**
|
||||
|
||||
```bash
|
||||
systemctl enable sonarr.service
|
||||
```
|
||||
|
||||
**Start Sonarr/NzbDrone service**
|
||||
**Start Sonarr service**
|
||||
|
||||
Start sonarr via systemd and verify status.
|
||||
|
||||
|
@ -5,7 +5,7 @@ Install Upstart
|
||||
|
||||
sudo apt-get install upstart
|
||||
|
||||
**Create the NzbDrone Upstart config file**
|
||||
**Create the Sonarr Upstart config file**
|
||||
|
||||
sudo nano /etc/init/nzbdrone.conf
|
||||
|
||||
@ -34,6 +34,6 @@ exec $MONO $DIR/NzbDrone.exe
|
||||
|
||||
Press <kbd>Ctrl</kbd>+<kbd>X</kbd> then <kbd>y</kbd> to save.
|
||||
|
||||
**Start NzbDrone**
|
||||
**Start Sonarr**
|
||||
|
||||
sudo start nzbdrone
|
||||
|
@ -1,50 +1,50 @@
|
||||
## Backing up NzbDrone ##
|
||||
## Backing up Sonarr ##
|
||||
|
||||
#### Using built-in backup ####
|
||||
|
||||
1. Go to System: Backup in the drone UI
|
||||
1. Go to System: Backup in the Sonarr UI
|
||||
2. Click the Backup button
|
||||
3. Download the zip after the backup is created for safe keeping
|
||||
|
||||
#### Using file system directly ####
|
||||
1. Find the location of the AppData directory for NzbDrone
|
||||
- Via the drone UI go to System: Info
|
||||
1. Find the location of the AppData directory for Sonarr
|
||||
- Via the Sonarr UI go to System: Info
|
||||
- Defaults
|
||||
- Windows - `C:\ProgramData\NzbDrone`
|
||||
- Ubuntu - `/home/user/.config/NzbDrone`
|
||||
- Synology - `/usr/local/nzbdrone/var/.config/NzbDrone`
|
||||
|
||||
2. Stop NzbDrone - This will prevent the database from being corrupted
|
||||
2. Stop Sonarr - This will prevent the database from being corrupted
|
||||
3. Copy the contents to a safe location
|
||||
|
||||
## Restoring from Backup ##
|
||||
|
||||
#### Using zip backup ####
|
||||
|
||||
1. Re-install NzbDrone
|
||||
2. Run NzbDrone once to get the AppData directory location
|
||||
3. Stop NzbDrone
|
||||
1. Re-install Sonarr
|
||||
2. Run Sonarr once to get the AppData directory location
|
||||
3. Stop Sonarr
|
||||
4. Extract the backup
|
||||
5. Delete the contents of the AppData directory
|
||||
6. Restore the files extracted from the zip
|
||||
7. Start NzbDrone
|
||||
7. Start Sonarr
|
||||
8. As long as the paths are the same, everything will pickup where it left off
|
||||
|
||||
#### Using file system backup ####
|
||||
1. Re-install NzbDrone
|
||||
2. Run NzbDrone once to get the AppData directory location
|
||||
3. Stop NzbDrone
|
||||
1. Re-install Sonarr
|
||||
2. Run Sonarr once to get the AppData directory location
|
||||
3. Stop Sonarr
|
||||
4. Delete the contents of the AppData directory
|
||||
5. Restore from your backup
|
||||
6. Start NzbDrone
|
||||
6. Start Sonarr
|
||||
7. As long as the paths are the same, everything will pickup where it left off
|
||||
|
||||
### Restore for Synology NAS ###
|
||||
**CAUTION: Restoring on a Synology requires knowledge of Linux and Root SSH access to the Synology Device.**
|
||||
|
||||
1. Re-install NzbDrone
|
||||
2. Run NzbDrone once to get the AppData directory location
|
||||
3. Stop NzbDrone
|
||||
1. Re-install Sonarr
|
||||
2. Run Sonarr once to get the AppData directory location
|
||||
3. Stop Sonarr
|
||||
4. Connect to the Synology NAS through SSH and login as root
|
||||
5. execute the following commands
|
||||
|
||||
@ -53,4 +53,4 @@
|
||||
cp -f /tmp/nzbdrone_backup/. /usr/local/nzbdrone/var/.config/NzbDrone/
|
||||
```
|
||||
|
||||
6. Start NzbDrone
|
||||
6. Start Sonarr
|
28
CentOS-6.md
28
CentOS-6.md
@ -1,10 +1,10 @@
|
||||
The following instructions are for installing NzbDrone on CentOS 6.
|
||||
The following instructions are for installing Sonarr on CentOS 6.
|
||||
|
||||
The installation should also be applicable to RHEL 6 and Fedora (12, 13, or 14) with minimal changes.
|
||||
|
||||
The installation assumes that you're not using the root user to install/run NZBDrone - the entries for **user:group** throughout the document will have to be modified to match your user configuration.
|
||||
The installation assumes that you're not using the root user to install/run Sonarr - the entries for **user:group** throughout the document will have to be modified to match your user configuration.
|
||||
|
||||
### Install NzbDrone
|
||||
### Install Sonarr
|
||||
|
||||
1. **[Optional] Configure sudo for your user**
|
||||
```bash
|
||||
@ -41,11 +41,11 @@ The installation assumes that you're not using the root user to install/run NZBD
|
||||
|
||||
5. **Compile sqlite3.8.5**
|
||||
|
||||
NZBDrone requires the COLUMN_METADATA option so we'll enable it.
|
||||
Sonarr requires the COLUMN_METADATA option so we'll enable it.
|
||||
<br>
|
||||
I didn't want to replace the system sqlite installation (v3.6.20) since CentOS depends on it so I'm using the --prefix option to install it to another directory.
|
||||
<br>
|
||||
The init script will be configured to call this new version when running NZBDrone.
|
||||
The init script will be configured to call this new version when running Sonarr.
|
||||
|
||||
```bash
|
||||
cd /tmp/sqlite-autoconf*
|
||||
@ -60,21 +60,21 @@ The installation assumes that you're not using the root user to install/run NZBD
|
||||
sudo make install
|
||||
```
|
||||
|
||||
6. **Download and extract NzbDrone and optionally rename it**
|
||||
6. **Download and extract Sonarr and optionally rename it**
|
||||
|
||||
```bash
|
||||
curl -L http://update.nzbdrone.com/v2/master/mono/NzbDrone.master.tar.gz -o /tmp/NzbDrone.master.tar.gz
|
||||
curl -L http://download.sonarr.tv/v2/master/mono/NzbDrone.master.tar.gz -o /tmp/NzbDrone.master.tar.gz
|
||||
sudo tar zxvf /tmp/NzbDrone.master.tar.gz -C /opt/
|
||||
```
|
||||
|
||||
I wanted to maintain lower-case naming so I renamed the NzbDrone program directory
|
||||
I wanted to maintain lower-case naming so I renamed the Sonarr program directory
|
||||
<br>
|
||||
```bash
|
||||
sudo mv /opt/NzbDrone /opt/nzbdrone
|
||||
```
|
||||
|
||||
|
||||
7. **Run NzbDrone to test**
|
||||
7. **Run Sonarr to test**
|
||||
|
||||
Just run it to verify everything is working the stop it (CTRL-C) and move to the next steps.
|
||||
|
||||
@ -82,7 +82,7 @@ The installation assumes that you're not using the root user to install/run NZBD
|
||||
<br>
|
||||
1. Set the LD_LIBRARY_PATH and PATH to point to the new sqlite and mono directories
|
||||
<br>
|
||||
2. Run NZB Drone
|
||||
2. Run Sonarr
|
||||
<br>
|
||||
3. Set the environment back to normal.
|
||||
|
||||
@ -94,7 +94,7 @@ The installation assumes that you're not using the root user to install/run NZBD
|
||||
export PATH=$PATH_BAK ; export LD_LIBRARY_PATH=$LPATH_BAK
|
||||
```
|
||||
|
||||
### Create NzbDrone init Service
|
||||
### Create Sonarr init Service
|
||||
|
||||
1. **Download init script and configuration files**
|
||||
|
||||
@ -116,19 +116,19 @@ The installation assumes that you're not using the root user to install/run NZBD
|
||||
sudo vi /etc/sysconfig/nzbdrone
|
||||
```
|
||||
|
||||
3. **Add the NzbDrone service to system services**
|
||||
3. **Add the Sonarr service to system services**
|
||||
|
||||
```bash
|
||||
sudo chkconfig --add nzbdrone
|
||||
```
|
||||
|
||||
4. **Configure NzbDrone service to start on system start up**
|
||||
4. **Configure Sonarr service to start on system start up**
|
||||
|
||||
```bash
|
||||
sudo chkconfig nzbdrone on
|
||||
```
|
||||
|
||||
5. **Start NzbDrone service**
|
||||
5. **Start Sonarr service**
|
||||
|
||||
```bash
|
||||
sudo service nzbdrone start
|
||||
|
@ -1,6 +1,6 @@
|
||||
# How to Contribute #
|
||||
|
||||
We're always looking for people to help make NzbDrone even better, there are a number of ways to contribute.
|
||||
We're always looking for people to help make Sonarr even better, there are a number of ways to contribute.
|
||||
|
||||
## Documentation ##
|
||||
Setup guides, FAQ, the more information we have on the wiki the better.
|
||||
@ -16,15 +16,15 @@ Setup guides, FAQ, the more information we have on the wiki the better.
|
||||
|
||||
### Getting started ###
|
||||
|
||||
1. Fork NzbDrone
|
||||
1. Fork Sonarr
|
||||
2. Clone (develop branch)
|
||||
3. Run `npm install`
|
||||
4. Run `grunt` - Used to compile the UI components and copy them (leave this window open)
|
||||
5. Compile in Visual Studio
|
||||
|
||||
### Contributing Code ###
|
||||
- If you're adding a new, already requested feature, please move it to In Progress on [Trello](http://trello.nzbdrone.com "Trello") so work is not duplicated.
|
||||
- Rebase from NzbDrone's develop branch, don't merge
|
||||
- If you're adding a new, already requested feature, please move it to In Progress on [Trello](https://trello.sonarr.tv "Trello") so work is not duplicated.
|
||||
- Rebase from Sonarr's develop branch, don't merge
|
||||
- Make meaningful commits, or squash them
|
||||
- Feel free to make a pull request before work is complete, this will let us see where its at and make comments/suggest improvements
|
||||
- Reach out to us on the forums or on IRC if you have any questions
|
||||
|
@ -3,15 +3,15 @@ These are guidelines that should help determine the appropriate log level and me
|
||||
## Levels ##
|
||||
|
||||
### Fatal ###
|
||||
NzbDrone has failed completely, or will be operating in a diminished state.
|
||||
Sonarr has failed completely, or will be operating in a diminished state.
|
||||
|
||||
|
||||
### Error ###
|
||||
NzbDrone was preventing from doing something and the user may need to take action to correct it (Unable to connect to an external service), NzbDrone will be unable to operate normally.
|
||||
Sonarr was preventing from doing something and the user may need to take action to correct it (Unable to connect to an external service), Sonarr will be unable to operate normally.
|
||||
|
||||
|
||||
### Warning ###
|
||||
NzbDrone was unable to perform an action, but the result doesn't prevent NzbDrone from operating normally.
|
||||
Sonarr was unable to perform an action, but the result doesn't prevent Sonarr from operating normally.
|
||||
|
||||
|
||||
### Info ###
|
||||
|
@ -2,11 +2,11 @@
|
||||
|
||||
## Disable Drone Factory Folder Scanning ##
|
||||
|
||||
You can disable drone factory folder scanning via the advanced setting "Drone Factory Interval" on the download client settings page, by setting it to zero.
|
||||
You can disable Drone Factory folder scanning via the advanced setting "Drone Factory Interval" on the download client settings page, by setting it to zero.
|
||||
|
||||
## Post Processing Script ##
|
||||
|
||||
You can configure your download client to run a script to send a command to NzbDrone's API instructing it to run a scan on the drone factory folder.
|
||||
You can configure your download client to run a script to send a command to Sonarr's API instructing it to run a scan on the Drone Factory folder.
|
||||
|
||||
The script will need to send a POST with a JSON body as described here: [Command](Command#downloadedepisodesscancommand)
|
||||
|
||||
|
54
FAQ.md
54
FAQ.md
@ -1,16 +1,16 @@
|
||||
### Does NzbDrone require a SABnzbd post-processing script to import downloaded episodes? ###
|
||||
### Does Sonarr require a SABnzbd post-processing script to import downloaded episodes? ###
|
||||
No. As long as you set the Drone Factory path `Settings > Download Client > Drone Factory` to the folder where sab downloads your TV Shows everything will be imported automatically. [[Sorting and Renaming]]
|
||||
|
||||
### How does NzbDrone find episodes? ###
|
||||
NzbDrone doesn't actively search for any episodes on its own, it uses the indexer's latest releases to find recently posted episodes. Typically the indexer returns the last 100 releases, which isn't much, so be wary if you shut your system down for an extended period of time you might miss some newly release episodes. also, sometimes older episodes are re-posted and might get downloaded if you haven't ignored them. Missing episodes are not actively searched for (missing is anything that aired prior to the current time), unless that episode has not yet been posted (aired recently) or is re-posted you will need to manually search for them. If drone is shut down for a period of time (more than 1 hour), it will attempt to search for recently aired episodes that have not been grabbed or imported yet, this is the only case where drone will search for a missing episode without user interaction.
|
||||
### How does Sonarr find episodes? ###
|
||||
Sonarr doesn't actively search for any episodes on its own, it uses the indexer's latest releases to find recently posted episodes. Typically the indexer returns the last 100 releases, which isn't much, so be wary if you shut your system down for an extended period of time you might miss some newly release episodes. also, sometimes older episodes are re-posted and might get downloaded if you haven't ignored them. Missing episodes are not actively searched for (missing is anything that aired prior to the current time), unless that episode has not yet been posted (aired recently) or is re-posted you will need to manually search for them. If Sonarr is shut down for a period of time (more than 1 hour), it will attempt to search for recently aired episodes that have not been grabbed or imported yet, this is the only case where Sonarr will search for a missing episode without user interaction.
|
||||
|
||||
### Why can't NzbDrone see my files on a remote server? ###
|
||||
This can be for various reasons, but the most common is, NzbDrone is running as a service, which causes one of two things:
|
||||
### Why can't Sonarr see my files on a remote server? ###
|
||||
This can be for various reasons, but the most common is, Sonarr is running as a service, which causes one of two things:
|
||||
|
||||
1. NzbDrone runs under the SYSTEM account by default which doesn't have access to protected remote file shares.
|
||||
1. Sonarr runs under the SYSTEM account by default which doesn't have access to protected remote file shares.
|
||||
|
||||
**Solutions:**
|
||||
- Run NzbDrone's service as another user that has access to that share [How to change a service's user account](http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sys_srv_logon_user.mspx?mfr=true)
|
||||
- Run Sonarr's service as another user that has access to that share [How to change a service's user account](http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/sys_srv_logon_user.mspx?mfr=true)
|
||||
- Run NzbDrone.exe using the Startup Folder
|
||||
|
||||
|
||||
@ -22,28 +22,28 @@ This can be for various reasons, but the most common is, NzbDrone is running as
|
||||
- Run NzbDrone.exe via the Startup Folder
|
||||
|
||||
|
||||
### How does NzbDrone handle scene numbering issues (American Dad!, etc)? ###
|
||||
NzbDrone relies on [TheXEM](TheXEM "http://thexem.de/"), a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network's numbering). There are a number of shows on there already, but its easy to add another and typically the changes are accepted within a couple days (if they're correct).
|
||||
### How does Sonarr handle scene numbering issues (American Dad!, etc)? ###
|
||||
Sonarr relies on [TheXEM](TheXEM "http://thexem.de/"), a community driven site that lets users create mappings of shows that the scene (the people that post the files) and TheTVDB (which typically follows the network's numbering). There are a number of shows on there already, but its easy to add another and typically the changes are accepted within a couple days (if they're correct).
|
||||
|
||||
### Why can't NzbDrone import episode files for series X? / Why can't NzbDrone find releases for series X? ###
|
||||
NzbDrone relies on being able to match titles, often the scene posts episodes using different titles, eg *CSI: Crime Scene Investigation* as just *CSI* so NzbDrone can't match the names without some help. NzbDrone maintains a list of problematic series which lets us solve this issue. To request a new mapping:
|
||||
### Why can't Sonarr import episode files for series X? / Why can't Sonarr find releases for series X? ###
|
||||
Sonarr relies on being able to match titles, often the scene posts episodes using different titles, eg *CSI: Crime Scene Investigation* as just *CSI* so Sonarr can't match the names without some help. Sonarr maintains a list of problematic series which lets us solve this issue. To request a new mapping:
|
||||
|
||||
1. Make sure it hasn't already been requested. [Requested Mappings](https://docs.google.com/spreadsheet/ccc?key=0Atcf2VZ47O8tdGdQN1ZTbjFRanhFSTBlU0xhbzhuMGc#gid=0)
|
||||
2. Make a new request here: [Scene Mapping Request Form]( https://docs.google.com/forms/d/15S6FKZf5dDXOThH4Gkp3QCNtS9Q-AmxIiOpEBJJxi-o/viewform)
|
||||
|
||||
*Typically these are added within 1-2 days*
|
||||
|
||||
### NzbDrone grabbed a release, why can't it import it? ###
|
||||
The reason it was able to grab the release in the first place was because the indexer returned the tv rage ID for the series and NzbDrone was able to match it to that, but that ID is not available during import, so it fails.
|
||||
### Sonarr grabbed a release, why can't it import it? ###
|
||||
The reason it was able to grab the release in the first place was because the indexer returned the tv rage ID for the series and Sonarr was able to match it to that, but that ID is not available during import, so it fails.
|
||||
|
||||
### Why can't I add a new show to NzbDrone, its on TheTVDB? ###
|
||||
NzbDrone use [trakt](http://trakt.tv/) for series/episode information and images (fanart, banners, images). Here are some reasons why you might not be able to find your show:
|
||||
### Why can't I add a new show to Sonarr, its on TheTVDB? ###
|
||||
Sonarr use [trakt](http://trakt.tv/) for series/episode information and images (fanart, banners, images). Here are some reasons why you might not be able to find your show:
|
||||
|
||||
1. Trakt doesn't like special characters to be used when searching for series through the API. Try your search without special characters. [Also vote on this issue so they can get it fixed](http://support.trakt.tv/forums/188762-general/suggestions/4199849-searching-for-shows-with-special-characters).
|
||||
2. The series hasn't been added to trakt yet, follow their [guide](http://support.trakt.tv/knowledgebase/articles/151225-how-do-i-add-a-new-tv-show-to-trakt) to get it added.
|
||||
|
||||
### I see that feature/bug X was fixed, why can't I see it? ###
|
||||
NzbDrone consists of two main branches of code, master and develop, master is released periodically, when the develop branch is stable and develop is for pre-release testing and people willing to live on the edge, if you want to help out testing or want more information on the two branches, please see: [[Release-Branches]]
|
||||
Sonarr consists of two main branches of code, master and develop, master is released periodically, when the develop branch is stable and develop is for pre-release testing and people willing to live on the edge, if you want to help out testing or want more information on the two branches, please see: [[Release-Branches]]
|
||||
When a feature is marked as In Develop it will only be available to users running the develop branch, once its been move to Live (in master) it is officially released.
|
||||
|
||||
### Episode Progress - How is it calculated? ###
|
||||
@ -58,29 +58,29 @@ There are two parts to the episode count, one being the number of episodes (Epis
|
||||
If a series has 10 episodes that have all aired and you don't have any files for them you would have 0/10 episodes, if you unmonitored all the episodes in that series you would have 0/0 and if you got all the episodes for that series, regardless of if the episodes are monitored or not, you would have 10/10 episodes.
|
||||
|
||||
### I got a pop-up that said config.xml was corrupt, what now? ###
|
||||
NzbDrone was unable to read your config file on start-up as it became corrupted somehow. In order to get NzbDrone back online, you will need to delete `C:\ProgramData\NzbDrone\Config.xml` (Windows), once deleted start NzbDrone and it will start on the default port (8989), you should now re-configure any settings you configured on the General Settings page.
|
||||
Sonarr was unable to read your config file on start-up as it became corrupted somehow. In order to get Sonarr back online, you will need to delete `C:\ProgramData\Sonarr\Config.xml` (Windows), once deleted start Sonarr and it will start on the default port (8989), you should now re-configure any settings you configured on the General Settings page.
|
||||
|
||||
### How do I access NzbDrone from another computer? ###
|
||||
By default NzbDrone doesn't listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server NzbDrone uses integrates with Windows (this also applies for current alternatives). If NzbDrone is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).
|
||||
### How do I access Sonarr from another computer? ###
|
||||
By default Sonarr doesn't listen to requests from all systems (when not run as administrator), it will only listen on localhost, this is due to how the Web Server Sonarr uses integrates with Windows (this also applies for current alternatives). If Sonarr is run as an administrator it will correctly register itself with Windows as well as open the Firewall port so it can be accessed from other systems on your network. Running as admin only needs to happen once (if you change the port it will need to be re-run).
|
||||
|
||||
### Why doesn't NzbDrone automatically search for missing episodes? ###
|
||||
There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when NzbDrone has been offline and unable to find episodes as it normally would. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.
|
||||
### Why doesn't Sonarr automatically search for missing episodes? ###
|
||||
There are two times when we would want to have missing episodes searched for, when a new series with existing aired episodes is added and when Sonarr has been offline and unable to find episodes as it normally would. Endlessly searching for episodes that have aired that are missing is a waste of resources, both in terms of local processing power and on the indexers and in our experience catches users off guard, wasting bandwidth.
|
||||
|
||||
In v1 of NzbDrone we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching.
|
||||
In v1 of Sonarr we had an opt in backlog search option, often people would turn it on and then get a bunch of old episodes and ask us why, we also had indexers ask why they saw an increase in API calls, which was due to the backlog searching.
|
||||
|
||||
In v2 we sat back and thought about it and realized the benefit is not really there, we could try to throttle the searching, but that just draws it out and still does the same thing; hammer the indexer with useless requests. If the episode wasn't there the last time the search was performed, why would it be there now? It would be if it was reposted, but if it was reposted, the automatic process that gets new episodes would see it was posted and act on it.
|
||||
|
||||
### I am getting an error: Invalid Newznab URL entered. ###
|
||||
First make sure you're using the correct URL (with https if applicable), such as: `https://indexer.nzbdrone.com`, not `https://indexer.nzbdrone.com/api`. If you're still having issues please see [[Newznab]]
|
||||
First make sure you're using the correct URL (with https if applicable), such as: `http://indexer.com`, not `https://indexer.com/api`. If you're still having issues please see [[Newznab]]
|
||||
|
||||
### I am getting an error: Database disk image is malformed. ###
|
||||
This means your sqlite database that stores most of the information for NzbDrone is corrupt. There is an excellent guide here to copy the contents from the corrupt database into a new one: http://techblog.dorogin.com/2011/05/sqliteexception-database-disk-image-is.html
|
||||
This means your sqlite database that stores most of the information for Sonarr is corrupt. There is an excellent guide here to copy the contents from the corrupt database into a new one: http://techblog.dorogin.com/2011/05/sqliteexception-database-disk-image-is.html
|
||||
|
||||
### Why does NzbDrone refresh series information so frequently? ###
|
||||
### Why does Sonarr refresh series information so frequently? ###
|
||||
|
||||
NzbDrone refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from trakt is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren't airing are being updated with new information.
|
||||
Sonarr refreshes series and episode information in addition to rescanning the disk for files every 12 hours. This might seem aggressive, but is a very important process. The data refresh from trakt is important, because new episode information is synced down, air dates, number of episodes, status (continuing/ended). Even shows that aren't airing are being updated with new information.
|
||||
|
||||
The disk scan is less important, but is used to check for new files that weren't sorted by NzbDrone and detect deleted files.
|
||||
The disk scan is less important, but is used to check for new files that weren't sorted by Sonarr and detect deleted files.
|
||||
|
||||
The most time consuming portion is the information refresh (assuming reasonable disk access speed), larger shows take longer due to the number of episodes to process.
|
||||
|
||||
|
@ -7,17 +7,17 @@ There are a couple components that make up the failed download handling process:
|
||||
a. Queue - Encrypted (passworded) as detected by SAB
|
||||
b. History - Failed, whatever the reason, not enough to repair or extraction failed
|
||||
|
||||
When drone finds a failed download it starts processing them and does a few things:
|
||||
When Sonarr finds a failed download it starts processing them and does a few things:
|
||||
|
||||
1. Adds a failed event to drone's history
|
||||
1. Adds a failed event to Sonarr's history
|
||||
2. Removes the failed download from SAB to free space (opt out)
|
||||
3. Starts searching for a replacement file (opt out)
|
||||
|
||||
2) Blacklisting
|
||||
Allows automatic skipping of nzbs when they fail, this means that nzb will not be automatically downloaded by drone ever again (You can still force the download via a manual search).
|
||||
Allows automatic skipping of nzbs when they fail, this means that nzb will not be automatically downloaded by Sonarr ever again (You can still force the download via a manual search).
|
||||
|
||||
There are 3 advanced options (on Download Client) that control the behavior of failed downloading in drone, at this time, they are all on by default.
|
||||
There are 3 advanced options (on Download Client) that control the behavior of failed downloading in Sonarr, at this time, they are all on by default.
|
||||
|
||||
Enable - Turns the checking of SAB and the blacklist functionality on or off
|
||||
Redownload - Controls whether or not drone will search for the same episode after a failure
|
||||
Redownload - Controls whether or not Sonarr will search for the same episode after a failure
|
||||
Remove - Whether or not the download should automatically be removed from SAB when the failure is detected
|
16
Fedora-20.md
16
Fedora-20.md
@ -1,4 +1,4 @@
|
||||
The following instructions are for installing Sonarr/NzbDrone on Fedora 20. The same method should work on Fedora 15-19 and RHEL 7 however I have not tested those environments.
|
||||
The following instructions are for installing Sonarr on Fedora 20. The same method should work on Fedora 15-19 and RHEL 7 however I have not tested those environments.
|
||||
|
||||
For system v init based versions of Fedora (anything prior to 15), reference the [[CentOS 6]] guide.
|
||||
|
||||
@ -6,7 +6,7 @@ Works on Fedora 21, however I suspect they will update the mono package for that
|
||||
|
||||
Automatic/scary install script at the end.
|
||||
|
||||
### Install Sonarr/NzbDrone
|
||||
### Install Sonarr
|
||||
|
||||
All commands run as root sudo -s if necessary.
|
||||
|
||||
@ -48,10 +48,10 @@ yum install mediainfo libzen libmediainfo curl gettext mono-opt mono-opt-devel s
|
||||
ln -s /opt/mono/bin/mono /usr/bin/mono
|
||||
```
|
||||
|
||||
**Download and extract Sonarr/NZBDrone**
|
||||
**Download and extract Sonarr**
|
||||
|
||||
```bash
|
||||
wget http://update.nzbdrone.com/v2/master/mono/NzbDrone.master.tar.gz
|
||||
wget http://download.sonarr.tv/v2/master/mono/NzbDrone.master.tar.gz
|
||||
tar -xvf ~/NzbDrone.master.tar.gz -C /opt/
|
||||
```
|
||||
|
||||
@ -61,7 +61,7 @@ chown -R sonarr:sonarr /opt/NzbDrone
|
||||
```
|
||||
|
||||
|
||||
### Create NzbDrone systemd Service and firewall rules
|
||||
### Create Sonarr systemd Service and firewall rules
|
||||
|
||||
**Create systemd service file**
|
||||
```bash
|
||||
@ -84,13 +84,13 @@ EOF
|
||||
mv sonarr.service /usr/lib/systemd/system/
|
||||
```
|
||||
|
||||
**Add Sonarr/NzbDrone to startup**
|
||||
**Add Sonarr to startup**
|
||||
|
||||
```bash
|
||||
systemctl enable sonarr.service
|
||||
```
|
||||
|
||||
**Start Sonarr/NzbDrone service**
|
||||
**Start Sonarr service**
|
||||
|
||||
Start sonarr via systemd and verify status.
|
||||
|
||||
@ -128,7 +128,7 @@ adduser -g sonarr -m -c "Sonarr User" -s /sbin/nologin sonarr
|
||||
wget -4 -O /etc/yum.repos.d/mono.repo http://download.opensuse.org/repositories/home:/tpokorra:/mono/Fedora_20/home:tpokorra:mono.repo
|
||||
yum install mediainfo libzen libmediainfo curl gettext mono-opt mono-opt-devel sqlite.x86_64
|
||||
ln -s /opt/mono/bin/mono /usr/bin/mono
|
||||
wget http://update.nzbdrone.com/v2/master/mono/NzbDrone.master.tar.gz
|
||||
wget http://download.sonarr.tv/v2/master/mono/NzbDrone.master.tar.gz
|
||||
tar -xvf ~/NzbDrone.master.tar.gz -C /opt/
|
||||
chown -R sonarr:sonarr /opt/NzbDrone
|
||||
cat > sonarr.service << EOF
|
||||
|
@ -1,11 +1,11 @@
|
||||
This page contains a list of health checks errors.
|
||||
These health checks are periodically performed performed by drone and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
|
||||
These health checks are periodically performed performed by Sonarr and on certain events. The resulting warnings and errors are listed here to give advice on how to resolve them.
|
||||
|
||||
### System warnings ###
|
||||
|
||||
#### Mono version is less than 3.2, upgrade for improved stability ####
|
||||
|
||||
NzbDrone is written in .Net and requires Mono to run. Versions of 3.2 and above resolved various stability issues we experienced in the past.
|
||||
Sonarr is written in .Net and requires Mono to run. Versions of 3.2 and above resolved various stability issues we experienced in the past.
|
||||
Updating to at least version 3.2 is therefore highly recommended.
|
||||
|
||||
#### New update is available ####
|
||||
@ -19,47 +19,47 @@ _(This warning will not appear if your current version is less than 14 days old)
|
||||
|
||||
#### Unable to update, running from write-protected folder ####
|
||||
|
||||
This means NzbDrone will be unable to update itself. You'll have to update drone manually or set the permissions on drone's Startup directory (the installation directory) to allow drone to update itself.
|
||||
This means Sonarr will be unable to update itself. You'll have to update Sonarr manually or set the permissions on Sonarr's Startup directory (the installation directory) to allow Sonarr to update itself.
|
||||
|
||||
#### Updating will not be possible to prevent deleting AppData on Update ####
|
||||
|
||||
NzbDrone detected that AppData folder for your Operating System is located inside the directory that contains the NzbDrone binaries. Normally it would be ```C:\ProgramData``` for Windows and, ```~/.config``` for linux.
|
||||
Sonarr detected that AppData folder for your Operating System is located inside the directory that contains the Sonarr binaries. Normally it would be ```C:\ProgramData``` for Windows and, ```~/.config``` for linux.
|
||||
Please look at System -> Info to see the current AppData & Startup directories.
|
||||
|
||||
This means NzbDrone will be unable to update itself without risking data-loss.
|
||||
This means Sonarr will be unable to update itself without risking data-loss.
|
||||
|
||||
If you're on linux, you'll probably have to change the home directory for the user that is running NzbDrone and copy the current contents of the ```~/.config/NzbDrone``` directory to preserve your database.
|
||||
If you're on linux, you'll probably have to change the home directory for the user that is running Sonarr and copy the current contents of the ```~/.config/Sonarr``` directory to preserve your database.
|
||||
|
||||
### Download Clients ###
|
||||
|
||||
#### No download client is available ####
|
||||
|
||||
A properly configured and enabled download client is required for NzbDrone to be able to download media.
|
||||
Since NzbDrone supports different download clients, you should determine which best matches your requirements.
|
||||
If you already have a download client installed, you should configure NzbDrone to use it and create a category. See Settings -> Download Client.
|
||||
A properly configured and enabled download client is required for Sonarr to be able to download media.
|
||||
Since Sonarr supports different download clients, you should determine which best matches your requirements.
|
||||
If you already have a download client installed, you should configure Sonarr to use it and create a category. See Settings -> Download Client.
|
||||
|
||||
#### Unable to communicate with download client ####
|
||||
|
||||
NzbDrone was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
|
||||
Sonarr was unable to communicate with the configured download client. Please verify if the download client is operational and double check the url. This could also indicate an authentication error.
|
||||
|
||||
#### Enable Completed Download Handling or configure Drone factory ####
|
||||
#### Enable Completed Download Handling or configure Drone Factory ####
|
||||
|
||||
NzbDrone requires Completed Download Handling or a properly configured Drone Factory to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
|
||||
Sonarr requires Completed Download Handling or a properly configured Drone Factory to be able to import files that were downloaded by the download client. It is recommended to enable Completed Download Handling.
|
||||
|
||||
_(Completed Download Handling is enabled by default for new users.)_
|
||||
|
||||
### Drone Factory ###
|
||||
|
||||
#### Drone factory folder does not exist ####
|
||||
#### Drone Factory folder does not exist ####
|
||||
|
||||
If you configure NzbDrone to use a Drone Factory the specified folder must exist. Please ensure that it indeed exists, or disable the Drone Factory.
|
||||
If you configure Sonarr to use a Drone Factory the specified folder must exist. Please ensure that it indeed exists, or disable the Drone Factory.
|
||||
|
||||
_(You might want to consider using Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients.)_
|
||||
|
||||
#### Unable to write to drone factory folder ####
|
||||
#### Unable to write to Drone Factory folder ####
|
||||
|
||||
You configured NzbDrone to use a Drone Factory, however NzbDrone was unable to creates a test file, this indicates permission issues.
|
||||
Please verify that the user NzbDrone runs under has the appropriate permissions.
|
||||
You configured Sonarr to use a Drone Factory, however Sonarr was unable to creates a test file, this indicates permission issues.
|
||||
Please verify that the user Sonarr runs under has the appropriate permissions.
|
||||
|
||||
### Completed/Failed Download Handling ###
|
||||
|
||||
@ -68,27 +68,27 @@ Please verify that the user NzbDrone runs under has the appropriate permissions.
|
||||
_(This warning is only generated for existing users before when the Completed Download Handling feature was implemented. This feature is disabled by default to ensure the system continued to operate as expected for current configurations.)_
|
||||
|
||||
It's recommended to switch to Completed Download Handling since it provides better compatibility for the unpacking and post-processing logic of various download clients.
|
||||
With it, drone will only import a download once the download client reports it as ready.
|
||||
With it, Sonarr will only import a download once the download client reports it as ready.
|
||||
|
||||
If you don't wish to enable Completed Download Handling at all and wants to remove the warning. You can enable and then disable Completed Download Handling. This obviously isn't recommended.
|
||||
|
||||
If you wish to enable Completed Download Handling you should verify the following:
|
||||
* **Warning**: Completed Download Handling only works properly if the download client and NzbDrone are on the same machine since it gets the path to be imported directly from the download client.
|
||||
* If you added a post-processing script to Sabnzbd/NzbGet to notify NzbDrone that it should scan the Drone Factory. You _SHOULD_ disable this script to prevent conflicts.
|
||||
* **Warning**: Completed Download Handling only works properly if the download client and Sonarr are on the same machine since it gets the path to be imported directly from the download client.
|
||||
* If you added a post-processing script to Sabnzbd/NzbGet to notify Sonarr that it should scan the Drone Factory. You _SHOULD_ disable this script to prevent conflicts.
|
||||
* Completed Download Handling and the Drone Factory cannot be configured for the same directory. If Completed Download Handling detects a download resides in the Drone Factory it will be ignored. (again to prevent conflicts)
|
||||
You should reconfigure NzbDrone to use a different Drone Factory Folder or disable it altogether.
|
||||
You should reconfigure Sonarr to use a different Drone Factory Folder or disable it altogether.
|
||||
Alternatively you can change the output folder for the Category, as long as that output folder is not a subdirectory of the Drone Factory Folder.
|
||||
|
||||
Both Completed Download Handling and the Drone Factory logic generates Import Events in history while importing files. However, only Completed Download Handling associates this Import event with a Download Client history item.
|
||||
If Completed Download Handling was enabled recently, your download client may still contain history items that were already imported but do not have a history event with the same unique id.
|
||||
NzbDrone attempts to resolve this issue automatically, occassionally drone may be unable to make that association and cause a 'Completed' download to be listed in the History -> Queue table forever.
|
||||
Sonarr attempts to resolve this issue automatically, occassionally Sonarr may be unable to make that association and cause a 'Completed' download to be listed in the History -> Queue table forever.
|
||||
The easiest way to resolve this is to clear your Download Client history, or only those individual items. Alternatively you can rename the category.
|
||||
|
||||
#### Download Client has history items in Drone Factory conflicting with Completed Download Handling ####
|
||||
|
||||
The Download Client put finished downloads inside the Drone Factory even though Completed Download Handling is configured.
|
||||
This could potentially cause both Completed Download Handling and the Drone Factory logic to import the same download simultaneously.
|
||||
To avoid conflicts NzbDrone will ignore those downloads during it's Completed Download Handling logic, leaving it to be handled by the Drone Factory.
|
||||
To avoid conflicts Sonarr will ignore those downloads during it's Completed Download Handling logic, leaving it to be handled by the Drone Factory.
|
||||
This is a suboptimal situation since this effectively disabled Completed Download Handling.
|
||||
|
||||
Resolution: Configure the Drone Factory to use a different folder.
|
||||
@ -99,12 +99,12 @@ _**TODO: Reword**_
|
||||
|
||||
#### No indexers are enabled ####
|
||||
|
||||
NzbDrone requires indexers to be able to discover new releases.
|
||||
Sonarr requires indexers to be able to discover new releases.
|
||||
Please read the wiki on instructions how to add indexers.
|
||||
|
||||
#### Enabled indexers do not support searching ####
|
||||
|
||||
None of the indexers you have enabled support searching. This means NzbDrone will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results.
|
||||
None of the indexers you have enabled support searching. This means Sonarr will only be able to find new releases via the RSS feeds. But searching for episodes (either Automatic Search or Manual Search) will never return any results.
|
||||
Obviously, the only way to remedy it is to add another indexer.
|
||||
|
||||
### Series Folders ###
|
||||
|
@ -1,16 +1,16 @@
|
||||
##Overview##
|
||||
All operations (search and sync) will be use all configured indexers when they run, with the exception of Womble's which supports sync only.
|
||||
|
||||
When searching, drone will request the first 100 results, if more than 90 successful results are returned it will request the next 100 results from the indexer, to a maximum of 1000 results. If the indexer doesn't support paging, we make every effort to avoid requesting additional results.
|
||||
When searching, Sonarr will request the first 100 results, if more than 90 successful results are returned it will request the next 100 results from the indexer, to a maximum of 1000 results. If the indexer doesn't support paging, we make every effort to avoid requesting additional results.
|
||||
|
||||
##Recent Releases Feed##
|
||||
This is the indexer's latest TV releases, which usually contains 100 releases. By default drone fetches this feed every 15 minutes, configurable on Settings-> Indexers (with advanced settings visible).
|
||||
This is the indexer's latest TV releases, which usually contains 100 releases. By default Sonarr fetches this feed every 15 minutes, configurable on Settings-> Indexers (with advanced settings visible).
|
||||
|
||||
##Episode Search##
|
||||
Performs a search to each configured indexer with for a single episode. In the case of Missing's "Search Selected" it will trigger a search for each selected episode individually.
|
||||
|
||||
##Season Search##
|
||||
When searching for a full season (from the Series' details page) drone will make a single call for the first page of results, if additional results are available them drone will request them as well.
|
||||
When searching for a full season (from the Series' details page) Sonarr will make a single call for the first page of results, if additional results are available them Sonarr will request them as well.
|
||||
|
||||
##Series Search##
|
||||
Each season is searched individually and follows the normal season searching as outlined above.
|
@ -1,8 +1,8 @@
|
||||
# Windows
|
||||
1. Download the latest version of NzbDrone from [http://www.sonarr.tv](http://www.sonarr.tv "http://www.sonarr.tv")
|
||||
2. Extract the zip file into your target directory. Use a folder that NzbDrone process would have write access to (**DO NOT** use `C:\Program Files` or `C:\Program Files (x86)`)
|
||||
1. Download the latest version of Sonarr from [https://sonarr.tv](https://sonarr.tv "https://sonarr.tv")
|
||||
2. Extract the zip file into your target directory. Use a folder that Sonarr process would have write access to (**DO NOT** use `C:\Program Files` or `C:\Program Files (x86)`)
|
||||
3. Run `NzbDrone.exe` once as administrator to register the port and URL with Windows (Required for remote access)<sup>1</sup>
|
||||
4. Manually start NzbDrone by running `Nzbdrone.exe` or `ServiceInstall.exe` to install NzbDrone as a Windows service.
|
||||
4. Manually start Sonarr by running `Nzbdrone.exe` or `ServiceInstall.exe` to install Sonarr as a Windows service.
|
||||
5. Open [http://localhost:8989](http://localhost:8989) in your browser
|
||||
|
||||
|
||||
@ -16,7 +16,7 @@
|
||||
|
||||
mono 3.10 is included for x86/x64 in our repo (mirrored from Xamarin's), for other platforms you may have to compile it yourself: http://www.lovesmesomecode.com/20130719-compiling-mono-3-in-ubuntu/
|
||||
|
||||
**Add NzbDrone's repository to your software source**
|
||||
**Add Sonarr's repository to your software source**
|
||||
|
||||
|
||||
sudo apt-key adv --keyserver keyserver.ubuntu.com --recv-keys FDA5DFFC
|
||||
@ -24,12 +24,12 @@ mono 3.10 is included for x86/x64 in our repo (mirrored from Xamarin's), for oth
|
||||
|
||||
*If you have issues with the repo being https you can install the `apt-transport-https` package or switch to http*
|
||||
|
||||
**Install/Update NzbDrone**
|
||||
**Install/Update Sonarr**
|
||||
|
||||
sudo apt-get update
|
||||
sudo apt-get install nzbdrone
|
||||
|
||||
**Start NzbDrone**
|
||||
**Start Sonarr**
|
||||
|
||||
mono /opt/NzbDrone/NzbDrone.exe
|
||||
|
||||
@ -37,7 +37,7 @@ mono 3.10 is included for x86/x64 in our repo (mirrored from Xamarin's), for oth
|
||||
|
||||
http://localhost:8989
|
||||
|
||||
**Automatically Start NzbDrone**
|
||||
**Automatically Start Sonarr**
|
||||
|
||||
[[Autostart on Linux]]
|
||||
|
||||
|
@ -1,5 +1,5 @@
|
||||
### Location ###
|
||||
The location of the log files depends on the OS, but is in NzbDrone's AppData directory, you can check the location of the AppData directory on the System Info page.
|
||||
The location of the log files depends on the OS, but is in Sonarr's AppData directory, you can check the location of the AppData directory on the System Info page.
|
||||
|
||||
##### Windows #####
|
||||
`C:\ProgramData\NzbDrone\logs`
|
||||
@ -9,7 +9,7 @@ The location of the log files depends on the OS, but is in NzbDrone's AppData di
|
||||
|
||||
|
||||
### Trace/Debug Logs ###
|
||||
You can enable Trace or Debug logging in Settings on the General tab. NzbDrone does not need to restarted for the change to take effect. This change only effects the log files, not the logging database.
|
||||
You can enable Trace or Debug logging in Settings on the General tab. Sonarr does not need to restarted for the change to take effect. This change only effects the log files, not the logging database.
|
||||
|
||||
|
||||
### Clearing Logs ###
|
||||
|
@ -5,11 +5,11 @@
|
||||
- Doesn't scan your hard drive every minute for new downloads to complete
|
||||
- Waits for files to be extracted by your download client and post-processing script run before attempting to move it (should eliminate issues with partially extract files being moved)
|
||||
- Tracks downloads through post processing state (instead of showing as missing until its imported)
|
||||
- Gets the file path to the download directly via the api, so the user doesn't have to configure it in drone.
|
||||
- Gets the file path to the download directly via the api, so the user doesn't have to configure it in Sonarr.
|
||||
- Better scene name handling. We can attach the actual scene name to database instead of the file name which can be pretty cryptic at times
|
||||
|
||||
##### Cons:
|
||||
- Requires NzbDrone and your download client to be on the same machine (they can be on different machines as long as both drone and your download client see the exact same path (not just the same location)
|
||||
- Requires Sonarr and your download client to be on the same machine (they can be on different machines as long as both Sonarr and your download client see the exact same path (not just the same location)
|
||||
|
||||
## Migration Scenarios
|
||||
|
||||
@ -20,7 +20,7 @@ The health check link will attempt to direct you to the scenario specific for yo
|
||||
|
||||
Steps:
|
||||
|
||||
1. Create a new category with different output path and select that category in the NzbDrone SABnzbd settings page.
|
||||
1. Create a new category with different output path and select that category in the Sonarr SABnzbd settings page.
|
||||
Do **not** adjust the Drone Factory Folder to use the same path.
|
||||
|
||||
2. Once that's done you're ready to enable Completed Download Handling.
|
||||
@ -31,24 +31,24 @@ _Your Download Client is configured to use a category which put completed downlo
|
||||
|
||||
Steps:
|
||||
|
||||
1. Create a new category with different output path and select that category in the NzbDrone Nzbget settings page.
|
||||
1. Create a new category with different output path and select that category in the Sonarr Nzbget settings page.
|
||||
Do **not** adjust the Drone Factory Folder to use the same path.
|
||||
|
||||
2. Once that's done you're ready to enable Completed Download Handling.
|
||||
|
||||
#### Nzbget: Enable Completed Download Handling
|
||||
|
||||
_NzbDrone didn't detect any potential conflicts with your configuration. So you should be ready to enable Completed Download Handling._
|
||||
_Sonarr didn't detect any potential conflicts with your configuration. So you should be ready to enable Completed Download Handling._
|
||||
|
||||
Steps:
|
||||
|
||||
1. Enable Completed Download Handling by toggling the switch on the NzbDrone Settings -> Download Client page.
|
||||
1. Enable Completed Download Handling by toggling the switch on the Sonarr Settings -> Download Client page.
|
||||
|
||||
#### Unsupported: Download Client on Different Computer
|
||||
|
||||
_As mentioned earlier, Completed Download Handling gets the file path to the download directly from the Download Client. Such a path is inaccessible from different computers and would prevent Completed Download Handling from importing the download._
|
||||
|
||||
The best solution to this problem is to run NzbDrone and your Download Client on the same computer.
|
||||
The best solution to this problem is to run Sonarr and your Download Client on the same computer.
|
||||
|
||||
_There are some advanced options to work around this limitation, but those will not be discussed here_
|
||||
|
||||
|
@ -2,7 +2,7 @@
|
||||
|
||||
If a series is monitored then the episodes in that series can be grabbed, depending on their monitored state. If a series is not monitored then no episodes in that series will be grabbed.
|
||||
|
||||
Series' can be be set as monitored from the following locations in NzbDrone:
|
||||
Series' can be be set as monitored from the following locations in Sonarr:
|
||||
|
||||
- Series Details
|
||||
- Use the bookmark icon to the left of the the title.
|
||||
@ -15,7 +15,7 @@ Series' can be be set as monitored from the following locations in NzbDrone:
|
||||
|
||||
Unmonitoring a season will unmonitor the episodes in that season, both current and future. If a season is unmonitored then the episodes within that season can still be marked as monitored. These episode will not be blocked in the same way as when a series is unmonitored.
|
||||
|
||||
A season's monitored state can be toggled from the following locations within NzbDrone:
|
||||
A season's monitored state can be toggled from the following locations within Sonarr:
|
||||
|
||||
- Series Details
|
||||
- Use the bookmark icon to the left of the season header
|
||||
@ -24,12 +24,12 @@ A season's monitored state can be toggled from the following locations within Nz
|
||||
|
||||
## Episode ##
|
||||
|
||||
If you came here looking for an answer why NzbDrone does not automatically search for missing episodes, please view the [FAQ](https://github.com/NzbDrone/NzbDrone/wiki/FAQ#why-doesnt-nzbdrone-automatically-search-for-missing-episodes).
|
||||
If you came here looking for an answer why Sonarr does not automatically search for missing episodes, please view the [FAQ](https://github.com/Sonarr/Sonarr/wiki/FAQ#why-doesnt-nzbdrone-automatically-search-for-missing-episodes).
|
||||
|
||||
|
||||
If an episode is not monitored then it will not be grabbed, regardless of the monitored state of the series. If an episode is monitored and the series is not, it will be considered unmonitored.
|
||||
|
||||
An episode's monitored state can be toggled from the following locations within NzbDrone:
|
||||
An episode's monitored state can be toggled from the following locations within Sonarr:
|
||||
|
||||
- Series Details
|
||||
- Use the bookmark icon next to the episode number on the left side
|
||||
|
@ -1,5 +1,5 @@
|
||||
## What is a profile ##
|
||||
A profile controls what qualities you want for a series, it lets you decide whether or not you want SDTV or HDTV only and if you eventually want episodes in DVD or Bluray. NzbDrone ships with a few default profiles, but you're able to edit and create your own to match your preferences. Sonarr uses your profile when considering a release for grabbing.
|
||||
A profile controls what qualities you want for a series, it lets you decide whether or not you want SDTV or HDTV only and if you eventually want episodes in DVD or Bluray. Sonarr ships with a few default profiles, but you're able to edit and create your own to match your preferences. Sonarr uses your profile when considering a release for grabbing.
|
||||
|
||||
## What makes a profile? ##
|
||||
|
||||
@ -26,13 +26,13 @@ SDTV
|
||||
SDTV
|
||||
|
||||
##### Scenario 1 #####
|
||||
No existing file exists. When drone finds a release for this episode it will accept either SDTV or DVD, any other quality is rejected.
|
||||
No existing file exists. When Sonarr finds a release for this episode it will accept either SDTV or DVD, any other quality is rejected.
|
||||
|
||||
##### Scenario 2 #####
|
||||
Existing file is SDTV. If a DVD release is found it will be rejected because the cutoff has already been met.
|
||||
|
||||
##### Scenario 3 #####
|
||||
No existing files exists. A search is performed and both SDTV and DVD are available, NzbDrone will grab the DVD release because it is the best allowed quality.
|
||||
No existing files exists. A search is performed and both SDTV and DVD are available, Sonarr will grab the DVD release because it is the best allowed quality.
|
||||
|
||||
|
||||
### HDTV 720p ###
|
||||
@ -48,7 +48,7 @@ WEBDL 720p
|
||||
|
||||
|
||||
##### Scenario 1 #####
|
||||
No existing file exists. if NzbDrone finds a WEBDL 720p release it would grab it.
|
||||
No existing file exists. if Sonarr finds a WEBDL 720p release it would grab it.
|
||||
|
||||
##### Scenario 2 #####
|
||||
Existing file exists at HDTV 720p. If a Bluray720p release is found it will be grabbed because the cutoff has not been met
|
||||
|
@ -1,8 +1,8 @@
|
||||
### Why do I need to create an Application ###
|
||||
Each user is required to create an application in order to avoid reaching the PushOver API call limit. Drone has reached a point where its best for our users and for PushOver if each user has their own account. This avoids hitting the API limit like we did in December 2013.
|
||||
Each user is required to create an application in order to avoid reaching the PushOver API call limit. Sonarr has reached a point where its best for our users and for PushOver if each user has their own account. This avoids hitting the API limit like we did in December 2013.
|
||||
|
||||
### What does this new application give me ###
|
||||
It gives you the ability to send up to 7500 messages per month, instead of the current 15000 limit we have imposed for all users.
|
||||
|
||||
### Where do I get the API Key? ###
|
||||
The API Key is found within application you created for your Drone, if you need to create one, you can do so here: https://pushover.net/apps/clone/nzbdrone
|
||||
The API Key is found within application you created for your Sonarr, if you need to create one, you can do so here: https://pushover.net/apps/clone/nzbdrone
|
@ -3,7 +3,7 @@
|
||||
We do everything we can to prevent issues when upgrading, but they occur, this will walk you through the steps of recovering your installation.
|
||||
|
||||
### Determine the issue ###
|
||||
The single best place to look when drone won't start after an update is to check your log files, before trying to start drone again, grab your log files [[Log Files]].
|
||||
The single best place to look when Sonarr won't start after an update is to check your log files, before trying to start Sonarr again, grab your log files [[Log Files]].
|
||||
|
||||
##### Migration Issue #####
|
||||
Migration errors won't be identical, but here is an example:
|
||||
@ -18,6 +18,6 @@ While Processing: "ALTER TABLE "QualityProfiles" ADD COLUMN "Items" TEXT"
|
||||
In the event of a migration issue there is much you can do immediately, if the issue is specific to you (or there are not yet any posts), please create a post of the forums, if there are others with the same issue, then rest assured we are working on it.
|
||||
|
||||
### Manually upgrading ###
|
||||
Grab the latest release from http://www.nzbdrone.com - if you're running the develop version you can get the latest release here: http://update.nzbdrone.com/v2/develop/latest
|
||||
Grab the latest release from https://sonarr.tv - if you're running the develop version you can get the latest release here: https://download.sonarr.tv/v2/develop/latest
|
||||
|
||||
Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run drone as you normally would.
|
||||
Install the update (.exe) or extract (.zip) the contents over your existing installation and re-run Sonarr as you normally would.
|
@ -17,7 +17,7 @@
|
||||
|
||||
You probably should update your sources.list file too if you installed using aptitude/apt-get:
|
||||
|
||||
deb http://update.nzbdrone.com/repos/apt/debian develop main
|
||||
deb http://apt.sonarr.tv/ develop main
|
||||
|
||||
## Checking the release notes/changes ##
|
||||
|
||||
|
10
SSL.md
10
SSL.md
@ -6,14 +6,14 @@
|
||||
- Hash/Thumbprint of the certificate (http://msdn.microsoft.com/en-us/library/ms734695.aspx)
|
||||
|
||||
### Enabling SSL ###
|
||||
You will need to edit NzbDrone's config file directly as these settings are not exposed in the UI
|
||||
You will need to edit Sonarr's config file directly as these settings are not exposed in the UI
|
||||
|
||||
1. Go to Settings -> General
|
||||
2. Show advanced options
|
||||
3. Enable SSL, set the SSL port and Certificate Hash (drone will remove all spaces from the hash as they are not required).
|
||||
3. Enable SSL, set the SSL port and Certificate Hash (Sonarr will remove all spaces from the hash as they are not required).
|
||||
4. Restart NzbDrone.exe or NzbDrone.Console.exe as administrator (so the SSL URL and Certificate can be registered with Windows).
|
||||
5. Verify SSL connectivity
|
||||
6. Restart NzbDrone in your preferred method (service, exe, console)
|
||||
6. Restart Sonarr in your preferred method (service, exe, console)
|
||||
|
||||
## Linux / OS X ##
|
||||
|
||||
@ -26,10 +26,10 @@ You will need to edit NzbDrone's config file directly as these settings are not
|
||||
3. Run pvk.exe via Command Prompt: `pvk.exe -in yourdomain.key -topvk -nocrypt -out yourdomain.pvk`
|
||||
- Load cert with httpcfg (comes with mono): httpcfg -add -port SSL_PORT -pvk yourdomain.pvk -cert yourdomain.crt
|
||||
|
||||
*replace SSL_PORT with the SSL port you set in drone*
|
||||
*replace SSL_PORT with the SSL port you set in Sonarr*
|
||||
|
||||
### Enabling SSL ###
|
||||
|
||||
1. Enable SSL on Settings -> General
|
||||
2. Restart NzbDrone
|
||||
2. Restart Sonarr
|
||||
3. Verify!
|
@ -10,14 +10,14 @@
|
||||
## SABnzbd
|
||||
- Disable TV sorting (Config -> Sorting -> Series Sorting)
|
||||
- Create a category for TV shows
|
||||
- Configure NzbDrone to use the TV category; ensuring the path back to your DroneFactory folder is accurate and reachable (if across a network)
|
||||
- Configure Sonarr to use the TV category; ensuring the path back to your DroneFactory folder is accurate and reachable (if across a network)
|
||||
|
||||
## NzbDrone
|
||||
## Sonarr
|
||||
- The TV category for your download client (if applicable)
|
||||
- The Drone Factory folder to be the same as your download client's *Completed Download Folder*/*Completed TV Download Folder* (if you're using a category with SABnzbd this needs to be the *Completed TV Download Folder* see SABnzbd's category config page for the path)
|
||||
|
||||
## The Import Process ##
|
||||
NzbDrone does a number of checks to verify that the download is acceptable for importing, including:
|
||||
Sonarr does a number of checks to verify that the download is acceptable for importing, including:
|
||||
- Sample file check (run time is longer than 90 seconds)
|
||||
- Upgrade for existing episode file (if any)
|
||||
- Not being unpack by the download client (_UNPACK_ in SABnzbd)
|
||||
|
10
Updating.md
10
Updating.md
@ -1,6 +1,6 @@
|
||||
## General ##
|
||||
|
||||
**Branch** - You can change the branch NzbDrone will use to update, see [[Release Branches]] for more information.
|
||||
**Branch** - You can change the branch Sonarr will use to update, see [[Release Branches]] for more information.
|
||||
|
||||
## Windows ##
|
||||
|
||||
@ -14,17 +14,17 @@ Both Linux and OS X now have the ability to update directly from the UI or autom
|
||||
**Automatic** - Enable automatic updating, please test the update process manually to ensure it will work for your setup before enabling
|
||||
|
||||
**Mechanism**
|
||||
- **Built-in** - Use NzbDrone's own updater
|
||||
- **Script** - Use a custom external script to update NzbDrone, it will need to take care of stopping and starting drone during the update process
|
||||
- **Built-in** - Use Sonarr's own updater
|
||||
- **Script** - Use a custom external script to update Sonarr, it will need to take care of stopping and starting Sonarr during the update process
|
||||
|
||||
**Script** - Visible only when *Mechanism* is set to *Script* - Path to update script
|
||||
|
||||
|
||||
### Update Process ###
|
||||
NzbDrone will download the update file, verify its integrity and extract it to a temporary location and call the chosen method. The update process will be be run under the same user that NzbDrone is run under, it will need permissions to update the NzbDrone files as well as stop/start NzbDrone.
|
||||
Sonarr will download the update file, verify its integrity and extract it to a temporary location and call the chosen method. The update process will be be run under the same user that Sonarr is run under, it will need permissions to update the Sonarr files as well as stop/start Sonarr.
|
||||
|
||||
#### Built-in ####
|
||||
The built-in method will backup NzbDrone files and settings, stop NzbDrone, update the installation and Start NzbDrone, if your system will not handle the stopping of NzbDrone and will attempt to restart it automatically it may be best to use a script instead. In the event of failure the previous version of NzbDrone will be restarted.
|
||||
The built-in method will backup Sonarr files and settings, stop Sonarr, update the installation and Start Sonarr, if your system will not handle the stopping of Sonarr and will attempt to restart it automatically it may be best to use a script instead. In the event of failure the previous version of Sonarr will be restarted.
|
||||
|
||||
|
||||
#### Script ####
|
||||
|
Loading…
Reference in New Issue
Block a user