2024-06-04T02:40:07.127Z mediasoup:ERROR:Channel [pid:54 ChannelMessageRegistrator::RegisterHandler() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists
2024-06-04T02:40:07.170Z mediasoup:ERROR:Channel [pid:54 Worker::HandleRequest() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists [method:transport.produceData]
2024-06-04T02:40:07.178Z mediasoup:WARN:Channel request failed [method:transport.produceData, id:53]: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists [method:transport.produceData]
2024-06-04T02:40:51.254Z mediasoup:ERROR:Channel [pid:54 ChannelMessageRegistrator::RegisterHandler() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists
2024-06-04T02:40:51.254Z mediasoup:ERROR:Channel [pid:54 Worker::HandleRequest() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists [method:transport.produceData]
2024-06-04T02:40:51.255Z mediasoup:WARN:Channel request failed [method:transport.produceData, id:71]: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists [method:transport.produceData]
2024-06-04T02:41:20.346Z mediasoup:ERROR:Channel [pid:54 ChannelMessageRegistrator::RegisterHandler() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists
2024-06-04T02:41:20.348Z mediasoup:ERROR:Channel [pid:54 Worker::HandleRequest() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists [method:transport.produceData]
2024-06-04T02:41:20.349Z mediasoup:WARN:Channel request failed [method:transport.produceData, id:88]: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists [method:transport.produceData]
2024-06-04T02:41:48.808Z mediasoup:ERROR:Channel [pid:54 ChannelMessageRegistrator::RegisterHandler() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists
2024-06-04T02:41:48.809Z mediasoup:ERROR:Channel [pid:54 Worker::HandleRequest() | throwing MediaSoupError: Channel request handler with ID c93bdf42-c7e6-4f63-b288-f8d9546165d2 already exists [method:transport.produceData]
The IDs in the messages come and go, but each one appears tens of thousands of times.
Possibly unrelated, but this morning I got a flurry of MongoDB connection errors (MongoPoolClearedError, PoolClearedOnNetworkError, MongoServerSelectionError), and when I tried loading the site a little later it failed the first try and then was quite slow to come up, though it since recovered AFAICT aside from the log spam.
I pushed a new docker image to trigger an update from HEAD (with whatever has landed in Git in the last couple of weeks) + restart and that seems to have stopped the log spam for the moment.
My JR instance has been up for ~3 weeks.
Starting on 6/4 (two days after https://github.com/deathandmayhem/jolly-roger/issues/2167 happened, with nothing else in between in the server logs), the logs started showing a repeated sequence like this:
The IDs in the messages come and go, but each one appears tens of thousands of times.
Possibly unrelated, but this morning I got a flurry of MongoDB connection errors (MongoPoolClearedError, PoolClearedOnNetworkError, MongoServerSelectionError), and when I tried loading the site a little later it failed the first try and then was quite slow to come up, though it since recovered AFAICT aside from the log spam.
I pushed a new docker image to trigger an update from HEAD (with whatever has landed in Git in the last couple of weeks) + restart and that seems to have stopped the log spam for the moment.