Jump to content

148 posts in this topic Last Reply

Recommended Posts

Anyone else seeing the video.meet.jitsi docker using more and more RAM while it is idle?

 

I installed using @SpaceInvaderOne youtube tutorial. Thankyou!

 

Everything appears to be working correctly. I have forwarded the correct ports including UDP 10000. I can access Jitsi from my letsencrypt subdomain and i'm able to host meetings.

 

I restarted Jitsi from Portainer yesterday by this morning video.meet.jitsi was using 3GB of RAM. I restarted it four hours ago and the RAM has already risen to 1.04GB. All of this has happened with no calls or video meets.

 

Log for video.meet.jitsi

Apr 28, 2020 1:50:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:50:50 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Running expire()
Apr 28, 2020 1:50:56 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=da5ba21b2fd0ab2a gid=null logging=false
Apr 28, 2020 1:50:56 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:51:06 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=adf53a44c98d816f gid=null logging=false
Apr 28, 2020 1:51:06 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:51:16 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=eb771cc1e4f11232 gid=null logging=false
Apr 28, 2020 1:51:16 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:51:26 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=be447f7dff3339ad gid=null logging=false
Apr 28, 2020 1:51:26 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:51:36 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=fbcca0c754e72b8f gid=null logging=false
Apr 28, 2020 1:51:36 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:51:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=6be89e8d7d38cc22 gid=null logging=false
Apr 28, 2020 1:51:46 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:51:50 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Running expire()
Apr 28, 2020 1:51:56 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=92e30cc88b43f7b0 gid=null logging=false
Apr 28, 2020 1:51:56 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:52:06 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=b4bdff39698e5c22 gid=null logging=false
Apr 28, 2020 1:52:06 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false
Apr 28, 2020 1:52:16 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=61637a55c912c8ea gid=null logging=false
Apr 28, 2020 1:52:16 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 3ms. Sticky failure: false
Apr 28, 2020 1:52:26 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: create_conf, id=93b77f7dead71923 gid=null logging=false
Apr 28, 2020 1:52:26 PM org.jitsi.utils.logging2.LoggerImpl log
INFO: Performed a successful health check in 2ms. Sticky failure: false

I'm hoping that someone has some ideas for taming the RAM consumption.

Share this post


Link to post
15 hours ago, jude said:

restarted Jitsi from Portainer yesterday by this morning video.meet.jitsi was using 3GB of RAM. I restarted it four hours ago and the RAM has already risen to 1.04GB. All of this has happened with no calls or video meets.

look at your LOG file sizes inside a container. by default, it logs all info messages. you should change log levels for each of container.

Share this post


Link to post
Posted (edited)
3 hours ago, uldise said:

look at your LOG file sizes inside a container. by default, it logs all info messages. you should change log levels for each of container.

OK when I go into Portainer to check the log location and size for docker video.meet.jitsi it gives this location

 

LogPath /var/lib/docker/containers/59c547b2df9694533b3e20444a0152279ad19096a515a3713a04e88c8cb94d3d/59c547b2df9694533b3e20444a0152279ad19096a515a3713a04e88c8cb94d3d-json.log

 

when I go to that location in /var and find 59c547b2df9694533b3e20444a0152279ad19096a515a3713a04e88c8cb94d3d-json.log it shows the log file as 12,106K and rising slowly.

At the same time Unraid's docker container management page shows video.meet.jitsi using 365.3MiB of RAM (and rising consistently)

 

So I'm not sure that the log entries are creating the expanding RAM usage.

 

Jitsi has been running for 25 minutes.

 

I can't see where or how to change the log levels for each container in Unraid dockers or in Portainer. Can you give me the location for that please and thank you

 

Edited by jude

Share this post


Link to post
1 hour ago, jude said:

I can't see where or how to change the log levels for each container in Unraid dockers or in Portainer. Can you give me the location for that please and thank you

i have jitsi running on VM, so i don't know where the config file resides on this container. Usually all config files are on appdata config folder that is mapped to particular container. on my system there is a file logging.properties near videobridge config file, and you set .level variable to WARNING for example to log only warning level and above.

according RAM usage - i don't notice any huge increase over time in my VM.

Share this post


Link to post
43 minutes ago, uldise said:

i have jitsi running on VM, so i don't know where the config file resides on this container. Usually all config files are on appdata config folder that is mapped to particular container. on my system there is a file logging.properties near videobridge config file, and you set .level variable to WARNING for example to log only warning level and above.

according RAM usage - i don't notice any huge increase over time in my VM.

Thanks I'm going to post my question into the Jitsi video support thread for @SpaceInvaderOne 's video. I should have posted there in the first place.

 

Share this post


Link to post

ok thought i had sorted out my issues but something else has come up now.

 

Before i had only tried connecting with 2 people one on local network and one on cellular which seemed to work ok.

 

just tried to setup a meeting for my daughter and her friends and soon as more than 2 connect everyone seems to loose video...

 

any Ideas?

Share this post


Link to post

ok so this seems to be an issue ongoing with setting things up and running a server but I don't know how to fix.

 

Basically if you have more than 2 people and its a mixture of internal to lan and external lan clients the internal and external people cant see eachother.

 

Seem multiple fixes but no idea how to fix it as its way above my head.

 

https://github.com/jitsi/docker-jitsi-meet/issues/403

 

https://github.com/jitsi/docker-jitsi-meet/issues/398

Share this post


Link to post
Posted (edited)

Hi, I am also trying to setup this following spaceinvader´s one video.

Pls, can anyone let me know how to connect using putty to xmpp.meet.jitsi?

 

Edit: Also, what should I write in the .env file in:


# Public URL for the web service
PUBLIC_URL=https://meet.magmajitsi.com

if my subdomain created in duckdns is "magmajitsi"?

imagen.png.3614f956ad0c22ed389f122cd6685836.png

 

So the server name should also be:

server_name meet.magmajitsi.com

 

Edited by luca2

Share this post


Link to post

HI Guys

Mine works just like it says on the tin from the video

But i am seeing some errors in Fix common problems

Has anybody got the same errors and how do you fix them.

Do not say hit the Apply Fix button as it does not work :)

 

Please can you explain how to fix this issue if you have managed to fix it?

Screenshot- 269.png

Share this post


Link to post

I give up.. this is far too complex to get working correctly.

 

easier to just go to the jitsi website and start a room

Share this post


Link to post
12 hours ago, OsoPolar said:

HI Guys

Mine works just like it says on the tin from the video

But i am seeing some errors in Fix common problems

Has anybody got the same errors and how do you fix them.

Do not say hit the Apply Fix button as it does not work :)

 

Please can you explain how to fix this issue if you have managed to fix it?

Screenshot- 269.png

I am also seeing this error.   Everything with the meetings appear to work.  But it is frustrating to have errors...  if you figure out how to fix let me know.  

 

Also I am wondering  how so we update

Share this post


Link to post

The method I have found to update each of the Jitsi docker involves using Portainer.

 

In the Portainer GUI, click Stacks > selected docker-jitsi-meet -> select all and stop all -> Select each Container one at a time (i.e. click on it's name) -> Click Recreate and click "Pull latest image" and then "Recreate" -> once all are updated start all containers -> restart letsencrypt -> done

 

@SpaceInvaderOne Is there a better way?

 

Also, can you help enable Colibri for Jitsi stats? I can't seem to figure it out with this set up.

 

Thank you!

 

 

 

Share this post


Link to post
Posted (edited)
On 5/2/2020 at 5:24 PM, Michael Woodson said:

I have just followed that fully and mine are still showing update available and still got the fix common problem issue with template

 

In the Portainer GUI, click Stacks > selected docker-jitsi-meet -> select all and stop all -> Select each Container one at a time (i.e. click on it's name) -> Click Recreate and click "Pull latest image" and then "Recreate" -> once all are updated start all containers -> restart letsencrypt -> done

 

@SpaceInvaderOne Is there a better way?

 

Also, can you help enable Colibri for Jitsi stats? I can't seem to figure it out with this set up.

 

Thank you!

 

 

 

 
 
 

1216102438_Screenshot-287.thumb.png.331ed3e464c4f8bf51245d8c09fcbbea.png

Screenshot- 269.png

Edited by OsoPolar

Share this post


Link to post

I have the same thing.  The current situation is kind of messy since it was installed song docker compose so Portainer is pretty much like “it isn’t mine” and Unraids docker manager isn’t like “not me!”   
 

I will probably reinstall the stack in Portainer or hopefully someone will roll an Unraid docker for jitsi that works well. It would actually be nice if they were rolled into one just for convenience. 
 

also if you are using Nginx Proxy Manager, you need to expose port 5280 on the prosody container in Portainer. 

Share this post


Link to post

I agree it is very messy and disjointed when you can use the website far easier.

If you link tinkering and having errors all over the place it is ok .

But i have OCD i cannot stand errors and messages and fix buttons that don’t work all over my dashboard.

I think it's going to have to go unless I fix is possible.

Share this post


Link to post
7 hours ago, tknx said:

I have the same thing.  The current situation is kind of messy since it was installed song docker compose so Portainer is pretty much like “it isn’t mine” and Unraids docker manager isn’t like “not me!”   
 

I will probably reinstall the stack in Portainer or hopefully someone will roll an Unraid docker for jitsi that works well. It would actually be nice if they were rolled into one just for convenience. 
 

also if you are using Nginx Proxy Manager, you need to expose port 5280 on the prosody container in Portainer. 

I wonder if you can explain how you might go about installing in portainer:?

 

Also would this get rid of the errors seen above? as I agree with comment by @Osopolar  that my OCD does not like seeing errors or things saying they need updates. 

 

I have tried updating via the portainer route described above. It did update by look of it. But on docker page still see the "update available." warning.. 

 

Share this post


Link to post

I doubt it would fix the Unraid issue, but I have been contemplating switching over to Portainer for all my dockers anyway.

 

For installing it in portainer, I will need to experiment with it but I suspect it should be straightforward. Not sure why spaceinvader didn't just do that if he was going to use the GUI for some parts and not others.

Share this post


Link to post
Posted (edited)

I just went through SpaceInvaderOne's vid for Jitsi (great work mate!) - all seems to be working internally.

 

When I tried to connect via https://meet.domain.com/ I just get the default LetsEncrypt page, "Welcome to our server".

 

I've got a pfSense firewall forwarding 4443 and 10000 to my unraid IP.  I've got other containers working with the LetsEncrypt reverse proxy.  I'm assuming I have something wrong in my jitsimeet.subdomain.conf file but I'm just using the one attached to SpaceInvaderOne's video with no changes.

 

The only hint that I can see is that in Portainer I don't have any published ports against any of the containers (I see them in the video).  I can ping 'meet.jitsi', etc from the LE container so I know it can see/reach the four jitsi containers - I'm just not sure about the ports.

 

image.thumb.png.11e0993839fb51243483695c2c317960.png

 

image.thumb.png.cfb7f6b184690ae14558dcfd1a4ef7ff.png

 

Any suggestions?

Edited by nug

Share this post


Link to post

@nug

I note that he uses a special network for his reverse proxying so if you have it setup the same way - you need to join that network in portainer.

 

Also, oddly enough, if you look at spaceinvader's video and even my own docker page, I don't have any ports mapped for xmpp besides 5280 that I manually added.

Share this post


Link to post
Posted (edited)

@tknx I noticed that but was trying to keep my current setup as the rest of my reverse proxy/containers work ok with what I have now, which is a VLAN created off of BR0:

 

image.png.99520f803d68eef63d4cd386da9b13d0.png

 

I like being able to use a VLAN as I have a bit more control in pfsense for firewalling, etc.

 

I went back to original video that he setup that Proxynet (the first 'setup a reverse proxy' one) and all he does is 'docker create network proxynet' but that must register it differently for Docker to use.

 

I noticed there is a difference between a VLAN created in Unraid and a Docker network:

 

image.png.36fd123426426e997c5c440f5b26f987.png

 

image.png.e9708641f44834042daab9d7e59121b8.png

 

I suspect it's the 'bridge' that allows it to work with Docker better?  I thought I might be onto something when I found an option in the Docker settings for 'Allow access to custom networks', which I've now enabled but that hasn't made a difference.

 

I'll try swapping my LE container and the rest of my proxied containers across to a new docker network today and see how I go - thanks for the suggestion.

Edited by nug

Share this post


Link to post

For the record - I'm an idiot.

 

It would have been working all along if I didn't accidentally name the LE conf file - jitsimeet.subdomain.com. Fixed that up, restarted LE and bang! She's up and running. Thanks for the help anyway!

Share this post


Link to post

Has anybody worked out how to update the containers correctly and hide the errors?

Share this post


Link to post
On 5/7/2020 at 3:01 AM, OsoPolar said:

Has anybody worked out how to update the containers correctly and hide the errors?

Going thru portainer you click on the container. Then there is a red button on the top that says "Recreate." After you click that, flip the toggle on that says pull latest image. Then recreate. Be advised that your container names will change and the proxy networks may not persist. You'll have to make those changes.

 

 

If that doesn't work, run thru the docker-compose commands in the terminal and rebuild the stack.

 

Neither of these suppressed the warnings I got in Fix Common Errors and the docker tab says I need updating.

 

I personally wouldn't update unless there's compelling reason to do so. Ed helped me troubleshoot all this after I updated and broke my setup. I vowed not to update jitsi until after my daughter's virtual birthday party next weekend.

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.