I'm using 6.13.0 :)
@Xavier,
most probably one need to check system logs to find KMS started twice
to kill process use `kill -9 ` (PID is a number, can be found using
`ps`)
This error:
* gzip: stdout: No space left on device*
is very much self-descriptive: you don't have free space in
Hi Marcus,
For people like me: which commands did you use to state that it started
twice / that a dead process blocked port ? How did you kill this
process?
By the way : if I had to restart the server, it was due to the fact that
I had following error (I can't remember what was
I have 6.10. seems like it has been started twice or a dead process blocked
port .
I killed the process blocking the port and fior now it seems to work
Am 5. April 2020 15:36:15 schrieb Maxim Solodovnik :
what version of KMS are you using?
On Sun, 5 Apr 2020 at 20:30, Xavier M wrote:
what version of KMS are you using?
On Sun, 5 Apr 2020 at 20:30, Xavier M wrote:
> For information : the same happened to me with OM-5.0.0-M1: no connexion
> was established with the Media Server anymore after a restart of my server
> due to another reason.
>
> This was the reason why I
For information : the same happened to me with OM-5.0.0-M1: no connexion
was established with the Media Server anymore after a restart of my
server due to another reason.
This was the reason why I installed M3 (and installed KMS again), such
as the very beginning of my last topic:
I would say it is weird
All "occupied" resources are at minimum level after restart
Can you do multiple restarts and check if this issue is reproducible?
BTW what version of KMS are you using?
On Sun, 5 Apr 2020 at 01:20, Marcus Schulz wrote:
> HI,
>
> for the kurento user it looks like this:
these limits are for currently logged in user
what user is used for KMS
according to the script, it seems there is a bug :(
On Sat, 4 Apr 2020 at 15:56, Marcus Schulz wrote:
> Hi,
>
> I run OpenMeetings M3 on a Ubuntu 18 Server wor two weeks without problems.
> Yesterday I did a reboot and
