... and it was, bit of a foot gun there. Thanks Greg, you were right on
the money.
So it looks like my 'make install' puts the libraries in /usr/lib (as
expected):
$ ls -l /usr/lib/librados.so.2.0.0
-rwxr-xr-x 1 root root 92296482 Mar 26 12:57 /usr/lib/librados.so.2.0.0
whereas the Ubuntu p
I see I have librbd1 and librados2 at 0.72.2 (due to having qemu
installed on this machine). That could be the source of the problem,
I'll see if I can update them (I have pending updates I think), and
report back.
Cheers
Mark
On 26/03/14 12:23, Mark Kirkwood wrote:
Yeah, it seems possible,
Yeah, it seems possible, however I'm installing 'em all the same way (in
particular the 0.77 that works and the 0.77 that does not). The method is:
$ ./autogen.sh
$ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
--with-radosgw
$ time make
$ sudo make install
[probablly not r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi Mark
On 25/03/14 00:37, Mark Kirkwood wrote:
> I'm redeploying my development cluster after building 0.78 from src
> on Ubuntu 14.04. Ceph version is ceph version 0.78-325-ge5a4f5e.
Just so you know, 0.78 is now in Ubuntu 14.04; it should be fol
So I don't remember exactly the relationships, but /usr/bin/ceph is a
bit of python wrapping some libraries. I think it should be getting
the version number from the right place, but wonder if some of them
aren't being updated appropriately. How are you installing these
binaries?
In particular, tha
And more interestingly 0.77-601-ge92d602 from 25 Feb does *not* have
this issue - so looks like something in the 0.77 development between 25
Feb and 18 Mar is triggering this.
On 25/03/14 16:52, Mark Kirkwood wrote:
Further - checking with 0.77 from 18th Mar shows the same problem, but
0.73 fr
Further - checking with 0.77 from 18th Mar shows the same problem, but
0.73 from 12 Dec 2013 does not have this issue. So anyway, looks like it
is not a 0.78 problem, but is some sort of problem!
Regards
Mark
On 25/03/14 15:09, Mark Kirkwood wrote:
Fresh clone and rebuild results in the same
Fresh clone and rebuild results in the same error.
$ /usr/bin/ceph --version
ceph version 0.78-325-ge5a4f5e (e5a4f5ed005c9349be94b19ef33d6fe08271c798)
/usr/bin/ceph-mon --version
ceph version 0.78-325-ge5a4f5e (e5a4f5ed005c9349be94b19ef33d6fe08271c798)
On 25/03/14 14:16, Mark Kirkwood wrote:
Ye
Yeah, that is my feeling too - however both ceph and ceph-mon claim to
be the same version...and the dates on the various binaries are all
today. But I'll rebuild anyway to double check!
Thanks
Mark
On 25/03/14 13:57, Gregory Farnum wrote:
That is pretty strange, but I think probably there's
That is pretty strange, but I think probably there's somehow a mismatch
between the installed versions. Can you check with the --version flag on
both binaries?
On Monday, March 24, 2014, Mark Kirkwood
wrote:
> Hi,
>
> I'm redeploying my development cluster after building 0.78 from src on
> Ubunt
Hi,
I'm redeploying my development cluster after building 0.78 from src on
Ubuntu 14.04. Ceph version is ceph version 0.78-325-ge5a4f5e.
So proceeding as usual:
$ ceph-deploy new vedavec
$ ceph-deploy mon create vedavec
The monitor comes up:
[vedavec][DEBUG ]
**
11 matches
Mail list logo
