camomile | gapless player for android | Music Player library

Found the issue. I had to change this line:

This should work for you.

It's a typo.

You save your tag and field in process_field(self, tag, field) in self.current_record.

What you are missing is this

It would seem that the error happens around the opam sandbox script running

Solution:

The solution, in this case, was to go into usr/local/bin where I had some previous versions of opam and opam v2 showing. I manually deleted all opam's. I then ran brew remove camlp4 ocamlbuild ocaml so that opam would only see the sandboxed version of the ocaml compiler. I deleted the ~/.opam directory then reinstalled it from git via wget https://raw.github.com/ocaml/opam/master/shell/install.sh because opam v2 is not yet available on homebrew which installs opam 1.2.

I then ran opam install core utop and ocamlbuild 1.8.0 is successfully installed.

Note: this setup did not break my reasonml projects.

I sometimes have the same problem. For whatever reason the first instance hasn't exited cleanly and is still listening on the addr/port combo of the mountpoint, preventing the new instance from binding to it. You can fix it without rebooting, you need to find the process causing the problem and then kill it.

For example let's say your mountpoint is listening on port 8800, you can use the lsof command to identify the old process. Add the -i option and specify the interface/port to return results for and you'll get something like this:

lsof -i:8800

OK, so Icecast itself seems to be running fine. (you can see it answering a simple request for '/' from localhost) If you don't see at least the very basic web interface, please check your firewall settings and browser. Consider adding :: and restarting Icecast (sudo systemctl restart icecast2.service or sudo /etc/init.d/icecast2 restart) for improved compatibility. (That will bind to IPv6 and legacy-IP aka IPv4. It's mostly cosmetic though.)

The EROR connection/_handle_connection HTTP request parsing failed is most likely unrelated to your problems. Possibly Liquidsoap or some other process doing something stupid, but not critical.

Make sure that Liquidsoap is using the password specified here: ******

Please also examine /home/username/liquidsoap-daemon/log/radioliq.log for further hints.

On Debian and its derivatives (Ubuntu, Mint, etc) Liquidsoap runs as the liquidsoap user. By default this user does not have write access to /home/username/liquidsoap-daemon/log/radioliq.log. Either that directory needs write access given to that user or one might elect to use /var/log/liquidsoap which is already set up appropriately.

If Liquidsoap can not start logging, then it will refuse to start. Just what seems to have happened here.

There may be other problems once that's corrected, please then refer to the log for details.