| View previous topic :: View next topic |
| Author |
Message |
Hash
Guest
|
 Posted: Mon Jun 27, 2005 10:58 am Post subject: win32: Icecast2.2 drops listener but not relay |
 |
|
Hello, i have an Icecast 2.20 server running on Windows 2003. I am manually updating the titles on the server using a script as the feed is a live audio feed. Titles are updated every 30 seconds.
Shoutcast 1.9.5 on the same machine is relaying the stream.
When listening to the icecast feed in Winamp - it drops after about 30 minutes, however it does not drop the shoutcast relay. Am i missing something here or is it a bug?
Many thanks
Hash
www.samurai.fm |
|
| Back to top |
|
 |
Anonymous
Guest
|
| Posted: Mon Jun 27, 2005 11:28 am Post subject: |
|
|
I Have running icecast 2.x.
My Have problems the playisting for icecast i can configuration playlist and icecast .
My Configuration:
| Code: |
<relay>
<server>10.0.0.4</server>
<port>8001</port>
<mount>/test.mp3</mount>
<local-mount>test.mp3</local-mount>
<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
|
My local Ip: 10.0.0.4 for personalized and configuration route.
Hi, My Leanguage ITALY.
Last edited by Anonymous on Sun Nov 20, 2005 12:49 pm; edited 1 time in total |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon Jun 27, 2005 7:41 pm Post subject: Re: win32: Icecast2.2 drops listener but not relay |
|
|
| Hash wrote: |
When listening to the icecast feed in Winamp - it drops after about 30 minutes, however it does not drop the shoutcast relay. Am i missing something here or is it a bug?
|
If the icecast log message indicates that the client has fallen too far behind then it's a slow connection to winamp. It may just be a temporary thing but that is hard to determine. Make sure you have a large enough queue size and note that the burst size is part of that.
karl |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon Jun 27, 2005 7:48 pm Post subject: |
|
|
| ukero wrote: |
I Have windows 2003 running icecast 2.x.
My Have problems the playisting for icecast i can configuration playlist and icecast for windows.
My Configuration:
| Code: |
<relay>
<server>10.0.0.4</server>
<port>8001</port>
<mount>/test.mp3</mount>
<local-mount>test.mp3</local-mount>
<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
|
My local Ip: 10.0.0.4 for personalized and configuration route.
Hi, My Leanguage ITALY. |
When relaying from a server, if you state a local-mount then it needs to begin with a / so try
<local-mount>/test.mp3</localmount>
The default local-mount will be the same as mount
karl. |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Mon Jun 27, 2005 8:12 pm Post subject: |
|
|
Hi, more for problems for HTTP:// -- FILE NOT FOUND.
copy/paste code configuration:
| Code: |
<icecast>
<limits>
<clients>100</clients>
<sources>2</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>hackme</source-password>
<!-- Relays log in username 'relay' -->
<relay-password>hackme</relay-password>
<!-- Admin logs in with the username given below -->
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
</authentication>
<!-- Uncomment this if you want directory listings -->
<!--
<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>15</yp-url-timeout>
<yp-url>http://www.oddsock.org/cgi-bin/yp-cgi</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>10.0.0.4</hostname>
<!-- You can use these two if you only want a single listener -->
<port>8000</port>
<bind-address>10.0.0.4</bind-address>
<!-- You may have multiple <listener> elements -->
<listen-socket>
<port>8000</port>
<bind-address>10.0.0.4</bind-address>
</listen-socket>
<listen-socket>
<port>8001</port>
</listen-socket>
<master-server>10.0.0.4</master-server>
<master-server-port>8001</master-server-port>
<master-update-interval>120</master-update-interval>
<master-password>hackme</master-password>
<relay>
<server>10.0.0.4</server>
<port>8001</port>
<mount>/test.mp3</mount>
<local-mount>/test.mp3</local-mount>
<relay-shoutcast-metadata>0</relay-shoutcast-metadata>
</relay>
<mount>
<mount-name>test</mount-name>
<username>othersource</username>
<password>hackmemore</password>
<max-listeners>10</max-listeners>
<dump-file>dump_test.mp3</dump-file>
<burst-size>65536</burst-size>
<fallback-mount>d:\programmi\icecast2\test.mp3</fallback-mount>
<fallback-override>1</fallback-override>
<hidden>1</hidden>
<no-yp>1</no-yp>
<authentication type="htpasswd">
<option name="filename" value="myauth"/>
<option name="allow_duplicate_users" value="0"/>
</authentication>
</mount>
<fileserve>1</fileserve>
<shoutcast-mount>/live.nsv</shoutcast-mount>
<paths>
<!-- basedir is only used if chroot is enabled -->
<basedir>.</basedir>
<!-- Note that if <chroot> is turned on below, these paths must both
be relative to the new root, not the original root -->
<logdir>./logs</logdir>
<webroot>./web</webroot>
<adminroot>./admin</adminroot>
<!-- <pidfile>./icecast.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>
|
|
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Mon Jun 27, 2005 9:21 pm Post subject: |
|
|
that xml file has a few configuration errors in it, ask youself a few questions to try and get an idea on what direction you want to go in, because we don't know what you are trying to achieve
. Do I want to talk to an icecast master server
. Do I want state a single relay of an existing stream
. Am I relaying any streams at all
. Should I use a source client
. Why do I miss out the initial / for a mount point names eg
<mount-name>test</mount-name>
. What do I think will happen with the following
<fallback-mount>d:\programmi\icecast2\test.mp3</fallback-mount>
- Have I read what the <mount> options do |
|
| Back to top |
|
|
Hash
Guest
|
| Posted: Tue Jun 28, 2005 7:33 am Post subject: |
|
|
Hang on it seems like someone has hijacked my topic!
If there is a bad connection to winamp (which i don't think there is because i have premium bandwidth co-lo and have no probs with a shoutcast relay) shouldn't Winamp try and reconnect?
Also, using the easy configuration XML, are the default settings in the full dist config applied?
thanks
Hash |
|
| Back to top |
|
|
Hash
Guest
|
| Posted: Tue Jun 28, 2005 7:40 am Post subject: |
|
|
| Also one other strange thing in the icecast access log is that there is no indication that Icecast dropped the listener!? |
|
| Back to top |
|
|
Anonymous
Guest
|
| Posted: Tue Jun 28, 2005 8:38 am Post subject: |
|
|
[edit]
Last edited by Anonymous on Sun Nov 20, 2005 12:50 pm; edited 1 time in total |
|
| Back to top |
|
|
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Tue Jun 28, 2005 1:27 pm Post subject: |
|
|
| Hash wrote: |
Hang on it seems like someone has hijacked my topic!
If there is a bad connection to winamp (which i don't think there is because i have premium bandwidth co-lo and have no probs with a shoutcast relay) shouldn't Winamp try and reconnect?
Also, using the easy configuration XML, are the default settings in the full dist config applied?
|
The hardcoded defaults will apply.
I would of thought winamp would try to reconnect, but it sounds like you don't know if it's even disconnecting, which would be a new problem. Either the server disconnects the listener (end of stream or stalling listener) or the listener disconnects itself (eg codec error). In either case something is logged in both error and access logs. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
