oidentd 2.5.0-1 fails after ~24-48hr on Debian testing - oidentd.socket: Failed to queue service startup job

Package: oidentd
Version: 2.5.0-1

Distribution: Debian Testing x86_64

Prior to the systemd/socket integration, oidentd has worked for 10-15+
years.  After being integrated with systemd it fails every ~24-48
hours.
I've had to add a canary/watcher to restart oidentd when it fails--
two examples of it failing:

Aug 23 10:09:25 machine-name systemd[1]:
/lib/systemd/system/[email protected]:10: Standard output type syslog
is obsolete, automatically updating to journal. Please update your
unit file, and consider removing the setting altogether.
Aug 23 10:09:25 machine-name systemd[1]: Started RFC 1413 compliant
per-connection ident daemon (127.0.0.1:53610).
Aug 23 10:09:25 machine-name systemd[1]:
[email protected]:113-127.0.0.1:53610.service: Succeeded.
Aug 23 10:14:25 machine-name systemd[1]:
/lib/systemd/system/[email protected]:10: Standard output type syslog
is obsolete, automatically updating to journal. Please update your
unit file, and consider removing the setting altogether.
Aug 23 10:14:25 machine-name systemd[1]: Started RFC 1413 compliant
per-connection ident daemon (127.0.0.1:53622).
Aug 23 10:14:25 machine-name systemd[1]:
[email protected]:113-127.0.0.1:53622.service: Succeeded.
Aug 23 10:19:25 machine-name systemd[1]:
/lib/systemd/system/[email protected]:10: Standard output type syslog
is obsolete, automatically updating to journal. Please update your
unit file, and consider removing the setting altogether.
Aug 23 10:19:25 machine-name systemd[1]: Started RFC 1413 compliant
per-connection ident daemon (127.0.0.1:53682).
Aug 23 10:19:25 machine-name systemd[1]:
[email protected]:113-127.0.0.1:53682.service: Succeeded.
Aug 23 10:24:25 machine-name systemd[1]:
/lib/systemd/system/[email protected]:10: Standard output type syslog
is obsolete, automatically updating to journal. Please update your
unit file, and consider removing the setting altogether.
Aug 23 10:24:25 machine-name systemd[1]: Started RFC 1413 compliant
per-connection ident daemon (127.0.0.1:53694).
Aug 23 10:24:25 machine-name systemd[1]:
[email protected]:113-127.0.0.1:53694.service: Succeeded.
Aug 23 10:29:25 machine-name systemd[1]:
/lib/systemd/system/[email protected]:10: Standard output type syslog
is obsolete, automatically updating to journal. Please update your
unit file, and consider removing the setting altogether.
Aug 23 10:29:25 machine-name systemd[1]: Started RFC 1413 compliant
per-connection ident daemon (127.0.0.1:53706).
Aug 23 10:29:25 machine-name systemd[1]:
[email protected]:113-127.0.0.1:53706.service: Succeeded.
Aug 23 10:31:08 machine-name systemd[1]: oidentd.socket: Failed to
queue service startup job (Maybe the service file is missing or not a
template unit?): Transport endpoint is not connected
Aug 23 10:31:08 machine-name systemd[1]: oidentd.socket: Failed with
result 'resources'.

Another example from earlier:

$ sudo systemctl status  oidentd.socket
● oidentd.socket - RFC 1413 compliant ident socket
     Loaded: loaded (/lib/systemd/system/oidentd.socket; enabled;
vendor preset: enabled)
     Active: failed (Result: resources) since Sat 2020-08-22 10:16:00
EDT; 5h 3min ago
   Triggers: ● [email protected]:113-1.2.3.4:52198.service
             ● [email protected]:113-1.2.3.4:52142.service
             ● [email protected]:113-1.2.3.4:52186.service
             ● [email protected]:113-1.2.3.4:52160.service
             ● [email protected]:113-1.2.3.4:52192.service
             ● [email protected]:113-1.2.3.4:52210.service
             ● [email protected]:113-1.2.3.4:52072.service
             ● [email protected]:113-1.2.3.4:52232.service
             ● [email protected]:113-1.2.3.4:52218.service
             ● [email protected]:113-1.2.3.4:52222.service
             ● [email protected]:113-1.2.3.4:52190.service
             ● [email protected]:113-1.2.3.4:52182.service
             ● [email protected]:113-1.2.3.4:52224.service
             ● [email protected]:113-1.2.3.4:52228.service
             ● [email protected]:113-1.2.3.4:52156.service
             ● [email protected]:113-1.2.3.4:52150.service
             ● [email protected]:113-1.2.3.4:52166.service
             ● [email protected]:113-1.2.3.4:52194.service
             ● [email protected]:113-1.2.3.4:52202.service
             ● [email protected]:113-1.2.3.4:52200.service
             ● [email protected]:113-1.2.3.4:52162.service
             ● [email protected]:113-1.2.3.4:52128.service
             ● [email protected]:113-1.2.3.4:52078.service
             ● [email protected]:113-1.2.3.4:52154.service
             ● [email protected]:113-1.2.3.4:52146.service
             ● [email protected]:113-1.2.3.4:52144.service
             ● [email protected]:113-1.2.3.4:52136.service
             ● [email protected]:113-1.2.3.4:52226.service
             ● [email protected]:113-1.2.3.4:52130.service
             ● [email protected]:113-1.2.3.4:52204.service
             ● [email protected]:113-1.2.3.4:52220.service
             ● [email protected]:113-1.2.3.4:52164.service
             ● [email protected]:113-1.2.3.4:52140.service
             ● [email protected]:113-1.2.3.4:52070.service
             ● [email protected]:113-1.2.3.4:52178.service
             ● [email protected]:113-1.2.3.4:52126.service
             ● [email protected]:113-1.2.3.4:52176.service
             ● [email protected]:113-1.2.3.4:52152.service
             ● [email protected]:113-1.2.3.4:52086.service
             ● [email protected]:113-1.2.3.4:52134.service
             ● [email protected]:113-1.2.3.4:52068.service
             ● [email protected]:113-1.2.3.4:52214.service
             ● [email protected]:113-1.2.3.4:52066.service
             ● [email protected]:113-1.2.3.4:52234.service
             ● [email protected]:113-1.2.3.4:52124.service
             ● [email protected]:113-1.2.3.4:52174.service
             ● [email protected]:113-1.2.3.4:52132.service
             ● [email protected]:113-1.2.3.4:52188.service
             ● [email protected]:113-1.2.3.4:52196.service
             ● [email protected]:113-1.2.3.4:52148.service
             ● [email protected]:113-1.2.3.4:52184.service
             ● [email protected]:113-1.2.3.4:52180.service
             ● [email protected]:113-1.2.3.4:52212.service
             ● [email protected]:113-1.2.3.4:52208.service
             ● [email protected]:113-1.2.3.4:52230.service
             ● [email protected]:113-1.2.3.4:52170.service
             ● [email protected]:113-1.2.3.4:52074.service
             ● [email protected]:113-1.2.3.4:52138.service
             ● [email protected]:113-1.2.3.4:52076.service
             ● [email protected]:113-1.2.3.4:52158.service
             ● [email protected]:113-1.2.3.4:52216.service
             ● [email protected]:113-1.2.3.4:52206.service
     Listen: [::]:113 (Stream)
   Accepted: 92; Connected: 62;

Aug 19 15:09:15 atom systemd[1]: Listening on RFC 1413 compliant ident socket.
Aug 22 10:16:00 atom systemd[1]: oidentd.socket: Failed to queue
service startup job (Maybe the service file is missing or not a
template unit?): Transport endpoint is not connected
Aug 22 10:16:00 atom systemd[1]: oidentd.socket: Failed with result 'resources'.

Regards,

Justin.