You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@openmeetings.apache.org by kaffeesurrogat <ka...@posteo.de> on 2020/04/26 08:49:07 UTC
Re: Lot of strange problems: OM 5.0.4, THERE YOU GO ;-) and another
question ...
Hey Maxim,
On 26/04/2020 06:42, Maxim Solodovnik wrote:
> I would recommend:
>
> 1) drop tomcat3 script from the system
> 1.1) remove it from autostart
> 2) run `sudo killall java`
> 3) use this script
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/main/assembly/scripts/openmeetings.service
> (bundled with OM)
> as described here
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/main/assembly/scripts/openmeetings.service#L15
> correct paths lines 28-30, 34, 35
> modify line 31 set `-Xmx=8G` (this should be enough)
i did find this option on duckduckgo, but they talked about differnt
java progs, never was able to figure out where to set it for
openmeetings ;-)
my steps:
1) I added openmeetings.service to /etc/systemd/system
2) chmod 664 /etc/systemd/system/openmeetings.service
3) systemctl daemon-reload
4) systemctl start openmeetings.service ........ fails with
--------------------------------------------------------------------------------------------------------------------------
Job for openmeetings.service failed because the control process exited
with error code.
See "systemctl status openmeetings.service" and "journalctl -xe" for
details.
--------------------------------------------------------------------------------------------------------------------------
Running
---------------------------------
journalctl -xe
---------------------------------
gives ...
------------------------------------------------------------------------------------
touch: '/opt/open504/logs/catalina.out' kann nicht berührt werden:
Keine Berechtigung
------------------------------------------------------------------------------------
(no rights to do so ...., permissions ....)
During installation following the guides from om wikis, I did a
-----------------------------------
chown -R nobody /opt/open504
-----------------------------------
most of the files belong now to nobody:root. Files in /opt/open504/logs/
all belong to root:root ...
mmmmm,
In
---------------------------------------
/etc/systemd/system/openmeetings.service
---------------------------------------
user is set to nobody and group to nogroup. Sounds good to me.
Next i changed the ownership in the logfiles to nobody:root . That was
definitely some kind of progress
That means
--------------------------------------
systemctl start openmeetings.service
------------------------------------
returns nothing anymore .
But
---------------------------------
sudo systemctl status openmeetings.service
---------------------------------
shows
--------------------------------
openmeetings.service - Apache OpenMeetings server
Loaded: loaded (/etc/systemd/system/openmeetings.service; disabled;
vendor preset: enabled)
Active: activating (auto-restart) (Result: exit-code) since Sun
2020-04-26 10:25:31 CEST; 5s ago
Process: 30922 ExecStart=/opt/open504/bin/startup.sh (code=exited,
status=0/SUCCESS)
Main PID: 30929 (code=exited, status=1/FAILURE)
----------------------------------
in the log (/opt/open504/logs/catalina.out)
i can find the following ...
-----------------------------------
NOTE: Picked up JDK_JAVA_OPTIONS:
--add-opens=java.base/java.lang=ALL-UNNAMED
--add-opens=java.base/java.io=ALL-UNNAMED
--add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
Invalid maximum heap size: -Xmx=8G
Error: Could not create the Java Virtual Machine.
Error: A fatal exception has occurred. Program will exit.
----------------------------------
mmmmmm, changed the line 31 in
-----------------------------------
/etc/systemd/system/openmeetings.service
-----------------------------------
to
----------------------------------
Environment='CATALINA_OPTS=-Xms1G -Xmx8G -server -XX:+UseParallelGC'
----------------------------------
doing
--------------------------------
systemctl daemon-reload
systemctl start openmeetings
systemctl status openmeetings
● openmeetings.service - Apache OpenMeetings server
Loaded: loaded (/etc/systemd/system/openmeetings.service; disabled;
vendor preset: enabled)
Active: active (running) since Sun 2020-04-26 10:39:40 CEST; 14s ago
Process: 32481 ExecStop=/opt/open504/bin/shutdown.sh (code=exited,
status=1/FAILURE)
Process: 32488 ExecStart=/opt/open504/bin/startup.sh (code=exited,
status=0/SUCCESS)
Main PID: 32495 (java)
Tasks: 80 (limit: 165)
CGroup: /system.slice/openmeetings.service
└─32495 /usr/lib/jvm/java-11-openjdk-amd64/bin/java
-Djava.util.logging.config.file=/opt/open504/conf/logging.properties
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
-Djava.awt.hea
Apr 26 10:39:40 : Starting Apache OpenMeetings server...
Apr 26 10:39:40 : Started Apache OpenMeetings server.
----------------------------------------------------------
There you go ...... ;-)
Sorry for writing down all those things mentioning every litte step, but
I guess it will help me to remember all the stuff, if not i hope to find
my mail again ...
Many many thanks to the openmeetings team, you are responsible for the
huge smile in my face ...
Now it is testing time again .... ;-) Check if all the weird problems,
disconnections, reconnections, more than one copy of the same user in
one room disappeared ....
I will keep you informed.
Oh btw. one more question:
Should I change the ownership of all files in /opt/open504 to
nobody:nogroup as the service is running under this presidency ?
Have fun,
kaffeesurrogat
> I guess that's it
>
> On Sun, 26 Apr 2020 at 03:33, kaffeesurrogat <ka...@posteo.de> wrote:
>> in my cataline.out file i've found a few lines stating
>>
>> "java.lang.OutOfMemoryError: unable to create native thread: possibly
>> out of memory or process/resource limits reached"
>>
>> "59 c.h.s.i.e.ExecutionService:69 [heduled.thread-] -
>> [81.169.223.177]:5701 [dev] [4.0] Failed to execute
>> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@71bc43b8[Completed
>> exceptionally: java.lang.OutOfMemoryError: unable to create native
>> thread: possibly out of memory or process/resource limits reached]"
>>
>>
>> i've although found that there is a limit(?) of pthreads for the kms ....
>>
>> sudo cat
>> /sys/fs/cgroup/pids/system.slice/kurento-media-server.service/pids.max
>>
>> returns 165
>>
>>
>> could this be related ...
>>
>> The catalina output file is attached to my previous email .....
>>
>> now i guess it is time to go to bed ;-)
>>
>> Have a good rest,
>>
>> kaffeesurrogat
>>
>>
>> On 25/04/2020 21:00, Alvaro wrote:
>>> ...be attention if "tomcat3" script appoint to
>>> open503 or open504:
>>>
>>> CATALINA_HOME=/opt/open503 or 504
>>>
>>>
>>>
>>> .................
>>>
>>>
>>> El sáb, 25-04-2020 a las 20:25 +0200, kaffeesurrogat escribió:
>>>> Dear Everybody,
>>>>
>>>> my Openmeetings instance is up an running on a Virtual Machine from
>>>> strato. It has about 32GB of ram, 8 vCores and last but not least 800GB
>>>> of ssd driven space.
>>>>
>>>> But I do have a lot of problems, they are popping up quite fast so its
>>>> hard to keep track.
>>>>
>>>>
>>>> 1) My tomcat3 crashed once. Restarting was refused because jdk didn't
>>>> have enough memory. I've killed a couple of java processes, to be able
>>>> to restart kms and tomcat3. I thought about adding a swapfile, but i'm
>>>> not allowed to do a swapon, not enough rights i guess. I do have root
>>>> access though. Strange.
>>>>
>>>>
>>>> 2) kms likes to crash quite often too.
>>>>
>>>>
>>>> 3) Right now I have "two" users logged in. Since the connection is quite
>>>> unstable, i've reloaded the page several times (address ending is
>>>> htpps://..../#rom/13). That got the user back in.
>>>> The last one who was kicked out by a failing connection was
>>>> unfortunately the admin user. Admin can't get into the room anymore
>>>> cause the group is full. I have two users left in the group and the user
>>>> panel shows six users, several of them with the same user name. Thats
>>>> weird ;-)
>>>>
>>>> 4) I don't know what is going on ;-)
>>>>
>>>> 5) I do not have coturn, turn, stun .... i've got myself a domain and an
>>>> ip ...
>>>>
>>>> I did install OM 5.0.3 on my laptop for testing purposes and i was
>>>> thrilled, cause openmeetings is doing exactly what I want to do my
>>>> teaching online. I did not have any problems like this ...
>>>>
>>>> Unfortunately I can't give u the error messages. They popped up, and
>>>> vanished shortly after.
>>>>
>>>>
>>>> Mmmmm, well have a nice evening,
>>>>
>>>>
>>>> kaffeessurrogat
>>>>
>>>>
>>>>
>
Re: Lot of strange problems: OM 5.0.4, THERE YOU GO ;-) and another
question ...
Posted by Maxim Solodovnik <so...@gmail.com>.
I would recommend to change owner of OM to nobody
As well as change the user who will start KMS to nobody as well
On Sun, Apr 26, 2020, 15:49 kaffeesurrogat <ka...@posteo.de> wrote:
> Hey Maxim,
>
>
> On 26/04/2020 06:42, Maxim Solodovnik wrote:
> > I would recommend:
> >
> > 1) drop tomcat3 script from the system
> > 1.1) remove it from autostart
> > 2) run `sudo killall java`
> > 3) use this script
> >
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/main/assembly/scripts/openmeetings.service
> > (bundled with OM)
> > as described here
> >
> https://github.com/apache/openmeetings/blob/master/openmeetings-server/src/main/assembly/scripts/openmeetings.service#L15
> > correct paths lines 28-30, 34, 35
> > modify line 31 set `-Xmx=8G` (this should be enough)
>
> i did find this option on duckduckgo, but they talked about differnt
> java progs, never was able to figure out where to set it for
> openmeetings ;-)
>
> my steps:
> 1) I added openmeetings.service to /etc/systemd/system
> 2) chmod 664 /etc/systemd/system/openmeetings.service
> 3) systemctl daemon-reload
> 4) systemctl start openmeetings.service ........ fails with
>
>
> --------------------------------------------------------------------------------------------------------------------------
> Job for openmeetings.service failed because the control process exited
> with error code.
> See "systemctl status openmeetings.service" and "journalctl -xe" for
> details.
>
> --------------------------------------------------------------------------------------------------------------------------
>
> Running
>
> ---------------------------------
> journalctl -xe
> ---------------------------------
>
> gives ...
>
>
> ------------------------------------------------------------------------------------
> touch: '/opt/open504/logs/catalina.out' kann nicht berührt werden:
> Keine Berechtigung
>
> ------------------------------------------------------------------------------------
> (no rights to do so ...., permissions ....)
>
> During installation following the guides from om wikis, I did a
>
> -----------------------------------
> chown -R nobody /opt/open504
> -----------------------------------
>
> most of the files belong now to nobody:root. Files in /opt/open504/logs/
> all belong to root:root ...
> mmmmm,
>
> In
> ---------------------------------------
> /etc/systemd/system/openmeetings.service
> ---------------------------------------
>
> user is set to nobody and group to nogroup. Sounds good to me.
>
> Next i changed the ownership in the logfiles to nobody:root . That was
> definitely some kind of progress
>
> That means
>
> --------------------------------------
> systemctl start openmeetings.service
> ------------------------------------
>
> returns nothing anymore .
>
> But
>
> ---------------------------------
> sudo systemctl status openmeetings.service
> ---------------------------------
>
> shows
>
> --------------------------------
> openmeetings.service - Apache OpenMeetings server
> Loaded: loaded (/etc/systemd/system/openmeetings.service; disabled;
> vendor preset: enabled)
> Active: activating (auto-restart) (Result: exit-code) since Sun
> 2020-04-26 10:25:31 CEST; 5s ago
> Process: 30922 ExecStart=/opt/open504/bin/startup.sh (code=exited,
> status=0/SUCCESS)
> Main PID: 30929 (code=exited, status=1/FAILURE)
> ----------------------------------
>
> in the log (/opt/open504/logs/catalina.out)
> i can find the following ...
>
> -----------------------------------
> NOTE: Picked up JDK_JAVA_OPTIONS:
> --add-opens=java.base/java.lang=ALL-UNNAMED
> --add-opens=java.base/java.io=ALL-UNNAMED
> --add-opens=java.rmi/sun.rmi.transport=ALL-UNNAMED
> Invalid maximum heap size: -Xmx=8G
> Error: Could not create the Java Virtual Machine.
> Error: A fatal exception has occurred. Program will exit.
> ----------------------------------
>
> mmmmmm, changed the line 31 in
>
> -----------------------------------
> /etc/systemd/system/openmeetings.service
> -----------------------------------
>
> to
>
> ----------------------------------
> Environment='CATALINA_OPTS=-Xms1G -Xmx8G -server -XX:+UseParallelGC'
> ----------------------------------
>
> doing
>
> --------------------------------
> systemctl daemon-reload
> systemctl start openmeetings
>
>
> systemctl status openmeetings
>
> ● openmeetings.service - Apache OpenMeetings server
> Loaded: loaded (/etc/systemd/system/openmeetings.service; disabled;
> vendor preset: enabled)
> Active: active (running) since Sun 2020-04-26 10:39:40 CEST; 14s ago
> Process: 32481 ExecStop=/opt/open504/bin/shutdown.sh (code=exited,
> status=1/FAILURE)
> Process: 32488 ExecStart=/opt/open504/bin/startup.sh (code=exited,
> status=0/SUCCESS)
> Main PID: 32495 (java)
> Tasks: 80 (limit: 165)
> CGroup: /system.slice/openmeetings.service
> └─32495 /usr/lib/jvm/java-11-openjdk-amd64/bin/java
> -Djava.util.logging.config.file=/opt/open504/conf/logging.properties
> -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager
> -Djava.awt.hea
>
> Apr 26 10:39:40 : Starting Apache OpenMeetings server...
> Apr 26 10:39:40 : Started Apache OpenMeetings server.
> ----------------------------------------------------------
>
> There you go ...... ;-)
>
>
> Sorry for writing down all those things mentioning every litte step, but
> I guess it will help me to remember all the stuff, if not i hope to find
> my mail again ...
>
> Many many thanks to the openmeetings team, you are responsible for the
> huge smile in my face ...
>
> Now it is testing time again .... ;-) Check if all the weird problems,
> disconnections, reconnections, more than one copy of the same user in
> one room disappeared ....
> I will keep you informed.
>
> Oh btw. one more question:
>
> Should I change the ownership of all files in /opt/open504 to
> nobody:nogroup as the service is running under this presidency ?
>
>
> Have fun,
>
> kaffeesurrogat
>
>
> > I guess that's it
> >
> > On Sun, 26 Apr 2020 at 03:33, kaffeesurrogat <ka...@posteo.de>
> wrote:
> >> in my cataline.out file i've found a few lines stating
> >>
> >> "java.lang.OutOfMemoryError: unable to create native thread: possibly
> >> out of memory or process/resource limits reached"
> >>
> >> "59 c.h.s.i.e.ExecutionService:69 [heduled.thread-] -
> >> [81.169.223.177]:5701 [dev] [4.0] Failed to execute
> >>
> java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@71bc43b8
> [Completed
> >> exceptionally: java.lang.OutOfMemoryError: unable to create native
> >> thread: possibly out of memory or process/resource limits reached]"
> >>
> >>
> >> i've although found that there is a limit(?) of pthreads for the kms
> ....
> >>
> >> sudo cat
> >> /sys/fs/cgroup/pids/system.slice/kurento-media-server.service/pids.max
> >>
> >> returns 165
> >>
> >>
> >> could this be related ...
> >>
> >> The catalina output file is attached to my previous email .....
> >>
> >> now i guess it is time to go to bed ;-)
> >>
> >> Have a good rest,
> >>
> >> kaffeesurrogat
> >>
> >>
> >> On 25/04/2020 21:00, Alvaro wrote:
> >>> ...be attention if "tomcat3" script appoint to
> >>> open503 or open504:
> >>>
> >>> CATALINA_HOME=/opt/open503 or 504
> >>>
> >>>
> >>>
> >>> .................
> >>>
> >>>
> >>> El sáb, 25-04-2020 a las 20:25 +0200, kaffeesurrogat escribió:
> >>>> Dear Everybody,
> >>>>
> >>>> my Openmeetings instance is up an running on a Virtual Machine from
> >>>> strato. It has about 32GB of ram, 8 vCores and last but not least
> 800GB
> >>>> of ssd driven space.
> >>>>
> >>>> But I do have a lot of problems, they are popping up quite fast so its
> >>>> hard to keep track.
> >>>>
> >>>>
> >>>> 1) My tomcat3 crashed once. Restarting was refused because jdk didn't
> >>>> have enough memory. I've killed a couple of java processes, to be able
> >>>> to restart kms and tomcat3. I thought about adding a swapfile, but i'm
> >>>> not allowed to do a swapon, not enough rights i guess. I do have root
> >>>> access though. Strange.
> >>>>
> >>>>
> >>>> 2) kms likes to crash quite often too.
> >>>>
> >>>>
> >>>> 3) Right now I have "two" users logged in. Since the connection is
> quite
> >>>> unstable, i've reloaded the page several times (address ending is
> >>>> htpps://..../#rom/13). That got the user back in.
> >>>> The last one who was kicked out by a failing connection was
> >>>> unfortunately the admin user. Admin can't get into the room anymore
> >>>> cause the group is full. I have two users left in the group and the
> user
> >>>> panel shows six users, several of them with the same user name. Thats
> >>>> weird ;-)
> >>>>
> >>>> 4) I don't know what is going on ;-)
> >>>>
> >>>> 5) I do not have coturn, turn, stun .... i've got myself a domain and
> an
> >>>> ip ...
> >>>>
> >>>> I did install OM 5.0.3 on my laptop for testing purposes and i was
> >>>> thrilled, cause openmeetings is doing exactly what I want to do my
> >>>> teaching online. I did not have any problems like this ...
> >>>>
> >>>> Unfortunately I can't give u the error messages. They popped up, and
> >>>> vanished shortly after.
> >>>>
> >>>>
> >>>> Mmmmm, well have a nice evening,
> >>>>
> >>>>
> >>>> kaffeessurrogat
> >>>>
> >>>>
> >>>>
> >
>
>
>