Problem:
System journal is full of errors from qpidd like:
Dec 01 14:36:51 qpidd[1804367]: 2021-12-01 14:36:51 [System] error Error reading socket: Encountered end of file [-5938]
Dec 01 14:36:51 qpidd[1804367]: 2021-12-01 14:36:51 [System] error Error reading socket: Encountered end of file [-5938]
Dec 01 14:37:06 qpidd[1804367]: 2021-12-01 14:37:06 [System] error Error reading socket: Encountered end of file [-5938]
Dec 01 14:37:06 qpidd[1804367]: 2021-12-01 14:37:06 [System] error Error reading socket: Encountered end of file [-5938]
I’ve done some searching, and can only find some very old issues which don’t seem to match the versions I have installed. Expected outcome:
No errors in the journal for normal operation Foreman and Proxy versions:
foreman-3.0.1-1.el8.noarch
foreman-proxy-3.0.1-1.el8.noarch Foreman and Proxy plugin versions:
katello-4.2.1-1.el8.noarch Distribution and version:
Oracle Linux 8.5 Other relevant data:
# systemctl status qpidd
_ qpidd.service - An AMQP message broker daemon.
Loaded: loaded (/usr/lib/systemd/system/qpidd.service; enabled; vendor preset: disabled)
Drop-In: /etc/systemd/system/qpidd.service.d
└─90-limits.conf, wait-for-port.conf
Active: active (running) since Wed 2021-11-24 11:54:29 UTC; 1 weeks 0 days ago
Docs: man:qpidd(1)
http://qpid.apache.org/
Main PID: 1804367 (qpidd)
Tasks: 10 (limit: 216020)
Memory: 15.5M
CGroup: /system.slice/qpidd.service
└─1804367 /usr/sbin/qpidd --config /etc/qpid/qpidd.conf
Clients talk to qdrouterd which routes connections to the qpidd service running on localhost so you can still end up with this situation if clients are rapidly opening and closing connections or have SSL issues. An example of the latter could be if you changed SSL certificates and a client with old ones is still out there trying to connect.
So, only just discovered this today, when I noticed some python cron jobs were failing - running the installer like above ended up removing a lot of core packages!