The first to log segments from journal/messages should not be related to your issue. qdrouterd is part of qpid and that is not used in communication with the smartproxy. The errors there should not have any impact on your environment, since qpid should only be used for communication with (the long deprecated) katello-agent.
The last segment is the one with actually important errors, though. Sadly, it does not say what’s actually going wrong. Could you raise the loglevel for foreman-proxy in /etc/foreman-proxy/settings.yml to DEBUG and restart the smart proxy? Maybe we can detect at what step it actually screws up. I assume the smart-proxy is having problems talking to some backend process that throws the actual
Also, the output of
curl -k --cacert /etc/foreman-proxy/foreman_ssl_ca.pem --cert /etc/foreman-proxy/foreman_ssl_cert.pem --key /etc/foreman-proxy/foreman_ssl_key.pem "https://localhost:9090/v2/features" | python -m json.tool might prove helpful, though this could possibly cause your “daily lockup” again.
Please be aware that both things I asked above will most likely include sensitive data like FQDNs and IPs, so you might want to anonymize those before putting them up here.