* vstart -d -n not working in 0.25.1
@ 2011-03-17 23:01 Noah Watkins
2011-03-17 23:54 ` Tommi Virtanen
0 siblings, 1 reply; 4+ messages in thread
From: Noah Watkins @ 2011-03-17 23:01 UTC (permalink / raw)
To: ceph-devel
I am having difficulties getting the standalone "test setup" working with 0.25.1, which was working with 0.24. Here is the following output from "./vstart -d -n".
The logs don't seem to have anything interesting, and no cmon,cmds, or cosd is running after this startup script runs.
Thanks,
Noah
nwatkins@kyoto:~/Projects/ceph/src$ ./vstart.sh -d -n
** going verbose **
=== mon.a ===
Stopping Ceph mon.a on kyoto...done
=== mon.b ===
Stopping Ceph mon.b on kyoto...done
=== mon.c ===
Stopping Ceph mon.c on kyoto...done
=== mds.a ===
Stopping Ceph mds.a on kyoto...done
=== mds.b ===
Stopping Ceph mds.b on kyoto...done
=== mds.c ===
Stopping Ceph mds.c on kyoto...done
=== osd.0 ===
Stopping Ceph osd0 on kyoto...done
hostname kyoto
ip ::1 127.0.1.1 128.114.52.36
./osdmaptool: osdmap file '/tmp/ceph_osdmap.13428'
./osdmaptool: writing epoch 1 to /tmp/ceph_osdmap.13428
./monmaptool --create --clobber --add a ::1 127.0.1.1 128.114.52.36:6789 --add b ::1 127.0.1.1 128.114.52.36:6790 --add c ::1 127.0.1.1 128.114.52.36:6791 --print /tmp/ceph_monmap.13428
./monmaptool: invalid ip:port '::1'
./cmon --mkfs -c ceph.conf -i a --monmap=/tmp/ceph_monmap.13428 --osdmap=/tmp/ceph_osdmap.13428
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
2011-03-17 15:58:24.828602 7f24aa4f6720 can't open /tmp/ceph_monmap.13428: error 2: No such file or directory
./cmon --mkfs -c ceph.conf -i b --monmap=/tmp/ceph_monmap.13428 --osdmap=/tmp/ceph_osdmap.13428
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
2011-03-17 15:58:24.837414 7fd5396dc720 can't open /tmp/ceph_monmap.13428: error 2: No such file or directory
./cmon --mkfs -c ceph.conf -i c --monmap=/tmp/ceph_monmap.13428 --osdmap=/tmp/ceph_osdmap.13428
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
2011-03-17 15:58:24.843145 7fc9858a5720 can't open /tmp/ceph_monmap.13428: error 2: No such file or directory
rm: cannot remove `/tmp/ceph_monmap.13428': No such file or directory
./cmon -i a -c ceph.conf
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
problem opening monitor store in dev/mon.a: No such file or directory
./cmon -i b -c ceph.conf
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
problem opening monitor store in dev/mon.b: No such file or directory
./cmon -i c -c ceph.conf
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
problem opening monitor store in dev/mon.c: No such file or directory
Loading class: .libs/libcls_rbd.so.1.0.0: rbd 1.3 x86-64
2011-03-17 15:58:25.899218 7f3e5b64d720 read 201250 bytes from .libs/libcls_rbd.so.1.0.0
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
2011-03-17 15:58:25.899496 7f3e5b64d720 ceph_tool_common_init failed.
mkfs osd0
./cosd -i 0 -c ceph.conf --mkfs
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
start osd0
./cosd -i 0 -c ceph.conf
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
creating dev/mds.a.keyring
2011-03-17 15:58:25.939144 7f0b91296720 read 149 bytes from dev/mds.a.keyring
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
2011-03-17 15:58:25.939304 7f0b91296720 ceph_tool_common_init failed.
./cmds -i a -c ceph.conf
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
creating dev/mds.b.keyring
2011-03-17 15:58:25.960736 7fcecc22a720 read 149 bytes from dev/mds.b.keyring
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
2011-03-17 15:58:25.960898 7fcecc22a720 ceph_tool_common_init failed.
./cmds -i b -c ceph.conf
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
creating dev/mds.c.keyring
2011-03-17 15:58:25.982370 7ffbe4871720 read 149 bytes from dev/mds.c.keyring
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
2011-03-17 15:58:25.982534 7ffbe4871720 ceph_tool_common_init failed.
./cmds -i c -c ceph.conf
** WARNING: Ceph is still under heavy development, and is only suitable for **
** testing and review. Do not trust it with important data. **
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
./ceph -c ceph.conf mds set_max_mds 3
unable to ceph.conf mon addr for mon.a (::1)
unable to ceph.conf mon addr for mon.b (::1)
unable to ceph.conf mon addr for mon.c (::1)
unable to find any monitors in conf
2011-03-17 15:58:25.997401 7f3031f33720 ceph_tool_common_init failed.
started. stop.sh to stop. see out/* (e.g. 'tail -f out/????') for debug output.
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: vstart -d -n not working in 0.25.1
2011-03-17 23:01 vstart -d -n not working in 0.25.1 Noah Watkins
@ 2011-03-17 23:54 ` Tommi Virtanen
2011-03-17 23:57 ` Noah Watkins
0 siblings, 1 reply; 4+ messages in thread
From: Tommi Virtanen @ 2011-03-17 23:54 UTC (permalink / raw)
To: Noah Watkins; +Cc: ceph-devel
On Thu, Mar 17, 2011 at 04:01:13PM -0700, Noah Watkins wrote:
> I am having difficulties getting the standalone "test setup" working
> with 0.25.1, which was working with 0.24. Here is the following
> output from "./vstart -d -n".
>
> The logs don't seem to have anything interesting, and no cmon,cmds,
> or cosd is running after this startup script runs.
...
> ./monmaptool --create --clobber --add a ::1 127.0.1.1 128.114.52.36:6789 --add b ::1 127.0.1.1 128.114.52.36:6790 --add c ::1 127.0.1.1 128.114.52.36:6791 --print /tmp/ceph_monmap.13428
vstart.sh can't handle hosts with IPv6 right now -- in fact, it can't
even handle some IPv4 configurations of /etc/resolv.conf. A simple
test is to run: hostname --ip-address
If it outputs more than one IP address, vstart.sh won't work for you
right now. On this Ubuntu 10.04 box, I get "::1 127.0.1.1 10.0.1.102".
My /etc/hosts is
10.0.1.102 dreamer # Added by NetworkManager
127.0.0.1 localhost.localdomain localhost
::1 dreamer localhost6.localdomain6 localhost6
127.0.1.1 dreamer
# 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
I don't have a good solution right now.
I'd file a ticket, but the tracker is down currently :(
--
:(){ :|:&};:
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: vstart -d -n not working in 0.25.1
2011-03-17 23:54 ` Tommi Virtanen
@ 2011-03-17 23:57 ` Noah Watkins
2011-03-18 0:02 ` Tommi Virtanen
0 siblings, 1 reply; 4+ messages in thread
From: Noah Watkins @ 2011-03-17 23:57 UTC (permalink / raw)
To: Tommi Virtanen; +Cc: ceph-devel
Ahh,
I was just poking around in vstart. Looks like the IP is determined by `hostname --ip-address`, which for some reason my machine is returning IPv6. Solution is ./vstart --localhost which then selects the IP to be 127.0.0.1. Not sure why my machine was returning:
nwatkins@kyoto:~$ hostname --ip-address
::1 127.0.1.1 128.114.52.36
Thanks for the help!
-n
On Mar 17, 2011, at 4:54 PM, Tommi Virtanen wrote:
> On Thu, Mar 17, 2011 at 04:01:13PM -0700, Noah Watkins wrote:
>> I am having difficulties getting the standalone "test setup" working
>> with 0.25.1, which was working with 0.24. Here is the following
>> output from "./vstart -d -n".
>>
>> The logs don't seem to have anything interesting, and no cmon,cmds,
>> or cosd is running after this startup script runs.
> ...
>> ./monmaptool --create --clobber --add a ::1 127.0.1.1 128.114.52.36:6789 --add b ::1 127.0.1.1 128.114.52.36:6790 --add c ::1 127.0.1.1 128.114.52.36:6791 --print /tmp/ceph_monmap.13428
>
> vstart.sh can't handle hosts with IPv6 right now -- in fact, it can't
> even handle some IPv4 configurations of /etc/resolv.conf. A simple
> test is to run: hostname --ip-address
>
> If it outputs more than one IP address, vstart.sh won't work for you
> right now. On this Ubuntu 10.04 box, I get "::1 127.0.1.1 10.0.1.102".
> My /etc/hosts is
>
> 10.0.1.102 dreamer # Added by NetworkManager
> 127.0.0.1 localhost.localdomain localhost
> ::1 dreamer localhost6.localdomain6 localhost6
> 127.0.1.1 dreamer
>
> # 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
>
> I don't have a good solution right now.
>
> I'd file a ticket, but the tracker is down currently :(
>
> --
> :(){ :|:&};:
^ permalink raw reply [flat|nested] 4+ messages in thread
* Re: vstart -d -n not working in 0.25.1
2011-03-17 23:57 ` Noah Watkins
@ 2011-03-18 0:02 ` Tommi Virtanen
0 siblings, 0 replies; 4+ messages in thread
From: Tommi Virtanen @ 2011-03-18 0:02 UTC (permalink / raw)
To: Noah Watkins; +Cc: ceph-devel
On Thu, Mar 17, 2011 at 04:57:00PM -0700, Noah Watkins wrote:
> I was just poking around in vstart. Looks like the IP is determined
> by `hostname --ip-address`, which for some reason my machine is
> returning IPv6. Solution is ./vstart --localhost which then selects
> the IP to be 127.0.0.1. Not sure why my machine was returning:
Yes, that'll work when you're running on just one machine.
The ticket for this is http://tracker.newdream.net/issues/898
--
:(){ :|:&};:
^ permalink raw reply [flat|nested] 4+ messages in thread
end of thread, other threads:[~2011-03-18 0:02 UTC | newest]
Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2011-03-17 23:01 vstart -d -n not working in 0.25.1 Noah Watkins
2011-03-17 23:54 ` Tommi Virtanen
2011-03-17 23:57 ` Noah Watkins
2011-03-18 0:02 ` Tommi Virtanen
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.