Rsyslog reports "Error while binding tcp socket: Address already in use" despite successful log reception.
Issue
-
The
rsyslogservice logs an error during startup or configuration reload, even though TCP log reception is functioning correctly. When checking logs via journalctl -u rsyslog, the following entries are visible:# journalctl -u rsyslog Aug 03 11:45:48 localhost.localdomain rsyslogd[3609]: module 'imtcp' already in this config, cannot be added [v8.2102.0-15.el8 try https://www.rsyslog.com/e/2221 ] Aug 03 11:45:48 localhost.localdomain systemd[1]: Started System Logging Service. Aug 03 11:45:48 localhost.localdomain rsyslogd[3609]: Error while binding tcp socket: Address already in use [v8.2102.0-15.el8] Aug 03 11:45:48 localhost.localdomain rsyslogd[3609]: Error while binding tcp socket: Address already in use [v8.2102.0-15.el8] Aug 03 11:45:48 localhost.localdomain rsyslogd[3609]: Could not create tcp listener, ignoring port 514 bind- address (null). [v8.2102.0-15.e>
Environment
- Red Hat Enterprise Linux (RHEL) 7, 8, 9, 10
- rsyslog
Subscriber exclusive content
A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.