RabbitMQ sends "event_type":"kick_out"

Hi all: We experienced some dead air today. One hour-long track was scheduled at Noon, but the program host reported dead air at 12:10pm. The pypo.log shows RabbitMQ sends “event_type”:“kick_out” at 12:12pm. I previewed the track (an .mp3 file), it sounds fine and appears complete.

“Kick out” sounds ominous. What does “kick_out” mean?

Below is a pypo.log excerpt.

I’m not too worried (yet), this is the first I’ve heard of this in over a year of running this instance of LibreTime.


2021-05-02 12:08:48,672 [pypoliqqueue] [INFO ] waiting 3071.327601s until next scheduled item
2021-05-02 12:12:57,044 [pypomessagehandler] [INFO ] Received event from RabbitMQ: {“schedule”:{“media”:{“2021-05-02-17-00-00”:{“start”:“2021-05-02-17-00-00”,“end”:“2021-05-02-17-00-00”,“event_type”:“kick_out”,“type”:"
2021-05-02 12:12:57,045 [pypomessagehandler] [INFO ] Handling command: update_schedule
2021-05-02 12:12:57,045 [pypomessagehandler] [INFO ] Updating schdule…
2021-05-02 12:12:57,072 [pypofetch] [INFO ] Received event from Pypo Message Handler: {“schedule”:{“media”:{“2021-05-02-17-00-00”:{“start”:“2021-05-02-17-00-00”,“end”:“2021-05-02-17-00-00”,“event_type”:“kick_out”,"type
2021-05-02 12:12:57,073 [pypofetch] [INFO ] Handling command: update_schedule
2021-05-02 12:12:57,077 [pypofetch] [INFO ] New timeout: 480
2021-05-02 12:12:57,077 [pypofetch] [INFO ] Loop #9246