Open j1elo opened 3 years ago
Hello @j1elo! :wave: we're sorry you found a bug... so first of all, thank you very much for reporting it.
To know about progress, check in Triage. All issues are considered Backlog Candidates until work priorities align and the issue is selected for development. It will then become part of our official Backlog.
I also encountered this problem, please j1elo can solve it in the next version, thank you very much
Prerequisites
Issue description
By default, KMS uses the default log handler function from GStreamer: https://gstreamer.freedesktop.org/documentation/gstreamer/gstinfo.html#gst_debug_log_default
this will print a timestamp reflecting the time since the process was started, as explained here: https://gstreamer.freedesktop.org/documentation/tutorials/basic/debugging-tools.html
however, when enabling the output to files (with
--logs-path
), the logging backend is changed to Boost, which prints the current system time.This issue is a improvement request, to always print the current system time, regardless of what is the selected logging mode / backend.
Context
Running KMS either directly by calling
/usr/bin/kurento-media-server
, orexec
as PID 1 in the Kurento Docker container, vs. running KMS as a system service.How to reproduce?
Expected & current behavior
Example of log shown with the Boost logger (
--logs-path
option enabled):Example of log shown with default GStreamer logger (
--logs-path
option not used / disabled):Expected log with
--logs-path
option not used / disabled:(Optional) Possible solution
It is not possible to configure the GStreamer logger, as a quick read of the code shows that the "time since start" is hardcoded:
So the remaining alternative is to redirect all GStreamer logs through Boost, and in there it would be possible to print the correct system time in the final log line.
INFO about Kurento Media Server