similar to: EROR connection/_handle_connection Wrong request type > from client

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

Hi, AFAIK, icecast only supports specific HTTP request methods (GET for listeners, PUT/SOURCE for sources). This message is logged when a client uses an unsupported request method (such as HEAD or POST). Please note that this might be inaccurate, but I saw this kind of logs during a development that involved unsupported request methods. ? Teddy Le 2018-05-01 13:00, Damian a ?crit?: >

Hi, I am currently running Icecast 2.4.4 on Debian stretch and am using the info from the status-json.xsl to display some stats on my radio webpage. This works well. On the same website, I have also managed to display listener stats. I looks like this https://systrum.net/listeners.png To get this data, my developer created a php script containing the icecast admin credentials so that I can

Thanks for the reply. So then does this message indicate an issue with my setup (I use Liquidsoap to stream to Icecast) or an issue with a listener client? It looks like the listener count drops immediately after someone connects which to seems like a problem at the listeners end. > On 2 May 2018, at 22:00, icecast-request at xiph.org wrote: > > Send Icecast mailing list submissions to

So, I’ll try to explain what I mean a little more by referring to some images. In the first image here, http://systrum.net/mount.png <http://systrum.net/mount.png> iTunes shows the mount-name of my stream. This is not the option that I want, but it is what seems to be the default that I am stuck with. In this second image, http://systrum.net/stream.png <http://systrum.net/stream.png>

Hi, needing some advice. I am running a backports version of icecast for Debian 10. I have found that with this version, the icecast server will usually run for about 7 days before it crashes. I found in the syslog that icecast gets terminated because it?s 'out of memory'. This never happened on the standard (stable) version of icecast that I ran on Debian 9 installed via apt. I?ve added

Hi Philipp, Edit (apologies for the repeated emails) Thanks for the quick response. I’ve run the command and you can find the output by following this link https://systrum.net/output.txt <https://systrum.net/output.txt> I'm running icecast with SSL enabled. I needed a a version of Icecast with SSL support which is why I am using the backports version. Regards Damian -------------- next

Hi, This thread seems to have stalled. Would anyone still be able to help me with this one? I?ve posted my log as requested. Any advice would be a great help. > > Message: 1 > Date: Tue, 29 Jan 2019 20:00:21 +1000 > From: Damian <db76 at riseup.net> > To: icecast at xiph.org > Subject: Re: [Icecast] Icecast Digest, Vol 175, Issue 11 > Message-ID:

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

I am using Darkice 0.17.1 and Icecast2 2.3.1 Darkice cannot talk to icecast, and I have no idee about there reason: Logentry on icecast server side: [2009-04-29 16:48:49] EROR connection/_handle_connection HTTP request parsing failed config for Icecast is a standard mount which works with ices. config for darkice is: [icecast-0] bitrateMode = vbr # constant bit rate bitrate

[2005-01-22 23:31:17] EROR yp/send_to_yp connection to http://dir.xiph.org/cgi-bin/yp-cgi failed with "Couldn't resolve host 'dir.xiph.org'" [2005-01-22 23:31:17] EROR yp/send_to_yp connection to http://www.oddsock.org/cgi-bin/yp-cgi failed with "Couldn't resolve host 'www.oddsock.org'" This happens in chroot. Out of chroot, no problems. So I did the

ehm, how many memory i need!? : ) i had first 64mb now i have 128mb but also: EROR stream/ices_instance_stream libshout error: Out of memory... --- >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.

Good morning, On Sun, 2020-10-11 at 10:24 +1000, Damian wrote: > Can I also ask, which is the recommended course of action? Sure, just keep in mind that we had weekend, so people were off. ;) > Should I rebuild icecast with OpenSSL or is there now a fixed version > via backports that I can use? Based on... On Sat, 2020-10-10 at 23:06 +1000, Damian wrote: > Edit (apologies for the

Greetings, I use Icecast for the live airing of my open phones podcast, and we've recently had some trouble with malicious actors attempting to disrupt the production in various ways, most of which are beyond the scope of this inquiry. Today the Icecast feed kept disconnecting and resetting the listener count. This happens on rare occasions, and I usually accept this as a noisy neighbor

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

I've downloaded and compiled icecast from cvs and the ices-0.2.3 from the download area for MP3 support.. (I'd use ogg, except I have 1000's of mp3. I'll re-rip them, but not today) 8) Is there a particular version of the icecast2 server that works w/ the ices-0.2.3 I'm using? I'm having difficulty getting the two to communicate. >From ices, I get the errors: Error

hello, I am tying to get to the bottom of why my icecast server crashed and failed to restart. The last entry in the error log is this: [2012-08-26 05:46:38] INFO source/source_read listener count on /stream now 7 [2012-08-26 05:48:02] INFO connection/wait_for_serversock HUP received, reread scheduled [2012-08-26 05:48:02] INFO connection/connection_thread connection thread

> libshout: :pserver:anoncvs@cvs.xiph.org:/usr/local/cvsroot > ices: :pserver:anoncvs@cvs.xiph.org:/cvs/ice > > Check out the ices-libshout_2 branch of ices. Libshout compiles fine, but ices wont configure correctly. It wouldn't find shout_new in libshout, lame_encode_flush_nogap in mp3lame nor ov_open in libvorbisfile.. (nor is libtool found, but I copied it from libshout.)

Good morning, first of all, thank you for your nice report. :) On Sat, 2020-10-10 at 20:32 +1000, Damian wrote: > Hi, needing some advice. > I am running a backports version of icecast for Debian 10. I have > found that with this version, the icecast server will usually run for > about 7 days before it crashes. I found in the syslog that icecast > gets terminated because it?s

On 09/25/2014 07:27 PM, uno wrote: > uno: >>> "Thomas B. R?cker": >>>> You can combine this with: default mount >>>> https://trac.xiph.org/ticket/1914#comment:1 >>>> Start with <mount type="default"> >>>> If you do this, you can basically do most things outside of Icecast to >>>> manage authentication