GLib-ERROR **: Creating pipes for GWakeup: Too many open files

[Mariano Mejia]

Hi! Kurento,

We had experiencing this kind of error with the server and now I can't start or restart the kurento-media-server.
Also I had tried to reboot it and doesn't response when I tried to start again.

BTW, I had attached the kurento media log file.
Just let me know how to fix this kind of issue.

I'm using the 5.0.4 version of kurento.

i  gstreamer1.0-plugins-bad:amd64              1.4.1-1ubuntu1kurento1               amd64        GStreamer plugins from the "bad" set

ii  gstreamer1.0-plugins-bad-faad:amd64         1.4.1-1ubuntu1kurento1               amd64        GStreamer faad plugin from the "bad" set

ii  gstreamer1.0-plugins-bad-videoparsers:amd64 1.4.1-1ubuntu1kurento1               amd64        GStreamer videoparsers plugin from the "bad" set

ii  gstreamer1.0-plugins-base:amd64             1.4.1-1~kurento1                     amd64        GStreamer plugins from the "base" set

ii  gstreamer1.0-plugins-good:amd64             1.4.1-1ubuntu1kurento1               amd64        GStreamer plugins from the "good" set

ii  gstreamer1.0-plugins-ugly:amd64             1.4.1-1~kurento1                     amd64        GStreamer plugins from the "ugly" set

ii  gstreamer1.0-x:amd64                        1.4.1-1~kurento1                     amd64        GStreamer plugins for X11 and Pango

ii  kurento-media-server                        5.0.4-trusty                         amd64        Kurento Media Server

ii  libgstreamer-plugins-bad1.0-0:amd64         1.4.1-1ubuntu1kurento1               amd64        GStreamer development files for libraries from the "bad" set

ii  libgstreamer-plugins-base1.0-0:amd64        1.4.1-1~kurento1                     amd64        GStreamer libraries from the "base" set

ii  libgstreamer-plugins-good1.0-0:amd64        1.4.1-1ubuntu1kurento1               amd64        GStreamer development files for libraries from the "good" set

ii  libgstreamer1.0-0:amd64                     1.4.1-1~kurento1                     amd64        Core GStreamer libraries and elements

ii  kms-core                                    5.0.4-trusty                         amd64        Kurento core module

ii  kms-elements                                5.0.4-trusty                         amd64        Kurento elements module

ii  kms-filters                                 5.0.4-trusty                         amd64        Kurento filters module

ii  kms-gstmarshal                              1.0.1-trusty                         amd64        Kurento marshal library

ii  kms-jsonrpc                                 0.1.2-trusty                         amd64        Kurento jsonrpc library

[Ivan Gracia]

Version 5.0.4 had some stability issues, and also was known to hang after some time, and could only be killed. Please update to the lates release 5.1.0, and see if you get the same errors.

Ivan Gracia

--
You received this message because you are subscribed to the Google Groups "kurento" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kurento+u...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[daa...@instapanel.com]

I received the same error on 5.1.0, although I was able to start the service again. See attached log, and dpkg info below. Any idea what the cause is?

$ dpkg -s kurento-media-server
Package: kurento-media-server
Status: install ok installed
Priority: optional
Section: net
Installed-Size: 1779
Maintainer: Kurento Maintenance Team <kur...@googlegroups.com>
Architecture: amd64
Version: 5.1.0-trusty
Replaces: kurento
Depends: kms-core (>= 5.1.0), kms-jsonrpc (>= 0.2.0), libboost-filesystem1.54.0, libboost-program-options1.54.0, libboost-system1.54.0, libc6 (>= 2.14), libgcc1 (>= 1:4.1.1), libglib2.0-0 (>= 2.12.0), libglibmm-2.4-1c2a (>= 2.36.2), libgnutls28 (>= 3.2.10-0), libgstreamer1.0-0 (>= 1.0.0), libjsoncpp0 (>= 0.6.0~rc2), librabbitmq1 (>= 0.4.1), libsigc++-2.0-0c2a (>= 2.0.2), libssl1.0.0 (>= 1.0.0), libstdc++6 (>= 4.8.1), kms-elements (>= 5.1.0), kms-filters (>= 5.1.0)
Breaks: kurento
Conflicts: kurento
Conffiles:
/etc/default/kurento-media-server 3f114639ae0156c88434116369c2f18b
/etc/kurento/kurento.conf.json 0bd2dc5ab93bce91a08cb3f40334befb
/etc/kurento/sdp_pattern.txt 21809b28a606c9a81ddd86ec4e17d239
/etc/init.d/kurento-media-server 135e1323a9dc3b7d2873c78c8007a284
Description: Kurento Media Server
The Kurento Media Server processes audio and video streams,
doing composable pipeline-based processing or media.

[Jose Antonio Santos Cadenas]

Hi,

too may open files problem is related with the number of thread that the process is consuming. If you have many endpoints running at the same time you can have this kind of problems. We are currently working on reducing the number of threads that each endpoint is consuming, and we expect that version 6 will be more efficient with resources consumption, specially with threads.

It may take some time, but we will keep you posted.

[Daavid Kahn]

Interesting, this was in my dev environment so it should only have been 1 simultaneous connection.

Am I perhaps not properly disposing of some resource after each connection ends?

--
You received this message because you are subscribed to a topic in the Google Groups "kurento" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/kurento/agVJHmxfVDQ/unsubscribe.
To unsubscribe from this group and all its topics, send an email to kurento+u...@googlegroups.com.

[Jose Antonio Santos Cadenas]

El lun., 30 de marzo de 2015 a las 23:06, Daavid Kahn (<daa...@instapanel.com>) escribió:

Interesting, this was in my dev environment so it should only have been 1 simultaneous connection.

Am I perhaps not properly disposing of some resource after each connection ends?

if you are only testing with one webrtcendpoint at once, it should not produce this error because threads are stopped once endpoints are disposed (at least we don't have this problems while developing). What are you doing to dispose elements?

[Daavid Kahn]

Currently, I dispose of endpoints using an API call from the client (not guaranteed to occur) and a server-side timeout. I call

'pipeline.release()' - that also releases the WebRtcEndpoint and RecorderEndpoint, right?

I posted another question asking how to listen for EndOfStream events in node: https://groups.google.com/forum/#!topic/kurento/A1xdIsJKVw4

Thanks José!

[Jose Antonio Santos Cadenas]

Yes releasing the pipe will release all the elements inside, but if it is not guaranteed to be called that could be the issue.

[grou...@gmail.com]

I see this error too, on 5.1.3 with about 10-20 clients and four streamers after some days of work. I'll move on to version 6, but I'm planning to scale to a large number of clients and streamers.

According to your answer I'm afraid that when I'll scale to hundreds or thousands I'll get this error again.

Is it correct? What is the streamer and client count limitation?

If that's true, I guess that the only solution is to make more instances of kurento and duplicate streamers between them (or distribute them wisely if possible)?