[systemd-devel] socket failed to queue socket startup job: Transport endpoint is not connected
fullung at gmail.com
Wed Jan 18 02:06:51 PST 2012
We've had a machine up for about 9 days with lots of connections to a
We noticed today that the socket had stopped listening. syslog said:
systemd: foo.socket failed to queue socket startup job: Transport
endpoint is not connected
systemd: Unit foo.socket entered failed state.
systemctl status said:
Loaded: loaded (/etc/systemd/system/foo.socket; enabled)
Active: failed since Wed, 18 Jan 2012 04:53:40 +0000; 5h 1min ago
Accepted: 902; Connected: 0
What does this error mean? Should the socket be failing?
We are running systemd v37 on Fedora 16.
More information about the systemd-devel