Your message dated Tue, 24 Aug 2021 08:30:54 +0200
with message-id <[email protected]>
and subject line Re: Bug#992321: freeradius isn't creating a PID file
has caused the Debian Bug report #992321,
regarding freeradius isn't creating a PID file
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
992321: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=992321
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: freeradius
Version: 3.0.21+dfsg-2.2
Severity: important
X-Debbugs-Cc: [email protected]
Dear Maintainer,
We use monit to check the PID file at /var/log/freeradius/freeradius.pid and
restart the service if it goes down, and this works in stretch and buster but
no PID file seems to be created in bullseye.
I tried checking the permissions of the folder and looking through log files
and can't find a reason it wouldn't be created.
After this I removed our configuration and did a base install and neither seems
to generate this file.
While there are workarounds I want to confirm if freeradius is still meant to
generate this file and isn't, or if there are any further troubleshooting steps
I can try.
Thanks
-- System Information:
Debian Release: 11.0
APT prefers stable-security
APT policy: (500, 'stable-security'), (500, 'stable')
Architecture: amd64 (x86_64)
Kernel: Linux 5.10.0-8-amd64 (SMP w/8 CPU threads)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8),
LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages freeradius depends on:
ii freeradius-common 3.0.21+dfsg-2.2
ii freeradius-config 3.0.21+dfsg-2.2
ii libc6 2.31-13
ii libcrypt1 1:4.4.18-4
ii libct4 1.2.3-1
ii libfreeradius3 3.0.21+dfsg-2.2
ii libgdbm6 1.19-2
ii libpam0g 1.4.0-9
ii libperl5.32 5.32.1-4+deb11u1
ii libreadline8 8.1-1
ii libsqlite3-0 3.34.1-3
ii libssl1.1 1.1.1k-1
ii libsystemd0 247.3-6
ii libtalloc2 2.3.1-2+b1
ii libwbclient0 2:4.13.5+dfsg-2
ii lsb-base 11.1.0
Versions of packages freeradius recommends:
ii freeradius-utils 3.0.21+dfsg-2.2
Versions of packages freeradius suggests:
pn freeradius-krb5 <none>
pn freeradius-ldap <none>
pn freeradius-mysql <none>
pn freeradius-postgresql <none>
pn freeradius-python3 <none>
pn snmp <none>
-- no debconf information
--- End Message ---
--- Begin Message ---
Am 24.08.21 um 04:43 schrieb Dan MacLeod:
Hi Dan,
> Thank you Bernhard, that's fixed the issue.
Thanks for the check.
>
> Is there any reason that the Bullseye version runs as a foreground
> process vs Buster which doesn't? Or is that a question for freeradius
> themselves?
This is a change upstream did, freeradius is now using the preferred
systemd way of daemon supervision (run in foreground, signal daemon
readyness through systemd-notify).
Bernhard
--- End Message ---
