Post reboot binlog router entered stuck state

After scheduled OS patching the following happened with a binlog router.

DB server reported
[Warning] Aborted connection 207574 to db: 'unconnected' user: 'maxscale' host: '10.90.194.37' (Got an error writing communication packets)

maxscale was erroring with
2023-06-28 15:13:14 error : (Replication-Proxy); Error received during replication from '10.90.194.79:3306': Could not open /var/lib/maxscale/binlogs//mariadb-bin.000049 for STOP_EVENT addition

Slave status was stuck in slave_io = connecting or timed out.

The binlog on maxscale was not malformed but just the header message.

Resolution was deleting all files in /var/lib/maxscale/binlog then turning service back on. This then properly repulled the bins and resumed operating properly.

The standby maxscale node did not suffer this problem