similar to: once again: [Too many errors (client not receiving data fast enough)]

Ok, I have seen that this is a common issue, and has been answered many times.... but I think mine is a bit different. Sorry if I am just being thick. <p><p>Local Setup: <p><p>Local net is 100mb, 9 boxes that don't do much, so no bandwidth issues. <p><p>Cable modem - 2mb down, 128k up (is there someplace I can 'measure' this?)

Hey group, I am getting this error from the icecast log whenever I try to connect to my server to listen: Kicking client 4 [xxx.blah.com] [Too many errors (client not receiving data fast enough)] [listener], connected for 1 seconds, 8192 bytes transfered. 0 clients connected I am not sure what is causing this, ices or icecast? I have tried re-compiling Icecast and Ices to not avail. I am

Hey all, I've been having the same "Client not receiving data fast enough" errors. I've got icecast configured so as not to send info to ANY yp directories. Even on a quiet 100MB connection between client and server, I can stay connected for only about 5 minutes at a shot if I'm lucky. I'm using Icecast 1.3.11, and Shout 0.8.0. The files I'm streaming are all

I'm running RedHat 7.2 (kernel 2.4.17) on a PII 300. I'm using Liveice with XMMS. I had no problem broadcasting with Shoutcast and Winamp back before I switched over to Linux. I'd love to get going on broadcasting... but Icecast refusing to open is a problem. Running icecast gives me the following. Starting thread engine... [04/Feb/2002:13:57:38] Icecast Version 1.3.10 Starting..

Jack, tried the CVS version still getting: -> [05/Aug/2001:12:25:01] Kicking client 4 [cr7890-a.wlfdle1.on.wave.home.com] [Too many errors (client not receiving data fast enough)] [listener], connected for 0 seconds, 26010 bytes transfered. 0 clients connected Any idea what it means? Is it a mis-configuration? Sometime to do w/ LAME? I have no clue where to start -Russ On Sun, 5 Aug

On Mon, 4 Feb 2002, Jack Moffitt wrote: > > I'm running RedHat 7.2 (kernel 2.4.17) on a PII 300. I'm using Liveice > > with XMMS. I had no problem broadcasting with Shoutcast and Winamp back > > before I switched over to Linux. I'd love to get going on broadcasting... > > but Icecast refusing to open is a problem. > > Did you use the hostname parameter in

At 05:19 PM 2/4/2002 -0500, Gary Major wrote: >Using Icecast 1.3.11 and Ices 0.2.2. Have compiled Ices with the optimize >flags defined. Using PII 266 - 160MB, RH 7.1 with default kernel (2.4.7 i >think) > >Situation that I have is interesting: Odd, I have them both running as background processes together with no problem (then though I'm running FreeBSD 4.5-STABLE). And I

> -> [05/Aug/2001:12:25:01] Kicking client 4 > [cr7890-a.wlfdle1.on.wave.home.com] [Too many errors (client not receiving > data fast enough)] [listener], connected for 0 seconds, 26010 bytes > transfered. 0 clients connected > > Any idea what it means? Is it a mis-configuration? Sometime to do w/ > LAME? I have no clue where to start Almost always this means that data

On Sunday, 05 August 2001 at 12:40, Russ wrote: > > Hmmm, I am using Winamp for my client, will upgrade it, but it works for > other shoutcast/icecast streams. There has to be something buggered up in > my config somewhere. It sounds as if Ices is sending data too quickly to > icecast(?), will blow it away and re-complie it and see what happens. > Thanks for the help so far.

Hi there ! As i tried that radio finally installed, i got that message from the server after ~ 1 minute ... I reduced and forced the streaming to 44000 instead of the 128000 proposed as default_bitrate in shout.conf. Now i can listen for 12 minutes and 46 seconds before i got the message. what's going on ? Should i modify the throttle parameter ? I have a DSL access for information

Hi, all Did anyone tried TDM400 card on old main board (Intel 440LX chipset -- PII)? The reason I am asking is because TDM400 needs PCI2.2 and main board is PCI2.1 I do not want to upgrade yet. Thanks, Rudolf

We have a test server that runs a single PIII 500MHz(256MB RAM) under Slackware, and we can get 12 SIP -> Zap calls running on it just fine. Over that and we have seen intermittant errors like call quality and very high load spikes. You should be able to get at least 24 SIP -> Zap on that setup. Post on the list when you do max it out. It's always good to see capacity specs. MATT---

Hi! I have moved our samba configuration to a new hardware. Old config: PII 266 MHz 96MB memory RedHat 7.2 20Gb ide hard drive for samba shares samba-*-2.2.7-3.7.2 packages installed kernel-2.4.20-28.7 New config: P4 2.4GHz 512MB memory RedHat 9.0 60GB scsi hard drive for samba shares and OS 40GB ide hard drive for backups samba-*-2.2.7a-8.9.0

Hmmm, I am using Winamp for my client, will upgrade it, but it works for other shoutcast/icecast streams. There has to be something buggered up in my config somewhere. It sounds as if Ices is sending data too quickly to icecast(?), will blow it away and re-complie it and see what happens. Thanks for the help so far. yeah, essentialmix.ca is directly related to the Essential mix broadcasts off

Tested floppy boot on two machines (one PII 350, one 486DX4) Floppy boot with syslinux is very very slow, more than 18 mn to boot a linux kernel from floppy on the 2 machines. Tested with 3 different disquettes that were know to work, boot is reached after this very long time. Noise from floppy head make think floppy wait approximatly one minute between each read. No problem with pxe boot with

Package: xen-utils-common Version: 3.0.3-0-2 Severity: important I have installed all the packages I can think of to get Xen going and it still fails with the following : /var/log/xen/xend-debug.log: Exception starting xend: (111, 'Connection refused') er.py", line 463, in process_request_thread self.finish_request(request, client_address) File "SocketServer.py",

I have experienced lots of apparently dropped packets (in other words, lots of short interruptions of what the other party tries to tell me) with a GS102 and chan_capi. The GS102 is connected through a lightly-loaded switch directly connected to the * server, so bandwidth/latency shouldn't pose a problem. Funny thing is that the switch indicates 10mbit on the GS102 port - is that correct?

John R Pierce wrote: > On 5/31/2017 10:13 AM, m.roth at 5-cent.us wrote: >> If I had realized it would run this long, I would have used DBAN.... For >> single drives, I do, and choose DoD 5220.22-M (seven passes), which is >> *way* overkill these days... but I sign my name to a certificate that >> gets stuck on the outside of the server, meaning I, personally, am

Hi, i am seeing an oops (every couple of days) on a UP PII system with SCSI disks, Kernel 2.2.19 and ext3 0.0.6b. All oops output passed the klogd thus i cant anymore pipe it through ksymoops - I ensured klogd got the correct System.map so the result should be reliable. Apr 25 17:03:10 Unable to handle kernel paging request at virtual address 8efd1fc8 current->tss.cr3 = 0981e000, %%cr3 =

Hi. I have 2 PC's connected with 1GBit NIC's. When I transfer a file from my File-Server(Redhat9.0, 256 SD-RAM, 300MHz PII, RTL8169 NIC, 2x Western Digital WD200JB RAID 0) to my Windows-PC(AMD Athlon XP 1800+, 1024 MB DDR-RAM, WINXP PRO, RTL8169 NIC, 2x Western Digital WD080JB RAID 0) with Samba, i get Speeds around 8-9MB/sec. I think this is too low for an GBit Network, so i tested the