Tracking ffmpeg instance by its logs

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

Tracking ffmpeg instance by its logs

FFmpeg-users mailing list
Hi there.

I'm having some trouble with a ffmpeg working with an external stream as input.
This are the logs I see:

```
(...)
Jun  8 10:57:05 server-name journal: [h264 @ 0x55a098c0c700] non-existing PPS 0 referenced
Jun  8 10:57:05 server-name journal: [h264 @ 0x55a098c0c700] decode_slice_header error
Jun  8 10:57:05 server-name journal: [h264 @ 0x55a098c0c700] non-existing PPS 0 referenced
(...)
Jun  8 10:57:05 server-name journal: [NULL @ 0x55a0984b5fc0] non-existing PPS 0 referenced
(...)
Jun  8 10:57:05 server-name journal: [h264 @ 0x55a098dbc740] non-existing PPS 0 referenced
Jun  8 10:57:05 server-name journal: [h264 @ 0x55a098dbc740] decode_slice_header error
Jun  8 10:57:05 server-name journal: [h264 @ 0x55a098dbc740] non-existing PPS 0 referenced
(...)
Jun  8 11:04:26 server-name journal: [h264 @ 0x55ae88d1c3c0] non-existing PPS 0 referenced
Jun  8 11:04:26 server-name journal: [h264 @ 0x55ae88d1c3c0] decode_slice_header error
Jun  8 11:04:26 server-name journal: [h264 @ 0x55ae88d1c3c0] no frame!
(...)
```

Thing is, I have several instances of ffmpeg running in the same server (configured as a system service, and thus the systemd journal logs), and can't find which one is triggering the errors. All I have is that memory address form the encoder/decoder.
So, I come to this mailing list to ask this question: does anybody knows a simple way to match that memory address with the current system proccess using it?

Thanks in advance.
_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".
Reply | Threaded
Open this post in threaded view
|

Re: Tracking ffmpeg instance by its logs

Nicolas George
Daniel Cantarin via ffmpeg-user (12020-06-10):
> So, I come to this mailing list to ask this question: does anybody
> knows a simple way to match that memory address with the current
> system proccess using it?

No, the address will not help you to that. Most likely it is randomized,
and even if it was not it is not reproducible.

Arrange for your logs to arrive to different places or with proper
tagging. If your several instances of ffmpeg are started by systemd, it
is probably already the case, and you just need to read journalctl's doc
to get the information you need.

Regards,

--
  Nicolas George

_______________________________________________
ffmpeg-user mailing list
[hidden email]
https://ffmpeg.org/mailman/listinfo/ffmpeg-user

To unsubscribe, visit link above, or email
[hidden email] with subject "unsubscribe".

signature.asc (849 bytes) Download Attachment