similar to: Client had recoverable error

Displaying 20 results from an estimated 3000 matches similar to: "Client had recoverable error"

2004 Sep 03
3
Client had recoverable error
Mhhh. I am streaming from a 8mbit adsl connection so it should be fast enough. I tried streaming with media player, it's working for 24 hours now, doesn't seem to have the problem, is my winamp 5.03 broken? Or is winamp broken in general? :) Thanks for the help. Silvester -----Original Message----- From: Karl Heyes [mailto:karl@xiph.org] Sent: donderdag 2 september 2004 22:57 To:
2004 Sep 02
0
Client had recoverable error
On Wed, 2004-09-01 at 23:06, Silvester Verdonkschot wrote: > Hi there, > > I?m using icecast 2.0.1 with darkice 0.14 streaming an 192kb mp3 stream. > Everything seems to work fine except that clients (eg winamp5) disconnect > after a period of time (5/10/20 minutes). The icecast log shows some weir > errors: > > [2004-08-18 01:24:54] DBUG
2005 Dec 14
1
Icecast 2.0 and Oddcast V3 - Debug error
Hi guys, i have an Icecast2 server with 3 source client (Oddcast V3). I can see in my error.log this lines: [2005-12-14 12:06:13] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error -1 [2005-12-14 12:06:13] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error -1 [2005-12-14 12:06:13] DBUG format-mp3/format_mp3_write_buf_to_client Client had
2004 Aug 06
3
Icecast 2 for Live365 MP3 Relaying
Hi All, I attempted to switch my MP3 server from Icecast 1 to Icecast 2 today. I run a Live365 station, Big Planet Radio, which simply relays my local Icecast server. My Icecast 2 error.log file shows a lot of the following messages when the Live365 server, Nanocaster 2.5.6, is connected to it: [2003-05-14 22:09:15] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error
2004 Aug 06
3
Icecast 2 for Live365 MP3 Relaying
Hi All, I attempted to switch my MP3 server from Icecast 1 to Icecast 2 today. I run a Live365 station, Big Planet Radio, which simply relays my local Icecast server. My Icecast 2 error.log file shows a lot of the following messages when the Live365 server, Nanocaster 2.5.6, is connected to it: [2003-05-14 22:09:15] DBUG format-mp3/format_mp3_write_buf_to_client Client had recoverable error
2004 Nov 27
3
Prevent client disconnecting fallen-too-far-behind
Hello, Does anybody know how I can configure icecast so it doesn't disconnect a client which "has fallen too far behind". We are using icecast2.01 streaming software for our church home-listening system. Our client we use a netgem-netbox. We are streaming 25kbps MP3 on V90-56kbps modem connection After around 45 minutes after starting the cleint the icecast error.log reports:
2004 Aug 06
1
client disconnects after one song is played
I'm using the latest CVS source under Linux using a playlist of ogg files. When I use a client to connect on the same machine, there is not any disconnect (xmms and zinf). When using a client on a Windows machine, I get mixed results. Zinf on windows will play thru the current song but then stops when the song is finished and does not play the next song being streamed (see log below).
2004 Aug 06
1
Log delay, recoverable error -1, replaygain
Hi! I have a few questions about the log files icecast produces, plus I have a little issue with replaygain but lets start with the icecast log stuff: If a client (listener) connects to icecast at, say, 12:00, the connection time is stored in the access log about 15-30 minutes later (or on disconnection). Is it possible to get icecast to log client connections immediately with the correct
2004 Aug 06
0
Icecast 2 for Live365 MP3 Relaying
this is probably caused by the lack of buffering in icecast2. Their relay client may be doing some buffering in itself, and if it's expecting for there to be buffering on the server side as well, it might exhibit a behavior you are seeing....(that also is a difference between iceast1 and icecast2 - no server-side buffering in icecast2 and there was in icecast1)... fwiw, I am trying to
2004 Nov 27
0
Prevent client disconnecting fallen-too-far-behind
On Sat, 2004-11-27 at 21:52, Henk van de Ridder wrote: > Hello, > > Does anybody know how I can configure icecast so it doesn't disconnect a > client which "has fallen too far behind". there isn't anything else icecast can do when that condition is reached > We are using icecast2.01 streaming software for our church home-listening > system. > Our client we
2004 Aug 06
4
Server disconnects clients
Hi I'm running Icecast2 with the IceS streamer which was installed from the ports on FreeBSD. Everything seems to be fine with my configuration as it starts up fine but as soon as I connect using a client like Media Player or WinAmp I see the following in the error.log [2003-10-27 21:00:27] DBUG format/format_generic_write_buf_to_client Client had recoverable error -1 [2003-10-27 21:00:27]
2004 Aug 06
2
WinAmp3 & Icecast2 compatibility?
Hello folks I'm having trouble playing ogg streams with WinAmp3. I run Icecast2 & Ices2 (both compiled from CVS about two weeks ago) on a Linux box, the files being streamed were encoded with oggenc (from oggutils1.0, managed 80kbitrate...) The problem is that WinAmp3 won't actually play the .ogg stream. When I give it the URL (http://myserver:8000/mount.ogg) it says
2004 Aug 06
1
Newbie support
I have just setup icecast on my RedHat 9 server and it's working fine except that every 2 minutes or so I get an error in icecast error log giving about 20 lines of : DBUG format/format_generic_write_buf_to_client Client had recoverable error -1 And then DBUG source/source_main Client has fallen too far behind, removing It then restarts streaming to the client The result is that the music
2004 Aug 06
0
Strange hanging...
Hi, I've been doing some experiments today with ices, icecast-2.0.1 server and using ogg123 to play the stream on a client device... Twice, the client appears to "lock" at around the same point - once at 189:45:56 and the second time at 187:45:40. The server log states: [2004-05-30 17:28:50] DBUG format/format_generic_write_buf_to_client Client had recoverable error -1
2004 Aug 06
2
Server disconnects clients
On Wednesday 29 October 2003 17:29, Ricardo wrote: > Excellent! > > With WinAmp 5 it works but after about 45seconds I get the same messages in > error.log > > [2003-10-29 08:38:33] DBUG format/format_generic_write_buf_to_client > Client had recoverable error -1 This should never happen. It looks like a bug present in some old versions (> 6 months old), are you sure a
2004 Aug 06
2
Re:Icecast with Winamp
Hi, I can get ices2/icecast2 to broadcast ogg files in a playlist to FOOBAR in MS-Windows (and various apps in Linux). When I try to connect in WinAmp in MS-Windows, I get in error.log: [2004-02-04 21:38:39] DBUG source/source_main Client added [2004-02-04 21:38:41] DBUG format/format_generic_write_buf_to_client Client had recoverable error -1 [2004-02-04 21:38:42] DBUG
2004 Aug 06
2
Server disconnects clients
I meant to include a download URL for Winamp 5 http://www.majorgeeks.com/download.php?det=2490 Ross. --- >8 ---- List archives: http://www.xiph.org/archives/ icecast project homepage: http://www.icecast.org/ To unsubscribe from this list, send a message to 'icecast-request@xiph.org' containing only the word 'unsubscribe' in the body. No subject is needed. Unsubscribe messages
2012 Jan 03
1
2 different APC UPS using USB get in power off recoverable state
Hi Yesterday I had 2 different APC UPS using USB get in power off recoverable state. dmesg said: 7705944.352083] usb 2-1: new low speed USB device using uhci_hcd and address 2 [7705944.477061] usb 2-1: device descriptor read/64, error -71 [7705944.709035] usb 2-1: device descriptor read/64, error -71 [7705944.925071] usb 2-1: new low speed USB device using uhci_hcd and address 3
2004 Aug 06
3
PATCH: increase network congestion resilience
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, find a patch which is an update to a patch sent months ago. Before it was in net/sock.c, now I moved it to format.c, so net CVS module is not affected. It polls the socket before trying to send() any byte to check if the TCP buffers are full due to network congestion. See below the warning messages of "normal" (at least in
2018 Jan 14
2
YP listing problem
I am having problems YP listing my opus and webm streams. The mp3 streams get listed though. my ffmpeg for the webm stream: ffmpeg \ -f v4l2 -video_size 640x480 -framerate 30 -i /dev/video0 \ -i http://mustafejen.se:8000/feting \ -f oss -i /dev/dsp1 \ -f webm -cluster_size_limit 2M -cluster_time_limit 5100 -content_type video/webm \ -c:a libvorbis -b:a 96K \ -c:v libvpx-vp9 -b:v 1.5M