Open josephmiller2000 opened 3 years ago
github-actions[bot]
commented
3 years ago Hello @josephmiller2000! :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.
j1elo
commented
3 years ago do you have any info in the errors.log file?
josephmiller2000
commented
3 years ago Ok here is the error.log file details
2021-01-04T08:04:55+00:00 -- New execution
0:00:00.026027216 9077 0x561dc5f9d530 WARN ladspa gstladspa.c:455:plugin_init: no LADSPA plugins found, check LADSPA_PATH
0:00:00.088263179 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0x120000: 'AVR (Audio Visual Research)' is not mapped
0:00:00.088277899 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0x180000: 'CAF (Apple Core Audio File)' is not mapped
0:00:00.088282197 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0x100000: 'HTK (HMM Tool Kit)' is not mapped
0:00:00.088285782 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0xc0000: 'MAT4 (GNU Octave 2.0 / Matlab 4.2)' is not mapped
0:00:00.088288959 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0xd0000: 'MAT5 (GNU Octave 2.1 / Matlab 5.0)' is not mapped
0:00:00.088291937 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0x210000: 'MPC (Akai MPC 2k)' is not mapped
0:00:00.088295381 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0xe0000: 'PVF (Portable Voice Format)' is not mapped
0:00:00.088298954 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0x160000: 'SD2 (Sound Designer II)' is not mapped
0:00:00.088303212 9077 0x561dc5f9d530 WARN default gstsf.c:98:gst_sf_create_audio_template_caps: format 0x190000: 'WVE (Psion Series 3)' is not mapped
2021-01-04T15:07:45+00:00 -- New execution
2021-01-04T18:43:57+00:00 -- New execution
2021-01-04T18:56:54+00:00 -- New execution
2021-01-05T10:21:18+00:00 -- New execution
2021-01-05T11:18:43+00:00 -- New execution
2021-01-05T11:29:26+00:00 -- New execution
2021-01-05T11:32:11+00:00 -- New execution
2021-01-07T07:59:20+00:00 -- New execution
[OpenH264] this = 0x0x7f3b46394680, Error: the pic_width_in_mbs exceeds the level limits!
2021-01-22T07:14:44+00:00 -- New executionOk kurento crashed again, without any errors. But this time, i could not start kurento again, until i reboot the server.
Here is the screenshot image, before i stopped kurento, you can check how long it was running without crash.
Here is the error i keep getting if i try to start the kurento, after todays crash.
About the error.log file, here is the details.
2021-01-05T11:29:26+00:00 -- New execution
2021-01-05T11:32:11+00:00 -- New execution
2021-01-07T07:59:20+00:00 -- New execution
[OpenH264] this = 0x0x7f3b46394680, Error: the pic_width_in_mbs exceeds the level limits!
2021-01-22T07:14:44+00:00 -- New execution
2021-02-09T04:34:07+00:00 -- New executionBefore trying to start KMS (sudo service kurento-media-server start), check that there are no other KMS instances running by some chance (Check your installation):
$ ps -fC kurento-media-server
UID PID PPID C STIME TTY TIME CMDNow if it's possible, clean the logs directory (delete or move them somewhere else just during these tests):
sudo service kurento-media-server stop
sudo mv /var/log/kurento-media-server /var/log/kurento-media-server_BACKUP
sudo service kurento-media-server startAnd paste here the tail of all log files (this is why I suggest moving out the old logs, so they don't show up here):
tail -n 20 /var/log/kurento-media-server/*.logAbout the error.log file, here is the details.
[OpenH264] this = 0x0x7f3b46394680, Error: the pic_width_in_mbs exceeds the level limits!
This message Error: the pic_width_in_mbs exceeds the level limits comes from the H.264 parser (OpenH264). It means that the encoder is sending a wrong H.264 stream.
Please provide more info about the H.264 video: where does it come from? Is it a web browser, an IP camera? Are you sending it to Kurento with a WebRtcEndpoint? RtpEndpoint? PlayerEndpoint?
If it is an IP camera or other kind of device under your control: how is the video configuration?
Access your device settings and make sure that H.264 is encoded with Constrained baseline profile and Level 3.1
josephmiller2000
commented
3 years ago About the error.log file, here is the details.
[OpenH264] this = 0x0x7f3b46394680, Error: the pic_width_in_mbs exceeds the level limits!This message _Error: the pic_width_inmbs exceeds the level limits comes from the H.264 parser (OpenH264). It means that the encoder is sending a wrong H.264 stream.
Please provide more info about the H.264 video: where does it come from? Is it a web browser, an IP camera? Are you sending it to Kurento with a WebRtcEndpoint? RtpEndpoint? PlayerEndpoint?
If it is an IP camera or other kind of device under your control: how is the video configuration?
Access your device settings and make sure that H.264 is encoded with Constrained baseline profile and Level 3.1
Thanks for the comment, but this is different issue i guess.
[OpenH264] this = 0x0x7f3b46394680, Error: the pic_width_in_mbs exceeds the level limits!
This error happened on, 2021-01-07T07:59:20+00:00
But the next two execution logs are clean without any errors.
Im using kurento for a public chat room, where users can broadcast their webcam video and rest of the people can see them.
It is a browser based application, and H.264 is sending through browser.
Prerequisites
These are MANDATORY, otherwise the issue will be automatically closed.
Issue description
last day on a odd time, kurento stopped working, cam broadcasting is not working, until i manually restarted kurento.
Context
How to reproduce?
Here is the screenshot of htop, which shows two process running with same kurento name, with different PID.
Not sure how to reproduce the error, because the logs are kind of weird, because two log files contains nothing in it, just empty.
Attaching another file log information in here
2021-01-14T232215.00073.pid13956.log
Expected & current behavior
Kurento should be running without crashing, not sure what went wrong.
Info about your environment
Ubuntu 18.04.5 LTS (GNU/Linux 4.15.0-128-generic x86_64) Intel(R) Xeon(R) E-2136 CPU @ 3.30GHz cores = 6 enabledcores = 6 threads = 12 System Memory = 32GiB
About Kurento Media Server
Kurento Media Server version: 6.15.0 Found modules: 'core' version 6.15.0 'elements' version 6.15.0 'filters' version 6.15.0
About your Application Server
Run these commands