From db76 at riseup.net  Sun Feb  3 10:06:49 2019
From: db76 at riseup.net (Damian)
Date: Sun, 3 Feb 2019 20:06:49 +1000
Subject: [Icecast] YP listings in version 2.5 beta
In-Reply-To: <mailman.2733.1548944944.15702.icecast@xiph.org>
References: <mailman.2733.1548944944.15702.icecast@xiph.org>
Message-ID: <92993FF9-64D0-46F5-8C62-9417D8EEEFD3@riseup.net>

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: <0A5CF382-90C0-4F15-961E-969610967578 at riseup.net>
> Content-Type: text/plain; charset="utf-8"
> 
> 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 icecast-2.5-beta2.tar.gz <http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz> on the icecast homepage. I installed my current working version 2.4.4 in the same way and installed curl at that time. The log is added below as requested.
> 
>> 
>> [2019-01-28  21:17:18] INFO main/main Icecast 2.4.99.2 server started
>> [2019-01-28  21:17:18] INFO main/__log_system_name Running on systrum.net <http://systrum.net/>; OS: Linux 4.9.0-8-amd64, systrum.net <http://systrum.net/>, #1 SMP Debian 4.9.130-2 (2018-10-27), x86_64; Address Bits: 64
>> [2019-01-28  21:17:18] WARN main/main YP server handling has been disabled
>> [2019-01-28  21:17:18] INFO connection/get_tls_certificate No TLS capability on any configured ports
>> [2019-01-28  21:17:19] DBUG slave/_slave_thread checking master stream list
>> [2019-01-28  21:19:19] DBUG slave/_slave_thread checking master stream list
>> [2019-01-28  21:19:20] DBUG connection/_handle_aliases alias has made / into /status.xsl
>> [2019-01-28  21:19:20] DBUG connection/_handle_authentication_mount_normal Trying <mount type="normal"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:20] DBUG connection/_handle_authentication_mount_default Trying <mount type="default"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17ad0's (role legacy-global-source) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17ad0
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17ad0 role legacy-global-source processed: no match
>> [2019-01-28  21:19:20] DBUG connection/_handle_authentication_global Trying global authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad0e2a0's (role legacy-admin) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad0e2a0
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad0e2a0 role legacy-admin processed: no match
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17120's (role legacy-relay) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17120
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17120 role legacy-relay processed: no match
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17500's (role anonymous) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17500
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17500 role anonymous processed: ok
>> [2019-01-28  21:19:20] DBUG connection/_handle_get_request Got client 0x560ccad1bb00 with URI /status.xsl
>> [2019-01-28  21:19:20] DBUG connection/_handle_get_request Stats request, sending XSL transformed stats
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 4
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG fserve/fserve_add_client Adding client 0x560ccad1bb00 to file serving engine
>> [2019-01-28  21:19:20] DBUG fserve/fserve_add_pending fserve handler waking up
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG client/client_destroy Called to destory client 0x560ccad1bb00
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG fserve/fserv_thread_function fserve handler exit
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global clients (1)
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global connections (1)
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global client_connections (1)
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global clients (0)
>> [2019-01-28  21:19:20] DBUG connection/_handle_authentication_mount_normal Trying <mount type="normal"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:20] DBUG connection/_handle_authentication_mount_default Trying <mount type="default"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17ad0's (role legacy-global-source) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17ad0
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17ad0 role legacy-global-source processed: no match
>> [2019-01-28  21:19:20] DBUG connection/_handle_authentication_global Trying global authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad0e2a0's (role legacy-admin) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad0e2a0
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad0e2a0 role legacy-admin processed: no match
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17120's (role legacy-relay) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17120
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17120 role legacy-relay processed: no match
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17500's (role anonymous) queue.
>> [2019-01-28  21:19:20] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17500
>> [2019-01-28  21:19:20] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:20] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17500 role anonymous processed: ok
>> [2019-01-28  21:19:20] DBUG connection/_handle_get_request Got client 0x560ccad1bb00 with URI /style.css
>> [2019-01-28  21:19:20] INFO fserve/fserve_client_create checking for file /style.css (/usr/local/share/icecast/web/style.css)
>> [2019-01-28  21:19:20] DBUG fserve/fserve_add_client Adding client 0x560ccad1bb00 to file serving engine
>> [2019-01-28  21:19:20] DBUG fserve/fserve_add_pending fserve handler waking up
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG client/client_destroy Called to destory client 0x560ccad1bb00
>> [2019-01-28  21:19:20] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:20] DBUG fserve/fserv_thread_function fserve handler exit
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global clients (1)
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global connections (2)
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global client_connections (2)
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global file_connections (1)
>> [2019-01-28  21:19:20] DBUG stats/modify_node_event update global clients (0)
>> [2019-01-28  21:19:21] DBUG connection/_handle_authentication_mount_normal Trying <mount type="normal"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:21] DBUG connection/_handle_authentication_mount_default Trying <mount type="default"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17ad0's (role legacy-global-source) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17ad0
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17ad0 role legacy-global-source processed: no match
>> [2019-01-28  21:19:21] DBUG connection/_handle_authentication_global Trying global authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad0e2a0's (role legacy-admin) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad0e2a0
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad0e2a0 role legacy-admin processed: no match
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17120's (role legacy-relay) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17120
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17120 role legacy-relay processed: no match
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17500's (role anonymous) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17500
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17500 role anonymous processed: ok
>> [2019-01-28  21:19:21] DBUG connection/_handle_get_request Got client 0x560ccad1bb00 with URI /favicon.ico
>> [2019-01-28  21:19:21] INFO fserve/fserve_client_create checking for file /favicon.ico (/usr/local/share/icecast/web/favicon.ico)
>> [2019-01-28  21:19:21] DBUG fserve/fserve_add_client Adding client 0x560ccad1bb00 to file serving engine
>> [2019-01-28  21:19:21] DBUG fserve/fserve_add_pending fserve handler waking up
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG client/client_destroy Called to destory client 0x560ccad1bb00
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG fserve/fserv_thread_function fserve handler exit
>> [2019-01-28  21:19:21] DBUG connection/_handle_authentication_mount_normal Trying <mount type="normal"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:21] DBUG connection/_handle_authentication_mount_default Trying <mount type="default"> specific authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17ad0's (role legacy-global-source) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17ad0
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17ad0 role legacy-global-source processed: no match
>> [2019-01-28  21:19:21] DBUG connection/_handle_authentication_global Trying global authenticators for client 0x560ccad1bb00.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad0e2a0's (role legacy-admin) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad0e2a0
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad0e2a0 role legacy-admin processed: no match
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17120's (role legacy-relay) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17120
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17120 role legacy-relay processed: no match
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_add_client Trying to add client 0x560ccad1bb00 to auth 0x560ccad17500's (role anonymous) queue.
>> [2019-01-28  21:19:21] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] INFO auth/auth_add_client adding client 0x560ccad1bb00 for authentication on 0x560ccad17500
>> [2019-01-28  21:19:21] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:19:21] DBUG auth/__handle_auth_client client 0x560ccad1bb00 on auth 0x560ccad17500 role anonymous processed: ok
>> [2019-01-28  21:19:21] DBUG connection/_handle_get_request Got client 0x560ccad1bb00 with URI /icecast.png
>> [2019-01-28  21:19:21] INFO fserve/fserve_client_create checking for file /icecast.png (/usr/local/share/icecast/web/icecast.png)
>> [2019-01-28  21:19:21] DBUG fserve/fserve_add_client Adding client 0x560ccad1bb00 to file serving engine
>> [2019-01-28  21:19:21] DBUG fserve/fserve_add_pending fserve handler waking up
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG client/client_destroy Called to destory client 0x560ccad1bb00
>> [2019-01-28  21:19:21] DBUG auth/auth_release ...refcount on auth_t (null) is now 1
>> [2019-01-28  21:19:21] DBUG fserve/fserv_thread_function fserve handler exit
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global clients (1)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global connections (3)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global client_connections (3)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global file_connections (2)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global clients (0)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global clients (1)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global connections (4)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global client_connections (4)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global file_connections (3)
>> [2019-01-28  21:19:21] DBUG stats/modify_node_event update global clients (0)
>> [2019-01-28  21:20:10] DBUG connection/_handle_authentication_mount_normal Trying <mount type="normal"> specific authenticators for client 0x560ccad1bce0.
>> [2019-01-28  21:20:10] DBUG connection/_handle_authentication_mount_default Trying <mount type="default"> specific authenticators for client 0x560ccad1bce0.
>> [2019-01-28  21:20:10] DBUG auth/auth_addref ...refcount on auth_t (null) is now 2
>> [2019-01-28  21:20:10] DBUG auth/auth_add_client Trying to add client 0x560ccad1bce0 to auth 0x560ccad17ad0's (role legacy-global-source) queue.
>> [2019-01-28  21:20:10] DBUG auth/auth_addref ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:20:10] INFO auth/auth_add_client adding client 0x560ccad1bce0 for authentication on 0x560ccad17ad0
>> [2019-01-28  21:20:10] DBUG auth/queue_auth_client ...refcount on auth_t (null) is now 3
>> [2019-01-28  21:20:10] DBUG auth/__handle_auth_client client 0x560ccad1bce0 on auth 0x560ccad17ad0 role legacy-global-source processed: ok
>> [2019-01-28  21:20:10] INFO connection/_handle_source_request Source logging in at mountpoint "/Systrum-Channel3" from 168.235.85.43 as role legacy-global-source
>> [2019-01-28  21:20:10] DBUG connection/connection_complete_source sources count is 0
>> [2019-01-28  21:20:10] WARN format/format_get_type Unsupported or legacy stream type: "audio/mpeg". Falling back to generic minimal handler for best effort.
>> [2019-01-28  21:20:10] DBUG source/source_apply_mount Applying mount information for "/Systrum-Channel3"
>> [2019-01-28  21:20:10] DBUG format-mp3/format_mp3_apply_settings sending metadata interval 16000
>> [2019-01-28  21:20:10] DBUG format-mp3/format_mp3_apply_settings charset ISO8859-1
>> [2019-01-28  21:20:10] DBUG source/source_apply_mount YP changed to 1
>> 
>> 
>> 
> -------------- next part --------------
> An HTML attachment was scrubbed...
> URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190129/8d991934/attachment.html>
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 
> 
> ------------------------------
> 
> End of Icecast Digest, Vol 175, Issue 13
> ****************************************



From petr.pisar at atlas.cz  Sun Feb  3 10:34:37 2019
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Sun, 3 Feb 2019 11:34:37 +0100
Subject: [Icecast] YP listings in version 2.5 beta
In-Reply-To: <92993FF9-64D0-46F5-8C62-9417D8EEEFD3@riseup.net>
References: <mailman.2733.1548944944.15702.icecast@xiph.org>
 <92993FF9-64D0-46F5-8C62-9417D8EEEFD3@riseup.net>
Message-ID: <20190203103436.GA12612@album.bayer.uni.cx>

On Sun, Feb 03, 2019 at 08:06:49PM +1000, Damian wrote:
> 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.
>
You have all the data needed to resolve the issue.

> > I installed from source using the tarball icecast-2.5-beta2.tar.gz
> > <http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz> on
> > the icecast homepage. I installed my current working version 2.4.4 in the
> > same way and installed curl at that time. The log is added below as
> > requested.

$ tar xzf icecast-2.5-beta2.tar.gz
$ cd icecast-2.4.99.2

> >> [2019-01-28  21:17:18] INFO main/main Icecast 2.4.99.2 server started
> >> [2019-01-28  21:17:18] INFO main/__log_system_name Running on systrum.net <http://systrum.net/>; OS: Linux 4.9.0-8-amd64, systrum.net <http://systrum.net/>, #1 SMP Debian 4.9.130-2 (2018-10-27), x86_64; Address Bits: 64
> >> [2019-01-28  21:17:18] WARN main/main YP server handling has been disabled

$ grep -C 20 -Hnr 'YP server handling has been disabled'
src/yp.h-24-#define  YP_CURRENT_SONG        8
src/yp.h-25-#define  YP_CLUSTER_PASSWORD    9
src/yp.h-26-#define  YP_SUBTYPE             10 
src/yp.h-27-
src/yp.h-28-#define YP_ADD_ALL              -1
src/yp.h-29-
src/yp.h-30-#ifdef USE_YP
src/yp.h-31-void yp_add (const char *mount);
src/yp.h-32-void yp_remove (const char *mount);
src/yp.h-33-void yp_touch (const char *mount);
src/yp.h-34-void yp_recheck_config (ice_config_t *config);
src/yp.h-35-void yp_initialize(void);
src/yp.h-36-void yp_shutdown(void);
src/yp.h-37-
src/yp.h-38-#else
src/yp.h-39-
src/yp.h-40-#define yp_add(x)               do{}while(0)
src/yp.h-41-#define yp_remove(x)            do{}while(0)
src/yp.h-42-#define yp_touch(x)             do{}while(0)
src/yp.h-43-#define yp_recheck_config(x)    do{}while(0)
src/yp.h:44:#define yp_initialize()         ICECAST_LOG_WARN("YP server handling has been disabled")
src/yp.h-45-#define yp_shutdown()           do{}while(0)
src/yp.h-46-
src/yp.h-47-#endif /* USE_YP */
src/yp.h-48-
src/yp.h-49-#endif
src/yp.h-50-
src/yp.h-51-

So your build does not define USE_YP. Why?

$ grep -Hnr USE_YP
configure:14723:$as_echo "#define USE_YP 1" >>confdefs.h
configure.ac:133:    AC_DEFINE([USE_YP], 1, [Define to compile in YP support code])
src/cfgfile.c:577:#ifdef USE_YP
src/cfgfile.c:653:#ifdef USE_YP
src/yp.h:30:#ifdef USE_YP
src/yp.h:47:#endif /* USE_YP */
config.h.in:197:#undef USE_YP

Why did not configure.ac do that:

   113  XIPH_PATH_CURL([
   114      AC_CHECK_DECL([CURLOPT_NOSIGNAL],
   115          [ AC_DEFINE([HAVE_AUTH_URL], 1, [Define to compile in auth URL support code])
   116          AC_CHECK_FUNCS([curl_global_init])
   117          ICECAST_OPTIONAL="$ICECAST_OPTIONAL auth_url.o event_url.o curl.o"
   118          enable_curl="yes"
   119          XIPH_VAR_APPEND([XIPH_CPPFLAGS],[$CURL_CFLAGS])
   120          XIPH_VAR_PREPEND([XIPH_LIBS],[$CURL_LIBS])
   121          ], [ AC_MSG_NOTICE([Your curl dev files are too old (7.10 or above required)])
   122          ], [#include <curl/curl.h>
   123          ])
   124      ],[ AC_MSG_NOTICE([libcurl not found])
   125      ])
   126  dnl -- YP support --
   127  AC_ARG_ENABLE([yp],
   128          AC_HELP_STRING([--disable-yp],[disable YP directory support]),
   129          enable_yp="$enableval",
   130          enable_yp="yes")
   131  if test "x$enable_yp" = "xyes" -a "x$enable_curl" = xyes
   132  then
   133      AC_DEFINE([USE_YP], 1, [Define to compile in YP support code])
   134      ICECAST_OPTIONAL="$ICECAST_OPTIONAL yp.o"
   135  else
   136      AC_MSG_NOTICE([YP support disabled])
   137  fi

Either you called ./configure with --disable-yp or with --without-curl (see
XIPH_PATH_CURL definitio in m4/xiph_curl.m4) or your
curl does meet the tested criteria. E.g. You are missing curl header files or
you have too old curl. What does ./configure output tell about curl support?

-- Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190203/fbf616ef/attachment.sig>

From db76 at riseup.net  Mon Feb  4 11:57:29 2019
From: db76 at riseup.net (Damian)
Date: Mon, 4 Feb 2019 21:57:29 +1000
Subject: [Icecast] YP listings in version 2.5 beta
In-Reply-To: <mailman.2871.1549190815.15702.icecast@xiph.org>
References: <mailman.2871.1549190815.15702.icecast@xiph.org>
Message-ID: <785C2892-D0F4-4725-A4D6-FA036B225068@riseup.net>

Hi Petr

Thanks for taking the time to respond and to try to help.

> 
> 
> Either you called ./configure with --disable-yp or with --without-curl (see
> XIPH_PATH_CURL definitio in m4/xiph_curl.m4)

So, I can see this? but what am I looking for exactly?


> or your
> curl does meet the tested criteria. E.g. You are missing curl header files or
> you have too old curl. What does ./configure output tell about curl support?
> 

I?m not sure ? can you explain what I need to do / where to look to find this out?
I?m feeling my way in the dark with most of this.

Doing curl ?version tells me the following ...

$ curl --version
curl 7.52.1 (x86_64-pc-linux-gnu) libcurl/7.52.1 OpenSSL/1.0.2q zlib/1.2.8 libidn2/0.16 libpsl/0.17.0 (+libidn2/0.16) libssh2/1.7.0 nghttp2/1.18.1 librtmp/2.3
Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtmp rtsp scp sftp smb smbs smtp smtps telnet tftp 
Features: AsynchDNS IDN IPv6 Largefile GSS-API Kerberos SPNEGO NTLM NTLM_WB SSL libz TLS-SRP HTTP2 UnixSockets HTTPS-proxy PSL 

 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190204/31fe508b/attachment.htm>

From petr.pisar at atlas.cz  Mon Feb  4 17:38:00 2019
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Mon, 4 Feb 2019 18:38:00 +0100
Subject: [Icecast] YP listings in version 2.5 beta
In-Reply-To: <785C2892-D0F4-4725-A4D6-FA036B225068@riseup.net>
References: <mailman.2871.1549190815.15702.icecast@xiph.org>
 <785C2892-D0F4-4725-A4D6-FA036B225068@riseup.net>
Message-ID: <20190204173800.GA22176@album.bayer.uni.cx>

On Mon, Feb 04, 2019 at 09:57:29PM +1000, Damian wrote:
> > 
> > Either you called ./configure with --disable-yp or with --without-curl (see
> > XIPH_PATH_CURL definitio in m4/xiph_curl.m4)
> 
> So, I can see this? but what am I looking for exactly?
>
How did you invoke the ./configure command when you was building the icecast?

> > or your
> > curl does meet the tested criteria. E.g. You are missing curl header files or
> > you have too old curl. What does ./configure output tell about curl support?
> > 
> 
> I?m not sure ? can you explain what I need to do / where to look to find this out?
> I?m feeling my way in the dark with most of this.
>
Build icecast again and look at the output of the configure command.

A correctly recognized curl library should be logged like this:

checking for curl-config... /usr/bin/curl-config
checking curl/curl.h usability... yes
checking curl/curl.h presence... yes
checking for curl/curl.h... yes
checking for libcurl... yes
checking whether CURLOPT_NOSIGNAL is declared... yes
checking for curl_global_init... yes

If some of these checks fail, the configure script will diable YP support and
will log "YP support disabled". Also the generated config.h won't contain
"#define USE_YP 1" line.

-- Petr
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 228 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190204/28db74d4/attachment.sig>

From db76 at riseup.net  Tue Feb  5 12:03:07 2019
From: db76 at riseup.net (Damian)
Date: Tue, 5 Feb 2019 22:03:07 +1000
Subject: [Icecast] Icecast Digest, Vol 176, Issue 3
In-Reply-To: <mailman.1.1549368001.13647.icecast@xiph.org>
References: <mailman.1.1549368001.13647.icecast@xiph.org>
Message-ID: <2BC8EB20-36E1-4C49-84C9-1852C7138BCA@riseup.net>

Hi,


>>> 
>>> Either you called ./configure with --disable-yp or with --without-curl (see
>>> XIPH_PATH_CURL definitio in m4/xiph_curl.m4)
>> 
>> So, I can see this? but what am I looking for exactly?
>> 
> How did you invoke the ./configure command when you was building the icecast?
> 


I extracted the source tarball in the /tmp directory. I then moved the exracted icecast dir to /opt and ran ./configure as root.
You were right. It?s not recognising the curl library. I ran ./configure again and it returned the following:


checking curl/curl.h usability... no
checking curl/curl.h presence... no
checking for curl/curl.h... no
checking for libcurl... no
configure: libcurl not found

I can see that usr/bin/curl exists. What would you advise from here?



>>> or your
>>> curl does meet the tested criteria. E.g. You are missing curl header files or
>>> you have too old curl. What does ./configure output tell about curl support?
>>> 
>> 
>> I?m not sure ? can you explain what I need to do / where to look to find this out?
>> I?m feeling my way in the dark with most of this.
>> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190205/5ebc77d0/attachment.htm>

From sigfood at dinorama.fr  Tue Feb  5 12:08:31 2019
From: sigfood at dinorama.fr (tth)
Date: Tue, 05 Feb 2019 13:08:31 +0100
Subject: [Icecast] Icecast Digest, Vol 176, Issue 3
In-Reply-To: <2BC8EB20-36E1-4C49-84C9-1852C7138BCA@riseup.net> (from
 db76@riseup.net on Tue Feb  5 13:03:07 2019)
References: <mailman.1.1549368001.13647.icecast@xiph.org>
 <2BC8EB20-36E1-4C49-84C9-1852C7138BCA@riseup.net>
Message-ID: <1549368511.23156.5@debian>

Le 05/02/2019 13:03:07, Damian a ?crit?:

> You were right. It?s not recognising the curl library. I ran  
> ./configure again and it returned the following:
> 
> 
> checking curl/curl.h usability... no
> checking curl/curl.h presence... no
> checking for curl/curl.h... no
> checking for libcurl... no
> configure: libcurl not found
> 
> I can see that usr/bin/curl exists. What would you advise from here?

    If you are on Debian, I think you have to install the -dev
    part of curl library :

libcurl4-openssl-dev/stable,stable 7.52.1-5+deb9u8 amd64
   development files and documentation for libcurl (OpenSSL flavour)

tTh.

From db76 at riseup.net  Wed Feb  6 13:18:27 2019
From: db76 at riseup.net (Damian)
Date: Wed, 6 Feb 2019 23:18:27 +1000
Subject: [Icecast] Icecast Digest, Vol 176, Issue 4
In-Reply-To: <mailman.1.1549454401.17853.icecast@xiph.org>
References: <mailman.1.1549454401.17853.icecast@xiph.org>
Message-ID: <EFC0F541-08C0-4E90-9EF3-EAD48D8538BC@riseup.net>

Hi and thanks for the reply. 

> 
> Message: 2
> Date: Tue, 05 Feb 2019 13:08:31 +0100
> From: tth <sigfood at dinorama.fr>
> To: Icecast streaming server user discussions <icecast at xiph.org>
> Subject: Re: [Icecast] Icecast Digest, Vol 176, Issue 3
> Message-ID: <1549368511.23156.5 at debian>
> Content-Type: text/plain; charset=UTF-8; DelSp=Yes; Format=Flowed
> 
> Le 05/02/2019 13:03:07, Damian a ?crit :
> 
>> You were right. It?s not recognising the curl library. I ran  
>> ./configure again and it returned the following:
>> 
>> 
>> checking curl/curl.h usability... no
>> checking curl/curl.h presence... no
>> checking for curl/curl.h... no
>> checking for libcurl... no
>> configure: libcurl not found
>> 
>> I can see that usr/bin/curl exists. What would you advise from here?
> 
>    If you are on Debian, I think you have to install the -dev
>    part of curl library :
> 
> libcurl4-openssl-dev/stable,stable 7.52.1-5+deb9u8 amd64
>   development files and documentation for libcurl (OpenSSL flavour)
> 

This looks to have solved it for me! I haven?t run icecast yet, but checking the ./configure output shows

checking for pthread_spin_lock... yes
checking for curl-config... /usr/bin/curl-config
checking curl/curl.h usability... yes
checking curl/curl.h presence... yes
checking for curl/curl.h... yes
checking for libcurl... yes


Thanks so much to Petr and tth for guiding me through this. I appreciate your patience.

Damian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190206/35b6e128/attachment.htm>

From db76 at riseup.net  Thu Feb  7 12:28:50 2019
From: db76 at riseup.net (Damian)
Date: Thu, 7 Feb 2019 22:28:50 +1000
Subject: [Icecast] Running version 2.5 beta as a service
Message-ID: <1EC2C659-2592-41BE-B833-2CF479BD04CD@riseup.net>

Hi,

When installing Icecast2 (stable) on Debian9 using ATP packet manager, we need to go into /etc/default/icecast and enable the init.d script with ENABLE=true if we want to run Icecast as a service. 

I?ve been playing with icecast 2.5 beta installed from source and obviously this means things are located in different places. I would like to know if it is also possible to run this version as a service and if so, where I need to look to enable init.d

Regrads
Damian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190207/ab2de2d7/attachment.htm>

From db76 at riseup.net  Mon Feb 11 12:02:45 2019
From: db76 at riseup.net (Damian)
Date: Mon, 11 Feb 2019 22:02:45 +1000
Subject: [Icecast] Running version 2.5 beta as a service
In-Reply-To: <1EC2C659-2592-41BE-B833-2CF479BD04CD@riseup.net>
References: <1EC2C659-2592-41BE-B833-2CF479BD04CD@riseup.net>
Message-ID: <52BDFD00-E96D-44E1-B0F5-3E0688E3E086@riseup.net>

Hi again,

I apologise for my persistence with this. Perhaps my last question has already been answered in another thread. If so, could anyone please point me to it.
Just needing to know how to enable Icecast as a service on Debian when installed from source. The option to enable it isn?t in the same directory (/etc/default/icecast) as when using apt-get install 

D

> On 7 Feb 2019, at 10:28 pm, Damian <db76 at riseup.net> wrote:
> 
> Hi,
> 
> When installing Icecast2 (stable) on Debian9 using APT packet manager, we need to go into /etc/default/icecast and enable the init.d script with ENABLE=true if we want to run Icecast as a service. 
> 
> I?ve been playing with icecast 2.5 beta installed from source and obviously this means things are located in different places. I would like to know if it is also possible to run this version as a service and if so, where I need to look to enable init.d
> 
> Regrads
> Damian

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190211/23a1a6b0/attachment.htm>

From thomas at ruecker.fi  Mon Feb 11 13:32:40 2019
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B=2e_R=c3=bccker?=)
Date: Mon, 11 Feb 2019 13:32:40 +0000
Subject: [Icecast] Running version 2.5 beta as a service
In-Reply-To: <52BDFD00-E96D-44E1-B0F5-3E0688E3E086@riseup.net>
References: <1EC2C659-2592-41BE-B833-2CF479BD04CD@riseup.net>
 <52BDFD00-E96D-44E1-B0F5-3E0688E3E086@riseup.net>
Message-ID: <dac87ccd-6ca5-9638-94ad-d111e4b701c3@ruecker.fi>

Hi,


On 2/11/19 12:02 PM, Damian wrote:
> Hi again,
>
> I apologise for my persistence with this. Perhaps my last question has
> already been answered in another thread. If so, could anyone please
> point me to it.
> Just needing to know how to enable Icecast as a service on Debian when
> installed from source. The option to enable it isn?t in the same
> directory (/etc/default/icecast) as when using apt-get install


You can either manually puzzle up the packaging. The source package can
be found alongside every package repository:

http://download.opensuse.org/repositories/multimedia:/xiph:/beta/Debian_9.0/

It's actually identical for all Debian and Ubuntu releases.


The other option is to build from source:

https://wiki.xiph.org/Icecast_Server/Git_workflow

so basically:

git clone --recursive https://git.xiph.org/icecast-server.git
cd icecast-server
./autogen.sh
./configure
make


Importantly: omit the "make install" and just manually replace the
binary - and if necessary the web and admin directories and the config.xml.
Basically "sudo cp src/icecast /usr/bin/icecast2" on a debian-ish system.


Cheers,

Thomas


PS: To EVERYONE participating in discussions on this mailing list. If
you want take ACTIVE part in discussions, then using a "digest"
subscription and replying to digest emails is frowned upon. It breaks
discussion threads and makes things really hard to read. Please don't,
we'll be eternally indebted and grateful to you. Thanks!




From dave at dashs.denver.co.us  Mon Feb 11 19:39:36 2019
From: dave at dashs.denver.co.us (Dave Serls)
Date: Mon, 11 Feb 2019 12:39:36 -0700
Subject: [Icecast] Running version 2.5 beta as a service
In-Reply-To: <52BDFD00-E96D-44E1-B0F5-3E0688E3E086@riseup.net>
References: <1EC2C659-2592-41BE-B833-2CF479BD04CD@riseup.net>
 <52BDFD00-E96D-44E1-B0F5-3E0688E3E086@riseup.net>
Message-ID: <20190211123936.735ff237@groucho.dashs.denver.co.us>

On Mon, 11 Feb 2019 22:02:45 +1000
Damian <db76 at riseup.net> wrote:

> Hi again,
> 
> I apologise for my persistence with this. Perhaps my last question has already been answered in another thread. If so, could anyone please point me to it.
> Just needing to know how to enable Icecast as a service on Debian when installed from source. The option to enable it isn?t in the same directory (/etc/default/icecast) as when using apt-get install 
> 
> D
> 
> > On 7 Feb 2019, at 10:28 pm, Damian <db76 at riseup.net> wrote:
> > 
> > Hi,
> > 
> > When installing Icecast2 (stable) on Debian9 using APT packet manager, we need to go into /etc/default/icecast and enable the init.d script with ENABLE=true if we want to run Icecast as a service. 
> > 
> > I?ve been playing with icecast 2.5 beta installed from source and obviously this means things are located in different places. I would like to know if it is also possible to run this version as a service and if so, where I need to look to enable init.d
> > 
> > Regrads
> > Damian  
> 

    I assume the source build produced a file /etc/init.d/icecast2.
    For automated service, "sudo systemctl enable icecast2".
    Formerly the distributed source also produced the file /etc/default/icecast2 which
    specified user, group, config file, and enable-state.
    Not sure if it's still that way.

-- 
************************************************************************
*   Dave Serls                                 Littleton, CO, USA      *
*   dashs.denver.co.us                         http://www.dashs.com    *
************************************************************************


From db76 at riseup.net  Tue Feb 12 12:51:07 2019
From: db76 at riseup.net (Damian)
Date: Tue, 12 Feb 2019 22:51:07 +1000
Subject: [Icecast] Running version 2.5 beta as a service
In-Reply-To: <mailman.1.1549972801.28525.icecast@xiph.org>
References: <mailman.1.1549972801.28525.icecast@xiph.org>
Message-ID: <E37E37D0-5E92-47A6-9FF3-E9D4E6ABBBD9@riseup.net>

Hi and thanks for the replies.

Thomas, is the second option you mention an installation of the daemon necessary for running as a service?
I have already installed the icecast 2.4.99 from source using http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz <http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz> at icecast.org and have built it using ?

./configure 
make 
make install. 

? so I got a little confused by your suggestions.


Dave, in response to your post, /etc/init.d/icecast2 and /etc/default/icecast2 are visible when installing icecast using the apt packet manager on Debian.
When installing from source however, I don?t see these 




> 
> You can either manually puzzle up the packaging. The source package can
> be found alongside every package repository:
> 
> http://download.opensuse.org/repositories/multimedia:/xiph:/beta/Debian_9.0/
> 
> It's actually identical for all Debian and Ubuntu releases.
> 
> 
> The other option is to build from source:
> 
> https://wiki.xiph.org/Icecast_Server/Git_workflow
> 
> so basically:
> 
> git clone --recursive https://git.xiph.org/icecast-server.git
> cd icecast-server
> ./autogen.sh
> ./configure
> make
> 
> 
> Importantly: omit the "make install" and just manually replace the
> binary - and if necessary the web and admin directories and the config.xml.
> Basically "sudo cp src/icecast /usr/bin/icecast2" on a debian-ish system.
> 


> 
>    I assume the source build produced a file /etc/init.d/icecast2.
>    For automated service, "sudo systemctl enable icecast2".
>    Formerly the distributed source also produced the file /etc/default/icecast2 which
>    specified user, group, config file, and enable-state.
>    Not sure if it's still that way.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190212/f538b542/attachment.htm>

From thomas at ruecker.fi  Tue Feb 12 13:23:52 2019
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B=2e_R=c3=bccker?=)
Date: Tue, 12 Feb 2019 13:23:52 +0000
Subject: [Icecast] Running version 2.5 beta as a service
In-Reply-To: <E37E37D0-5E92-47A6-9FF3-E9D4E6ABBBD9@riseup.net>
References: <mailman.1.1549972801.28525.icecast@xiph.org>
 <E37E37D0-5E92-47A6-9FF3-E9D4E6ABBBD9@riseup.net>
Message-ID: <9372f97d-0cae-bb1d-652a-c21e45a3937e@ruecker.fi>

Hi,

On 2/12/19 12:51 PM, Damian wrote:
> Hi and thanks for the replies.
>
> Thomas, is the second option you mention an installation of the daemon
> necessary for running as a service?
> I have already installed the icecast 2.4.99 from source using
> http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz?at
> icecast.org <http://icecast.org> and have built it using ?


I guess I was too terse in my explanation. See below.


>
> ./configure?
> make?
> make install.?
>
> ? so I got a little confused by your suggestions.
>
>
> Dave, in response to your post, /etc/init.d/icecast2 and
> /etc/default/icecast2 are visible when installing icecast using the
> apt packet manager on Debian.
> When installing from source however, I don?t see these


Yes and that's what I actually meant. Install the latest beta(!) version
from our repositories and then replace the binary with what you built
from source. If necessary also webroot and adminroot contents. You could
also for style points align the PREFIX with the one from the package and
just make install over things.

There are many ways to get to a usable development setup.


Please note that this is starting to outgrow the basic scope of this
mailing list. If you want to run latest git and provide feedback and
patches, then the icecast-dev mailing list is better suited.


Cheers,

Thomas




From db76 at riseup.net  Wed Feb 13 23:11:15 2019
From: db76 at riseup.net (Damian)
Date: Thu, 14 Feb 2019 09:11:15 +1000
Subject: [Icecast] Icecast Digest, Vol 176, Issue 8
In-Reply-To: <mailman.1.1550059201.31748.icecast@xiph.org>
References: <mailman.1.1550059201.31748.icecast@xiph.org>
Message-ID: <EF09BD05-223E-4FE2-9730-0758CFD6AF2E@riseup.net>

Hi Thomas,

Thanks for clarifying. I?m generally okay with how to do this now. I really appreciate your time and patience. 

Regards
Damian 

>> Thomas, is the second option you mention an installation of the daemon
>> necessary for running as a service?
>> I have already installed the icecast 2.4.99 from source using
>> http://downloads.xiph.org/releases/icecast/icecast-2.5-beta2.tar.gz at
>> icecast.org <http://icecast.org> and have built it using ?
> 
> 
> I guess I was too terse in my explanation. See below.
> 
> 
>> 
>> ./configure 
>> make 
>> make install. 
>> 
>> ? so I got a little confused by your suggestions.
>> 
>> 
>> Dave, in response to your post, /etc/init.d/icecast2 and
>> /etc/default/icecast2 are visible when installing icecast using the
>> apt packet manager on Debian.
>> When installing from source however, I don?t see these
> 
> 
> Yes and that's what I actually meant. Install the latest beta(!) version
> from our repositories and then replace the binary with what you built
> from source. If necessary also webroot and adminroot contents. You could
> also for style points align the PREFIX with the one from the package and
> just make install over things.
> 
> There are many ways to get to a usable development setup.
> 
> 
> Please note that this is starting to outgrow the basic scope of this
> mailing list. If you want to run latest git and provide feedback and
> patches, then the icecast-dev mailing list is better suited.
> 
> 
> Cheers,
> 
> Thomas
> 
> 
> 
> 
> ------------------------------
> 
> Subject: Digest Footer
> 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 
> 
> ------------------------------
> 
> End of Icecast Digest, Vol 176, Issue 8
> ***************************************



From jessicaoleary at outlook.com  Fri Feb  1 16:31:14 2019
From: jessicaoleary at outlook.com (Jessica O'Leary)
Date: Fri, 1 Feb 2019 16:31:14 +0000
Subject: [Icecast] Icecast set up
Message-ID: <AM6PR10MB1942A059EB7A13A2681D1170B4920@AM6PR10MB1942.EURPRD10.PROD.OUTLOOK.COM>

Hello,

We are trying to download and run your Icecast 2.4.4 programme. We?ve followed the instructions from the website and am up to where it says ?once the configured file is modified, you should be able to start the server with the following command?. 

We?re trying to put the command into the command prompt but it?s not letting us type in at all so we?re stuck and can?t go any further.

I didn?t know if you could help at all. We?ve looked online at tutorials but most have older versions or look different to what we have on our screen.

Thank you,

Jess 

From webmaster at xiph.org  Thu Feb 14 08:33:10 2019
From: webmaster at xiph.org (Xiph.org Webmaster)
Date: Thu, 14 Feb 2019 08:33:10 +0000
Subject: [Icecast] Announcement - Digest delivery has been discontinued
Message-ID: <15d370aa-35a2-9128-649b-386aacee00e6@xiph.org>

Hello everyone,


We're sorry to notify you that we have taken the decision to discontinue
the possibility of "digest" subscriptions to this mailing list.

The practical impact for subscribers previously on 'digest'
subscriptions should be fairly low, as this is not a high volume mailing
list. We'd nevertheless like to apologize for the inconvenience.

If you haven't yet, may we suggest setting up a mail filter to sort
mailing list mails in a separate directory of your email account. This
is a common practice and convenient to see all discussions in one place.


Xiph.org listmaster



From jordan at coolmic.net  Thu Feb 14 16:21:38 2019
From: jordan at coolmic.net (Jordan Erickson)
Date: Thu, 14 Feb 2019 08:21:38 -0800
Subject: [Icecast] Icecast set up
In-Reply-To: <AM6PR10MB1942A059EB7A13A2681D1170B4920@AM6PR10MB1942.EURPRD10.PROD.OUTLOOK.COM>
References: <AM6PR10MB1942A059EB7A13A2681D1170B4920@AM6PR10MB1942.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <69a0e73d-f4b9-00ec-205f-b4090fb67ca7@coolmic.net>

Hi Jess,

The issue of "not letting us type in at all" at a command prompt is an
issue separate from / not related to Icecast. You may want to refer to
your operating system documentation / online help for this.


Cheers,
Jordan


On 2/1/19 8:31 AM, Jessica O'Leary wrote:
> Hello,
> 
> We are trying to download and run your Icecast 2.4.4 programme. We?ve followed the instructions from the website and am up to where it says ?once the configured file is modified, you should be able to start the server with the following command?. 
> 
> We?re trying to put the command into the command prompt but it?s not letting us type in at all so we?re stuck and can?t go any further.
> 
> I didn?t know if you could help at all. We?ve looked online at tutorials but most have older versions or look different to what we have on our screen.
> 
> Thank you,
> 
> Jess 
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
> 


From jv.oliveirag at gmail.com  Thu Feb 14 14:01:20 2019
From: jv.oliveirag at gmail.com (=?UTF-8?Q?Jo=C3=A3o_Victor_Oliveira?=)
Date: Thu, 14 Feb 2019 12:01:20 -0200
Subject: [Icecast] Trying to compile icecast in Toradex apalis imx6
Message-ID: <CA+9OK-rydef7rt7t26Br=Kog3wiEptPTg91ohQJRkqdAB-=56g@mail.gmail.com>

Hi!

I'm using a Toradex apalis imx6 board to make a project for my bussiness
and I need Icecast running on it, but I can't compile it in the board. It
shows an error in "xslt" while compiling- I'm using Yocto.

Do yow have any idea how can I compile Icecast source code in my Toradex
apalis board without using this xslt?

Thanks in advance!

<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>
Livre
de v?rus. www.avast.com
<https://www.avast.com/sig-email?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=webmail>.
<#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190214/ceb701c7/attachment.htm>

From thomas at ruecker.fi  Thu Feb 14 18:58:47 2019
From: thomas at ruecker.fi (=?UTF-8?Q?Thomas_B=2e_R=c3=bccker?=)
Date: Thu, 14 Feb 2019 18:58:47 +0000
Subject: [Icecast] Trying to compile icecast in Toradex apalis imx6
In-Reply-To: <CA+9OK-rydef7rt7t26Br=Kog3wiEptPTg91ohQJRkqdAB-=56g@mail.gmail.com>
References: <CA+9OK-rydef7rt7t26Br=Kog3wiEptPTg91ohQJRkqdAB-=56g@mail.gmail.com>
Message-ID: <3e3d6d54-4aef-04d4-ce14-b39f7fa1da93@ruecker.fi>

Hi,

On 2/14/19 2:01 PM, Jo?o Victor Oliveira wrote:
> I'm using a Toradex apalis imx6 board to make a project for my
> bussiness and I need Icecast running on it, but I can't compile it in
> the board. It shows an error in "xslt" while compiling- I'm using Yocto.


By that you mean you are using the OpenEmbedded framework to bitbake a
custom Linux distribution for your board. (The Yocto Project offers
various layers that get used by OE for that purpose)


> Do yow have any idea how can I compile Icecast source code in my
> Toradex apalis board without using this xslt?


libXSLT is a requirement for building Icecast.


I'm not sure why you are trying to build Icecast on the device itself if
you have a whole massive build automation framework for embedded Linux
at hand.

If writing a Bitbake recipe for Icecast is not your cup of tea you could
also go the manual route of cross-compiling. For this you'd need to
build "an SDK" with your environment first. Then use it.

In all cases, you must ensure that the header files of libraries you are
linking against are available at build time. Most important for Icecast
are: libVorbis, libOgg, libXML2, libXSLT and libCURL


If you have trouble to get the OE framework to do your bidding, you
might want to ask the OE and Yocto communities for help.


Cheers,

Thomas




From jessicaoleary at outlook.com  Fri Feb 15 18:14:38 2019
From: jessicaoleary at outlook.com (Jessica O'Leary)
Date: Fri, 15 Feb 2019 18:14:38 +0000
Subject: [Icecast] Set up
Message-ID: <AM0PR10MB1940EC293AA9CE23153A2EE4B4600@AM0PR10MB1940.EURPRD10.PROD.OUTLOOK.COM>

Hello,

We are trying to download and run your Icecast 2.4.4 programme. We?ve followed the instructions from the website and am up to where it says ?once the configured file is modified, you should be able to start the server with the following command?. 

We?re trying to put the command into the command prompt but it?s not letting us type in at all so we?re stuck and can?t go any further.

I didn?t know if you could help at all. We?ve looked online at tutorials but most have older versions or look different to what we have on our screen.

Thank you

From ashleyb1019 at gmail.com  Fri Feb 15 19:25:10 2019
From: ashleyb1019 at gmail.com (Ashley Bernard)
Date: Fri, 15 Feb 2019 14:25:10 -0500
Subject: [Icecast] Set up
In-Reply-To: <AM0PR10MB1940EC293AA9CE23153A2EE4B4600@AM0PR10MB1940.EURPRD10.PROD.OUTLOOK.COM>
References: <AM0PR10MB1940EC293AA9CE23153A2EE4B4600@AM0PR10MB1940.EURPRD10.PROD.OUTLOOK.COM>
Message-ID: <B836E34F-F35E-418E-A6AC-A0B78FC24DC4@gmail.com>

What is the command you are using? Also what operating system?

Sent from my iPhone

> On Feb 15, 2019, at 1:14 PM, Jessica O'Leary <jessicaoleary at outlook.com> wrote:
> 
> Hello,
> 
> We are trying to download and run your Icecast 2.4.4 programme. We?ve followed the instructions from the website and am up to where it says ?once the configured file is modified, you should be able to start the server with the following command?. 
> 
> We?re trying to put the command into the command prompt but it?s not letting us type in at all so we?re stuck and can?t go any further.
> 
> I didn?t know if you could help at all. We?ve looked online at tutorials but most have older versions or look different to what we have on our screen.
> 
> Thank you
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast


From mvandop at xs4all.nl  Thu Feb 21 09:30:20 2019
From: mvandop at xs4all.nl (Michel van Dop)
Date: Thu, 21 Feb 2019 10:30:20 +0100
Subject: [Icecast] Icecast 2.4.4 and packet loss on CentOS 7
Message-ID: <527a8db8e049cb7c1fa21ccec2270f03@xs4all.nl>

Hi, 

We have some time-outs when there connecting more thane 1400 listeners
to Icecast.
We use CentOS Linux release 7.6.1810 on port 80 and 443 for SSL on IPv4
and IPv6. 
The stream have many mountpoint 16 active (8 main en 8 fallback and 8
file when faillback is down)
The server have 2 CPU's on 3Ghz and 6000mb memory. And we 1 GB uplink
(we use 130mbit on peak). We use a hardware firewall Mikrotik CCR1036
and extra software firewall (Arno's Iptables Firewall)
We use Cacti to check server mem,cpu and load en traffic. We see 34% CPU
and 0,5 load on peak. 
We change the CONNTRACK on the server to 32384 and we change some limits
for application in /etc/security/limits.conf
* soft core 8388608
* soft nofile 65000
* hard nofile 65000 

We use on Icecast t:
<queue-size>524288</queue-size>
<client-timeout>20</client-timeout>
<header-timeout>15</header-timeout>
<source-timeout>10</source-timeout>
<burst-size>65536</burst-size> 

When we have the problem the disconnect mountpoints and we see 16-20%
packet loss to icmp to the IPv4 address. And when we login on ssh the
system is response slower. 

We see no error in the system log or Icecast log. 

Do anyone have some tips to check or tune the configs? 
We have running other servers the have more listeners but no problems
but the have no SSL or so many mountpoints. 

Best regards,
Michel

--
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190221/e8bd3fff/attachment.htm>

From larry at acbradio.org  Mon Feb 25 21:19:41 2019
From: larry at acbradio.org (Larry Turnbull)
Date: Mon, 25 Feb 2019 21:19:41 +0000
Subject: [Icecast] increase source limit
Message-ID: <019101d4cd4f$d019f6e0$704de4a0$@acbradio.org>

Hi all:

 

I am working on an Icecast server that is running on windows server 2012.

 

I edited the config file to raise the source limit from 2 to 5.

 

I restarted the program and restarted the Icecast server.

 

The server starts with no issue.

 

However, the  server still won't allow more than 2 sources at  a time.

 

I am specifying different mounts on each source so that doesn't appear to be
the issue.

 

Do I need to set up specific mount points in the config file to allow more
than 2 sources?

 

Thanks.

 

Larry

 


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190225/790b02e8/attachment.htm>

From jeffares.robert at gmail.com  Mon Feb 25 22:29:28 2019
From: jeffares.robert at gmail.com (Robert Jeffares)
Date: Tue, 26 Feb 2019 11:29:28 +1300
Subject: [Icecast] increase source limit
In-Reply-To: <019101d4cd4f$d019f6e0$704de4a0$@acbradio.org>
References: <019101d4cd4f$d019f6e0$704de4a0$@acbradio.org>
Message-ID: <d14e9423-a2c9-6348-877e-b74f7e70f6da@gmail.com>

Increase the number from 5 to 50

You will then be able to attach your 5.

1 source may mean more then one connection especially if you have audio 
and text.

regards

Robert


On 26/02/19 10:19, Larry Turnbull wrote:
>
> Hi all:
>
> I am working on an Icecast server that is running on windows server 2012.
>
> I edited the config file to raise the source limit from 2 to 5.
>
> I restarted the program and restarted the Icecast server.
>
> The server starts with no issue.
>
> However, the ?server still won?t allow more than 2 sources at ?a time.
>
> I am specifying different mounts on each source so that doesn?t appear 
> to be the issue.
>
> Do I need to set up specific mount points in the config file to allow 
> more than 2 sources?
>
> Thanks.
>
> Larry
>
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190226/a869ff1f/attachment.htm>

From larry at acbradio.org  Tue Feb 26 12:01:12 2019
From: larry at acbradio.org (Larry Turnbull)
Date: Tue, 26 Feb 2019 12:01:12 +0000
Subject: [Icecast] increase source limit
In-Reply-To: <d14e9423-a2c9-6348-877e-b74f7e70f6da@gmail.com>
References: <019101d4cd4f$d019f6e0$704de4a0$@acbradio.org>
 <d14e9423-a2c9-6348-877e-b74f7e70f6da@gmail.com>
Message-ID: <008901d4cdca$db488d80$91d9a880$@acbradio.org>

I tried 50 and that didn?t work.

 

I increased it to 100, still no go.

 

I exited the program and then restarted Icecast win32 and restarted the server.

 

It still doesn?t allow more than 2 sources.

 

Larry

 

 

From: Icecast <icecast-bounces at xiph.org> On Behalf Of Robert Jeffares
Sent: Monday, February 25, 2019 4:29 PM
To: icecast at xiph.org
Subject: Re: [Icecast] increase source limit

 

Increase the number from 5 to 50

You will then be able to attach your 5.

1 source may mean more then one connection especially if you have audio and text.

regards

Robert

 

On 26/02/19 10:19, Larry Turnbull wrote:

Hi all:

 

I am working on an Icecast server that is running on windows server 2012.

 

I edited the config file to raise the source limit from 2 to 5.

 

I restarted the program and restarted the Icecast server.

 

The server starts with no issue.

 

However, the  server still won?t allow more than 2 sources at  a time.

 

I am specifying different mounts on each source so that doesn?t appear to be the issue.

 

Do I need to set up specific mount points in the config file to allow more than 2 sources?

 

Thanks.

 

Larry

 






_______________________________________________
Icecast mailing list
Icecast at xiph.org <mailto:Icecast at xiph.org> 
http://lists.xiph.org/mailman/listinfo/icecast

 



-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190226/3637c0cd/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 332 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190226/3637c0cd/attachment.jpe>

From phschafft at de.loewenfelsen.net  Tue Feb 26 13:07:17 2019
From: phschafft at de.loewenfelsen.net (Philipp Schafft)
Date: Tue, 26 Feb 2019 13:07:17 +0000
Subject: [Icecast] increase source limit
In-Reply-To: <019101d4cd4f$d019f6e0$704de4a0$@acbradio.org>
References: <019101d4cd4f$d019f6e0$704de4a0$@acbradio.org>
Message-ID: <1551186437.2164.17.camel@de.loewenfelsen.net>

Good morning,

On Mon, 2019-02-25 at 21:19 +0000, Larry Turnbull wrote:
> I am working on an Icecast server that is running on windows server 2012.

I'm not into windows at all, but is there still support for Windows
Server 2012? Maybe an upgrade might be desirable.


> I edited the config file to raise the source limit from 2 to 5. 
> 
> I restarted the program and restarted the Icecast server.

> The server starts with no issue. 

ok.


> However, the  server still won't allow more than 2 sources at  a time.

What is in the error and in the access log for the corresponding
connects?


> I am specifying different mounts on each source so that doesn't appear to be
> the issue.

Ok.


> Do I need to set up specific mount points in the config file to allow more
> than 2 sources?

No. Most people break Icecast by having too much config. You should
NEVER have <mount> sections unless your stream NEEDS to have different
configuration than the other streams.

In fact most servers just work fine with only setting the passwords, the
hostname, and the contact information.

With best regards,

-- 
Philipp Schafft (CEO/Gesch?ftsf?hrer) 
Telephon: +49.3535 490 17 92

L?wenfelsen UG (haftungsbeschr?nkt)     Registration number:
Bickinger Stra?e 21                     HRB 12308 CB
04916 Herzberg (Elster)                 VATIN/USt-ID:
Germany                                 DE305133015
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 490 bytes
Desc: This is a digitally signed message part
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190226/1cf54c12/attachment.sig>

From leonardo.ortiz at marisolsa.com  Thu Feb 28 02:52:30 2019
From: leonardo.ortiz at marisolsa.com (Leonardo Oliveira Ortiz)
Date: Thu, 28 Feb 2019 02:52:30 +0000
Subject: [Icecast] Using butt in same mount point that is used for relay
Message-ID: <59E8C16E83D82B439E20698AAC790B5F01D69D71AC@ma46>

Hello.

We are using icecast to relay a radio station on local network and I have a question: There is a way to send streaming from a mic (with butt) using same mount point that we are using for relay? Or some workaround for it like using fallback mount point?
Azuracast can do it but the software have some bugs (in general usage) and I need a more fast solution for now....

Best regards.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190228/3d9bd52f/attachment.htm>

From wantom428 at gmail.com  Thu Feb 28 03:01:06 2019
From: wantom428 at gmail.com (mas wanto)
Date: Thu, 28 Feb 2019 10:01:06 +0700
Subject: [Icecast] Using butt in same mount point that is used for relay
In-Reply-To: <59E8C16E83D82B439E20698AAC790B5F01D69D71AC@ma46>
References: <59E8C16E83D82B439E20698AAC790B5F01D69D71AC@ma46>
Message-ID: <CAC7mMM-2HXm02weGtxeRn4dG+-W99fs4vpLmJmZ-RDpo03sQ6A@mail.gmail.com>

Sam broadcaster and fallback mount

Pada tanggal Kam, 28 Feb 2019 09.58 Leonardo Oliveira Ortiz <
leonardo.ortiz at marisolsa.com menulis:

> Hello.
>
>
>
> We are using icecast to relay a radio station on local network and I have
> a question: There is a way to send streaming from a mic (with butt) using
> same mount point that we are using for relay? Or some workaround for it
> like using fallback mount point?
>
> Azuracast can do it but the software have some bugs (in general usage) and
> I need a more fast solution for now?.
>
>
>
> Best regards.
>
>
> _______________________________________________
> Icecast mailing list
> Icecast at xiph.org
> http://lists.xiph.org/mailman/listinfo/icecast
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190228/91541492/attachment.htm>

From wantom428 at gmail.com  Thu Feb 28 12:53:20 2019
From: wantom428 at gmail.com (mas wanto)
Date: Thu, 28 Feb 2019 19:53:20 +0700
Subject: [Icecast] Using butt in same mount point that is used for relay
In-Reply-To: <CAC7mMM-2HXm02weGtxeRn4dG+-W99fs4vpLmJmZ-RDpo03sQ6A@mail.gmail.com>
References: <59E8C16E83D82B439E20698AAC790B5F01D69D71AC@ma46>
 <CAC7mMM-2HXm02weGtxeRn4dG+-W99fs4vpLmJmZ-RDpo03sQ6A@mail.gmail.com>
Message-ID: <CAC7mMM_7MJ80D6ZUaskg8NCCwp+vP+6AuygA-ZCoFVXC6Rn+jQ@mail.gmail.com>

Thank you

Pada tanggal Kam, 28 Feb 2019 10.01 mas wanto <wantom428 at gmail.com menulis:

> Sam broadcaster and fallback mount
>
> Pada tanggal Kam, 28 Feb 2019 09.58 Leonardo Oliveira Ortiz <
> leonardo.ortiz at marisolsa.com menulis:
>
>> Hello.
>>
>>
>>
>> We are using icecast to relay a radio station on local network and I have
>> a question: There is a way to send streaming from a mic (with butt) using
>> same mount point that we are using for relay? Or some workaround for it
>> like using fallback mount point?
>>
>> Azuracast can do it but the software have some bugs (in general usage)
>> and I need a more fast solution for now?.
>>
>>
>>
>> Best regards.
>>
>>
>> _______________________________________________
>> Icecast mailing list
>> Icecast at xiph.org
>> http://lists.xiph.org/mailman/listinfo/icecast
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190228/0961c6eb/attachment.htm>

From wantom428 at gmail.com  Thu Feb 28 12:56:36 2019
From: wantom428 at gmail.com (mas wanto)
Date: Thu, 28 Feb 2019 19:56:36 +0700
Subject: [Icecast] Using butt in same mount point that is used for relay
In-Reply-To: <CAC7mMM_7MJ80D6ZUaskg8NCCwp+vP+6AuygA-ZCoFVXC6Rn+jQ@mail.gmail.com>
References: <59E8C16E83D82B439E20698AAC790B5F01D69D71AC@ma46>
 <CAC7mMM-2HXm02weGtxeRn4dG+-W99fs4vpLmJmZ-RDpo03sQ6A@mail.gmail.com>
 <CAC7mMM_7MJ80D6ZUaskg8NCCwp+vP+6AuygA-ZCoFVXC6Rn+jQ@mail.gmail.com>
Message-ID: <CAC7mMM_FrgBpip22zy3-x7f4iDizchePMKFH5Yau+Psnh-4epg@mail.gmail.com>

Not result if sam broadcaster active ?

Pada tanggal Kam, 28 Feb 2019 19.53 mas wanto <wantom428 at gmail.com menulis:

> Thank you
>
> Pada tanggal Kam, 28 Feb 2019 10.01 mas wanto <wantom428 at gmail.com
> menulis:
>
>> Sam broadcaster and fallback mount
>>
>> Pada tanggal Kam, 28 Feb 2019 09.58 Leonardo Oliveira Ortiz <
>> leonardo.ortiz at marisolsa.com menulis:
>>
>>> Hello.
>>>
>>>
>>>
>>> We are using icecast to relay a radio station on local network and I
>>> have a question: There is a way to send streaming from a mic (with butt)
>>> using same mount point that we are using for relay? Or some workaround for
>>> it like using fallback mount point?
>>>
>>> Azuracast can do it but the software have some bugs (in general usage)
>>> and I need a more fast solution for now?.
>>>
>>>
>>>
>>> Best regards.
>>>
>>>
>>> _______________________________________________
>>> Icecast mailing list
>>> Icecast at xiph.org
>>> http://lists.xiph.org/mailman/listinfo/icecast
>>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190228/6843334f/attachment.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: Screenshot_2019-02-28-19-55-52-092_com.android.chrome.png
Type: image/png
Size: 120261 bytes
Desc: not available
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20190228/6843334f/attachment.png>