freeradius - Bullseye - port for 0.0.0.0 port 1812 in use

[Maurizio Caloro]

Hello

 

Please fithting with the freeradius server, yes installed also Mysql and I have the problem that the Error binding to port for 0.0.0.0 appair.

 

No other service are running on this port 1812, yes I’am shure. Today installed a new version bullseye on one other machine. And I have

the same issue…..

 

Yes kill -9 PID always done, without any change

->Ps -ax | grep freeradius, appair only if this are active

->Port are always only one time listening

 

Failed binding to auth interface enp3s0 address * port 1812 bound to server default: Address already in use

/etc/freeradius/3.0/sites-enabled/default[59]: Error binding to port for 0.0.0.0 port 1812

 

In this folder > /etc/freeradius/3.0/sites-enabled/default file installed, for now and also remarked IPv6 Listen, no success.

 

Linux HPT610.caloro.m 5.10.0-11-amd64 #1 SMP Debian 5.10.92-1 (2022-01-18) x86_64 GNU/Linux

 

root@name:/etc/default# dpkg -l |  grep freeradius

ii  freeradius                      3.0.21+dfsg-2.2+deb11u1

ii  freeradius-common  3.0.21+dfsg-2.2+deb11u1

ii  freeradius-config        3.0.21+dfsg-2.2+deb11u1

ii  freeradius-mysql        3.0.21+dfsg-2.2+deb11u1

ii  freeradius-utils            3.0.21+dfsg-2.2+deb11u1

ii  libfreeradius3               3.0.21+dfsg-2.2+deb11u1

 

thanks for any possible help

Mauri

 

[Greg Wooledge]

On Sun, Feb 06, 2022 at 03:02:59PM +0100, Maurizio Caloro wrote:
> No other service are running on this port 1812, yes I'am shure.

Don't just tell us. SHOW us.

unicorn:~$ sudo lsof -i :1812
[sudo] password for greg:
unicorn:~$

If there's something using that port, lsof will show it:

unicorn:~$ sudo lsof -i :25
COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
tcpserver 657 qpsmtpd 3u IPv4 15669 0t0 TCP *:smtp (LISTEN)
/usr/loca 182487 qpsmtpd 0u IPv4 1625329 0t0 TCP 10.0.0.7:smtp->ip246.tervelnet.com:11288 (ESTABLISHED)
/usr/loca 182487 qpsmtpd 1u IPv4 1625329 0t0 TCP 10.0.0.7:smtp->ip246.tervelnet.com:11288 (ESTABLISHED)
/usr/loca 182490 qpsmtpd 0u IPv4 1625339 0t0 TCP 10.0.0.7:smtp->212.70.149.89:6882 (ESTABLISHED)
/usr/loca 182490 qpsmtpd 1u IPv4 1625339 0t0 TCP 10.0.0.7:smtp->212.70.149.89:6882 (ESTABLISHED)
/usr/loca 182494 qpsmtpd 0u IPv4 1624452 0t0 TCP 10.0.0.7:smtp->5.34.205.151:64226 (ESTABLISHED)
/usr/loca 182494 qpsmtpd 1u IPv4 1624452 0t0 TCP 10.0.0.7:smtp->5.34.205.151:64226 (ESTABLISHED)

> Yes kill -9 PID always done, without any change

STOP that!!

DO NOT use kill -9 unless it's ABSOLUTELY necessary! Even if you think
it's absolutely necessary, consider rebooting instead. You might have to
anyway, if some process is stuck on a hardware failure.

> Failed binding to auth interface enp3s0 address * port 1812 bound to server
> default: Address already in use
>
> /etc/freeradius/3.0/sites-enabled/default[59]: Error binding to port for
> 0.0.0.0 port 1812

Sure sounds like something is using the port. lsof should show it. Or
ss, or netstat, if you use them correctly.

unicorn:~$ ss -ntl | grep :25
LISTEN 0 20 0.0.0.0:25 0.0.0.0:*

unicorn:~$ sudo ss -ntlp | grep :25
LISTEN 0 20 0.0.0.0:25 0.0.0.0:* users:(("tcpserver",pid=657,fd=3))

(The -p option requires superuser privs.)

[Maurizio Caloro]

Thanks for your answer, please have a look:


root@Name:# systemctl status freeradius
● freeradius.service - FreeRADIUS multi-protocol policy server
Loaded: loaded (/lib/systemd/system/freeradius.service; enabled; vendor preset: enabled)
Active: active (running) since Sun 2022-02-06 08:57:45 CET; 7h ago
Docs: man:radiusd(8)
man:radiusd.conf(5)
http://wiki.freeradius.org/
http://networkradius.com/doc/
Process: 21647 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -lstdout (code=exited, s>
Main PID: 21648 (freeradius)
Status: "Processing requests"
Tasks: 6 (limit: 8869)
Memory: 79.3M (limit: 1.0G)
CPU: 846ms
CGroup: /system.slice/freeradius.service
└─21648 /usr/sbin/freeradius -f -P

root@name:# lsof -i :1812

COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME

freeradiu 21648 freerad 8u IPv4 1149216 0t0 UDP *:radius

Freeradius -X
[SNIP]

Failed binding to auth interface enp3s0 address * port 1812 bound to server default: Address already in use
/etc/freeradius/3.0/sites-enabled/default[59]: Error binding to port for 0.0.0.0 port 1812

root@name:#


-----Ursprüngliche Nachricht-----
Von: Greg Wooledge <gr...@wooledge.org>
Gesendet: Sonntag, 6. Februar 2022 15:47
An: debia...@lists.debian.org
Betreff: Re: freeradius - Bullseye - port for 0.0.0.0 port 1812 in use

[Greg Wooledge]

On Sun, Feb 06, 2022 at 04:08:14PM +0100, Maurizio Caloro wrote:
> Thanks for your answer, please have a look:
>
>
> root@Name:# systemctl status freeradius
> ● freeradius.service - FreeRADIUS multi-protocol policy server
> Loaded: loaded (/lib/systemd/system/freeradius.service; enabled; vendor preset: enabled)
> Active: active (running) since Sun 2022-02-06 08:57:45 CET; 7h ago
> Docs: man:radiusd(8)
> man:radiusd.conf(5)
> http://wiki.freeradius.org/
> http://networkradius.com/doc/
> Process: 21647 ExecStartPre=/usr/sbin/freeradius $FREERADIUS_OPTIONS -Cx -lstdout (code=exited, s>
> Main PID: 21648 (freeradius)
> Status: "Processing requests"
> Tasks: 6 (limit: 8869)
> Memory: 79.3M (limit: 1.0G)
> CPU: 846ms
> CGroup: /system.slice/freeradius.service
> └─21648 /usr/sbin/freeradius -f -P
>
> root@name:# lsof -i :1812
> COMMAND PID USER FD TYPE DEVICE SIZE/OFF NODE NAME
> freeradiu 21648 freerad 8u IPv4 1149216 0t0 UDP *:radius

These results confirm that something *is* using the port. Specifically,
it's "freeradius", which is apparently a user name, a program name, and
a service name.

> Freeradius -X
> [SNIP]
> Failed binding to auth interface enp3s0 address * port 1812 bound to server default: Address already in use
> /etc/freeradius/3.0/sites-enabled/default[59]: Error binding to port for 0.0.0.0 port 1812
> root@name:#

So... it's not surprising that you get this result when you try to use
the port a second time.

What result were you expecting to see?

What are you trying to do?

[Maurizio Caloro]

>These results confirm that something *is* using the port. Specifically, it's "freeradius", which is apparently a user name, a program name, and a service name.
>

>So... it's not surprising that you get this result when you try to use the port a second time.
>
>What result were you expecting to see?
>
>What are you trying to do?
>

I need only a running radius server to logon with a test radtest username passwort locahost:1812 0

root@name:# systemctl stop freeradius

● freeradius.service - FreeRADIUS multi-protocol policy server
Loaded: loaded (/lib/systemd/system/freeradius.service; enabled; vendor preset: enabled)

Active: inactive (dead) since Sun 2022-02-06 16:24:18 CET; 2min 47s ago

Docs: man:radiusd(8)
man:radiusd.conf(5)
http://wiki.freeradius.org/
http://networkradius.com/doc/

root@name:# lsof -i :1812

root@name:#

but If start systemctl start freeradius
the system are thinks that this port are already in use

[Greg Wooledge]

On Sun, Feb 06, 2022 at 04:29:36PM +0100, Maurizio Caloro wrote:
> I need only a running radius server to logon with a test radtest username passwort locahost:1812 0
>
> root@name:# systemctl stop freeradius
> ● freeradius.service - FreeRADIUS multi-protocol policy server
> Loaded: loaded (/lib/systemd/system/freeradius.service; enabled; vendor preset: enabled)
> Active: inactive (dead) since Sun 2022-02-06 16:24:18 CET; 2min 47s ago
> Docs: man:radiusd(8)
> man:radiusd.conf(5)
> http://wiki.freeradius.org/
> http://networkradius.com/doc/
>
> root@name:# lsof -i :1812
> root@name:#
>
> but If start systemctl start freeradius
> the system are thinks that this port are already in use

Because it *is*. The system is starting freeradius for you. It's
running. You've seen that it's running.

But now you want to start it *again*? Why? What's wrong with the one
that's currently running?

If you want to change the options that it uses, or something like that,
then you should configure the service so that it starts with the options
you require.