similar to: nice: EROR stream/ices_instance_stream libshout error: Out of memory

i can do it, but i mean it would not talk much to you ; ) [2003-05-31 12:00:25] INFO ices-core/main ices started... [2003-05-31 12:00:25] EROR stream/ices_instance_stream libshout error: Out of memory [2003-05-31 12:00:31] INFO signals/signal_int_handler Shutdown requested... [2003-05-31 12:16:47] INFO ices-core/main ices started... [2003-05-31 12:16:47] EROR stream/ices_instance_stream

On Sat, 2003-05-31 at 13:02, Paul wrote: > i can do it, but i mean it would not talk much to you ; ) > > [2003-05-31 12:00:25] INFO ices-core/main ices started... > [2003-05-31 12:00:25] EROR stream/ices_instance_stream libshout error: Out > of memory hmmm, right at the very start..look suspicious > ehm, befor i get this message i remove the password for icecast in the ices

Hi... first post to this list so be gentle with me! I've got Icecast 2.2.0 running well, and using Ices 2.0.1 to feed the OGGs. All was working, then all of a sudden I've started getting these messages in the (ices) log... [2005-05-08 12:10:19] INFO ices-core/main IceS 2.0.1 started... [2005-05-08 12:10:19] EROR stream/ices_instance_stream libshout error: Out of memory [2005-05-08

Hello Everyone, I have a bit of a problem trying to set up Icecast2 + Ice2, on my debian box, I installed icecast2 ver 2.3.2-6 and ices2 2.0.1-8. I'm able to start icecast2 as shown in the logs: [2012-12-24 20:34:27] INFO main/main Icecast 2.3.2 server started [2012-12-24 20:34:27] DBUG yp/yp_recheck_config Updating YP configuration [2012-12-24 20:34:27] INFO

Hi, I wonder if you can help. I am running Icecast 2.4.4, Ices 2.0.2 and libshout 2.4.3. There has been a recent upgrade to libshout and I notice that my previous ices configuration no longer works. In the ices log I get the error message: [2019-07-10 11:10:30] INFO ices-core/main IceS 2.0.2 started... [2019-07-10 11:10:30] INFO signals/signal_usr1_handler Metadata update requested [2019-07-10

Okay I was poking around the logs, getting ready to test the yp server update, and then I decided to check the configs. I still had localhost set for the hostname, so I changed it to my real hostname. Now I get this in my ices.log when trying to start (although icecast is started fine): [2003-06-05 12:27:00] EROR stream/ices_instance_stream Failed initial connect to myreal.hostname.net:8000

Hi! I've installed icecast and ices on a FreeBSD box. When I try to start ices, I get following output: [2003-08-11 11:02:14] INFO ices-core/main ices started... [2003-08-11 11:02:14] INFO signals/signal_usr1_handler Metadata update requested [2003-08-11 11:02:14] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/home/wim/playlist.txt" [2003-08-11

Hello, recently I have tried to use Ices2 to encode my live (line-in) audio and I can't get rid of this error message: [2003-01-17 04:37:39] EROR stream/ices_instance_stream Failed initial connect to 147.32.127.199:8000 (Unknown error) I have checked all the settings on the server and in the ices-live.xml, but it's still the same. /dev/dsp and /dev/mixer seems to be set up correctly.

Hi ! my question is how to totally switch off the Ices2 logging into the Icecast server ? I wan't to use ices only to save archives (24h/d), without any streaming, but when I try start Ices, see: [2005-01-19 17:27:05] EROR stream/ices_instance_stream Failed initial connect to localhost:8000 (Couldn't connect: Connection refused) and Ices clears buffers etc. and shuts itself down :-(

>it supposed to, check the log file for details but there is no reason >for it not to work with 2 instances. > >Note as well, that you should have 2 instances each of which has the >icecast connection details and an encode section. > I don't quite understand. You always talk about two instances. Do you really mean two instances of ices2 called seperately? Do I have to make

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

I'm using ices2's metadata facility to update the name of a track in a vorbis stream: <input> <module>alsa</module> <param name="rate">44100</param> <param name="channels">2</param> <param name="device">hw:1,0</param> <param name="metadata">1</param>

On Sun, 2003-11-23 at 00:35, Kerry Cox wrote: > Now I tried to add a third stream by adding the following <instance> to > the above config: > > <instance> > <hostname>xx.xxx.x.xxx</hostname> > <port>8000</port> > <password>secretpasswd</password> >

Hi, Is it possible to generate an ogg stream at less than 22KBps ? I tried several configuration with ices and darkice, but I always get an configure encoder error: [2003-03-17 16:07:17] INFO input-oss/oss_open_module Opened audio device /dev/dsp at 2 channel(s), 44100 Hz [2003-03-17 16:07:17] INFO audio/resample_initialise Initialised resampler for 2 channels, from 44100 Hz to 22050 Hz

... [2009-02-14 20:54:27] INFO ices-core/main Shutdown complete [2009-02-14 21:01:02] INFO ices-core/main IceS 2.0.1 started... [2009-02-14 21:01:02] INFO signals/signal_usr1_handler Metadata update requested [2009-02-14 21:01:02] INFO playlist-basic/playlist_basic_get_next_filename Loading playlist from file "/etc/ices2/playlist.txt" [2009-02-14 21:01:02] WARN

On Sun, 2003-11-23 at 03:51, Kerry Cox wrote: > Hmmm, I guess more is incorrect here than I thought. I changed the > resample in-rate to be 44100 like it should have have been. > But still no joy. Here is the error message as shown in the error.log > file. I'm looking things over and am not seeing my error. > It looks like the audio resample for this particular stream is good.

Thanks Karl, I will give it a try. Do I have to install your modified libshout or isn't it required if I am live streaming? Cheers, Matt On 5 Aug 2003, Karl Heyes wrote: > not in CVS ices2, the problem is fairly involved to get into, not so > much for the initial filename but for things such as timing out or if > there's a problem with the link to icecast. > > If you

Now every thin works fine good, thanks a lot for helping me, but there is another problem. in ices-playlist.ogg the are to sections first section is: <input> <module>playlist</module> <param name="type">basic</param><!-- Only 'basic' implemented --> <param

Both icecast and ices are on the same server. Where shall i change to "localhost"? /Daniel Den sön 25 okt. 2020 kl 18:49 skrev Kwame Bahena <informatux at gmail.com>: > Is your icecast server in another server? > If not, if you are running ices on the same server as your icecast, try > using localhost instead of "bananradion.bananklubben.se" > > >

Hi, I have been digging through the icecast mailing list archives trying to find out the meaning of this recurring message in my error.log [2018-05-01 19:50:16] EROR connection/_handle_connection Wrong request type from client [2018-05-01 19:50:16] EROR connection/_handle_connection Wrong request type from client [2018-05-01 19:50:16] INFO source/source_main listener count on /Systrum now 1