gronod/headphones
1
0
Fork 0
mirror of https://github.com/rembo10/headphones.git synced 2026-07-21 16:34:01 +01:00
Code Issues Packages Projects Releases Wiki Activity

Updated Troubleshooting (markdown)

basilfx
2014-11-04 18:30:08 -08:00
parent 2fa1c2cc52
commit b48707cc7c
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files
Troubleshooting.md
+3 -3
@@ -158,9 +158,9 @@ Or:
Headphones does not run at startup, even though I installed it as daemon.
_Solutions_:
* See if it is actually running. Under Ubuntu/Debian `ps awx | grep Headphones` should list a process with it's startup arguments if it has started.
* See if it is not actually running. Under Ubuntu/Debian `ps awx | grep Headphones` should list a process with it's startup arguments if it has started.
* Check the log files.
* 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 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.
* 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.