Closed GoogleCodeExporter closed 8 years ago
Hi,
we couldn't reproduce your error with R13B01, could you please update to the
latest
version and change one line in src/boot.erl:
%tracer:start(),
to
tracer:start(),
This will give a more detailed error report. Rebuild scalaris, rerun boot.sh and
please post the new output.
Original comment by schu...@gmail.com
on 22 Jan 2010 at 5:16
Thanks Thorsten. I updated to the lastest SVN and toggled the tracer:start()
line. Attached is the full terminal history about what I do.
Side-note 1: I always have to change `hostname -f | ...` to `hostname -i | ...`
in all scripts that check for a fully qualified domain name, as "-i"
doesn't print the IP address but rather the hostname. Maybe there is already
something wrong here? This is my etc/hostname file and my etc/hosts file:
$ cat /etc/hostname
simpknot
$ cat /etc/hosts
127.0.0.1 localhost.localdomain localhost
#127.0.1.1 simpknot
10.17.101.33 simpknot
# The following lines are desirable for IPv6 capable hosts
::1 localhost ip6-localhost ip6-loopback
fe00::0 ip6-localnet
ff00::0 ip6-mcastprefix
ff02::1 ip6-allnodes
ff02::2 ip6-allrouters
ff02::3 ip6-allhosts
Side-note 2: I also have to change the scalaris.cfg file, as in the newer SVN
releases there are four (4) know_hosts registers, and after ./boot.sh Erlang
can't find the latter three (3). So I modify the file like the following. Maybe
this is also a cause for the crashes?
--- {known_hosts, [{{127,0,0,1},14195, service_per_vm}, {{127,0,0,1},14196,
service_per_vm},
--- {{127,0,0,1},14197, service_per_vm}, {{127,0,0,1},14198,
service_per_vm}]}.
+++ {known_hosts, [{{127,0,0,1},14195, service_per_vm}]}.
Original comment by Uwe.Daue...@gmail.com
on 25 Jan 2010 at 8:57
Attachments:
(a) hostname issue: I could solved that issue. It was a lack configuration in
my
/etc/hosts file.
(b) known_hosts issue: I created the scalaris.local.cfg and there only set one
know_hosts.
(c) After reinstallation my r13b1 installation, this one works again. Can't
understand how it could break.
Will also test to reinstall my r12b5 installation and test it again. I suggest
this
will also solve this issue.
Apologies for bothering...
Original comment by Uwe.Daue...@gmail.com
on 25 Jan 2010 at 2:44
No, problem. I will close this issue now.
Original comment by schu...@gmail.com
on 26 Jan 2010 at 10:05
Original issue reported on code.google.com by
Uwe.Daue...@gmail.com
on 22 Jan 2010 at 4:40