Updated Troubleshooting (markdown)

basilfx
2014-11-10 04:11:07 -08:00
parent 4e6585c57d
commit 4120b8d003
+19 -7
@@ -24,7 +24,7 @@ There are a lot of issues that can be solved by just reviewing your settings. Be
* Use Google! It's for a reason we put so much logging in Headphones. Sometimes, Google just yields the answer by copy-pasting the error message.
## Cannot reach MusicBrainz server ##
_Symptons_:
_Symptoms_:
```
WARNING Attempt to query MusicBrainz for XXXX failed (retried 3 times, caused by: HTTP Error 502: Bad Gateway)
```
@@ -56,7 +56,7 @@ _Solutions_:
* 5xx — Remote server error, nothing you can do right now.
## (Auto) update does not work ##
_Symptons_:
_Symptoms_:
Headphones tells you there is a new version available, but an update fails. The version number does not change.
Or:
@@ -105,7 +105,7 @@ Sometimes, you just want to go back to an older version. For instance, there is
* `git reset --hard PUT_HASH_HERE` — this WILL overwrite all local changes! It will spare your config and database.
## SSL-enabled servers/indexers/search providers don't work ##
_Symptons:_
_Symptoms:_
When using SSL-enabled search providers (ones starting with HTTPS in their URL), it fails to connect and return search results. Optionally, if I surf to the URL, my browser gives a certificate warning.
@@ -122,7 +122,7 @@ _Solutions_:
* Start Headphones again.
## Settings cannot be saved or disappear ##
_Symptons_:
_Symptoms_:
When I settings are saved, they don't persist.
Or:
@@ -137,7 +137,7 @@ _Solutions_:
* Disable auto complete. There are reports of browsers autocompleting fields.
## Snatched downloads aren't picked up by downloader
_Symptons_:
_Symptoms_:
When Headphones snatches a release, it doesn't appear in my downloader (NZBget, SABnzbd, Transmission, uTorrent, black hole).
_Solutions_:
@@ -150,7 +150,7 @@ _Solutions_:
* Check the watch interval settings of your downloader.
## Headphones installed as daemon does not work
_Symptons_:
_Symptoms_:
When I installed Headphones as a daemon, it does nothing when I start it (e.g. `service headphones start`).
Or:
@@ -163,4 +163,16 @@ _Solutions_:
* Make sure you have the service enabled. For instance, under Ubuntu/Debian you have to mark a service to startup on boot with `sudo update-rc.d headphones defaults`. Refer to [[Install as a daemon]] for more information.
* Make sure that the daemon user has write permissions to the data folder, and that the data folder exist. A common mistake is that Headphones was first setup to run as normal, and then installed as daemon with a special daemon user. In most cases, the daemon user cannot access normal user's files.
* Make sure no other service is running on the configured port. Also note that ports below 1024 require root privileges.
* Debug the startup script. One way is to edit the startup script and remove the `--daemon` and `--quiet` option from the launch options and add the `--verbose` option. For instance, see [Line 112](https://github.com/rembo10/headphones/blob/master/init-scripts/init.ubuntu#L112) in the Ubuntu launch script. Now when you start the script, it should start in the foreground. Any errors will now be printed to console or log file.
* Debug the startup script. One way is to edit the startup script and remove the `--daemon` and `--quiet` option from the launch options and add the `--verbose` option. For instance, see [Line 112](https://github.com/rembo10/headphones/blob/master/init-scripts/init.ubuntu#L112) in the Ubuntu launch script. Now when you start the script, it should start in the foreground. Any errors will now be printed to console or log file.
## Database problems ##
_Symptoms_:
I regularly see `Database is locked` in the logs.
or
I get exceptions such as `DatabaseError: database disk image is malformed`.
_Solutions_:
* In case of locked databases, try to increase interval settings for scanning and so forth. If you have a huge library, scanning takes a while. Any other operations may already be started, causing locking conflicts.
* In case of corruption, see [#1178](https://github.com/rembo10/headphones/issues/1178), [#1053](https://github.com/rembo10/headphones/issues/1053), [#1676](https://github.com/rembo10/headphones/issues/1676) or [#1981](https://github.com/rembo10/headphones/issues/1981).