Jicofo and JVB container keep crashing on launch

Niponika · April 21, 2020, 10:52am

Hello,
I have been trying to do a manual setup of the Jitsi stack for the previous days, but can’t seem to get Jicofo nor JVB to launch properly.

I’m pulling all the latest images from docker hub. Web and prosody start without any issue, but Jicofo and JVB get in a crash loop.

From what I see in the log it looks like they both manage to see each other through prosody after launch, but for some reason that I can’t identify S6’s shutdown scripts kick in.

Here are the logs I get for the containers.

Jicofo - Logs: https://pastebin.com/Aa3Kb45P
JVB - Logs: https://pastebin.com/Yzk7E8i2
Prosody - Logs: pastebin [dot] com [slash] BHeq1bdQ

I’m feeling like I’m probably missing something obvious here, but would gladly get some help.
Best regards

Niponika · April 21, 2020, 1:38pm

Figured out it was due to my health-checks on k8s.

I was using port 80 for http calls to the REST API of both of them. JVB users port 8080 for its private API by default.

I still cannot get it to work for Jicofo however. Is there some additional settings to pass to the program in order to have enable the API?

github.com

jitsi/jicofo/blob/master/doc/health-checks.md

The REST API allows querying Jicofo whether it deems itself in a healthy state (i.e. the application is operational and the functionality it provides should perform as expected) at the time of the query or not. Videorbidge will run an internal test in response to the request to determine its current health status.

<table>
  <tr>
    <th>HTTP Method</th>
    <th>Resource</th>
    <th>Response</th>
  </tr>
  <tr>
    <td><code>GET</code></td>
    <td><code>/about/health</code></td>
    <td>
      <ul>
        <li><code>200 OK</code> if Jicofo ran its internal test to determine its current health status and the test completed successfully. The response is with <code>Content-Type: application/json</code> but no JSON value is provided i.e. <code>Content-Length: 0</code>.</li>
        <li><code>503 Service Unavailable</code> if Jicofo is currently unable to run its health check. The reasons for the failure include (but are not limited to):
          <ul>
            <li>The REST API server has been brought up but the core conference-related functionality of Jicofo is still initializing. Videbridge could be considered healthy if the client chooses to interpret the HTTP status in such a fashion since the application may pass though the described transitional state under normal operation.</li>
            <li>The core conference-related functionality of Jicofo has commenced a shutdown procedure but the REST API server has not shut down yet. Videbridge could be considered healthy if the client chooses to interpret the HTTP status in such a fashion since the application may pass though the described transitional state under normal operation.</li>
            <li>The core conference-related functionality of Jicofo is in an unhealthy state and the REST API server is operating as expected.</li>
          </ul>

This file has been truncated. show original

Niponika · April 21, 2020, 1:55pm

Found my answer to this one too.

For reference, the default API ports are the following:
Jicofo: 8888
Videobridge: 8080

Videobridge also requires the environment variable JVB_ENABLE_APIS to be set to ‘rest’