From mcc at fid4.com  Mon Oct 16 17:37:21 2023
From: mcc at fid4.com (Michael C Cambria)
Date: Mon, 16 Oct 2023 13:37:21 -0400
Subject: [Icecast] "Could not create listener socket on port" error only
 when using systemd service
Message-ID: <41ecb20c-16cb-fedf-54ac-8ec035d407c8@fid4.com>


Hi,

I'm using icecast via Fedora 37 package and systemd service to start.

I've added multiple <listen-socket> but get:

"EROR connection/connection_setup_sockets Could not create listener 
socket on port xxx"

Nothing listens on the ports in question, I verified via nc(1) and 
manually starting icecast via

"/usr/bin/icecast -c /etc/icecast.xml"

I can't find anything (chroot?) in icecast.service file [1] that might 
explain how the port is used for a short time causing start to fail.? 
Anyone have an idea what to try?

Thanks,
Michael

[1]

icecast.service:

[Unit]
Description=Icecast Network Audio Streaming Server
After=network.target

[Service]
ExecStart=/usr/bin/icecast -c /etc/icecast.xml
ExecReload=/bin/kill -HUP $MAINPID

[Install]
WantedBy=multi-user.target

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

From jordan at subj.am  Mon Oct 16 19:34:42 2023
From: jordan at subj.am (Jordan Erickson)
Date: Mon, 16 Oct 2023 12:34:42 -0700
Subject: [Icecast] "Could not create listener socket on port" error only
 when using systemd service
In-Reply-To: <41ecb20c-16cb-fedf-54ac-8ec035d407c8@fid4.com>
References: <41ecb20c-16cb-fedf-54ac-8ec035d407c8@fid4.com>
Message-ID: <723b3c62-d11e-4648-a647-6cf449c2a71a@subj.am>

On 10/16/23 10:37, Michael C Cambria wrote:
>
> Hi,
>
> I'm using icecast via Fedora 37 package and systemd service to start.
>
> I've added multiple <listen-socket> but get:
>
> "EROR connection/connection_setup_sockets Could not create listener 
> socket on port xxx"
*snip*

That error sounds like it could either be an issue relating to which 
user is starting the Icecast daemon (f.e. typically only root can listen 
on ports < 1024), or there'salready a service running on the requested 
port (which you seem to have verified it's not).

What are these multiple listening sockets you've got going btw? Sounds 
related. Post the part of the config for this if you're able.


Cheers,
Jordan

https://subj.am/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.xiph.org/pipermail/icecast/attachments/20231016/07588bd5/attachment.htm>

From petr.pisar at atlas.cz  Tue Oct 17 08:51:52 2023
From: petr.pisar at atlas.cz (Petr Pisar)
Date: Tue, 17 Oct 2023 10:51:52 +0200
Subject: [Icecast] "Could not create listener socket on port" error only
 when using systemd service
In-Reply-To: <723b3c62-d11e-4648-a647-6cf449c2a71a@subj.am>
References: <41ecb20c-16cb-fedf-54ac-8ec035d407c8@fid4.com>
 <723b3c62-d11e-4648-a647-6cf449c2a71a@subj.am>
Message-ID: <ZS5LKC4nELgqfTv+@dhcp-0-146.brq.redhat.com>

V?Mon, Oct 16, 2023 at 12:34:42PM -0700,?Jordan Erickson napsal(a):
> On 10/16/23 10:37, Michael C Cambria wrote:
> > I'm using icecast via Fedora 37 package and systemd service to start.
> > 
> > I've added multiple <listen-socket> but get:
> > 
> > "EROR connection/connection_setup_sockets Could not create listener
> > socket on port xxx"
> *snip*
> 
> That error sounds like it could either be an issue relating to which user is
> starting the Icecast daemon (f.e. typically only root can listen on ports <
> 1024), or there'salready a service running on the requested port (which you
> seem to have verified it's not).
> 
> What are these multiple listening sockets you've got going btw? Sounds
> related. Post the part of the config for this if you're able.
> 
It's rather caused by a SELinux policy which only allows icecast daemon to
listen on TCP/8000 port:

# sesearch --allow -s icecast_t -c tcp_socket
[...]
allow icecast_t port_type:tcp_socket name_bind; [ icecast_use_any_tcp_ports ]:True
allow icecast_t port_type:tcp_socket name_connect; [ icecast_use_any_tcp_ports ]:True
allow icecast_t port_type:tcp_socket { recv_msg send_msg }; [ icecast_use_any_tcp_ports ]:True
allow icecast_t soundd_port_t:tcp_socket { name_bind name_connect recv_msg send_msg };

If it's the cause, a corresponding log entry about denying the deamon to bind
a socket to the nonstandard port should appear in /var/log/audit/audit.log
when the deamon starts.

If one indeed wants to use any port by icecast, one can enable
icecast_use_any_tcp_ports SELinux boolean with

# setsebool icecast_use_any_tcp_ports on

The status can be queried like this:

# getsebool icecast_use_any_tcp_ports
icecast_use_any_tcp_ports --> on

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

From mcc at fid4.com  Tue Oct 17 12:37:37 2023
From: mcc at fid4.com (Michael C Cambria)
Date: Tue, 17 Oct 2023 08:37:37 -0400
Subject: [Icecast] "Could not create listener socket on port" error only
 when using systemd service
In-Reply-To: <ZS5LKC4nELgqfTv+@dhcp-0-146.brq.redhat.com>
References: <41ecb20c-16cb-fedf-54ac-8ec035d407c8@fid4.com>
 <723b3c62-d11e-4648-a647-6cf449c2a71a@subj.am>
 <ZS5LKC4nELgqfTv+@dhcp-0-146.brq.redhat.com>
Message-ID: <83c8fc04-a3d1-119f-c81b-f98f6cc4815b@fid4.com>



On 10/17/23 04:51, Petr Pisar wrote:
> V?Mon, Oct 16, 2023 at 12:34:42PM -0700,?Jordan Erickson napsal(a):
>> On 10/16/23 10:37, Michael C Cambria wrote:
>>> I'm using icecast via Fedora 37 package and systemd service to start.
>>>
>>> I've added multiple <listen-socket> but get:
>>>
>>> "EROR connection/connection_setup_sockets Could not create listener
>>> socket on port xxx"
>> *snip*
>>
> It's rather caused by a SELinux policy which only allows icecast daemon to
> listen on TCP/8000 port:
[deleted]


The problem does appear to be selinux related.? I was making changes 
remotely and didn't notice alerts until I had console access.? But why 
only via systemd?? When I started manually via bash things worked as 
expected?

Thanks,
MikeC





From uktony at radiocompany.net  Sun Oct 22 04:01:46 2023
From: uktony at radiocompany.net (Tony Harding)
Date: Sun, 22 Oct 2023 12:01:46 +0800
Subject: [Icecast] Icecast does not like Alexa
In-Reply-To: <41ecb20c-16cb-fedf-54ac-8ec035d407c8@fid4.com>
Message-ID: <20231022040910.235D6402F4@smtp2.osuosl.org>

I have a problem with a Windows icecast 2.4.4 on Windows 2012 R2

 ?

It appears to be working correctly and I can connect and listen but after about a week Alexa units, mostly Echo/1.0(APNG), cannot connect, or connect for only a few seconds.

 ?

I suspect that this is a .Net update problem as this worked fine for 18 months. 

 ?

Has anyone else experienced this?

 ?

I have uninstalled the icecast and reinstalled it and that fixed it for 10 days then the problem started again.

 ?

Tony

 ?

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