Dear Mukul, please reply to list, i made the error myself a couple of times ...
Have you checked on the contents of the script ? it looks like this .... ############################################ [Unit] Description=Apache OpenMeetings server After=network.target [Service] Type=forking Environment=JAVA_HOME=/usr/lib/jvm/java-11-openjdk-amd64 Environment=CATALINA_PID=/var/run/openmeetings.pid WorkingDirectory=/opt/openmeetings Environment=CATALINA_HOME=/opt/openmeetings Environment=CATALINA_BASE=/opt/openmeetings Environment='CATALINA_OPTS=-Xms1G -Xmx4G -server -XX:+UseParallelGC' Environment='JAVA_OPTS=-Djava.awt.headless=true -Djava.security.egd=file:/dev/./urandom' ExecStart=/opt/openmeetings/bin/startup.sh ExecStop=/opt/openmeetings/bin/shutdown.sh User=nobody Group=nogroup UMask=0007 RestartSec=10 Restart=always [Install] WantedBy=multi-user.target ############################################ You need to change WorkingDirectory, CATALINE_HOME, ..... to match your installation path. You can get and share more information if you have a look at the log files, for example sudo less /var/log/syslog You might have a different logger so but it will help to find the cause for your problems The ouput would be similar to this, if the path is wrong ############################################# Starting Apache OpenMeetings server... Sep 11 20:15:13 systemd[14869]: openmeetings.service: Changing to the requested working directory failed: No such file or directory Sep 11 20:15:13 systemd[14869]: openmeetings.service: Failed at step CHDIR spawning /opt/open50134/bin/startup.sh: No such file or directory ep 11 20:15:13 ystemd[14869]: openmeetings.service: Failed at step CHDIR spawning /opt/open50134/bin/startup.sh: No such file or directory Sep 11 20:15:13 systemd[1]: openmeetings.service: Control process exited, code=exited status=200 Sep 11 20:15:13 systemd[1]: openmeetings.service: Failed with result 'exit-code'. Sep 11 20:15:13 systemd[1]: Failed to start Apache OpenMeetings server. ############################################# On 11/09/2020 14:20, Mukul Shukla wrote: > Got this error > > sudo systemctl restart openmeetings > Job for openmeetings.service failed because the control process exited > with error code. > See "systemctl status openmeetings.service" and "journalctl -xe" for > details. > > > On Fri, Sep 11, 2020 at 5:30 PM kaffeesurrogat > <kaffeesurro...@posteo.de <mailto:kaffeesurro...@posteo.de>> wrote: > > sorry for sending it as a personal message. hit the wrong button .... > > On 11/09/2020 13:54, Mukul Shukla wrote: > > I am using Ubuntu Server 20.04 > > > > On Fri, Sep 11, 2020 at 5:22 PM kaffeesurrogat > > <kaffeesurro...@posteo.de <mailto:kaffeesurro...@posteo.de> > <mailto:kaffeesurro...@posteo.de > <mailto:kaffeesurro...@posteo.de>>> wrote: > > > > Hey Mukul, > > > > on Ubuntu 18.04 LTS you need to copy openmeetings.service to > > /etc/systemd/system > > > > I guess you need to modify it. Have a look inside. > > > > After modifying you need to issue a > > > > sudo systemctl daemon-reload > > > > if you do use some other linux system google around for hints > > like, how > > to implement your own startup script for systemd .... > > > > Have fun, > > > > Kaffeesurrogat > > > > > > > > On 09/09/2020 18:40, Mukul Shukla wrote: > > > When I try to run sudo systemctl enable openmeetings > > > > > > I get this message: > > > > > > Failed to enable unit: Unit file openmeetings.service does not > > exist. > > > > > > On Wed, Sep 9, 2020 at 9:37 PM Maxim Solodovnik > > <solomax...@gmail.com <mailto:solomax...@gmail.com> > <mailto:solomax...@gmail.com <mailto:solomax...@gmail.com>> > > > <mailto:solomax...@gmail.com <mailto:solomax...@gmail.com> > <mailto:solomax...@gmail.com <mailto:solomax...@gmail.com>>>> wrote: > > > > > > Hello, > > > > > > I personally using this > > > > > > script: > https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/main/assembly/scripts/openmeetings.service > > > At Ubuntu > > > the instructions to start stop are in > > > > > > comments > https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/main/assembly/scripts/openmeetings.service#L15 > > > > > > To enable autostart you need to run `sudo systemctl enable > > > openmeetings` > > > > > > In case regular `init.d` script is used you need to run > > something like > > > `sudo update-rc.d tomcat3 defaults` > > > > > > > > > On Wed, 9 Sep 2020 at 21:12, Mukul Shukla > > <mukulma...@gmail.com <mailto:mukulma...@gmail.com> > <mailto:mukulma...@gmail.com <mailto:mukulma...@gmail.com>> > > > <mailto:mukulma...@gmail.com > <mailto:mukulma...@gmail.com> <mailto:mukulma...@gmail.com > <mailto:mukulma...@gmail.com>>>> > > wrote: > > > > > > Dear All, > > > > > > I have installed the latest instance of > OpenMeetings on > > Ubuntu > > > 20.04 using the Wiki guide. Everytime the machine > comes up I > > > have to run the command /etc/init.d/tomcat3 start. > > > > > > Is there a way to start all the services automatically > > of the > > > OpenMeetings including tomcat on Ubuntu Server 20.04? > > > > > > Thanks > > > > > > Mukul > > > > > > > > > > > > -- > > > Best regards, > > > Maxim > > > > > > > >
