BBB Version 2.7.7
although rare, I've had a couple of instances where the recording notification fails to deliver, example:
I, [2024-05-22T11:02:18.768356 #2951603] INFO -- : Recording Ready Notify for [5c310f45e5f5a8d4fe28647ec5efea4174ac046c-1716387391456] starts
I, [2024-05-22T11:02:18.768476 #2951603] INFO -- : Task: Getting meeting metadata
I, [2024-05-22T11:02:18.784869 #2951603] INFO -- : Making callback for recording ready notification
I, [2024-05-22T11:02:18.785227 #2951603] INFO -- : Task: Getting external meeting id
I, [2024-05-22T11:02:18.785273 #2951603] INFO -- : Task: Getting meeting metadata
I, [2024-05-22T11:02:18.799526 #2951603] INFO -- : Sending request to [REDACTED]
I, [2024-05-22T11:02:19.273013 #2951603] INFO -- : Rescued
I, [2024-05-22T11:02:19.273145 #2951603] INFO -- : end of file reached
I, [2024-05-22T11:02:19.273225 #2951603] INFO -- : Recording Ready notify ends
instead of "Recording notifier successful: ..." I get a "Rescued" followed by an "end of file reached". the receiving server does not log anything in the apache log for the callback.
the recording ready url is local on the same network as the BBB server and was working fine just before and just after this incident.
this callback function is very important for recording management and fixing it after the fact is a chore.
Does anyone know what the messages mean?
Is it possible to set an automatic retry when something like this happens?
any details appreciated.
Thanks,
Les