My external script isn't being executed. I have made sure it's not an issue with permissions.
=ERROR REPORT==== 2008-05-15 14:08:08 ===
** State machine <0.262.0> terminating
** Last event in was {xmlstreamelement,
{xmlelement,"iq",
[{"type","set"},{"id","JCOM_10"}],
[{xmlelement,"query",
[{"xmlns","jabber:iq:auth"}],
[{xmlelement,"username",[],
[{xmlcdata,<<"011104000102399">>}]},
{xmlelement,"password",[],
[{xmlcdata,<<"ffffffff">>}]},
{xmlelement,"resource",[],
[{xmlcdata,<<"FSA_1.0_90-TM8SL">>}]}]}]}}
** When State == wait_for_auth
** Data == {state,#Port<0.321>,<0.263.0>,gen_tcp,"1292258527",
undefined,c2s,c2s_shaper,false,true,false,false,
[{certfile,"/etc/jabber/ssl.pem"}],
false,undefined,[],"domain.net",[],undefined,
{0,nil},
{0,nil},
{0,nil},
{0,nil},
undefined,undefined,undefined,false,none,[]}
** Reason for termination =
** {badarg,[{extauth,call_port,2},
{lists,any,2},
{ejabberd_c2s,wait_for_auth,2},
{gen_fsm,handle_msg,7},
{proc_lib,init_p,5}]}
FlappySocks wrote:My
My external script isn't being executed. I have made sure it's not an issue with permissions.
The error message you show here indicates that the erlang process that handles the extauth script couldn't be contacted. Probably earlier in the ejabberd log file you have other error message informing that the extauth script couldn't be started. Maybe that initial error message provides some clue on why the script couldn't be started.
Did you write the extauth script yourself? If so, note that the script must have an endless loop: it must keep running forever! ejabberd starts the script at the beginning. This is explained in the .