Icecast Streaming Media Server Forum Index Icecast Streaming Media Server
Icecast is a Xiph Foundation Project
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

Directory listings
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
 
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Icecast Server
View previous topic :: View next topic  
Author Message
gee2803



Joined: 11 Aug 2006
Posts: 48

PostPosted: Fri Nov 04, 2011 3:30 am    Post subject: Reply with quote

Thank you. The directory listing was not activated on the slaves. I will reconfigure this later.

Is it possible to have a look at the master server to read out the concurrent listener data or will it always just show the mountpoint data?

At the moment we are retrieving all listener stats from each server but the master server should know how many listeners are attached or doesn't it?
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Fri Nov 04, 2011 3:51 pm    Post subject: Reply with quote

The master will only know about the data relating to itself, the slaves are not communicating there details up. The stats link could be used for that but it's not ready for that yet.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
YASPE



Joined: 24 Feb 2012
Posts: 3

PostPosted: Sat Feb 25, 2012 5:17 pm    Post subject: New YP Directory Reply with quote

There is a new yp directory for your icecast server. Here is the source code:

<directory>
<yp-url-timeout>15</yp-url-timeout>
<yp-url>http://www.radioes.net/yp.asp</yp-url>
</directory>

You can see it at www.radioes.net/icecast.asp
Back to top
View user's profile Send private message Visit poster's website
tisho



Joined: 21 May 2012
Posts: 5

PostPosted: Thu Jun 07, 2012 11:28 am    Post subject: Not listed Reply with quote

Code:
<icecast>
    <limits>
        <clients>50</clients>
        <sources>3</sources>
        <threadpool>5</threadpool>
        <queue-size>102400</queue-size>
        <client-timeout>30</client-timeout>
        <header-timeout>15</header-timeout>
        <source-timeout>10</source-timeout>
        <!-- If enabled, this will provide a burst of data when a client
             first connects, thereby significantly reducing the startup
             time for listeners that do substantial buffering. However,
             it also significantly increases latency between the source
             client and listening client.  For low-latency setups, you
             might want to disable this. -->
        <burst-on-connect>1</burst-on-connect>
        <!-- same as burst-on-connect, but this allows for being more
             specific on how much to burst. Most people won't need to
             change from the default 64k. Applies to all mountpoints  -->
        <burst-size>65535</burst-size>
    </limits>

    <authentication>
        <!-- Sources log in with username 'source' -->
        <source-password>djpassword</source-password>
        <!-- Relays log in username 'relay' -->
        <relay-password>password</relay-password>

        <!-- Admin logs in with the username given below -->
        <admin-user>admin</admin-user>
        <admin-password>password</admin-password>
    </authentication>


    <directory>
        <yp-url-timeout>15</yp-url-timeout>
        <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
    </directory>

    <directory>
        <yp-url-timeout>10</yp-url-timeout>
        <yp-url>http://openradiodirectory.org/yp.php</yp-url>
    </directory>
 
     

    <!-- This is the hostname other people will use to connect to your server.
    It affects mainly the urls generated by Icecast for playlists and yp
    listings. -->
    <hostname>host.address.com</hostname>

    <!-- You can use these two if you only want a single listener -->
    <port>8000</port>
    <bind-address>79.124.67.XXX</bind-address>

    <!-- You may have multiple <listener> elements -->
    <!--
    <listen-socket>
        <port>8050</port>
        <bind-address>192.168.0.10</bind-address>
    </listen-socket>
    -->

   
    <!--
    <listen-socket>
        <port>8001</port>
    </listen-socket>
    -->

    <!-- {%comment-open-if:icecast.master-server==""%} --> <!--
    <relays-on-demand>1</relays-on-demand>
    <master-server>r1.hostname.com</master-server>
    <master-server-port>8000</master-server-port>
    <master-update-interval>10</master-update-interval>
    <master-password>password</master-password>
    --> <!-- {%comment-close-if:icecast.master-server==""%} -->
   
    <!-- {%comment-open-if:icecast.relay.server==""%} --> <!--
    <relay>
        <server>79.124.67.XXX</server>
        <port>8000</port>
        <mount>/live.ogg</mount>
        <local-mount>/stream</local-mount>
        <username>username</username>
        <password>password</password>

        <relay-shoutcast-metadata>1</relay-shoutcast-metadata>
      <on-demand>1</on-demand>
    </relay>
    --> <!-- {%comment-close-if:icecast.relay.server==""%} -->

    <!-- Only define a <mount> section if you want to use advanced options,
         like alternative usernames or passwords -->
    <mount cc="main">
        <mount-name>/stream</mount-name>

        <intro></intro>
        <fallback-mount>/live</fallback-mount>
        <fallback-override>1</fallback-override>
        <fallback-when-full>0</fallback-when-full>
      <!-- {%comment-open-if:icecast.suppressmeta=="0"%} -->
        <mp3-metadata-interval>0</mp3-metadata-interval>
      <!-- {%comment-close-if:icecast.suppressmeta=="0"%} -->

        <!--<no-yp>1</no-yp>-->
    </mount>

    <mount cc="live">
        <mount-name>/live</mount-name>

   <intro></intro>
        <fallback-mount>/autodj</fallback-mount>
        <fallback-override>1</fallback-override>
        <fallback-when-full>0</fallback-when-full>
      <!-- {%comment-open-if:icecast.suppressmeta=="0"%} -->
        <mp3-metadata-interval>0</mp3-metadata-interval>
      <!-- {%comment-close-if:icecast.suppressmeta=="0"%} -->

       <!--<no-yp>1</no-yp>-->
    </mount>

    <mount cc="autodj">
        <mount-name>/autodj</mount-name>
        <bitrate>128</bitrate>

        <intro></intro>
      <fallback-mount></fallback-mount>
      <fallback-override>1</fallback-override>
      <fallback-when-full>0</fallback-when-full>
      <!-- {%comment-open-if:icecast.suppressmeta=="0"%} -->
        <mp3-metadata-interval>0</mp3-metadata-interval>
      <!-- {%comment-close-if:icecast.suppressmeta=="0"%} -->
            
        <!--<no-yp>1</no-yp>-->
   <charset>UTF-8</charset>
    </mount>

   <fileserve>1</fileserve>

    <!-- set the mountpoint for a shoutcast source to use, the default if not
         specified is /stream but you can change it here if an alternative is
         wanted or an extension is required
    <shoutcast-mount>/live.nsv</shoutcast-mount>
    -->

    <paths>
      <!-- basedir is only used if chroot is enabled -->
        <basedir>/home/centovacast/vhosts/username/</basedir>

        <!-- Note that if <chroot> is turned on below, these paths must both
             be relative to the new root, not the original root -->
        <logdir>var/log/</logdir>
        <webroot>web/</webroot>
        <adminroot>admin/</adminroot>
        <pidfile>var/run/server.pid</pidfile>

        <!-- Aliases: treat requests for 'source' path as being for 'dest' path
             May be made specific to a port or bound address using the "port"
             and "bind-address" attributes.
          -->
        <!--
        <alias source="/foo" dest="/bar"/>
          -->
        <!-- Aliases: can also be used for simple redirections as well,
             this example will redirect all requests for http://server:port/ to
             the status page
          -->
        <alias source="/" dest="/status.xsl"/>
    </paths>

    <logging>
        <accesslog>access.log</accesslog>
        <errorlog>error.log</errorlog>
        <playlistlog>playlist.log</playlistlog>
         <loglevel>4</loglevel> <!-- 4 Debug, 3 Info, 2 Warn, 1 Error -->
    </logging>

    <security>
        <chroot>0</chroot>
        <!--
        <changeowner>
            <user>nobody</user>
            <group>nogroup</group>
        </changeowner>
        -->
    </security>
</icecast>


Where is the problem ?
My radiostation is not listed in any of the online YP...
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jun 07, 2012 1:40 pm    Post subject: Reply with quote

There are many possible reasons for not listing on the YP, the error log is one place to look, just look for lines with yp in them. Could be a icecast built without libcurl, to an incorrect <hostname> setting or just streams not flagged as public.

If you strip away all the comments from the xml then it looks like it could but obviously we don't have enough information to say why it is not listing.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
tisho



Joined: 21 May 2012
Posts: 5

PostPosted: Thu Jun 07, 2012 5:49 pm    Post subject: Reply with quote

karlH wrote:
There are many possible reasons for not listing on the YP, the error log is one place to look, just look for lines with yp in them. Could be a icecast built without libcurl, to an incorrect <hostname> setting or just streams not flagged as public.
karl.


Nothing "YP" related in the error.log and in the other logs.
And with IP in <hostname>IP</hostname> still nothing Sad
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Thu Jun 07, 2012 6:24 pm    Post subject: Reply with quote

At level 4 you will see either the fact the yp is disabled or that the directory entries you have specified have been added. Those have to occur before a stream has a chance to list.

If you are saying that nothing related appears then email me what version you have, build environment and your complete error log contents you have.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ashum



Joined: 05 Oct 2012
Posts: 3

PostPosted: Tue Oct 09, 2012 2:25 pm    Post subject: Reply with quote

How to use another port in listing directory?
I use nginx for public access to icecast:
listener -> nginx (8000 port) -> icecast (8001 port, allow nginx ip only)
source -> icecast (7000 port, allow source ip only)

Code:
   <directory>
        <yp-url-timeout>15</yp-url-timeout>
        <yp-url>http://dir.xiph.org/cgi-bin/yp-cgi</yp-url>
    </directory>

    <hostname>x.x.x.x</hostname>   
    <listen-socket>                 
        <port>7000</port>
        <bind-address>x.x.x.x</bind-address>
    </listen-socket>
    <listen-socket>
        <port>8001</port>           
        <bind-address>127.0.0.1</bind-address>
    </listen-socket>


So icecast is not available from outside directly. How to point xiph directory to use port 8000 for connections?
Now it uses address x.x.x.x:7000/mountpoint
I want it uses address x.x.x.x:8000/mountpoint.
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Tue Oct 09, 2012 9:07 pm    Post subject: Reply with quote

try adding <port>8000</port> just after <hostname> but before <listen-socket>

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
ashum



Joined: 05 Oct 2012
Posts: 3

PostPosted: Wed Oct 10, 2012 7:46 am    Post subject: Reply with quote

Thank you, Karl. It helped.
Back to top
View user's profile Send private message
BillGoldsmith



Joined: 24 Aug 2010
Posts: 9
Location: Paradise, CA

PostPosted: Sat Sep 14, 2013 6:58 pm    Post subject: Reply with quote

I have 3-4 public Icecast servers all relaying the same streams. It appears that the directory is only listing one of them, rather than grouping identical streams together, which I understand is the expected behavior. All relays of a given stream have the same mountpoint & metadata.

In the log I see entries like:

EROR yp/send_to_yp YP add on http://dir.xiph.org/cgi-bin/yp-cgi failed: Add refused. Reason: Entry already in the YP.

Any ideas?
_________________
---
Bill Goldsmith
www.radioparadise.com
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Sun Sep 15, 2013 9:57 pm    Post subject: Reply with quote

I suspect you have the same <hostname> set for each of your icecasts.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
BillGoldsmith



Joined: 24 Aug 2010
Posts: 9
Location: Paradise, CA

PostPosted: Sun Sep 15, 2013 10:08 pm    Post subject: Reply with quote

karlH wrote:
I suspect you have the same <hostname> set for each of your icecasts.

karl.


Right you are. Forgot to change those when I replicated the XML file.

Thanks!
_________________
---
Bill Goldsmith
www.radioparadise.com
Back to top
View user's profile Send private message
BillGoldsmith



Joined: 24 Aug 2010
Posts: 9
Location: Paradise, CA

PostPosted: Mon Sep 16, 2013 5:08 pm    Post subject: Reply with quote

karlH wrote:
I suspect you have the same <hostname> set for each of your icecasts.

karl.


I changed the hostnames to the correct values & did a kill -HUP on the process. Still getting the same error. I show the correct hostname in the admin interface. Do I need to do a full restart?
_________________
---
Bill Goldsmith
www.radioparadise.com
Back to top
View user's profile Send private message
karlH
Code Warrior
Code Warrior


Joined: 13 Jun 2005
Posts: 5476
Location: UK

PostPosted: Mon Sep 16, 2013 9:21 pm    Post subject: Reply with quote

You are right that the HUP is required to reload the xml, but the streams need to be restarted to update the listen url (should be visible on the admin stats). Only the add method on the YP is known to accept that data so disconnecting the stream is the only way. Whether restarting the whole icecast is a simpler approach is up to you.

karl.
Back to top
View user's profile Send private message Send e-mail Visit poster's website
Display posts from previous:   
Post new topic   Reply to topic    Icecast Streaming Media Server Forum Index -> Icecast Server All times are GMT
Goto page Previous  1, 2, 3, 4, 5, 6, 7, 8  Next
Page 7 of 8

 
Jump to:  
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum


Powered by phpBB © 2001, 2002 phpBB Group
subRebel style by ktauber