Icecast Streaming Media Server

luca066 · Joined: 01 Dec 2011 Posts: 42

Hi Karl,

I'm doing some tests with the duration parameters.
I've set 86400 seconds (one day) and I've seen that usually it works.
But, if during the day I reload the configuration from the admin web pages, the duration counter restart from the begin?

Have you got any plan to create the possibility to set an exact time when the logs are archived?
Probably a fixed time like every midnight cuold be a good archive rule.

Luca

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

A reload triggers a re-open of the logs so the timer will reset. As for an absolute time then why not use cron and HUP it?

karl.

luca066 · Joined: 01 Dec 2011 Posts: 42

Hi Karl,

I'm using windows server, is it possible to HUP it?
If yes, how?

Another question: I'm using Icecast 2.3.2-kh31.4 but I need to make it works on two different tcp ports.
At the moment, I've to specify the ip address of the machine on the <listen-socket> section, otherwise the server works only using http://localhost:port_number (and it works only locally).
It's seems that this icecast version, if I don't specify the ip address, bind the IPV6 localhost address.
So, I've this:

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

Firstly, I've updated the current test build

www.xiphicecast.webspace.virginmedia.com/icecast-2.3.2-kh31.13_setup.exe

Can you confirm whether or not the issues still affect the current tree.

Obviously you cannot use HUP, but the provided admin pages do link in a reload option which you can use on windows.

I've just tried using multiple listen-socket definitions with and without bind and it works as expected here. If you have an issue then send me the xml and a netstat -an listing referring to the sockets in question.

karl.

luca066 · Joined: 01 Dec 2011 Posts: 42

Hi Karl,

I'm sorry if I answer too late.
I confirm that with kh31.13 I can bind more that one ports using the listen socket:

karlH · Code Warrior Joined: 13 Jun 2005 Posts: 5476 Location: UK

I don't do anything different in the code between 2003 and 2008 so any difference is done at the windows OS side of things.

From some checking I've done it seems that MS introduced a bug on the call listing the ipv4/ipv6 details and pass back the local interfaces first which is what you are experiencing. The adding of bind-address means that the returned list has those local addresses removed.

http://support.microsoft.com/kb/2621067

It looks like they have done a fix but I'm unsure if they are intending to put this into the main updates or not.

karl.