Thanks all for the info! The server has been running flawlessly for over a week now, so hopefully it's just a few tracks with this metadata in our pile. I keep the logs and look for the output when it crashes. So I should be able to find the files and correct them. The documentation for Liquidsoap feels pretty experimental, not very many examples at all. It seems you just need to know things But I think we'll stick with 1.1.1 for now anyway. I could probably compile my own version of Liquidsoap, but I don't think it would be worth it It works now anyway and I want to keep from stirring too much when things are working

No problem. The Liquidsoap documentation is in some ways a little light on, and in other ways quite comprehensive. Unfortunately, it being a dynamically typed languages, the API docs are a little frustrating. And the nature of streaming radio makes debugging tools a bit hard to use. If you need any more help, feel free to hit me up. Thanks for getting the music back

Glad I could help and thanks for bringing the music back online. My workdays are better for it.

I have made som progress with posting of the current playing track. However, there are issues of course. I think the software Liquidsoap is a bit crapped. Does any of you guys out there who installed it for helping out still have it? I could use some help I'm using version 1.1 and there is a new one, version 1.2 that I would like to install. However it's not available over the usual apt-get. It's still on 1.1. Is there a way to get the new version? I don't want to download 100000 libraries and compile the junk myself, that'd be over the top probably Help!

I'm looking into it: it seems that they haven't released .debs upstream yet; I might be able to package one up. What features of 1.2 are you trying to use? Any chance you could PM me with the API you're using to post metadata on the site?

They patched a bug with http.post and http.get which didn't close the connection properly. I think that what's might mess things up for me. It's either http.post or their to.json function. I actually just want to post the full meta data as JSON when a track update happens. But it's messed up and broken on the receiving end. However, I can live with that and I do some hacking, cutting and splicing on the other end, so I actually get what I need from that broken JSON So I think I should be able to get our track information back If you could get a packaged 1.2 file I'd be happy! I'm not much of a pro with these things. I just expect things to work, and that's not something *nix does when you get off the beaten path

Alright, I think and hope I solved the track posting sufficiently using http.get instead. It seems to work! Order restored in Rivendell!