[jitsi-users] How to configure InfluxDB for Jitsi Meet running in different docker container?


#1

Hello,

We are running jitsi-meet, videobridge, jicofo and a ejabberd instance in
seperate docker containers. Videobridge and jicofo we are manually building
and executing it as root in every container. We tried to configure influx
db following the instructions in
https://github.com/jitsi/jitsi-meet/blob/master/doc/influxdb.md . We
confirmed our db setup is working by adding data to it using the api.

We put the properties inside
/root/.sip-communicator/sip-communicator.properties on both jicofo
container and videobridge container. In the videobridge log these
properties are being shown but not in that of jicofo. We set logStats to
true in jitsi meet config.

But still nothing seems to be logging inside the db.

Can someone point us to what we are missing here to do?

Any help is hugely appreciated.

Thank you,
Adhil Azeez NV


#2

Hi,

Hello,

We are running jitsi-meet, videobridge, jicofo and a ejabberd instance
in seperate docker containers. Videobridge and jicofo we are manually
building and executing it as root in every container. We tried to
configure influx db following the instructions in
https://github.com/jitsi/jitsi-meet/blob/master/doc/influxdb.md . We
confirmed our db setup is working by adding data to it using the api.

We put the properties inside
/root/.sip-communicator/sip-communicator.properties on both jicofo
container and videobridge container. In the videobridge log these
properties are being shown but not in that of jicofo.

I just noticed that in my testing env jicofo doesn't log these properties. I don't know why that is, but it doesn't prevent logging from working.

Both videobridge and jicofo log a message like this, though:
"Initialized InfluxDBLoggingService for https://..."

Check their logs for any error messages that mention influxdb. One possible problem is a failure to verify the SSL certificate.

We set logStats to
true in jitsi meet config.

You can postpone this step until you have the system running -- you should see logs every time you create a conference regardless of this setting.

Regards,
Boris

ยทยทยท

On 05/04/15 15:01, Adhil Azeez NV wrote: