| View previous topic :: View next topic |
| Author |
Message |
Praveen
Joined: 04 Nov 2008 Posts: 8 Location: Hyderabad
|
Posted: Fri Aug 07, 2009 9:08 am Post subject: Master Server Streamlist access Failed |
|
|
WARN slave/ Failed URL access "http://10.0.1.28:8001/admin/streamlist.txt" (couldn't connect to host)
Why This Error Happen..... _________________ Prawin |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Fri Aug 07, 2009 1:02 pm Post subject: |
|
|
you have configured your icecast to be a slave to another icecast and you have told it that the master icecast is at 10.0.1.28 port 8001 however when this slave icecast tries to retrieve a list of streams to relay, it cannot because that server is not accessible.
karl. |
|
| Back to top |
|
 |
Praveen
Joined: 04 Nov 2008 Posts: 8 Location: Hyderabad
|
Posted: Mon Aug 10, 2009 4:51 am Post subject: |
|
|
Thnx Karl.
Now I have configured the master and as well as slave servers.
I am getting the following error.
Client 15064 (10.0.2.36) has fallen too far behind, removing
Actually i have increased the queue size also. Please check the following configurations & Logs of both master and slave servers.
//master_icecast.xml
<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>
<burst-on-connect>1</burst-on-connect>
<burst-size>65536</burst-size>
</limits>
<authentication>
<source-password>hackme</source-password>
<relay-user>relay</relay-user>
<relay-password>hackme</relay-password>
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
</authentication>
<hostname>master</hostname>
<listen-socket>
<port>8000</port>
</listen-socket>
<master-server>10.0.1.28</master-server>
<master-server-port>8008</master-server-port>
<master-update-interval>120</master-update-interval>
<relays-on-demand>0</relays-on-demand>
<mount>
<mount-name>/telugu_latest.mp3</mount-name>
</mount>
//slave_icecast.xml
<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>
<burst-on-connect>1</burst-on-connect>
<burst-size>65536</burst-size>
</limits>
<authentication>
<source-password>hackme</source-password>
<relay-user>relay</relay-user>
<relay-password>hackme</relay-password>
<admin-user>admin</admin-user>
<admin-password>hackme</admin-password>
</authentication>
<hostname>localhost</hostname>
<listen-socket>
<port>8000</port>
</listen-socket>
<relay>
<server>10.0.1.28</server>
<port>8000</port>
<mount>/telugu_latest.mp3</mount>
<local-mount>/imiradio</local-mount>
<on-demand>0</on-demand>
<enable>1</enable>
</relay>
//master_icecast logs
[2009-08-10 10:11:31] INFO main/ Icecast 2.3.2-kh4 server started
[2009-08-10 10:11:31] INFO connection/ connection thread started
[2009-08-10 10:11:31] INFO connection/ No SSL capability on any configured ports
[2009-08-10 10:11:31] INFO connection/ listener socket on port 8000
[2009-08-10 10:11:31] INFO connection/ 1 listening sockets setup complete
[2009-08-10 10:13:41] INFO fserve/ checking for file /telugu_latest.mp3 (./web/telugu_latest.mp3)
[2009-08-10 10:13:56] INFO fserve/ checking for file /telugu_latest.mp3 (./web/telugu_latest.mp3)
//slave_icecast logs
[2009-08-10 10:13:40] INFO main/ Icecast 2.3.2-kh4 server started
[2009-08-10 10:13:40] INFO connection/ connection thread started
[2009-08-10 10:13:40] INFO connection/ No SSL capability on any configured ports
[2009-08-10 10:13:40] INFO connection/ listener socket on port 8000
[2009-08-10 10:13:40] INFO connection/ 1 listening sockets setup complete
[2009-08-10 10:13:41] INFO slave/ Starting relayed source at mountpoint "/imiradio"
[2009-08-10 10:13:41] INFO slave/ connecting to 10.0.1.28:8000
[2009-08-10 10:13:41] INFO source/ Applying mount information for "/imiradio"
[2009-08-10 10:13:41] INFO source/ listener count on /imiradio now 0
[2009-08-10 10:13:47] INFO source/ End of Stream /imiradio
[2009-08-10 10:13:47] INFO source/ Source "/imiradio" exiting
[2009-08-10 10:13:47] WARN source/ buffer is 2
[2009-08-10 10:13:56] INFO slave/ Starting relayed source at mountpoint "/imiradio"
[2009-08-10 10:13:56] INFO slave/ connecting to 10.0.1.28:8000
[2009-08-10 10:13:56] INFO source/ Applying mount information for "/imiradio"
[2009-08-10 10:13:56] INFO source/ listener count on /imiradio now 0
[2009-08-10 10:14:00] INFO source/ listener count on /imiradio now 1
[2009-08-10 10:14:00] INFO source/ Client 15064 (10.0.2.36) has fallen too far behind, removing
[2009-08-10 10:14:00] INFO source/ listener count on /imiradio now 0
[2009-08-10 10:14:03] INFO source/ End of Stream /imiradio
[2009-08-10 10:14:03] INFO source/ Source "/imiradio" exiting _________________ Prawin |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Mon Aug 10, 2009 2:52 pm Post subject: |
|
|
100kbytes is not much for queue size, considering that 64k of that is burst quickly at the beginning. I would increase that, and update the version, kh12 is the latest.
karl. |
|
| Back to top |
|
 |
Praveen
Joined: 04 Nov 2008 Posts: 8 Location: Hyderabad
|
Posted: Tue Aug 11, 2009 5:25 am Post subject: |
|
|
Karl,
i have downloaded the latest version from www.icecast.org but my problem is not rectified. The same error i am receiving.
Another thing is that i am streaming 320kbps mp3 file from master. _________________ Prawin |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Aug 11, 2009 11:50 am Post subject: |
|
|
you seem to be referring to a different discussion. The question you posted about the queue size were not errors, The failed to get streamlist.txt was a problem with accessing another server and an update to the kh tree is not from the main icecast site but my own website.
karl. |
|
| Back to top |
|
 |
Praveen
Joined: 04 Nov 2008 Posts: 8 Location: Hyderabad
|
Posted: Tue Aug 11, 2009 12:09 pm Post subject: |
|
|
Sorry Karl,
I have solved the configuration problem.
In my second reply i have mentioned the same. But after doing the proper master, slave configurations i am getting the "Client 15064 (10.0.2.36) has fallen too far behind, removing" problem. for that only i have mentioned the config & log details.
Please send me the latest version of IceCast link. _________________ Prawin |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Tue Aug 11, 2009 2:08 pm Post subject: |
|
|
increase your queue size, 100k is not that much especially when 64k of it is sent quickly. It is why we ship the sample with around 500k. An updated kh version is on my web site, just check the www link on my profile.
karl. |
|
| Back to top |
|
 |
Praveen
Joined: 04 Nov 2008 Posts: 8 Location: Hyderabad
|
Posted: Wed Aug 12, 2009 9:16 am Post subject: |
|
|
I have updated the latest kh12 version on both ends.
Still i am getting the same problem. plz. find the error and its config setting.
[2009-08-12 14:45:30] INFO source/ Client 1 (10.0.2.36) has fallen too far behind, removing
<limits>
<clients>100</clients>
<sources>2</sources>
<workers>1</workers>
<queue-size>5004288</queue-size>
<client-timeout>30</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-size>65535</burst-size>
</limits>
Actually i have set all these settings in slave-server only. Is there any settings necessary in master-server. _________________ Prawin |
|
| Back to top |
|
 |
karlH Code Warrior

Joined: 13 Jun 2005 Posts: 5476 Location: UK
|
Posted: Wed Aug 12, 2009 11:48 am Post subject: |
|
|
The INFO message you are posting is because a client is not reading quickly enough so ends up dropping to the back of the queue and eventually has to be dropped. Even slaves reading from the master server can lag behind in certain cases.
If the client being dropped is logged from the slave then the connection to the the listener is not sufficient for the stream, If th master is logging that then you may need to increase the queue size on there as well (doesn't have to be 5Meg but 100k is small).
The unusual thing here is that 10.x.x.x addresses are typically fairly local so bandwidth should not be an issue. I don't know your network structure to determine why but check what route this client has to take to get to icecast. A max'd out link or poor router/cable could cause problems likes this.
karl. |
|
| Back to top |
|
 |
|