#1178 Race condition on host deactivation

Reporter Zash
Owner Nobody
Stars ★ (1)
  • Priority-Medium
  • Type-Defect
  • Status-CantReproduce
  1. Zash on

    Theory: 1. It closes down all s2s connections. 2. It unloads modules. 3. Some module sends something towards s2s. (MUC probably) 4. New outgoing s2s is initiated. 5. Everything else is unloaded. 6. Host is deactivated. 7. The outgoing connection is established, triggering onconnect. Error + traceback: core/s2smanager.lua:78: attempt to index field '?' (a nil value) core/s2smanager.lua:78: in function 's2s_destroy_session' mod_s2s/mod_s2s.lua:630: in function 'disconnect' net/server_select.lua:400: in function </usr/lib/prosody/net/server_select.lua:371> What version of the product are you using? 0.10.2 Please provide any additional information below. hostmanager: Deactivating host: chat.example.com ... mod_s2s: opening a new outgoing connection for this stanza (MUC kick perhaps) ... (s2s creation, dns lookup) mod_s2s: Connection attempt in progress... stanzarouter: Unhandled s2sout_unauthed stream element or stanza: features; xmlns=http://etherx.jabber.org/streams s2sout2347bb0: Disconnecting chat.example.com[s2sout_unauthed], <stream:error> is: unsupported-stanza-type s2sout2347bb0: Destroying outgoing session ... mod_s2s: Traceback[s2s]: /usr/lib/prosody/core/s2smanager.lua:78: attempt to index field '?' (a nil value)

  2. Zash on

    0.10 is EOL, I don't recall seeing this since.

    • tags Milestone-0.10 Status-CantReproduce

New comment

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