From c622517ea937972aaf4a75b4b5daecf5acb1f958 Mon Sep 17 00:00:00 2001 From: basilfx Date: Thu, 25 Sep 2014 17:50:01 -0700 Subject: [PATCH] Updated Troubleshooting (markdown) --- Troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/Troubleshooting.md b/Troubleshooting.md index 05e0849..fa027bd 100644 --- a/Troubleshooting.md +++ b/Troubleshooting.md @@ -15,10 +15,10 @@ The second option will be the easiest option in most cases, especially for Synol ## Second of all: rule-out human error ## There are a lot of issues that can be solved by just reviewing your settings. Before continuing (or posting an issue), consider the following general advice: -* Review your settings. If possible, start from scratch (backup your files!) +* Review your settings. If possible, try to start from scratch (just run a separate install from another directory), to isolate the problem. * Check the permissions. Under Linux, `ls -al` should list the files in the current folder. The user owning the files is shown too, which should match the running user. * Try to start Headphones directly, not via an init script or service. Type `python Headphones.py -h` to see how to start it directly, and as a tip: make sure the paths to your configuration files are correct! -* Use Google! It's for a reason we put so much logging in Headphones. Sometimes, Google yields the answer by just copy-pasting the error message. +* 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_: