Skip to content
GitLab
Open
Created by Citronalco@geierbOwner

Could not create a new SASL object

Nachdem der IMAP-Server ein paar Stunden ist war, funktioniert auch kein Login mehr für Bytewerk-Leute bis Prosody neu gestartet wird.

prosody.err:

Sep 04 14:03:35 sasl_imap       error   error connecting to imap at 'mail.bingo-ev.de:993': timeout
Sep 04 14:03:35 general error   Top-level error, please report:
/usr/lib64/prosody/modules/mod_saslauth.lua:253: attempt to index local 'sasl_handler' (a nil value)
Sep 04 14:03:35 general error   
stack traceback:
        [C]: in function 'loop'
        /usr/lib64/prosody/net/server_event.lua:770: in function </usr/lib64/prosody/net/server_event.lua:769>
        [C]: in function 'xpcall'
        /usr/lib64/prosody/../../bin/prosody:76: in function 'loop'
        /usr/lib64/prosody/../../bin/prosody:86: in main chunk
        [C]: ?
Sep 04 14:05:46 sasl_imap       error   error connecting to imap at 'mail.bingo-ev.de:993': timeout
Sep 04 14:05:46 general error   Top-level error, please report:
/usr/lib64/prosody/modules/mod_saslauth.lua:253: attempt to index local 'sasl_handler' (a nil value)
Sep 04 14:05:46 general error   
stack traceback:
        [C]: in function 'loop'
        /usr/lib64/prosody/net/server_event.lua:770: in function </usr/lib64/prosody/net/server_event.lua:769>
        [C]: in function 'xpcall'
        /usr/lib64/prosody/../../bin/prosody:76: in function 'loop'
        /usr/lib64/prosody/../../bin/prosody:86: in main chunk
        [C]: ?
Sep 04 14:07:02 sasl_imap       error   error initializing ssl connection to imap at 'mail.bingo-ev.de:993': closed
Sep 04 14:07:02 modulemanager   error   Error initializing module 'auth_imap' on 'bingo-ev.de': ...ty-modules/mod_auth_imap/auth_imap/mod_auth_imap.lua:37: Could not create a new SASL object
stack traceback:
        [C]: in function 'assert'
        ...ty-modules/mod_auth_imap/auth_imap/mod_auth_imap.lua:37: in main chunk
        [C]: in function 'xpcall'
        /usr/lib64/prosody/core/modulemanager.lua:183: in function 'do_load_module'
        /usr/lib64/prosody/core/modulemanager.lua:261: in function 'load'
        /usr/lib64/prosody/core/usermanager.lua:67: in function '?'
        /usr/lib64/prosody/util/events.lua:79: in function </usr/lib64/prosody/util/events.lua:75>
        (tail call): ?
        /usr/lib64/prosody/core/hostmanager.lua:108: in function 'activate'
        /usr/lib64/prosody/core/hostmanager.lua:58: in function '?'
        /usr/lib64/prosody/util/events.lua:79: in function </usr/lib64/prosody/util/events.lua:75>
        (tail call): ?
        /usr/lib64/prosody/util/startup.lua:393: in function 'prepare_to_start'
        /usr/lib64/prosody/util/startup.lua:629: in function 'f'
        /usr/lib64/prosody/util/async.lua:139: in function 'func'
        /usr/lib64/prosody/util/async.lua:127: in function </usr/lib64/prosody/util/async.lua:125>

prosody.log:

Sep 05 00:40:30 c2s55dc9df63b40 info    Client connected
Sep 05 00:40:30 c2s55dc9df63b40 warn    No available SASL mechanisms, verify that the configured authentication module is working
Sep 05 00:40:30 c2s55dc9df63b40 warn    No stream features to offer
Sep 05 00:40:30 c2s55dc9df63b40 info    Client disconnected: connection closed
Sep 05 00:41:04 c2s55dc9dc2ef40 info    Client connected
Sep 05 00:41:04 c2s55dc9dc2ef40 warn    No available SASL mechanisms, verify that the configured authentication module is working
Sep 05 00:41:04 c2s55dc9dc2ef40 warn    No stream features to offer
Sep 05 00:41:04 c2s55dc9dc2ef40 info    Client disconnected: connection closed