Post reboot binlog router entered stuck state

After patching the OS and rebooting the host the binlog router entered a failed state. Timeline of errors:

• 22:25 - MaxScale Stopped
• 22:36 - MaxScale Started
• 22:38:30 - Database Switchover triggered
• 22:38:35 - `error: Binlog error: Could not open /var/lib/maxscale/binlogs//mariadb-bin.000015 for reading: 2, No such file or directory`
• 22:38:36 - Database Switchover complete
• 22:38:37 - `error: (BinlogRouter-Proxy); Error received during replication from '10.60.76.234:3306': Could not open /var/lib/maxscale/binlogs//mariadb-bin.000015 for STOP_EVENT addition`

The last message repeats until the binlog files are purged manually.

Also, about two hours before patching, this error was added to the logs:

`error: Binlog error: Sequence error, binlog file /var/lib/maxscale/binlogs//mariadb-bin.000013 has a STOP_EVENT but the Inventory has no successor for it`