[ejabberd] freebsd upgrade and now auth failures

Randy Bush randy at psg.com
Sat Apr 11 08:19:31 MSD 2009


> Then first go to a state where ejabberd runs correctly and shows the
> good information (accounts, rosters...). You tried to fix your current
> installation, but from what you say, it seems you didn't succeed.
> 
> There is another plan that you can consider: go back in time to the
> last state where you were happy with your installation. From what you
> said:
> 
> > all was working and then i did a portupgrade, looks like from ejabberd-1.1.4_2
> 
> You have all the pieces to reproduce that old working installation, right?
> If that ejabberd-1.1.4_2 package is no longer available, you can
> compile from source package.
> 
> Once you get some ejabberd to run your database (1.1.4, 2.0.5, source
> package, ports, whatever), then you no longer are on a desperate
> situation, and you can carefully plan your next moves, right?

yep

so i reverted to 1.1.4.  was easy.  and i have the node up.  but
ejabberdctl in 1.1.4 seems not to have dump.  and when i try to do it
anyway, some sort of "duplicate_name" error, whatever that means.

    work0.psg.com:/root# ejabberdctl dump /tmp/ej.dump
    {error_logger,{{2009,4,11},{4,9,17}},"Protocol: ~p: register error: ~p~n",["inet_tcp",{{badmatch,{error,duplicate_name}},[{inet_tcp_dist,listen,1},{net_kernel,start_protos,4},{net_kernel,start_protos,3},{net_kernel,init_node,2},{net_kernel,init,1},{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}]}
    {error_logger,{{2009,4,11},{4,9,17}},crash_report,[[{pid,<0.20.0>},{registered_name,net_kernel},{error_info,{exit,{error,badarg},[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},{initial_call,{net_kernel,init,['Argument__1']}},{ancestors,[net_sup,kernel_sup,<0.8.0>]},{messages,[]},{links,[#Port<0.94>,<0.17.0>]},{dictionary,[{longnames,false}]},{trap_exit,true},{status,running},{heap_size,377},{stack_size,23},{reductions,474}],[]]}
    {error_logger,{{2009,4,11},{4,9,17}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfa,{net_kernel,start_link,[[ejabberd,shortnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
    {error_logger,{{2009,4,11},{4,9,17}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,shutdown},{offender,[{pid,undefined},{name,net_sup},{mfa,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
    {error_logger,{{2009,4,11},{4,9,17}},crash_report,[[{pid,<0.7.0>},{registered_name,[]},{error_info,{exit,{shutdown,{kernel,start,[normal,[]]}},[{application_master,init,4},{proc_lib,init_p_do_apply,3}]}},{initial_call,{application_master,init,['Argument__1','Argument__2','Argument__3','Argument__4']}},{ancestors,[<0.6.0>]},{messages,[{'EXIT',<0.8.0>,normal}]},{links,[<0.6.0>,<0.5.0>]},{dictionary,[]},{trap_exit,true},{status,running},{heap_size,377},{stack_size,23},{reductions,124}],[]]}
    {error_logger,{{2009,4,11},{4,9,17}},std_info,[{application,kernel},{exited,{shutdown,{kernel,start,[normal,[]]}}},{type,permanent}]}
    {"Kernel pid terminated",application_controller,"{application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}}"}

    Crash dump was written to: /var/log/ejabberd//erl_crash_20090411-040917.dump
    Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})

the dump is at http://archive.psg.com/erl_crash.dump

i get a similar dump with just issuing

    ejabberdctl

i am going to try to move forward as if all this was a normal upgrade.
i have left all the stuff i need to revert.

randy


More information about the ejabberd mailing list