File descriptors leak

Submitted by marekvi on #1

Hello Michael,

I have been using Virtual Here server on Raspberry Pi 3B (server version 4.2.0) with three clients - Windows 10, Ubuntu 20.04 and Mac OS 11 (client version 5.2.0) for some time and I have noticed that after some time - two weeks usually, the Virtual Here server process runs out available file descriptors (Linux limits 1024 for the process) and I receive the following message: Error 24 opening device (/dev/bus/usb/001/043) file descriptor, No file descriptors available

I think that there must be some sort of file descriptor leak. Could you please help me find the problem? I have pasted the list of all VH file descriptors to file here (output of lsof command): https://drive.google.com/file/d/1rRYuA7nRie1IXT5J9FlMUveBKeqziIHC/view?…

Thanks,
Marek

Submitted by Michael on Wed, 2021/12/15 - 05:49

#2

Hi, thanks for the detailed, log. Could you update the server to the latest server version, i think that fixes the leak. The leak was related to avahi integration.

Submitted by gexogen on Sat, 2022/03/05 - 17:05

#3

Hi! I've got the similar problem vhusbdx86_64 v4.3.7 on Intel NUC with Ubuntu server 20.04
Mar 05 06:46:08 virtualhere-nuc vhusbdx86_64[3341]: Error 24 starting client authorization, No file descriptors available
Mar 05 06:46:08 virtualhere-nuc vhusbdx86_64[3341]: Error binding device 111 [0a89:0025] to connection 227, BIND_ERROR
Mar 05 06:46:12 virtualhere-nuc vhusbdx86_64[3341]: Error 24 starting client authorization, No file descriptors available
Mar 05 06:46:12 virtualhere-nuc vhusbdx86_64[3341]: Error binding device 1132 [0a89:0025] to connection 227, BIND_ERROR

Submitted by Michael on Sat, 2022/03/05 - 20:05

#4

Can you post the output of lsof on the server when it happens again? Maybe in pastebin

Submitted by Michael on Wed, 2022/03/09 - 16:42

#6

Thanks, can you stop the virtualhere server then edit the server config.ini file and add the line

UseAVAHIServiceFile=1

Then save and start the process again. See if that resolves it

Submitted by gexogen on Thu, 2022/03/10 - 05:17

#7

Thank you. I'll try it and return with feedback.

Submitted by gexogen on Fri, 2022/03/11 - 18:11

#8

Michael, it looks like this doesn't helps. It's been 36 hours since I've restarted virtualhere server and the number of its open file descriptors are already reached 50k and continues to grow.

Submitted by Michael on Fri, 2022/03/11 - 18:29

#9

Can you post here your server config.ini file

Submitted by Michael on Sat, 2022/03/12 - 22:07

#11

What does auth.sh do? I wonder if that could that be leaking instead (it would be a child of the vhusbdx86_64 process). VirtualHere only uses one netlink socket and that doesnt leak so im wondering if it might be some program you are calling in auth.sh.

Submitted by Michael on Mon, 2022/03/21 - 11:01

#13

Do you have this directory /etc/avahi/services on your server, with files in it?

Submitted by gexogen on Mon, 2022/03/21 - 16:43

#14

No. It seems like no avahi in my system at all.

Submitted by Michael on Mon, 2022/03/21 - 16:54

#15

Ah ok, so thats it. Actually if you look carefully in the log it will probably say "Linux AVAHI daemon not installed, using built-in mdns server instead"

So can you install avahi so that virtualhere server can use it.

sudo apt install avahi-daemon

Then reboot your server or stop/start the virtualhere server service

(The fallback is to use the mdns internal server but it has a leak in it and thats what you are encountering)

Submitted by gexogen on Mon, 2022/03/21 - 17:21

#16

Thank you. I'll try it and continue to monitor and return with any updates.

Submitted by gexogen on Sat, 2022/03/26 - 20:13

#17

Thank you again! Your advice helped me to solve this problem.

Submitted by Michael on Sat, 2022/03/26 - 21:28

#18

OK thats great, im glad its all fixed now