Daemonize-liquidsoap.sh fails, Unable to find liquidsoap_binary in your path

[dikkedimi]

I'm having trouble daemonizing liquidsoap.

I first tried by installing release 1 from the liquidsoap-daemon repo

wget https://github.com/savonet/liquidsoap-daemon/releases/download/1.0.0/liquidsoap-daemon-1.0.0.tar.gz
tar -xf liquidsoap-daemon-1.0.0.tar.gz
cd ~/liquidsoap-daeon-1.0.0/
./daemonize-liquidsoap.sh /etc/liquidsoap/sharedencoding-failover.liq
sudo ./daemonize-liquidsoap.sh /etc/liquidsoap/sharedencoding-failover
Unable to find liquidsoap_binary in your path.
user@radio:~/liquidsoap-daemon-1.0.0$ ./daemonize-liquidsoap.sh /etc/liquidsoap/sharedencoding-failover
./daemonize-liquidsoap.sh: 79: cannot create /home/user/liquidsoap-daemon-1.0.0/script//etc/liquidsoap/sharedencoding-failover-run.liq: Directory nonexistent
./daemonize-liquidsoap.sh: 87: cannot create /home/user/liquidsoap-daemon-1.0.0/script//etc/liquidsoap/sharedencoding-failover-run.liq: Directory nonexistent
./daemonize-liquidsoap.sh: 97: cannot create /home/user/liquidsoap-daemon-1.0.0/script//etc/liquidsoap/sharedencoding-failover-run.liq: Directory nonexistent
Creating dummy file
./daemonize-liquidsoap.sh: 101: cannot create /home/user/liquidsoap-daemon-1.0.0/script//etc/liquidsoap/sharedencoding-failover.liq: Directory nonexistent
./daemonize-liquidsoap.sh: 110: cannot create /etc/liquidsoap/sharedencoding-failover-liquidsoap.systemd: Permission denied

I then tried to install it using opam, after removing the liquidsoap-daeon-1.0.0 directory.

user@radio:~/liquidsoap-2.0.0-beta2$ opam install liquidsoap-daemon
The following actions will be performed:
  ∗ install liquidsoap-daemon 1.0.0  This package installs the daemonize-liquidsoap.sh script in your $PATH. Once installed, you should
                                     execute it to configure the liquidsoap daemon. Please see: https://github.com/savonet/liquidsoap-daemon
                                     for more information about how to run the script.

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><><><>
⬇ retrieved liquidsoap-daemon.1.0.0  (https://opam.ocaml.org/cache)
∗ installed liquidsoap-daemon.1.0.0
Done.
user@radio:~/liquidsoap-2.0.0-beta2$ daemonize-liquidsoap.sh /home/user/assets/recipes/sharedencoding-failover.liq 
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 17: [: /: unexpected operator
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 25: cd: can't cd to /home/user/.opam/4.08.0/bin//home/user/.opam/4.08.0/share
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 79: cannot create /home/user/liquidsoap-2.0.0-beta2/script//home/user/assets/recipes/sharedencoding-failover.liq-run.liq: Directory nonexistent
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 87: cannot create /home/user/liquidsoap-2.0.0-beta2/script//home/user/assets/recipes/sharedencoding-failover.liq-run.liq: Directory nonexistent
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 97: cannot create /home/user/liquidsoap-2.0.0-beta2/script//home/user/assets/recipes/sharedencoding-failover.liq-run.liq: Directory nonexistent
Creating dummy file
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 101: cannot create /home/user/liquidsoap-2.0.0-beta2/script//home/user/assets/recipes/sharedencoding-failover.liq.liq: Directory nonexistent
cat: liquidsoap.systemd.in: No such file or directory
user@radio:~$ daemonize-liquidsoap.sh ../user/assets/recipes/sharedencoding-failover.liq
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 17: [: /: unexpected operator
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 25: cd: can't cd to /home/user/.opam/4.08.0/bin//home/user/.opam/4.08.0/share
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 79: cannot create /home/user/script/../user/assets/recipes/sharedencoding-failover.liq-run.liq: Directory nonexistent
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 87: cannot create /home/user/script/../user/assets/recipes/sharedencoding-failover.liq-run.liq: Directory nonexistent
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 97: cannot create /home/user/script/../user/assets/recipes/sharedencoding-failover.liq-run.liq: Directory nonexistent
Creating dummy file
/home/user/.opam/4.08.0/bin/daemonize-liquidsoap.sh: 101: cannot create /home/user/script/../user/assets/recipes/sharedencoding-failover.liq.liq: Directory nonexistent
cat: liquidsoap.systemd.in: No such file or directory
cp: cannot create regular file '/etc/systemd/system/../user/assets/recipes/sharedencoding-failover.liq-liquidsoap.service': No such file or directory
user@radio:~/liquidsoap-2.0.0-beta2$ eval $(opam env)
user@radio:~/liquidsoap-2.0.0-beta2$ sudo ./daemonize-liquidsoap.sh /etc/liquidsoap/sharedencoding-failover
[sudo] password for user: 
sudo: ./daemonize-liquidsoap.sh: command not found

what I did notice is
can't cd to /home/user/.opam/4.08.0/bin//home/user/.opam/4.08.0/share

but as I understand,

$ eval $(opam env)

should remedy this?

With version 1 of the liquidsoap-daemon, I understand the script I want to daemonize should be in
~/liquidsoap-daemon/script

or whatever the install folder for the daemonize script is.

I'm not sure what path I should follow when installing it through opam. apparently it is in the path, but when i

sudo find / -name "daemonize-liquidsoap.sh"

it returns nothing
Any hint or breadcrumb much appreciated

[toots]

Hi,

Everything that is installed via opam lives in a local folder located at ~/.opam/<ocaml version>, typically, binaries are at: ~/.opam/<ocaml version>/bin.

eval $(opam env) updates your shell PATH variable to make sure that binaries are available from that local path. However, you need to make sure that you call the absolute binary name daemonize-liquidsoap.sh, not the relative binary name ./daemonize-liquidsoap.sh.

To investigate the error where liquidsoap cannot be found in the path, I believe you can just use the which liquidsoap command and see if it can find it.

Lastly, yes, scripts should all live under the same user's home directory for which you are using opam or, at least, a directory writable by that user.

Hope this helps!