You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by Viktor Kotliar <Vi...@ihep.ru> on 2021/02/01 05:56:31 UTC

Re: What i must stop ?

netstat -anp|egrep ":(443|80 )"

apache

On 30.01.2021 01:13, Alvaro wrote:
> ...please, Maxim...
> 
> 
> 
> ...............
> 
> 
> El vie, 29-01-2021 a las 21:28 +0100, Soper Certus escribió:
>> greetings to all
>>
>> I have installed the Latest Live ISO , it's work fine, but...
>>
>> What service i must stop to run openmeetings on port 80/443?
>>
>> I have modified server.xml but don't work, problably due a
>> conflict..
>> it's exact?
>>
>>
>> Thanks to all
>>
>> Mark.
>>
>>
>>

Re: errors in upgrade backup and import functionality ?

Posted by Maxim Solodovnik <so...@gmail.com>.
Hello Ed,

if you prefer UI then
1) go to Admin -> Backup
2) click System Backup
wait for the file to be prepared and completely downloaded

(your "notconfirmed+sting_of_numbers.crdownload" is incomplete download)

Also please check your openmeetings.log
there might be some errors during backup (unfortunate)
Or maybe it was "Insufficient free disk space" on server ...


On Tue, 2 Feb 2021 at 02:30, <in...@bureau-de-poste.net> wrote:

> Hi,
>
> I just updated to 5.1.0 from 5.0.3 and when I followed the upgrade guide
> and clicked on the system backup button, nothing seemed to happen and I
> couldn't find a backup that had been generated anywhere on the server!
> But I had a funny named file in my downloads directory a
> "notconfirmed+sting_of_numbers.crdownload" file. Is this the OM backup?
>
> When I tried importing it on a test instance of OM 5.1.0 it threw an
> error stating "configs.xml missing"
>
> What to do?
>
> Ed
>


-- 
Best regards,
Maxim

errors in upgrade backup and import functionality ?

Posted by in...@bureau-de-poste.net.
Hi,

I just updated to 5.1.0 from 5.0.3 and when I followed the upgrade guide 
and clicked on the system backup button, nothing seemed to happen and I 
couldn't find a backup that had been generated anywhere on the server! 
But I had a funny named file in my downloads directory a 
"notconfirmed+sting_of_numbers.crdownload" file. Is this the OM backup?

When I tried importing it on a test instance of OM 5.1.0 it threw an 
error stating "configs.xml missing"

What to do?

Ed

Re: best practice to autostart kms in docker container and tomcat3 for Om 5.1.0 ?

Posted by Alvaro <zu...@gmail.com>.
...Thanks, it is good to know :)

...............



El mar, 02-02-2021 a las 15:01 +0700, Maxim Solodovnik escribió:
> You can use
> `sudo update-rc.d tomcat3 defaults`
> instead of manual link creation :)
> 
> On Tue, 2 Feb 2021 at 02:10, <in...@bureau-de-poste.net> wrote:
> > Hello,
> > 
> > Thanks - is that the best way?   I think a best practice is to add 
> > --restart unless-stopped  to your tutorial docker run command so
> > it 
> > looks like:
> > 
> > docker run -d --restart unless-stopped --name kms -p 8888:8888 --
> > mount 
> > type=bind,source=/opt/open510/webapps/openmeetings/data,target=/opt
> > /open510/webapps/openmeetings/data
> > kurento/kurento-media-server
> > 
> > This is on debian buster. Thus kms won't automatically restart if
> > you 
> > stop it, but it will auto-restart if the server is rebooted or
> > docker 
> > itself is restarted.
> > 
> > I have tested this and it works great!
> > 
> > Ed
> > 
> > Le 2021-02-01 20:34, Alvaro a écrit :
> > > For docker:
> > > 
> > > sudo systemctl enable docker.service
> > > 
> > > ...and for kms you can add it in the script we
> > > made. Then the script will look so:
> > > 
> > > #!/bin/bash
> > > docker start kms
> > > /etc/init.d/tomcat3 start
> > > 
> > > ...am thinking you are in Ubuntu 20.04 ???
> > > 
> > > ..................
> > > 
> > > 
> > > El lun, 01-02-2021 a las 19:07 +0000, Alvaro escribió:
> > >> Hi Ed,
> > >> 
> > >> It i do to run OpenMeetings when turn on the machine
> > >> or reboot it is:
> > >> 
> > >> sudo nano /etc/init.d/boot
> > >> 
> > >> ...paste the 2 following lines:
> > >> 
> > >> #!/bin/bash
> > >> /etc/init.d/tomcat3 start
> > >> 
> > >> ...push Ctrl+X, will ask to save then press Y,
> > >> and Enter to exit nano editor.
> > >> 
> > >> Now give execution permission to this script:
> > >> 
> > >> sudo +x /etc/init.d/boot
> > >> 
> > >> ...and now a symlink:
> > >> 
> > >> ln -s /etc/init.d/boot /etc/rc3.d/S98boot
> > >> 
> > >> 
> > >> Works for me.
> > >> 
> > >> 
> > >> 
> > >> 
> > >> El lun, 01-02-2021 a las 18:18 +0100, info@bureau-de-poste.net
> > >> escribió:
> > >> > Hello,
> > >> >
> > >> > Does anyone have a best practice for autostarting kms inside
> > >> > docker
> > >> > whenever there is a docker or server restart?
> > >> >
> > >> > Could you share it please?
> > >> >
> > >> > Also, for tomcat3 to restart automatically on reboot I had to
> > add
> > >> > the
> > >> > following symlinks:
> > >> >
> > >> > ln -s /etc/init.d/tomcat3 /etc/rc0.d/K01tomcat3
> > >> > ln -s /etc/init.d/tomcat3 /etc/rc1.d/K01tomcat3
> > >> > ln -s /etc/init.d/tomcat3 /etc/rc6.d/K01tomcat3
> > >> > ln -s /etc/init.d/tomcat3 /etc/rc2.d/S01tomcat3
> > >> > ln -s /etc/init.d/tomcat3 /etc/rc3.d/S01tomcat3
> > >> > ln -s /etc/init.d/tomcat3 /etc/rc4.d/S01tomcat3
> > >> > ln -s /etc/init.d/tomcat3 /etc/rc5.d/S01tomcat3
> > >> >
> > >> > Does anyone ahve abetter way to enable tomcat autorestart on
> > >> > server
> > >> > reboot?  If so, could you share it please?
> > >> >
> > >> > Thanks,
> > >> >
> > >> > Ed
> 
> 


Re: best practice to autostart kms in docker container and tomcat3 for Om 5.1.0 ?

Posted by Maxim Solodovnik <so...@gmail.com>.
You can use
`sudo update-rc.d tomcat3 defaults`
instead of manual link creation :)

On Tue, 2 Feb 2021 at 02:10, <in...@bureau-de-poste.net> wrote:

> Hello,
>
> Thanks - is that the best way?   I think a best practice is to add
> --restart unless-stopped  to your tutorial docker run command so it
> looks like:
>
> docker run -d --restart unless-stopped --name kms -p 8888:8888 --mount
> type=bind,source=/opt/open510/webapps/openmeetings/data,target=/opt/open510/webapps/openmeetings/data
>
> kurento/kurento-media-server
>
> This is on debian buster. Thus kms won't automatically restart if you
> stop it, but it will auto-restart if the server is rebooted or docker
> itself is restarted.
>
> I have tested this and it works great!
>
> Ed
>
> Le 2021-02-01 20:34, Alvaro a écrit :
> > For docker:
> >
> > sudo systemctl enable docker.service
> >
> > ...and for kms you can add it in the script we
> > made. Then the script will look so:
> >
> > #!/bin/bash
> > docker start kms
> > /etc/init.d/tomcat3 start
> >
> > ...am thinking you are in Ubuntu 20.04 ???
> >
> > ..................
> >
> >
> > El lun, 01-02-2021 a las 19:07 +0000, Alvaro escribió:
> >> Hi Ed,
> >>
> >> It i do to run OpenMeetings when turn on the machine
> >> or reboot it is:
> >>
> >> sudo nano /etc/init.d/boot
> >>
> >> ...paste the 2 following lines:
> >>
> >> #!/bin/bash
> >> /etc/init.d/tomcat3 start
> >>
> >> ...push Ctrl+X, will ask to save then press Y,
> >> and Enter to exit nano editor.
> >>
> >> Now give execution permission to this script:
> >>
> >> sudo +x /etc/init.d/boot
> >>
> >> ...and now a symlink:
> >>
> >> ln -s /etc/init.d/boot /etc/rc3.d/S98boot
> >>
> >>
> >> Works for me.
> >>
> >>
> >>
> >>
> >> El lun, 01-02-2021 a las 18:18 +0100, info@bureau-de-poste.net
> >> escribió:
> >> > Hello,
> >> >
> >> > Does anyone have a best practice for autostarting kms inside
> >> > docker
> >> > whenever there is a docker or server restart?
> >> >
> >> > Could you share it please?
> >> >
> >> > Also, for tomcat3 to restart automatically on reboot I had to add
> >> > the
> >> > following symlinks:
> >> >
> >> > ln -s /etc/init.d/tomcat3 /etc/rc0.d/K01tomcat3
> >> > ln -s /etc/init.d/tomcat3 /etc/rc1.d/K01tomcat3
> >> > ln -s /etc/init.d/tomcat3 /etc/rc6.d/K01tomcat3
> >> > ln -s /etc/init.d/tomcat3 /etc/rc2.d/S01tomcat3
> >> > ln -s /etc/init.d/tomcat3 /etc/rc3.d/S01tomcat3
> >> > ln -s /etc/init.d/tomcat3 /etc/rc4.d/S01tomcat3
> >> > ln -s /etc/init.d/tomcat3 /etc/rc5.d/S01tomcat3
> >> >
> >> > Does anyone ahve abetter way to enable tomcat autorestart on
> >> > server
> >> > reboot?  If so, could you share it please?
> >> >
> >> > Thanks,
> >> >
> >> > Ed
>


-- 
Best regards,
Maxim

Re: best practice to autostart kms in docker container and tomcat3 for Om 5.1.0 ?

Posted by in...@bureau-de-poste.net.
Hello,

Thanks - is that the best way?   I think a best practice is to add 
--restart unless-stopped  to your tutorial docker run command so it 
looks like:

docker run -d --restart unless-stopped --name kms -p 8888:8888 --mount 
type=bind,source=/opt/open510/webapps/openmeetings/data,target=/opt/open510/webapps/openmeetings/data 
kurento/kurento-media-server

This is on debian buster. Thus kms won't automatically restart if you 
stop it, but it will auto-restart if the server is rebooted or docker 
itself is restarted.

I have tested this and it works great!

Ed

Le 2021-02-01 20:34, Alvaro a écrit :
> For docker:
> 
> sudo systemctl enable docker.service
> 
> ...and for kms you can add it in the script we
> made. Then the script will look so:
> 
> #!/bin/bash
> docker start kms
> /etc/init.d/tomcat3 start
> 
> ...am thinking you are in Ubuntu 20.04 ???
> 
> ..................
> 
> 
> El lun, 01-02-2021 a las 19:07 +0000, Alvaro escribió:
>> Hi Ed,
>> 
>> It i do to run OpenMeetings when turn on the machine
>> or reboot it is:
>> 
>> sudo nano /etc/init.d/boot
>> 
>> ...paste the 2 following lines:
>> 
>> #!/bin/bash
>> /etc/init.d/tomcat3 start
>> 
>> ...push Ctrl+X, will ask to save then press Y,
>> and Enter to exit nano editor.
>> 
>> Now give execution permission to this script:
>> 
>> sudo +x /etc/init.d/boot
>> 
>> ...and now a symlink:
>> 
>> ln -s /etc/init.d/boot /etc/rc3.d/S98boot
>> 
>> 
>> Works for me.
>> 
>> 
>> 
>> 
>> El lun, 01-02-2021 a las 18:18 +0100, info@bureau-de-poste.net
>> escribió:
>> > Hello,
>> >
>> > Does anyone have a best practice for autostarting kms inside
>> > docker
>> > whenever there is a docker or server restart?
>> >
>> > Could you share it please?
>> >
>> > Also, for tomcat3 to restart automatically on reboot I had to add
>> > the
>> > following symlinks:
>> >
>> > ln -s /etc/init.d/tomcat3 /etc/rc0.d/K01tomcat3
>> > ln -s /etc/init.d/tomcat3 /etc/rc1.d/K01tomcat3
>> > ln -s /etc/init.d/tomcat3 /etc/rc6.d/K01tomcat3
>> > ln -s /etc/init.d/tomcat3 /etc/rc2.d/S01tomcat3
>> > ln -s /etc/init.d/tomcat3 /etc/rc3.d/S01tomcat3
>> > ln -s /etc/init.d/tomcat3 /etc/rc4.d/S01tomcat3
>> > ln -s /etc/init.d/tomcat3 /etc/rc5.d/S01tomcat3
>> >
>> > Does anyone ahve abetter way to enable tomcat autorestart on
>> > server
>> > reboot?  If so, could you share it please?
>> >
>> > Thanks,
>> >
>> > Ed

Re: best practice to autostart kms in docker container and tomcat3 for Om 5.1.0 ?

Posted by Alvaro <zu...@gmail.com>.
For docker:

sudo systemctl enable docker.service

...and for kms you can add it in the script we
made. Then the script will look so:

#!/bin/bash
docker start kms
/etc/init.d/tomcat3 start

...am thinking you are in Ubuntu 20.04 ???

..................


El lun, 01-02-2021 a las 19:07 +0000, Alvaro escribió:
> Hi Ed,
> 
> It i do to run OpenMeetings when turn on the machine
> or reboot it is: 
> 
> sudo nano /etc/init.d/boot
> 
> ...paste the 2 following lines:
> 
> #!/bin/bash
> /etc/init.d/tomcat3 start
> 
> ...push Ctrl+X, will ask to save then press Y,
> and Enter to exit nano editor.
> 
> Now give execution permission to this script:
> 
> sudo +x /etc/init.d/boot
> 
> ...and now a symlink:
> 
> ln -s /etc/init.d/boot /etc/rc3.d/S98boot
> 
> 
> Works for me.
> 
> 
> 
> 
> El lun, 01-02-2021 a las 18:18 +0100, info@bureau-de-poste.net
> escribió:
> > Hello,
> > 
> > Does anyone have a best practice for autostarting kms inside
> > docker 
> > whenever there is a docker or server restart?
> > 
> > Could you share it please?
> > 
> > Also, for tomcat3 to restart automatically on reboot I had to add
> > the 
> > following symlinks:
> > 
> > ln -s /etc/init.d/tomcat3 /etc/rc0.d/K01tomcat3
> > ln -s /etc/init.d/tomcat3 /etc/rc1.d/K01tomcat3
> > ln -s /etc/init.d/tomcat3 /etc/rc6.d/K01tomcat3
> > ln -s /etc/init.d/tomcat3 /etc/rc2.d/S01tomcat3
> > ln -s /etc/init.d/tomcat3 /etc/rc3.d/S01tomcat3
> > ln -s /etc/init.d/tomcat3 /etc/rc4.d/S01tomcat3
> > ln -s /etc/init.d/tomcat3 /etc/rc5.d/S01tomcat3
> > 
> > Does anyone ahve abetter way to enable tomcat autorestart on
> > server 
> > reboot?  If so, could you share it please?
> > 
> > Thanks,
> > 
> > Ed


Re: best practice to autostart kms in docker container and tomcat3 for Om 5.1.0 ?

Posted by Alvaro <zu...@gmail.com>.
Hi Ed,

It i do to run OpenMeetings when turn on the machine
or reboot it is: 

sudo nano /etc/init.d/boot

...paste the 2 following lines:

#!/bin/bash
/etc/init.d/tomcat3 start

...push Ctrl+X, will ask to save then press Y,
and Enter to exit nano editor.

Now give execution permission to this script:

sudo +x /etc/init.d/boot

...and now a symlink:

ln -s /etc/init.d/boot /etc/rc3.d/S98boot


Works for me.




El lun, 01-02-2021 a las 18:18 +0100, info@bureau-de-poste.net
escribió:
> Hello,
> 
> Does anyone have a best practice for autostarting kms inside docker 
> whenever there is a docker or server restart?
> 
> Could you share it please?
> 
> Also, for tomcat3 to restart automatically on reboot I had to add
> the 
> following symlinks:
> 
> ln -s /etc/init.d/tomcat3 /etc/rc0.d/K01tomcat3
> ln -s /etc/init.d/tomcat3 /etc/rc1.d/K01tomcat3
> ln -s /etc/init.d/tomcat3 /etc/rc6.d/K01tomcat3
> ln -s /etc/init.d/tomcat3 /etc/rc2.d/S01tomcat3
> ln -s /etc/init.d/tomcat3 /etc/rc3.d/S01tomcat3
> ln -s /etc/init.d/tomcat3 /etc/rc4.d/S01tomcat3
> ln -s /etc/init.d/tomcat3 /etc/rc5.d/S01tomcat3
> 
> Does anyone ahve abetter way to enable tomcat autorestart on server 
> reboot?  If so, could you share it please?
> 
> Thanks,
> 
> Ed


best practice to autostart kms in docker container and tomcat3 for Om 5.1.0 ?

Posted by in...@bureau-de-poste.net.
Hello,

Does anyone have a best practice for autostarting kms inside docker 
whenever there is a docker or server restart?

Could you share it please?

Also, for tomcat3 to restart automatically on reboot I had to add the 
following symlinks:

ln -s /etc/init.d/tomcat3 /etc/rc0.d/K01tomcat3
ln -s /etc/init.d/tomcat3 /etc/rc1.d/K01tomcat3
ln -s /etc/init.d/tomcat3 /etc/rc6.d/K01tomcat3
ln -s /etc/init.d/tomcat3 /etc/rc2.d/S01tomcat3
ln -s /etc/init.d/tomcat3 /etc/rc3.d/S01tomcat3
ln -s /etc/init.d/tomcat3 /etc/rc4.d/S01tomcat3
ln -s /etc/init.d/tomcat3 /etc/rc5.d/S01tomcat3

Does anyone ahve abetter way to enable tomcat autorestart on server 
reboot?  If so, could you share it please?

Thanks,

Ed

Re: What i must stop ?

Posted by Maxim Solodovnik <so...@gmail.com>.
On Mon, 1 Feb 2021 at 12:56, Viktor Kotliar <Vi...@ihep.ru> wrote:

> netstat -anp|egrep ":(443|80 )"
>
> apache
>

+1 :)
first you need to understand who currently uses port 443
Usually it is Apache HTTPD server of Nginx

Alternatively you might have issues starting Tomcat at port 443 due to this
port is privileged


>
> On 30.01.2021 01:13, Alvaro wrote:
> > ...please, Maxim...
> >
> >
> >
> > ...............
> >
> >
> > El vie, 29-01-2021 a las 21:28 +0100, Soper Certus escribió:
> >> greetings to all
> >>
> >> I have installed the Latest Live ISO , it's work fine, but...
> >>
> >> What service i must stop to run openmeetings on port 80/443?
> >>
> >> I have modified server.xml but don't work, problably due a
> >> conflict..
> >> it's exact?
> >>
> >>
> >> Thanks to all
> >>
> >> Mark.
> >>
> >>
> >>
>


-- 
Best regards,
Maxim