Recording failed; no corresponding WAV file was generated.
I maintainer di solito rispondono entro 1 giorno
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 15/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Ferma
- Stack tecnologico
- c
- Ambito
- audio-video-rtc
Direzione di ricerca
The trace comes from rtpengine-recording: the inotify watcher (inotify.c) and metafile handling (metafile.c). In the failing call the 'Opened output media file' line never appears before the streams hit EOF, so the WAV sink is never created even though the meta file is processed and freed. Start by reading the daemon's main loop and the callback that opens output files, asking how a close/delete event can race past it. Done means the output file opens reliably for every meta file, with a documented repro of the intermittent case.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
rtpengine version the issue has been seen with
Version: 13.5.1.2-1~bpo12+1
Used distribution and its version
Debian 12
Linux kernel version used
6.1.0-40-amd64
CPU architecture issue was seen on (see uname -m)
x86_64
Expected behaviour you didn't see
No response
Unexpected behaviour you saw
This is my configuration file:
output-format = wav
spool-dir = /var/spool/rtpengine
output-dir = /home/call/recording
One out of every 100 calls will fail to generate a recording file.I've enabled debug logging, and this is the error message related to the recording failure:
2025-11-13T08:58:17.496537+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496543+08:00 rtpengine-recording[1261597]: INFO: [core] New call for recording: 'a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta'
2025-11-13T08:58:17.496580+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496589+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496621+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496660+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496673+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496678+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496686+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496723+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496768+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496789+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496827+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.496930+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497013+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497228+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497498+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:17.497583+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:23] inotify close_write(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:51.847198+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-0-media-1-component-2-RTCP-id-3] [core] EOF on stream tag-0-media-1-component-2-RTCP-id-3
2025-11-13T08:58:51.847215+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-0-media-1-component-1-RTP-id-2] [core] EOF on stream tag-0-media-1-component-1-RTP-id-2
2025-11-13T08:58:51.847232+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-1-media-1-component-2-RTCP-id-1] [core] EOF on stream tag-1-media-1-component-2-RTCP-id-1
2025-11-13T08:58:51.847268+08:00 rtpengine-recording[1261597]: INFO: [C a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta] [S tag-1-media-1-component-1-RTP-id-0] [core] EOF on stream tag-1-media-1-component-1-RTP-id-0
2025-11-13T08:58:51.847324+08:00 rtpengine-recording[1261597]: DEBUG: [core] [inotify.c:29] inotify delete(a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta)
2025-11-13T08:58:51.847328+08:00 rtpengine-recording[1261597]: INFO: [core] Recording for call 'a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta' finished
2025-11-13T08:58:54.144143+08:00 rtpengine-recording[1261597]: DEBUG: [core] [metafile.c:29] freeing metafile info for a2088227d63616c6c29db3db2%40192.168.0.1-f17a462ee0ba0317.meta
Compared to normal logs：
Nov 13 11:27:51 ecs-crs-100 rtpengine-recording[2575716]: INFO: [core] New call for recording: '91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta'
Nov 13 11:27:51 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-0-media-1-component-1-RTP-id-2] [0x8119a0cc] [core] Opened output media file '/home/call/recording/a14ff43d-ae78-406f-93ec-59509b72149b.wav' for writing
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-0-media-1-component-2-RTCP-id-3] [core] EOF on stream tag-0-media-1-component-2-RTCP-id-3
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-0-media-1-component-1-RTP-id-2] [core] EOF on stream tag-0-media-1-component-1-RTP-id-2
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-1-media-1-component-2-RTCP-id-1] [core] EOF on stream tag-1-media-1-component-2-RTCP-id-1
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [C 91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta] [S tag-1-media-1-component-1-RTP-id-0] [core] EOF on stream tag-1-media-1-component-1-RTP-id-0
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [core] Recording for call '91d3e2e6-3ae3-123f-8c82-fa163eb0c030-7688a37b28f33fad.meta' finished
Nov 13 11:28:03 ecs-crs-100 rtpengine-recording[2575716]: INFO: [core] Closing output media file '/home/call/recording/a14ff43d-ae78-406f-93ec-59509b72149b.wav'
Steps to reproduce the problem
No response
Additional program output to the terminal or logs illustrating the issue
Anything else?
No response
- Lingua principale
- Perl
- Stelle
- 992
- Fork
- 459
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di sipwise/rtpengine
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 75/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 5/5 Più di una settimana Idoneità per principianti 12/100
sipwise/rtpengine#2210 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
-
HTTP/WS worker threads spin forever in `__websocket_write_done()` (`sched_yield` loop) — 100% CPU with `--listen-http`Forse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 15/100
sipwise/rtpengine#2197 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Kernel NULL pointer dereference in target_put() during target deletionForse già presa Una pull request collegata a questa issue è aperta o già unita. Apertabug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 38/100
sipwise/rtpengine#2190 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
Calls using a third logical interface are silently never written to Redis (breaks keyspace-notification HA)Forse già presa Una pull request collegata a questa issue è aperta o già unita. Aperta
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
sipwise/rtpengine#2181 · 4 commenti ·
I maintainer di solito rispondono entro 1 giorno
Tutte le issue di sipwise/rtpengine
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 80/100
jimsalterjrs/sanoid#1116 · 1 reazione ·
-
Add .gitattributes so share/skel keeps LF on a Windows git checkoutForse già presa @sadhana-s-codez l’ha presa 2 giorni fa. Aperta
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 85/100
PerlDancer/Dancer2#1854 · 1 commento ·
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
major/MySQLTuner-perl#1007 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100