similar to: Empty auth error message, URL auth problems on Windows Server

Hello, In order to identify if was some issue regard to the auth api we include some trace logs and we move it to other machine. Bellow is what trace we are generating (date, result, elapsed time in milleseconds, request): [8/29/18 11:49:00 AM] 200 0.3721 action=listener_add&server=r22&port=443&client=2616&mount=/alphafmsp&user=&p

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:

Hi Thanks for the reply > >> >> Set logging to verbose, starts Icecast, have it running for a while and >> then >> provide us with the error log please. >> >> Chances are your beta lacks cURL. Where did you get the beta from? >> >> On 27 Jan 2019, at 11:33, Damian wrote: >> > > > I installed from source using the tarball

Hello, We are using url authentication and getting the item bellow at the log: [2018-08-24 23:26:05] INFO auth_url/url_add_listener client auth (http://127.0.0.1:8001/listener/add) failed with "" I put try/catch and reviewed all my code ensure always return a proper status and header error code, so what trigger this kind of error? Regards, Thiago --------------

Hi, I installed from source using the tarball on the liquidsoap website. I installed curl as a prerequisite before building icecast from source. A version check shows that I have the current version of curl as follows: curl 7.52.1 (x86_64-pc-linux-gnu) libcurl/7.52. The first part of the log shows that YP server handling is disabled though. (I pasted a fuller snippet of the log earlier but it’s

hallo firstly sorry for posting to wrong thread i want to ask if somebody could explain meaning of log records below DBUG stats/modify_node_event update global connections (686) DBUG stats/modify_node_event update global client_connections (685) number in parentheeses is increasing in every log line what is menaing of this number? because this number goes over 59669 and it seems that after

Linux blort.psg.com 3.13.0-29-generic #53-Ubuntu SMP Wed Jun 4 21:02:19 UTC 2014 i686 i686 i686 GNU/Linux # icecast2 --version Icecast 2.3.3 <listen-socket> <port>43000</port> </listen-socket> <listen-socket> <port>43001</port> <shoutcast-compat>1</shoutcast-compat> </listen-socket> source is

Thanks for this information, but the two connections do not die out when using my player in the Android browser. In fact they even stay when the Audio.src is set to some invalid string. You can observe this here: http://concertzender.nl/wp-content/themes/cz-theme/App/test/ , by clicking one of the large icons - and then monitor the corresponding stream here: http://streams.greenhost.nl:8080/

Eric Kolotyluk schrieb: > Thanks for getting back to me - I would really like to figure this out. > > My Icecast service is running and the address of my server is > 14.83.23.157. Could someone try connecting to it with a source and see > if you have any luck. > > More below.. > > Thomas B. Ruecker wrote: >> Eric Kolotyluk schrieb: >> >>> I have

Klaas, You will find that there often are multiple connections, particularly for HTML5 audio elements in WebKit browsers as they probe to see if the media is seekable or not. The multiple connections die out soon after starting though, leaving you one connection for actually streaming the audio. You can verify this yourself with a packet sniffer such as Wireshark. It wouldn't hurt to double

You're likely seeing the browser's built-in handling of your stream, and not actually a page. It's unlikely that the issue has anything to do with connectivity. If you can provide a URL to your actual stream, we might be able to help diagnose the issue. *Brad Isbell // AudioPump, Inc.* brad at audiopump.co Skype: bradisbell Phone: +1 312-488-4680 On Wed, Jul 18, 2018 at 2:50 PM,

Hi, On 10/04/2013 06:27 PM, Andy Martin wrote: > I looked at these requests and started trying to interpret the data of > the header and the stream. I receive a header, and even when I added > the parameter to the request to try and get meta-data, it seems that > it is not being included. Namely, the number that is supposed to tell > the distance between each meta-data section that

Hello I always have had best results encoding the stream .mp3 it works on all devices. I also suggest the source to be the same or better than your stream.. this saves in many areas. it sounds like you are possibly debugging a time lapsed source/ stream.. i did not read all so if this is not so i apologize On May 5, 2015 3:11 AM, "Klaas van der Linden" < vanderlinden at

Dear all , I have a problem with Icecast mount Point function . The goal of creating mount point : Run mutable streaming icecast in the same time , but with deffrient passwords , it hink this is the way icecast work but I did not get it , what the problem ! hope you do know it ! Each user will have his/her own OddCast station and he/she will streaming a deferent music in the same time ! And

Dear all , I have a problem with Icecast mount Point function . The goal of creating mount point : Run mutable streaming icecast in the same time , but with deffrient passwords , it hink this is the way icecast work but I did not get it , what the problem ! hope you do know it ! Each user will have his/her own OddCast station and he/she will streaming a deferent music in the same time

I am running icecast 2.2.0 on Windows XP and am trying to get yp listed so my server will show on the Icecast Stream Directory under WinAMP. My sense is that the error.log line seen below ending in "preventing YP listings" indicates a problem on my end but I do not easily see what it may be. Any ideas? Neil MPHMedia [2005-12-03 16:03:47] INFO stats/stats.c stats thread started

Hi, You don't check for malloc failure. I've made a patch that is possibly wrong but it saves the program from SIGSEGV and replaces it with SIGABRT. -peter diff -ru icecast-2.3.2-ORIG/src/admin.c icecast-2.3.2/src/admin.c --- icecast-2.3.2-ORIG/src/admin.c Fri May 2 17:40:00 2008 +++ icecast-2.3.2/src/admin.c Thu Apr 28 19:53:03 2011 @@ -291,6 +291,9 @@

This is what I get in the icecast logfile. [2005-03-27 15:35:13] INFO main/main Icecast 2.2.0 server started [2005-03-27 15:35:13] WARN main/main YP server handling has been disabled [2005-03-27 15:35:13] INFO stats/_stats_thread stats thread started [2005-03-27 15:35:13] INFO fserve/fserv_thread_function file serving thread started [2005-03-27 15:36:38] INFO admin/admin_handle_request Bad

I looked at these requests and started trying to interpret the data of the header and the stream. I receive a header, and even when I added the parameter to the request to try and get meta-data, it seems that it is not being included. Namely, the number that is supposed to tell the distance between each meta-data section that is sent in the stream. I couldn't figure out the config setting

hem here it is the patch. ;) bye kysucix -------------- next part -------------- Index: conf/icecast.xml.in =================================================================== --- conf/icecast.xml.in (revisione 10365) +++ conf/icecast.xml.in (copia locale) @@ -62,6 +62,7 @@ <port>8001</port> </listen-socket> --> +