#1659 mod_limits in the traceback / by pausing and resuming connections

Reporter mirux
Owner Nobody
Created
Updated
Stars ★ (1)
Tags
  • Status-Accepted
  • Milestone-0.11
  • Type-Defect
  • Priority-Medium
  1. mirux on

    What steps will reproduce the problem? 1. patched prosody server Version 0.11.2 (debian) to 0.11.2-1+deb10u2] What is the expected output? No upgrade related error message in prosody.err What do you see instead? May 23 08:41:46 timer error Traceback[timer]: /usr/lib/prosody/net/server_select.lua:685: table index is nil stack traceback: /usr/lib/prosody/net/server_select.lua:685: in function 'addsocket' /usr/lib/prosody/net/server_select.lua:471: in function </usr/lib/prosody/net/server_select.lua:460> (...tail calls...) /usr/lib/prosody/modules/mod_limits.lua:76: in function </usr/lib/prosody/modules/mod_limits.lua:72> [C]: in function 'xpcall' /usr/lib/prosody/util/timer.lua:39: in function 'callback' /usr/lib/prosody/net/server_select.lua:876: in function '?' /usr/lib/prosody/net/server_select.lua:907: in function </usr/lib/prosody/net/server_select.lua:899> [C]: in function 'xpcall' /usr/bin/prosody:80: in function 'loop' /usr/bin/prosody:90: in main chunk [C]: in ? What version of the product are you using? On what operating system? Version 0.11.2 ((debian) to 0.11.2-1+deb10u2) / raspberian, Linux 5.10.17-v7+ armv7l Please provide any additional information below.

  2. Zash on

    Theory: Attempt to resume connection after it was closed. Unsure how this can happen since the connection should have been removed from the session at this point.

    Changes
    • tags Status-Accepted Milestone-0.11

New comment

Not published. Used for spam prevention and optional update notifications.