unable to create first node in scalaris

[Kunal Balani]

Hello everyone,
I need some help to get started with scalaris.
I have install erlang and the other packages on my local machine
(ubuntu 11.10).
I try to create the first node by executing ./bin/firstnode.sh
But I get an error saying that

ERROR: erl could not create a Erlang VM named 'firstnode'
Are you already running a Scalaris server with this name?
You can change the name by the -n option (see -h).
'scalarisctl list' gives you a list of currently registered Erlang VMs
We were trying to run: erl -noinput -name firstnode -eval 'halt(0).'

Any help would be highly appreciated.
Thanks

-best
Kunal Balani

[Ghilain Matthieu]

Maybe you already have one started? You should check the list of
launched processes.

[Kunal Balani]

Ghailain , thanks for reply,

I did that
> scalarisctl list

It shows me as:
epmd: up and running on port 4369 with data:

I don't see any firstnode running on my machine.
I wan't to run scalaris on my local machine.

Seems something wrong with erlang??
I don't know what exactly the issue ?

-best
Kunal

[Nico Kruber]

could you please try executing the following commands and post the output?
erl -name firstnode -eval 'halt(0).'

also, please try
erl -name firstnode@`hostname -f` -eval 'halt(0).'

The latter technique ist used by the current trunk version of Scalaris to
start the Erlang node and should work as long as "hostname -f" returns a
correct hostname. If you don't want to switch to trunk, it would probably be
sufficient to just checkout the new scalarisctl.in script.

Regards
Nico Kruber

[Kunal Balani]

Thanks Nico for the reply,
here is the output for erl -name firstnode -eval 'halt(0).'

{error_logger,{{2011,11,26},{20,8,13}},"Can't set long node
name!\nPlease check your configuration\n",[]}
{error_logger,{{2011,11,26},{20,8,13}},crash_report,[[{initial_call,{net_kernel,init,['Argument__1']}},{pid,<0.20.0>},{registered_name,[]},{error_info,{exit,{error,badarg},[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},{ancestors,[net_sup,kernel_sup,<0.9.0>]},{messages,[]},{links,[<0.17.0>]},{dictionary,[{longnames,true}]},{trap_exit,true},{status,running},{heap_size,987},{stack_size,24},{reductions,701}],[]]}
{error_logger,{{2011,11,26},{20,8,13}},supervisor_report,[{supervisor,{local,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{offender,[{pid,undefined},{name,net_kernel},{mfargs,{net_kernel,start_link,[[firstnode,longnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,worker}]}]}
{error_logger,{{2011,11,26},{20,8,13}},supervisor_report,[{supervisor,{local,kernel_sup}},{errorContext,start_error},{reason,shutdown},{offender,[{pid,undefined},{name,net_sup},{mfargs,{erl_distribution,start_link,[]}},{restart_type,permanent},{shutdown,infinity},{child_type,supervisor}]}]}
{error_logger,{{2011,11,26},{20,8,13}},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: erl_crash.dump
Kernel pid terminated (application_controller)
({application_start_failure,kernel,{shutdown,{kernel,start,[normal,[]]}}})

here is the output of the second statement:
Erlang R14B03 (erts-5.8.4) [source] [64-bit] [smp:4:4] [rq:4]
[async-threads:0] [hipe] [kernel-poll:false]

Eshell V5.8.4 (abort with ^G).

PFA the erl_crash.dump file.

-best
Kunal

[Nico Kruber]

that's what I expected - erlang sometimes can not create a long node name,
i.e. including the domain part. If you explicitly set one, it works.

Please download the new scalarisctl.in from
https://code.google.com/p/scalaris/source/browse/trunk/bin/scalarisctl.in
and replace your version with that (then configure && make).
It should work afterwards.

Alternatively, edit firstnode.sh etc and set the long nodename explicitely,
e.g. in firstnode.sh set NAME="firstnode@"`hostname -f` or start Scalaris
using scalarisctl and specify the long nodename with
scalarisctl -f -s -m -n "firstnode@"`hostname -f`
(you may need to change those options depending on your needs)

Nico

On Saturday 26 November 2011 20:16:58 Kunal Balani wrote:
> Thanks Nico for the reply,
> here is the output for erl -name firstnode -eval 'halt(0).'
>
> {error_logger,{{2011,11,26},{20,8,13}},"Can't set long node
> name!\nPlease check your configuration\n",[]}
> {error_logger,{{2011,11,26},{20,8,13}},crash_report,[[{initial_call,{net_ker
> nel,init,['Argument__1']}},{pid,<0.20.0>},{registered_name,[]},{error_info,{
> exit,{error,badarg},[{gen_server,init_it,6},{proc_lib,init_p_do_apply,3}]}},
> {ancestors,[net_sup,kernel_sup,<0.9.0>]},{messages,[]},{links,[<0.17.0>]},{d
> ictionary,[{longnames,true}]},{trap_exit,true},{status,running},{heap_size,9
> 87},{stack_size,24},{reductions,701}],[]]}
> {error_logger,{{2011,11,26},{20,8,13}},supervisor_report,[{supervisor,{loca
> l,net_sup}},{errorContext,start_error},{reason,{'EXIT',nodistribution}},{off
> ender,[{pid,undefined},{name,net_kernel},{mfargs,{net_kernel,start_link,[[fi
> rstnode,longnames]]}},{restart_type,permanent},{shutdown,2000},{child_type,w
> orker}]}]}
> {error_logger,{{2011,11,26},{20,8,13}},supervisor_report,[{supervisor,{loca

[Kunal Balani]

thanks Nico .... .now its working.

-best
Kunal