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.