Strange SASL issue
Antoine Nguyen
ngu.antoine at gmail.com
Thu Sep 7 16:13:20 EEST 2017
2017-09-07 15:04 GMT+02:00 Sami Ketola <sami.ketola at dovecot.fi>:
>
> > On 7 Sep 2017, at 16.03, Antoine Nguyen <ngu.antoine at gmail.com> wrote:
> >
> > 2017-09-07 14:29 GMT+02:00 Aki Tuomi <aki.tuomi at dovecot.fi>:
> >
> >>
> >>
> >> On 07.09.2017 15:26, Antoine Nguyen wrote:
> >>> Hi all,
> >>>
> >>> I've just upgraded my server from debian 8 to debian 9 and I now
> >> encounter
> >>> a strange issue. I'm using prosody (XMPP server), configured to
> >>> authenticate against dovecot using SASL and a unix socket.
> >>>
> >>> This setup was working fine on debian 8.
> >>>
> >>> Now, each time I try to connect using my XMPP client, the
> authentication
> >>> fails and I see the following error in logs:
> >>>
> >>> auth: Error: BUG: Authentication client said it's PID 0
> >>>
> >>> Have you ever heard about this?
> >>>
> >>> For information, dovecot version is 2.2.27.
> >>>
> >>> Thank you,
> >>> Antoine Nguyen
> >> That seems to be a bug in XMPP. It should not use PID 0.
> >>
> >>
> > The XMPP server runs as 'prosody' user, not root...
>
>
> PID is process id, not user id.
>
>
>
Sorry, I replied too quickly. I don't how prosody manages authentication
but the main process ID is not 0 of course. How can I debug this?
Antoine
More information about the dovecot
mailing list