So I keep seeing this issue with some of my live DJs connecting and disconnecting repeatedly for no discernable reason.

To the listener this usually results in the AutoDJ coming on and the below filling up the log, but sometimes the only way to get everything normal again is to restart the shoutcast instance from inside Centova), the following is just a tiny snippet of what I see in my log (this will go on for ages until either the dj gives up and another one plays or they restart BUTT or as stated, the shoutcast instance is restarted from inside Centova)

2018-09-27 13:25:08   I   msg:[DJMGR] No DJ currently active. Run permission granted for `djname'
2018-09-27 13:25:08   I   msg:[DJPROTOCOLSHOUTCAST] Connected
2018-09-27 13:25:08   I   msg:[BROADCASTSTALLMANAGER] Timed content set to TRUE
2018-09-27 13:25:09   I   msg:[DJMGR] DJ `djname' is done.
2018-09-27 13:25:09   I   msg:[BROADCASTSTALLMANAGER] Timed content set to FALSE
2018-09-27 13:25:09   I   msg:[DJMGR] No DJ currently active. Run permission granted for `djname'
2018-09-27 13:25:09   I   msg:[DJPROTOCOLSHOUTCAST] Connected
2018-09-27 13:25:09   I   msg:[BROADCASTSTALLMANAGER] Timed content set to TRUE
2018-09-27 13:25:10   I   msg:[DJMGR] DJ `djname' is done.
2018-09-27 13:25:10   I   msg:[BROADCASTSTALLMANAGER] Timed content set to FALSE
2018-09-27 13:25:10   I   msg:[DJMGR] No DJ currently active. Run permission granted for `djname'
2018-09-27 13:25:10   I   msg:[DJPROTOCOLSHOUTCAST] Connected
2018-09-27 13:25:10   I   msg:[BROADCASTSTALLMANAGER] Timed content set to TRUE
2018-09-27 13:25:11   I   msg:[DJMGR] DJ `djname' is done.
2018-09-27 13:25:11   I   msg:[BROADCASTSTALLMANAGER] Timed content set to FALSE
2018-09-27 13:25:12   I   msg:[DJMGR] No DJ currently active. Run permission granted for `djname'
2018-09-27 13:25:12   I   msg:[DJPROTOCOLSHOUTCAST] Connected
2018-09-27 13:25:12   I   msg:[BROADCASTSTALLMANAGER] Timed content set to TRUE
2018-09-27 13:25:12   I   msg:[DJMGR] DJ `djname' is done.

But ultimately I want to know what exactly is happening here so I can hopefully put a stop to it.

Any ideas on this would be great.

No one ever heard of this?
It's happened twice in the past 4 hours