Icecast Streaming Media Server

[cmodyssey]

Hi,

I'd like to get some summary information from the icecast server and put it in a file or web page.

I'm looking to get some key events to do with source connection and disconnection, so I'd want to log the date/time and source IP address of the source for each of these events:

Source tries to connect but is unsuccessful and log why it didn't succeed (E.G. wrong password etc.)
Source connects successfully
Source disconnects from Icecast successfully
Icecast disconnects from Source and log why (E.G. timeout etc.)

I want something like this to get to the bottom of problems that occur during live broadcasting and it takes quite a while to trawl through the icecast log files, picking out stuff to start to investigate what's wrong.

Has anyone done anything like this before?

Can anyone give me any pointers?

Are there any scripts about that does something like this?

Any help in this would be greatly appreciated.

Thanks in advance.

[karlH]

If you ignore the stats updates and listener changes then you should have a small enough list of events. search for words like timeout or exit.

karl.

[cmodyssey]

Hi karl,

Thank you for getting back to me

I have been going through the log and pasted an extract from my error.log in code tags at the bottom of this posing. This shows a source connecting normally and I have put the lines that I am interested in between <interested> and </interested> virtual tags.

I can a PERL script together to extract most of what I'm interested in but I am going to have great difficulty in extracting the interested section that begins with "public (0)".

I only want to extract the log that is relevant to the mountpoint called "/live_mount"

Each set of log lines that begins with "public (0)" is logging from each mountpoint. I have three mount points set up in my icecast. I can't see a way of identifying which mountpoint the "public (0)" set of lines is for.

Can you think of a way I can successfully identify the mountpoint that I am interested in?

Thanks again.

Richard.

[karlH]

The stats engine could do with reporting the mountpoint as well (something for a later release), but the order you see them in the log is the order in which they are processed. The public setting under /live_mount is 0.

I cannot comment on why /replay_mount does not stay up but it does die immediately. If this is 2.3.1 then you may be seeing a lot more stats updating than is necessary.

karl.

[cmodyssey]

Hi Karl,

Thanks for your reply.

I know what is going on with /replay_mount.

When a source connects to /live_mount it calls the script /home/bcast/ezstream/botstop which stops my bot that is responsible for launching ezstream when there is no one playing on /live_mount

My bot connects to /replay_mount so that's why it does not stay up.

As far as the logging goes and requesting that the mountpoint name is included in the log lines when knows, shall I raise an enhancement request under trac.xiph.org?

Thank you.

Richard.

[karlH]

If you do raise it on trac then it won't get forgotten about.

karl.