Replies: 2 comments
-
Can you check if it can be an issue like this? |
Beta Was this translation helpful? Give feedback.
0 replies
-
Thanks, but I don't longer use KMS 6. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I'm having an older KMS 6.16.0 installation running since months now. No issues so far. Yesterday evening it all stoped out of the sudden with a "request timeout" seen from my Node JS server in the attempt to communicate with KMS (as so many successful times before).
I examined the KMS log and my Node server log and found nothing really disturbing. It seems, that the KMS really stopped responding on the socket interface.
I can recognise starting sessions in KMS log like so (TURN/STUN IP obfuscated):
In my Node log, which triggers the attempt, this looks like so (in fact, this one was the last successful):
So I'm making KMS generating an OFFER, which I send back to the desired publisher
At this time not more than 5 users where active in the system and this session was the last one succeeding. No further errors in both logs.
But all subsequent publish attempts end like so for me:
...while the KMS log jabbers happily, not seeing any further request:
In the end somebody killed the server (I suppose restarting the KMS would have been the better option).
Anyway, my log settings for KMS are as follows:
I'm now looking for a better logging setup, which would allow to see the root of the problem. Any suggestions?
Beta Was this translation helpful? Give feedback.
All reactions