[ejabberd] External authentication crashed with reason: bad argument in extauth:call_port/2

Holger Weiß holger at zedat.fu-berlin.de
Thu Jul 21 18:20:29 MSK 2016


* David Cunningham <dcunningham at voisonics.com> [2016-07-21 22:10]:
>     exception error: bad argument:
> [{extauth,call_port,2,[{file,"src/extauth.erl"},{line,101}]},{ejabberd_auth_external,check_password_extauth,4,[{file,"src/ejabberd_auth_external.erl"},{line,189}]},{ejabberd_auth_external,check_password_external_cache,4,[{file,"src/ejabberd_auth_external.erl"},{line,251}]},{ejabberd_auth,check_password_loop,2,[{file,"src/ejabberd_auth.erl"},{line,160}]},{ejabberd_auth,check_password,4,[{file,"src/ejabberd_auth.erl"},{line,108}]},{ejabberd_web_admin,get_auth_account,5,[{file,"src/ejabberd_web_admin.erl"},{line,267}]},{ejabberd_web_admin,process,2,[{file,"src/ejabberd_web_admin.erl"},{line,222}]},{ejabberd_http,process,5,[{file,"src/ejabberd_http.erl"},{line,363}]}]

Is the 'extauth' script still running after that error?  Are you sure it
was running immediately before that error?  Do you see any [error] or
[critical] messages in the log before this happens?

Does the script work for other things (such as authenticating with an
XMPP client) or did you not test that?

Holger


More information about the ejabberd mailing list