It's true that in /etc/default/kurento-media-server the user was set
to "kurento" - changing it to "nobody" (which I HAD done before but
probably forgot to do with update from 6.10 to 6.13 did not help:
● kurento-media-server.service - LSB: Kurento Media Server daemon
Loaded: loaded (/etc/init.d/kurento-media-server; generated)
Active: failed (Result: exit-code) since Fri 2020-03-27 17:00:24
CET; 6s ago
Docs: man:systemd-sysv-generator(8)
Process: 6939 ExecStart=/etc/init.d/kurento-media-server start
(code=exited, status=2)
Mar 27 17:00:24 server1.searchy.biz systemd[1]: Starting LSB:
Kurento Media Server daemon...
Mar 27 17:00:24 server1.searchy.biz kurento-media-server[6939]:
Start Kurento Media Server:Configure Kernel resource limits for
Kurento Media Serv
Mar 27 17:00:24 server1.searchy.biz kurento-media-server[6939]:
/etc/init.d/kurento-media-server: 122:
/etc/init.d/kurento-media-server: Pipe call
Mar 27 17:00:24 server1.searchy.biz systemd[1]:
kurento-media-server.service: Control process exited, code=exited,
status=2/INVALIDARGUMENT
Mar 27 17:00:24 server1.searchy.biz systemd[1]:
kurento-media-server.service: Failed with result 'exit-code'.
Mar 27 17:00:24 server1.searchy.biz systemd[1]: Failed to start LSB:
Kurento Media Server daemon.
You probably don't have time to help with this now, Maxim, as work on
getting 5.0.0 to release is more important I understand. If someone
else has this up and running - especially M4 (which I plan to move to
tomorrow) on buster, please let me know if you can help debug om logs.
regards,
ed
Quoting Maxim Solodovnik <solomax...@gmail.com>:
/etc/default/kurento-media-server
START_DAEMON="true"
DAEMON_USER="nobody" #### SAME USER AS STARTED OM
On Fri, 27 Mar 2020 at 22:15, <i...@bureau-de-poste.net> wrote:
systemctl status kurento-media-server.status returns:
● kurento-media-server.service - LSB: Kurento Media Server daemon
Loaded: loaded (/etc/init.d/kurento-media-server; generated)
Active: failed (Result: exit-code) since Sat 2020-03-21 22:12:26
CET; 5 days ago
Docs: man:systemd-sysv-generator(8)
Process: 7791 ExecStart=/etc/init.d/kurento-media-server start
(code=exited, status=2)
Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Starting LSB:
Kurento Media Server daemon...
Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]:
Start Kurento Media Server:Configure Kernel resource limits for
Kurento Media Server.
Mar 21 22:12:26 server1.searchy.biz[1] kurento-media-server[7791]:
/etc/init.d/kurento-media-server: 122:
/etc/init.d/kurento-media-server: Pipe call failed
Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]:
kurento-media-server.service: Control process exited, code=exited,
status=2/INVALIDARGUMENT
Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]:
kurento-media-server.service: Failed with result 'exit-code'.
Mar 21 22:12:26 server1.searchy.biz[1] systemd[1]: Failed to start
LSB: Kurento Media Server daemon.
root@server1 ~ # aptitude show kurento-media-server
Package: kurento-media-server
Version: 6.13.0-0kurento1.18.04
New: yes
State: installed
Automatically installed: no
Priority: optional
Section: video
Maintainer: Kurento <kure...@googlegroups.com>
Architecture: amd64
Uncompressed Size: 2,043 k
Depends: kms-core (>= 6.7.0), kms-jsonrpc, kmsjsoncpp,
libboost-filesystem1.65.1, libboost-log1.65.1,
libboost-program-options1.65.1,
libboost-system1.65.1, libboost-thread1.65.1, libc6 (>=
2.24), libgcc1 (>= 1:3.0), libglib2.0-0 (>= 2.41.1), libglibmm-2.4-1v5
(>= 2.54.0),
libgstreamer1.5-0 (>= 1.8.1), libsigc++-2.0-0v5 (>= 2.8.0),
libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 6), binutils, gstreamer1.5-libav,
gstreamer1.5-plugins-bad, gstreamer1.5-plugins-base,
gstreamer1.5-plugins-good, gstreamer1.5-plugins-ugly, kms-elements (>=
6.7.0), kms-filters
(>= 6.7.0), libgstreamer-plugins-base1.5-0
Suggests: kurento-dbg
Breaks: kurento-media-server-6.0
Replaces: kurento-media-server-6.0
Description: Kurento Media Server
KMS is a WebRTC-compatible server that processes audio and video
streams, doing composable pipeline-based processing of media.
Homepage: https://www.kurento.org
this is the output of /opt/log/openmeetings.log:
INFO 03-14 15:54:38.301 o.s.w.c.ContextLoader:271 [main] - Root
WebApplicationContext: initialization started
INFO 03-14 15:54:38.953 o.s.o.j.LocalEntityManagerFactoryBean:416
[main] - Initialized JPA EntityManagerFactory for persistence unit
'openmeetings'
INFO 03-14 15:54:39.170 o.s.s.c.ThreadPoolTaskExecutor:171 [main]
- Initializing ExecutorService 'taskExecutor'
INFO 03-14 15:54:40.406 o.k.j.c.JsonRpcClientNettyWebSocket:191
[rbeatExec-e1-t0] - [KurentoClient] Connecting native client
INFO 03-14 15:54:40.409 o.k.j.c.JsonRpcClientNettyWebSocket:220
[rbeatExec-e1-t0] - [KurentoClient] Creating new NioEventLoopGroup
INFO 03-14 15:54:40.526 o.k.j.c.JsonRpcClientNettyWebSocket:234
[ntLoopGroup-2-1] - [KurentoClient] Initiating new Netty channel.
Will create new handler too!
WARN 03-14 15:54:40.579 o.k.j.c.JsonRpcClientNettyWebSocket:308
[rbeatExec-e1-t0] - [KurentoClient] Trying to close a
JsonRpcClientNettyWebSocket with channel == null
WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:270
[rbeatExec-e1-t0] - [KurentoClient] Error sending heartbeat to
server. Exception: [KurentoClient] Exception connecting to WebSocket
server ws://127.0.0.1:8888/kurento
INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:191
[main] - [KurentoClient] Connecting native client
WARN 03-14 15:54:40.581 o.k.j.c.JsonRpcClient:287
[rbeatExec-e1-t0] - [KurentoClient] Stopping heartbeat and closing
client: failure during heartbeat mechanism
INFO 03-14 15:54:40.581 o.k.j.c.JsonRpcClientNettyWebSocket:220
[main] - [KurentoClient] Creating new NioEventLoopGroup
INFO 03-14 15:54:40.582 o.k.j.c.JsonRpcClientNettyWebSocket:234
[ntLoopGroup-3-1] - [KurentoClient] Initiating new Netty channel.
Will create new handler too!
WARN 03-14 15:54:40.584 o.k.j.c.JsonRpcClientNettyWebSocket:308
[main] - [KurentoClient] Trying to close a
JsonRpcClientNettyWebSocket with channel == null
WARN 03-14 15:54:40.585 o.a.o.c.r.KurentoHandler:124 [main] - Fail
to create Kurento client, will re-try in 10000 ms
INFO 03-14 15:54:40.707 o.q.i.StdSchedulerFactory:1220 [main] -
Using default implementation for ThreadExecutor
INFO 03-14 15:54:40.716 o.q.c.SchedulerSignalerImpl:61 [main] -
Initialized Scheduler Signaller of type: class
org.quartz.core.SchedulerSignalerImpl
INFO 03-14 15:54:40.716 o.q.c.QuartzScheduler:229 [main] - Quartz
Scheduler v.2.3.2 created.
INFO 03-14 15:54:40.717 o.q.s.RAMJobStore:155 [main] - RAMJobStore
initialized.
INFO 03-14 15:54:40.717 o.q.c.QuartzScheduler:294 [main] -
Scheduler meta-data: Quartz Scheduler (v2.3.2)
'org.springframework.scheduling.quartz.SchedulerFactoryBean#0' with
instanceId 'NON_CLUSTERED'
Scheduler class: 'org.quartz.core.QuartzScheduler' - running locally.
NOT STARTED.
Currently in standby mode.
Number of jobs executed: 0
Using thread pool 'org.quartz.simpl.SimpleThreadPool' - with
10 threads.
Using job-store 'org.quartz.simpl.RAMJobStore' - which does not
support persistence. and is not clustered.
port 8888 is not firewalles - neither is 5443.
Any idea what to do to start KMS on buster - tomcat3 is running fine -
this is 5.0.0 M3 adn I want to install M4 very soon.
Thanks for any ideas or help
Ed
--
WBR
Maxim aka solomax
Links:
------
[1] http://server1.searchy.biz
