Prosody error at high load

Any ideas about this error ?

Prosody global config enabled some settings:
use_libevent = true
network_backend = “epoll”

Prosody domain config settings:
storage = “memory”

Prosody logs:

Jan 11 10:27:00 socket warn server.lua: Disallowed FD number: 1026
Jan 11 10:27:00 socket warn server.lua: Disallowed FD number: 1026
Jan 11 10:27:00 timer error Traceback[timer]: …itsi-meet/prosody-plugins/mod_speakerstats_component.lua:193: attempt to index field ‘speakerStats’ (a nil value)
stack traceback:

…itsi-meet/prosody-plugins/mod_speakerstats_component.lua:193: in function ‘?’

/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>

(…tail calls…)

/usr/lib/prosody/modules/muc/muc.lib.lua:561: in function </usr/lib/prosody/modules/muc/muc.lib.lua:498>

(…tail calls…)

/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>

(…tail calls…)

/usr/lib/prosody/core/stanza_router.lua:180: in function ‘core_post_stanza’

/usr/lib/prosody/modules/mod_presence.lua:357: in function ‘?’

/usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>

(…tail calls…)

/usr/lib/prosody/core/sessionmanager.lua:107: in function ‘sm_destroy_session’

/usr/lib/prosody/modules/mod_bosh.lua:90: in function </usr/lib/prosody/modules/mod_bosh.lua:87>

(…tail calls…)

[C]: in function ‘xpcall’

/usr/lib/prosody/util/timer.lua:39: in function ‘callback’

/usr/lib/prosody/net/server_select.lua:885: in function ‘?’

/usr/lib/prosody/net/server_select.lua:916: in function </usr/lib/prosody/net/server_select.lua:908>

[C]: in function ‘xpcall’

/usr/bin/prosody:76: in function ‘loop’

/usr/bin/prosody:86: in main chunk

[C]: in ?

This is fixed in the latest versions in unstable and testing repo and will soon hit stable.

1 Like

maybe this can help, disable components related to speakerstats?

- speakerstats_component = "speakerstats.jitsi"

         modules_enabled = {
             "bosh";
             "pubsub";
             "ping";
         - "speakerstats";
             "turncredentials";
             "conference_duration";
             "muc_lobby_rooms";
             "presence_identity"
         }

- Component "speakerstats.jitsi" "speakerstats_component"
- muc_component = "conference.jitsi"
1 Like

Diabling speakerstats as above fixed the situation for us. Looking forward to see the improvement in stable.