How to read the prosody and ldap log correctly??

[Никита Потапов]

Friends, I need help with logging.
I have my own Jitsi Meet server with authorization via prosody (ldap2) and I need an automated collection of failed authorizations.
With standard settings and unsuccessful authorization, an entry appears in the prosody log:
Feb 09 16:08:19 mod_bosh    error    Traceback[bosh]: /usr/lib/prosody/modules/ldap.lib.lua:218: attempt to index local 'attribs' (a nil value)
stack traceback:
    /usr/lib/prosody/modules/ldap.lib.lua:218: in function 'singlematch'
    /usr/lib/prosody/modules/ldap.lib.lua:187: in function </usr/lib/prosody/modules/ldap.lib.lua:179>
    (...tail calls...)
    /usr/lib/prosody/modules/mod_auth_ldap2/mod_auth_ldap2.lua:54: in function 'plain_test'
    /usr/lib/prosody/util/sasl/plain.lua:75: in function </usr/lib/prosody/util/sasl/plain.lua:39>
    (...tail calls...)
    /usr/lib/prosody/modules/mod_saslauth.lua:80: in function </usr/lib/prosody/modules/mod_saslauth.lua:69>
    (...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:142: in function 'dispatch_stanza'
    /usr/lib/prosody/modules/mod_bosh.lua:323: in function 'func'
    /usr/lib/prosody/util/async.lua:127: in function </usr/lib/prosody/util/async.lua:125>
stack traceback:
    /usr/lib/prosody/util/async.lua:211: in function 'run'
    /usr/lib/prosody/modules/mod_bosh.lua:465: in function 'cb_handlestanza'
    /usr/lib/prosody/util/xmppstream.lua:182: in function </usr/lib/prosody/util/xmppstream.lua:162>
    [C]: in function 'parse'
    /usr/lib/prosody/util/xmppstream.lua:285: in function 'feed'
    /usr/lib/prosody/modules/mod_bosh.lua:134: in function '?'
    /usr/lib/prosody/util/events.lua:79: in function </usr/lib/prosody/util/events.lua:75>
    (...tail calls...)
    /usr/lib/prosody/net/http/server.lua:229: in function </usr/lib/prosody/net/http/server.lua:176>
    [C]: in function 'xpcall'
    /usr/lib/prosody/net/http/server.lua:108: in function 'process_next'
    /usr/lib/prosody/net/http/server.lua:124: in function 'success_cb'
    /usr/lib/prosody/net/http/parser.lua:177: in function 'feed'
    /usr/lib/prosody/net/http/server.lua:155: in function </usr/lib/prosody/net/http/server.lua:154>
    (...tail calls...)
    /usr/lib/prosody/net/server_select.lua:924: 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 ?


I would like to see in the log at least the ip address from which the failure appeared.

Thank you in advance!

[Kim Alvefur]

Hi Никита,

On Thu, Feb 09, 2023 at 05:26:44AM -0800, Никита Потапов wrote:
>Friends, I need help with logging.
>I have my own Jitsi Meet server with authorization via prosody (ldap2) and
>I need an automated collection of failed authorizations.
>With standard settings and unsuccessful authorization, an entry appears in
>the prosody log:
>Feb 09 16:08:19 mod_bosh error Traceback[bosh]:
>/usr/lib/prosody/modules/ldap.lib.lua:218: attempt to index local 'attribs'
>(a nil value)
>stack traceback:
> /usr/lib/prosody/modules/ldap.lib.lua:218: in function 'singlematch'
> /usr/lib/prosody/modules/ldap.lib.lua:187: in function

(snip)

>
>
>I would like to see in the log at least the ip address from which the
>failure appeared.

This is a programming error of some kind, not a failed authentication
attempt. I'm not familiar with mod_auth_ldap2 and friends, so I have no
idea what's going on here and can't really help you with it. Prosody
includes mod_auth_ldap these days, maybe try that one as you will will
have an easier time finding supporting for it.

--
Regards,
Zash