Dmsg issue when a dmsg-server is closed incorrectly

[ersonp]

Describe the bug
When a dmsg-server is closed with Ctrl+Z few of the modules in the visor basically locked along with the hypervisor UI which becomes unresponsive.

Environment information:

• OS: Linux
• Platform: Linux 5.13.0-44-generic x86_64

Steps to Reproduce
Steps to reproduce the behavior:

1. Start integration env
2. Let everything run for a few seconds and close the dmsg-server with Ctrl+Z
3. Check logs of visor B and UI
4. See error
5. Stop the dmsg-server by getting it's PID from htop and killing it with sudo kill -9 <pid>
6. Check logs of visor B and UI
7. Re-start the dmsg-server with source integration/dmsg-server-env.sh; ./bin/dmsg-server ./integration/dmsg-server.json --syslog localhost:514 --tag MSG_SRV
8. Check the visor B
9. It won't reconnect to the server