[darkice] Re: watch darkice errors and restart if necessarily
- From: "Nathan Roberts" <nathan.roberts@xxxxxxxxx>
- To: <darkice@xxxxxxxxxxxxx>
- Date: Tue, 17 Jan 2012 23:06:42 -0000
What's the benefit in the configuration mentioned below which I understand
to be:
darkice>local shoutcast>remote shoutcast
i.e. why is this more robust?
I run my shoutcast server with autodj. AutoDJ has some tracks to loop
(keeping the stream live for any listeners who connect early) and then when
I need to broadcast from a venue, I connect over a 3G connection. While it
generally works well, as you'll appreciate network issues can be a challenge
from time to time so I'm keen to improve the robustness of the system as
best I can.
Thanks
Nathan
-----Original Message-----
From: darkice-bounce@xxxxxxxxxxxxx [mailto:darkice-bounce@xxxxxxxxxxxxx] On
Behalf Of drew Roberts
Sent: 14 January 2012 16:57
To: darkice@xxxxxxxxxxxxx
Subject: [darkice] Re: watch darkice errors and restart if necessarily
On Saturday 14 January 2012 06:16:18 JoergSorge wrote:
> Hi,
> I'm new to darkice. We will switch from an existing
> WinXP/Oddcast/Icecast to a fitPC with LinuxMint/darkice/Icecast in a
> little public Radiostation.
>
> I've all setup and it workes good up to one thing:
>
> Mostly once at a Day, I got an Error (from darkice) like "Failed to
> write to ring buffer". I mean, that occurs when darkice reconnect due
> the disconnect by the IP-Provider.
>
> Now, I try to catch up this Message and reconnect darkice.
> But my skills in Batch-Scripting are very small.
> I'd like to write a script, that:
> - start jack
> - start meterbridge
> - start rotter
> - start darkice with first stream
> - start darkice with second stream
>
> I use the scripts from Niles Dettenbach to start and stop darkice.
>
> How can I get the errormessage.
> She is not logging in the darcice.logfile, only in the terminal. But to
> Day, for me it's very hard to understand 2>&1 and so on.
>
> Can anyone help me?
First, I suggest you stop using darkice to send the stream to a remote
machine. Send to a local icecast or shoutcast (same machine or on the local
lan) and let the remote machine get the stream from the local machine. See
if
your problems go away.
>
> Regards,
> Jörg
all the best,
drew
Other related posts:
