| View previous topic :: View next topic |
| Author |
Message |
mobhaku
Joined: 18 May 2006
Posts: 8
|
 Posted: Thu Mar 31, 2011 9:17 am Post subject: disconnected sources when it's crowded |
 |
|
Hi!
It seems that I have a problem with disconnected sources due to a socket timeout when it is crowded on our icecast server.
Before we had a problem with a limitation on open files, but since that has been solved we get this problem. It seems to appear when there are around 1400 to 1500 clients connected, mainly in the morning. The rest of the day we normally don't see this and when it is less crowdy in the morning this problem also doesn't occur.
It is defenately not due the fact that there is no bandwidth, because we do have a 1Gbit up and download link.
We are running icecast 2.3.2 on a Debian Linux server.
The socket-timeout is set to 20 seconds.
Does somebody know some reasons why this can occur and where we can look at?
Below a part of the error-log in which the disconnects occurs.
A bit later, also the other source will disconnect due to the same problem and after that, the encoders will connect again.
Thanks in advance and best regards,
Harreld.
| Code: |
[2011-03-31 07:33:36] INFO source/source_main listener count on /r538.aac now 640
[2011-03-31 07:33:36] INFO source/source_main listener count on /r538_hi.aac now 782
[2011-03-31 07:33:36] INFO source/source_main listener count on /r538.aac now 657
[2011-03-31 07:33:36] INFO source/source_main listener count on /r538_hi.aac now 785
[2011-03-31 07:33:36] INFO source/source_main listener count on /r538.aac now 664
[2011-03-31 07:33:37] INFO source/source_main listener count on /r538_hi.aac now 794
[2011-03-31 07:33:37] INFO source/source_main listener count on /r538.aac now 672
[2011-03-31 07:33:37] WARN source/get_next_buffer Disconnecting source due to socket timeout
[2011-03-31 07:33:37] INFO source/source_shutdown Source "/r538.aac" exiting
[2011-03-31 07:33:37] INFO fserve/fserve_client_create checking for file /r538.aac (/usr/share/icecast2/web/r538.aac)
[2011-03-31 07:33:37] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/r538.aac" No such file or directory
[2011-03-31 07:33:37] INFO fserve/fserve_client_create checking for file /r538.aac (/usr/share/icecast2/web/r538.aac)
[2011-03-31 07:33:37] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/r538.aac" No such file or directory
::
::
[2011-03-31 07:33:43] INFO source/source_main listener count on /r538_hi.aac now 718
[2011-03-31 07:33:43] INFO fserve/fserve_client_create checking for file /r538.aac (/usr/share/icecast2/web/r538.aac)
[2011-03-31 07:33:43] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/r538.aac" No such file or directory
[2011-03-31 07:33:43] INFO connection/_handle_source_request Source logging in at mountpoint "/r538.aac"
[2011-03-31 07:33:43] INFO source/get_next_buffer End of Stream /r538.aac
[2011-03-31 07:33:43] INFO source/source_main listener count on /r538.aac now 1
[2011-03-31 07:33:43] INFO source/source_shutdown Source "/r538.aac" exiting
[2011-03-31 07:33:44] INFO source/source_main listener count on /r538_hi.aac now 723
[2011-03-31 07:33:44] INFO fserve/fserve_client_create checking for file /r538.aac (/usr/share/icecast2/web/r538.aac)
[2011-03-31 07:33:44] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/r538.aac" No such file or directory
[2011-03-31 07:33:44] INFO fserve/fserve_client_create checking for file /r538.aac (/usr/share/icecast2/web/r538.aac)
[2011-03-31 07:33:44] WARN fserve/fserve_client_create req for file "/usr/share/icecast2/web/r538.aac" No such file or directory
::
::
|
|
|
| Back to top |
|
 |
karlH
Code Warrior
Joined: 13 Jun 2005
Posts: 5476
Location: UK
|
| Posted: Thu Mar 31, 2011 10:00 pm Post subject: |
|
|
The process does not crash, just that the sources drop with a timeout? The only time I've seen this sort of effect is with people on BSD where the mbufs settings are not enough and that causes all sorts of weird effects. As it's debian you don't have that issue but do check the system log files as something else may be apparent.
karl. |
|
| Back to top |
|
|
|
FAQ
Search
Memberlist
Usergroups
Register
Profile
Log in to check your private messages
Log in
