similar to: rfc: bring ices-kh60 into mainline asap

Hiya Karl (and everybody else), I noticed today that ices 2.0-kh60a came out last January, and opted to give it a try. Unfortunately, it just wouldn't work at all, so I had to back down to 2.0-kh60. What I get in my log is this: [2006-04-21 21:16:18] DBUG om_shout/check_shout_connected Time we started stream on ice.imars.net:8000/cigr.ogg [2006-04-21 21:16:19] EROR

hi, i am desperately trying to get this version of ices up and running on debian etch. i used the apt repository at http://www.fbriere.net/debian/ices2/ but i found this also affects the "official" source package at http://mediacast1.com/~karl/ when i try to run an edited version of either the example file provided with the source package or the deb at /usr/share/doc/ices2-kh/ i

On Sun, 2005-02-20 at 12:15, Fr?d?ric Bri?re wrote: > I've been running ices2 like this 24/7 for months now, only restarting > it once a week for log rotation. Never had a problem since. setting <logsize> will cause an automatic log rotation when a certain file size has been reached. It renames <logfile> to <logfile>.1 then opens a new file <logfile> karl.

hi everyone, congratulations on the release of icecast 2.1.0 I presume this is the right place to post about iceS. please correct if wrong. I have a two instance setup, and have been finding that after a network error occurs, the instance does not reconnect. The source server is behind a linux NAT box. I have simulated the problem by using iptables REJECT with tcp-reset and here is the

Hi everybody, I'm in charge of an ices2 setup that's broadcasting a local radio station on the Net, and I'm currently under fire because one of our streams has been down twice in two days, forcing me to restart ices2 on each occasion. Our client is understandably unhappy about this. OUR SETUP: I've got ices2 installed on a local machine, broadcasting to an icecast server across

hello, I've just got ices-kh60 running with jack. It's working OK apart from a problem where the latency on the stream creeps up from about 15-20 secs to around 7 minutes. The stream plays OK, but the audio coming out is 7 minutes behind what goes in. I'm not sure how this can be happening, seeing as I don't think there are any buffers that long in the system, but it is.

Andy Baxter wrote: > hello, > > I've just got ices-kh60 running with jack. It's working OK apart from a > problem where the latency on the stream creeps up from about 15-20 secs to > around 7 minutes. The stream plays OK, but the audio coming out is 7 minutes > behind what goes in. I'm not sure how this can be happening, seeing as I > don't think there are

Hi, I have the following config; 4 ices hosts, ices-kh60 2 are streaming to icecast2.1kh5 server. 2 are streaming to icecast2.2kh9 server. The 2 hosts streaming to icecast2.2kh9 are crashing (machine crash...) twice a week. I was thinking of hardware problem, but it think it's not the case. To feed ices, I use: rawrec | ices Which I found very sensitive and may cause machine handup if

On Wed, Nov 24, 2004 at 07:26:27PM -0600, Keith Whyte wrote: > I have a two instance setup, and have been finding that after a network > error occurs, the instance does not reconnect. > > The ESTABLISHED connection is the instance which didn't get blocked by > iptables. > and those sockets seem to remain in CLOSE_WAIT until i kill the ices > process. This sounds

On Sat, Apr 22, 2006 at 01:45:27PM +0100, Karl Heyes wrote: > >I should point out that the server is 2.0.0. (Yeah, I know how old that > >is. Unfortunately, I only manage the client; the server is out of my > >hands.) Has anything changed in 2.0-kh60a that would require a more > >recent version of icecast? > > wow, v2.0.0 is old, won't make a difference for

On Sun, Feb 20, 2005 at 08:15:42PM +0000, Karl Heyes wrote: > setting <logsize> will cause an automatic log rotation when a certain > file size has been reached. It renames <logfile> to <logfile>.1 then > opens a new file <logfile> Since all my other logs are rotated on a daily/weekly basis, I want my ices logs to behave in the same way. Nevertheless, this thread

I'm using KH branch, into production, and work amazing well, with the latest change into the Worker manager, one server can handle 25k concurrent users with 8 cores, using nothing of ram... really the KH branch work amazing well. 2012/7/8 R?cker Thomas <thomas.ruecker at tieto.com> > On 08/07/12 18:21, Paul Martin wrote: > > On Sun, Jul 08, 2012 at 12:15:52AM +0300, R?cker

Package: logcheck Version: 1.2.39 Severity: normal Since I've upgraded my servers to sarge, I'm getting mail every hour for stuff that was duly included in /etc/logcheck/logcheck.ignore. Turns out that sarge's version no longer reads that file. If this was a conscious decision, then there should be some warning about this when upgrading (via debconf of NEWS.Debian). Also, the

On 08/07/12 20:42, Alejandro wrote: > I'm using KH branch, into production, and work amazing well, with the > latest change into the Worker manager, one server can handle 25k > concurrent users with 8 cores, using nothing of ram... really the KH > branch work amazing well. > > 2012/7/8 R?cker Thomas <thomas.ruecker at tieto.com > <mailto:thomas.ruecker at

Package: logcheck-database Version: 1.2.61 Severity: wishlist File: /etc/logcheck/ignore.d.server/proftpd Two weeks ago, I got a rush of these: Sep 8 12:37:07 goretex proftpd: PAM-listfile: Refused user news for service proftpd (Apparently, fail2ban managed to miss those.) This is triggered by pam_listfile, which is used by proftpd (and other FTP daemons) to block users listed in

Hello, I have a computer with this sound card (from lspci): 0000:01:04.0 Multimedia audio controller: Creative Labs SB Audigy LS Alsa is installed (maybe not properly...) # cat /proc/asound/cards 0 [CA0106 ]: CA0106 - CA0106 Live! 7.1 24bit [SB0410] at 0xc800 irq 10 But I have the impression alsa is ok : :~# aplay -l **** List of PLAYBACK Hardware Devices **** card

tobias wrote: > hi, > > i am desperately trying to get this version of ices up and running on debian > etch. i used the apt repository at http://www.fbriere.net/debian/ices2/ but i > found this also affects the "official" source package at > http://mediacast1.com/~karl/ > when i try to run an edited version of either the example file provided with > the

Package: logtail Version: 1.2.68 Severity: normal Hi, logtail does not cleanly update from logtail2: $ sudo dpkg --install /var/cache/apt/archives/logtail_1.2.68_all.deb (Reading database ... 26564 files and directories currently installed.) Unpacking logtail (from .../logtail_1.2.68_all.deb) ... dpkg: error processing /var/cache/apt/archives/logtail_1.2.68_all.deb (--install): trying to

Hi, I hope this is useful for some of you: I'm just finished building unofficial debian packages for icecast2 and libtheora for Sarge (stable). The idea behind this is to keep all the servers which take part on the GISS stream-ring in sync, running the same version of icecast2 kh branch, thus having a common ground for testing and debugging, and stay always on the cutting-edge of

So this is just an update of what I've been doing lately. I don't post to this list much but I'm on IRC a lot. So hi everyone... I had this idea that a live input module for ices on OS X would be a good thing. I started to look into the CoreAudio API but then I discovered that JACK can theoretically run on OS X. JACK is cool and Karl's most recent source has an input module