Installation Problem(RPC failed on the node ejabberd@localhost: nodedown)

This is my first post here and its been a week now searching for a solution of this problem, but still not solved. So any of you here with a knowledge on how to solve this, kindly lend me a hand please.

I successfully installed EJABBERD(2.0.5) in FEDORA 10.0, all was set and things needed to configured and successfully connected to the IM client(PIDGIN) I tried to use for testing. The problem of mine came when I reboot my server. I start the ejabberdctl service, then when I display the status, below is the error shown. I tried to search the net for a step by step method on how to solve this since Im only new to this technology and even in LINUX environment.

[root@chat ~]# ejabberdctl status
RPC failed on the node ejabberd@localhost: nodedown

=ERROR REPORT==== 29-Jul-2009::18:20:40 ===
Error in process <0.33.0> on node 'ejabberdctl@chat' with exit value: {badarg,[{erlang,list_to_existing_atom,["ejabberd@chat"]},{dist_util,recv_challenge,1},{dist_util,handshake_we_started,1}]}

When I viewed the [ejabberdctl live], below is the error displayed:

{error_logger,{{2009,7,29},{18,18,22}},"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,7,29},{18,18,22}},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,610},{stack_size,23},{reductions,474}],[]]}
{error_logger,{{2009,7,29},{18,18,22}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfa,{net_kernel,start_link,[['ejabberd@localhost',shortnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2009,7,29},{18,18,22}},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,7,29},{18,18,22}},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,233},{stack_size,23},{reductions,123}],[]]}
{error_logger,{{2009,7,29},{18,18,22}},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_20090729-181821.dump
Kernel pid terminated (application_controller) ({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})

kindly give me some insights on how to solve this.

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

> when I reboot my server. I

> when I reboot my server. I start the ejabberdctl service, then when I display the status, below is the error shown.

> {badarg,[{erlang,list_to_existing_atom,["ejabberd@chat"]},

I've seen this error rarely, but I don't remember what exactly is the reason.

I propose you a slow but sure way to know where the problem is:

  1. Stop ejabberd, uninstall it, delete config and Mnesia spool dir.
  2. Install ejabberd. Don't change the default configuration.
  3. Start ejabberd
  4. Check it works correctly.
  5. Stop ejabberd
  6. Restart computer
  7. Start ejabberd
  8. Check now: does it work correctly?
  9. If works well, then change the 'hosts' in ejabberd.cfg to the jabberservername you want to use.
  10. Stop ejabberd. Start ejabberd. Check if works.
  11. If works, then change something else in the config, restart ejabberd, check ...
  12. After some time, you will either have ejabberd fully configured, or at least you will know what is the problem, when it happened, how did you produce it, and how to reproduce it.

> ["inet_tcp",{{badmatch,{error,duplicate_name}}

See error, duplicate_name

same problem here

After clean installation of ejabberd, on step 5 (stop ejabberd) I get this error here:

Quote:

Stopping ejabberd:Failed RPC connection to the node ejabberd@localhost: nodedown

this is a content of my ejabberd.log file:

Quote:

=ERROR REPORT==== 2010-05-06 14:13:57 ===
C(<0.186.0>:ejabberd_captcha:331) : The option captcha_cmd is not configured, but some module wants to use the CAPTCHA feature.

=INFO REPORT==== 2010-05-06 14:13:57 ===
I(<0.37.0>:ejabberd_app:69) : ejabberd 2.1.2 is started in the node ejabberd@localhost

=INFO REPORT==== 2010-05-06 14:14:04 ===
I(<0.477.0>:ejabberd_listener:232) : (#Port<0.1509>) Accepted connection {{127,0,0,1},50805} -> {{127,0,0,1},5280}

=INFO REPORT==== 2010-05-06 14:14:04 ===
I(<0.478.0>:ejabberd_http:137) : started: {gen_tcp,#Port<0.1509>}

=ERROR REPORT==== 2010-05-06 14:14:11 ===
W(<0.478.0>:ejabberd_web_admin:204) : Access {"admin","admin"} failed with error: "inexistent-account"
{request,'GET',
["admin"],
[{nokey,[]}],
undefined,
{"admin","admin"},
"en-us",[],
{{127,0,0,1},50805},
"localhost",5280,http,
[{'Authorization',"Basic YWRtaW46YWRtaW4="},
{'Connection',"keep-alive"},
{'Keep-Alive',"300"},
{'Accept-Charset',"ISO-8859-1,utf-8;q=0.7,*;q=0.7"},
{'Accept-Encoding',"gzip,deflate"},
{'Accept-Language',"en-us,en;q=0.5"},
{'Accept',"text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8"},
{'User-Agent',"Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.3) Gecko/20090914 Mandriva Linux/1.9.1.3-2mdv2010.0 (2010.0) Firefox/3.5.3"},
{'Host',"localhost:5280"}]}

=ERROR REPORT==== 2010-05-06 14:14:32 ===
** Connection attempt from disallowed node 'ctl-ejabberd@localhost' **

=INFO REPORT==== 2010-05-06 14:14:55 ===
I(<0.475.0>:ejabberd_listener:232) : (#Port<0.1522>) Accepted connection {{192,168,1,102},1406} -> {{192,168,1,100},5222}

=INFO REPORT==== 2010-05-06 14:15:40 ===
I(<0.475.0>:ejabberd_listener:232) : (#Port<0.1536>) Accepted connection {{192,168,1,100},34071} -> {{192,168,1,100},5222}

Something wrong in the installation

broncho wrote:

After clean installation of ejabberd

Quote:

=ERROR REPORT==== 2010-05-06 14:14:32 ===
** Connection attempt from disallowed node 'ctl-ejabberd@localhost' **

You called ejabberdctl, but it failed to connect to ejabberd, due to something related to the .erlang.cookie file. This should work correctly. It doesn't work correctly in your case for some reason that only you can find.

????????

What kind of advise is that??? "Some reason that only you can find." Way to go hero!!

the rest of my message is

the rest of my message is here, cause it's too big and i cannot post it here:
http://docs.google.com/View?id=dhf6np45_193cgvr6rf2

Syndicate content