Hi
I'm glad to hear that you did it. You can fix the pid file problem as
follows. Problem is that user kurento can't write PID file to
/var/run/openmeetings.pid
Well, create dir
sudo mkdir /var/run/openmeetings
Grant ownership of the directory just created
sudo chown kurento /var/run/openmeetings
Change file /etc/systemd/system/openmeetings.service line
Environment=CATALINA_PID=/var/run/openmeetings.pid
to
Environment=CATALINA_PID=/var/run/openmeetings/openmeetings.pid
Reload
sudo systemctl daemon-reload
And finally, restart openmeetings
sudo systemctl restart openmeetings
Good luck!
El 5/5/20 a las 19:32, Peter-Otto Weber escribió:
Together with Maxim and Juan (they had the brain and i had the
fingers) i was able to configure my OpenMeetings m3 to work on Port 443.
The base system follows the guides
* Installation OpenMeetings 5.0.0-M3 on Ubuntu 18.04 LTS.pdf
* Installation SSL certificates and Coturn for OpenMeetings 5.0.0-M3.pdf
The main problems were with firewall and Coturn using „kurento“ as
user and not „nobody“.
After all it was not so many things to do:
Backup /opt(open503/openmeetings.service
Backup /opt/open503/config/server.xml
Change openmeetings.service
[Service]
Type=forking
ADD THIS LINE à AmbientCapabilities=CAP_NET_BIND_SERVICE
Change all folders /openmeetings/ to /open503/
Change User=nobody to User = kurento
Copy this file to /etc/systemd/system/openmeetings.service
Change all port 5443 to 443 in server.xml (two places)
Check firewall and open port 443 if not open as in my case 😉 )
Reboot
sudo /etc/init.d/mysql start MariaDB
data server
sudo /etc/init.d/kurento-media-server start Kurento media server
sudo systemctl start openmeetings openmeetings
There’s still a problem with creating pid file – i will check out later…
Best wishes
POW
