Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Paul Mansfield]

On 23/09/15 15:11, Jason Dillaman wrote:
> It looks like the issue you are experiencing was fixed in the 
> Infernalis/master branches [1].  I've opened a new tracker ticket to backport 
> the fix to Hammer [2].

thanks for that

we managed to build ceph using the SRPM (having tried and failed at git
cloning or following the instructions on the wiki).

We found we were able to add --without-lttng to the .SPEC file, and then
if we replaced *just* libradosstriper with the rpm just built, our
programs didn't crash, confirming that libradosstriper is trying to
initialise lttng and clashing.
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Paul Mansfield]

On 22/09/15 19:48, Jason Dillaman wrote:
> It's not the best answer, but it is the reason why it is currently
> disabled on RHEL 7.  Best bet for finding a long-term solution is
> still probably attaching with gdb and catching the abort function
> call.  Once the offending probe can be found, we can figure out how to
fix it.

I tried gdb and strace. I didn't find anything that gave me any insight.

Here's running it with gdb. I've not used gdb in anger in years, so
quite possibly I'm doing it wrongly

$ gdb ./testprogram
GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1)
Copyright (C) 2010 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later

This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-redhat-linux-gnu".
For bug reporting instructions, please see:
...
Reading symbols from /foo/bar/testprogram...done.
(gdb) handle SIGABRT stop nopass
SignalStop  Print   Pass to program Description
SIGABRT   Yes   Yes No  Aborted
(gdb) start
Temporary breakpoint 1 at 0x4017ac: file testprogram, line 184.
Starting program: /foo/bar/testprogram
[Thread debugging using libthread_db enabled]
[New Thread 0x7fffed9da700 (LWP 53014)]
[New Thread 0x7fffed1d9700 (LWP 53015)]
LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
registration of tracepoint probes having the same name is not allowed.

Program received signal SIGABRT, Aborted.
0x724b8925 in raise () from /lib64/libc.so.6
Missing separate debuginfos, use: debuginfo-install
CUnit-2.1.2-6.el6.x86_64 boost-system-1.41.0-18.el6.x86_64
boost-thread-1.41.0-18.el6.x86_64 cassandra-cpp-driver-2.0.1-1.el6.amd64
glibc-2.12-1.132.el6.x86_64 keyutils-libs-1.4-4.el6.x86_64
krb5-libs-1.10.3-15.el6_5.1.x86_64 libcom_err-1.41.12-18.el6.x86_64
libgcc-4.4.7-4.el6.x86_64 librados2-0.94.3-0.el6.x86_64
libradosstriper1-0.94.3-0.el6.x86_64
libselinux-2.0.94-5.3.el6_4.1.x86_64 libstdc++-4.4.7-4.el6.x86_64
libuuid-2.17.2-12.14.el6.x86_64 libuv-1.2.1-1.el6.x86_64
lttng-ust-2.4.1-1.el6.x86_64 nspr-4.10.2-1.el6_5.x86_64
nss-3.15.3-6.el6_5.x86_64 nss-util-3.15.3-1.el6_5.x86_64
openssl-1.0.1e-16.el6_5.7.x86_64 userspace-rcu-0.7.7-1.el6.x86_64
zlib-1.2.3-29.el6.x86_64
(gdb) backtrace
#0  0x724b8925 in raise () from /lib64/libc.so.6
#1  0x724ba105 in abort () from /lib64/libc.so.6
#2  0x758c58f4 in ?? () from /usr/lib64/librados.so.2
#3  0x758f4936 in ?? () from /usr/lib64/librados.so.2
#4  0x7fffe9a8 in ?? ()
#5  0x0001 in ?? ()
#6  0x7fffe9a8 in ?? ()
#7  0x7555f51b in _init () from /usr/lib64/librados.so.2
#8  0x77fea000 in ?? ()
#9  0x77deb555 in _dl_init_internal () from
/lib64/ld-linux-x86-64.so.2
#10 0x77dddb3a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#11 0x0001 in ?? ()
#12 0x7fffec44 in ?? ()
#13 0x in ?? ()



This didn't tell me much. I tried using "nm" on the librados and
libradosstriper libraries and there was no symbol information.


I also tried strace which revealed two sub processes

$ grep "/dev/shm/lttng-ust" strace.out
[pid 49682] open("/dev/shm/lttng-ust-wait-5",
O_RDONLY|O_NOFOLLOW|O_CLOEXEC) = 3
[pid 49683] open("/dev/shm/lttng-ust-wait-5-2489",
O_RDONLY|O_NOFOLLOW|O_CLOEXEC) = 3



$ grep "pid 49682" strace.out | more
[pid 49682] set_robust_list(0x7fe69cb5b9e0, 0x18 
[pid 49682] <... set_robust_list resumed> ) = 0
[pid 49682] socket(PF_FILE, SOCK_STREAM, 0 
[pid 49682] <... socket resumed> )  = 3
[pid 49682] fcntl(3, F_SETFD, FD_CLOEXECProcess 49683 attached
[pid 49682] connect(3, {sa_family=AF_FILE,
path="/var/run/lttng/lttng-ust-sock-5"}, 110 
[pid 49682] <... connect resumed> ) = -1 ENOENT (No such file or
directory)
[pid 49682] close(3 
[pid 49682] <... close resumed> )   = 0
[pid 49682] statfs("/dev/shm/",  
[pid 49682] <... statfs resumed> {f_type=0x1021994, f_bsize=4096,
f_blocks=8242437, f_bfree=8242435, f_bavail=8242435, f_files=8242437,
f_ffree=8242434, f_fsid={0, 0}, f_n
amelen=255, f_frsize=4096}) = 0
[pid 49682] futex(0x7fe69fd6b300, FUTEX_WAKE_PRIVATE, 2147483647) = 0
[pid 49682] open("/dev/shm/lttng-ust-wait-5",
O_RDONLY|O_NOFOLLOW|O_CLOEXEC) = 3
[pid 49682] fcntl(3, F_GETFD)   = 0x1 (flags FD_CLOEXEC)
[pid 49682] read(3, "\0\0\0\0", 4)  = 4
[pid 49682] mmap(NULL, 4096, PROT_READ, MAP_SHARED, 3, 0) = 0x7fe6a717b000
[pid 49682] close(3)= 0
[pid 49682] futex(0x7fe6a13f15e0, FUTEX_WAKE_PRIVATE, 1) = 1
[pid 49682] futex(0x7fe6a717b000, FUTEX_WAIT, 0, NULL 
[pid 49682] +++ killed by SIGABRT (core dumped) +++


$ grep "pid 49683" strace.out | more
[pid 49683] set_robust_list(0x7fe69c35a9e0, 0x18 
[pid 49683] <... set_robust_list resumed> ) = 0
[pid 49683] 

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Jason Dillaman]

It looks like the issue you are experiencing was fixed in the Infernalis/master 
branches [1].  I've opened a new tracker ticket to backport the fix to Hammer 
[2].

-- 

Jason Dillaman 

[1] 
https://github.com/sponce/ceph/commit/e4c27d804834b4a8bc495095ccf5103f8ffbcc1e
[2] http://tracker.ceph.com/issues/13210

- Original Message -
> From: "Paul Mansfield" <paul.mansfi...@alcatel-lucent.com>
> To: "Jason Dillaman" <dilla...@redhat.com>
> Cc: ceph-users@lists.ceph.com
> Sent: Wednesday, September 23, 2015 6:25:36 AM
> Subject: Re: [ceph-users] lttng duplicate registration problem when using 
> librados2 and libradosstriper
> 
> On 22/09/15 19:48, Jason Dillaman wrote:
> > It's not the best answer, but it is the reason why it is currently
> > disabled on RHEL 7.  Best bet for finding a long-term solution is
> > still probably attaching with gdb and catching the abort function
> > call.  Once the offending probe can be found, we can figure out how to
> fix it.
> 
> I tried gdb and strace. I didn't find anything that gave me any insight.
> 
> Here's running it with gdb. I've not used gdb in anger in years, so
> quite possibly I'm doing it wrongly
> 
> $ gdb ./testprogram
> GNU gdb (GDB) Red Hat Enterprise Linux (7.2-60.el6_4.1)
> Copyright (C) 2010 Free Software Foundation, Inc.
> License GPLv3+: GNU GPL version 3 or later
> <http://gnu.org/licenses/gpl.html>
> This is free software: you are free to change and redistribute it.
> There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
> and "show warranty" for details.
> This GDB was configured as "x86_64-redhat-linux-gnu".
> For bug reporting instructions, please see:
> <http://www.gnu.org/software/gdb/bugs/>...
> Reading symbols from /foo/bar/testprogram...done.
> (gdb) handle SIGABRT stop nopass
> SignalStop  Print   Pass to program Description
> SIGABRT   Yes   Yes No  Aborted
> (gdb) start
> Temporary breakpoint 1 at 0x4017ac: file testprogram, line 184.
> Starting program: /foo/bar/testprogram
> [Thread debugging using libthread_db enabled]
> [New Thread 0x7fffed9da700 (LWP 53014)]
> [New Thread 0x7fffed1d9700 (LWP 53015)]
> LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
> registration of tracepoint probes having the same name is not allowed.
> 
> Program received signal SIGABRT, Aborted.
> 0x724b8925 in raise () from /lib64/libc.so.6
> Missing separate debuginfos, use: debuginfo-install
> CUnit-2.1.2-6.el6.x86_64 boost-system-1.41.0-18.el6.x86_64
> boost-thread-1.41.0-18.el6.x86_64 cassandra-cpp-driver-2.0.1-1.el6.amd64
> glibc-2.12-1.132.el6.x86_64 keyutils-libs-1.4-4.el6.x86_64
> krb5-libs-1.10.3-15.el6_5.1.x86_64 libcom_err-1.41.12-18.el6.x86_64
> libgcc-4.4.7-4.el6.x86_64 librados2-0.94.3-0.el6.x86_64
> libradosstriper1-0.94.3-0.el6.x86_64
> libselinux-2.0.94-5.3.el6_4.1.x86_64 libstdc++-4.4.7-4.el6.x86_64
> libuuid-2.17.2-12.14.el6.x86_64 libuv-1.2.1-1.el6.x86_64
> lttng-ust-2.4.1-1.el6.x86_64 nspr-4.10.2-1.el6_5.x86_64
> nss-3.15.3-6.el6_5.x86_64 nss-util-3.15.3-1.el6_5.x86_64
> openssl-1.0.1e-16.el6_5.7.x86_64 userspace-rcu-0.7.7-1.el6.x86_64
> zlib-1.2.3-29.el6.x86_64
> (gdb) backtrace
> #0  0x724b8925 in raise () from /lib64/libc.so.6
> #1  0x724ba105 in abort () from /lib64/libc.so.6
> #2  0x758c58f4 in ?? () from /usr/lib64/librados.so.2
> #3  0x758f4936 in ?? () from /usr/lib64/librados.so.2
> #4  0x7fffe9a8 in ?? ()
> #5  0x0001 in ?? ()
> #6  0x7fffe9a8 in ?? ()
> #7  0x7555f51b in _init () from /usr/lib64/librados.so.2
> #8  0x77fea000 in ?? ()
> #9  0x77deb555 in _dl_init_internal () from
> /lib64/ld-linux-x86-64.so.2
> #10 0x77dddb3a in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
> #11 0x0001 in ?? ()
> #12 0x7fffec44 in ?? ()
> #13 0x in ?? ()
> 
> 
> 
> This didn't tell me much. I tried using "nm" on the librados and
> libradosstriper libraries and there was no symbol information.
> 
> 
> I also tried strace which revealed two sub processes
> 
> $ grep "/dev/shm/lttng-ust" strace.out
> [pid 49682] open("/dev/shm/lttng-ust-wait-5",
> O_RDONLY|O_NOFOLLOW|O_CLOEXEC) = 3
> [pid 49683] open("/dev/shm/lttng-ust-wait-5-2489",
> O_RDONLY|O_NOFOLLOW|O_CLOEXEC) = 3
> 
> 
> 
> $ grep "pid 49682" strace.out | more
> [pid 49682] set_robust_list(0x7fe69cb5b9e0, 0x18 
> [pid 49682] <... set_robust_list resumed> ) = 0
> [pid 49682] socket(PF_FILE, SOCK_STREAM, 0 
> [pid 49682] <... socket resumed> 

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Paul Mansfield]

On 22/09/15 19:48, Jason Dillaman wrote:
>> On 22/09/15 17:46, Jason Dillaman wrote:
>>> As a background, I believe LTTng-UST is disabled for RHEL7 in the Ceph
>>> project only due to the fact that EPEL 7 doesn't provide the required
>>> packages [1].
>>
>> interesting. so basically our program might only work on RHEL7 by accident!!
>>
> 
> It's not the best answer, but it is the reason why it is currently disabled 
> on RHEL 7.  Best bet for finding a long-term solution is still probably 
> attaching with gdb and catching the abort function call.  Once the offending 
> probe can be found, we can figure out how to fix it.

thanks, we will try that.

is it possible in the meanwhile to build some R6 packages with tracing
disabled?


___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Jason Dillaman]

As a background, I believe LTTng-UST is disabled for RHEL7 in the Ceph project 
only due to the fact that EPEL 7 doesn't provide the required packages [1].

[1] https://bugzilla.redhat.com/show_bug.cgi?id=1235461

-- 

Jason Dillaman 


- Original Message -
> From: "Paul Mansfield" <paul.mansfi...@alcatel-lucent.com>
> To: ceph-users@lists.ceph.com
> Sent: Tuesday, September 22, 2015 12:35:11 PM
> Subject: Re: [ceph-users] lttng duplicate registration problem when using 
> librados2 and libradosstriper
> 
> On 18/09/15 17:15, Paul Mansfield wrote:
> > LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
> > registration of tracepoint probes having the same name is not allowed.
> > /bin/sh: line 1: 61001 Aborted (core dumped) ./$test
> 
> I have made an interesting discovery. I was building my test program on
> and for Red Hat Enterprise Linux version 6*, using the rpm files with
> version -0.94.3-0.el6.x86_64. This gives me the lttng clash.
> 
> 
> I then took a RHEL7.1 box and build my test program against the el7
> versions of the packages (namely 0.94.3-0.el7.x86_64) and it works just
> fine, no problems with lttng clashes at all.
> 
> 
> When I examine the libraries for differences using ldd, I find that the
> el7 versions don't need lttng at all, but the el6 do.
> 
> 
> So it appears that the el6 libraries had -WITH-LTTNG enabled when they
> were built, but the el7 don't.
> 
> 
> I've tried building ceph from sources on centos6 to get a copy of the
> libraries without lttng. I've tried both git cloning the hammer branch,
> or downloading the .tar.bz2 and using rpmbuild as per the wiki, but
> neither work, something always fails critically along the way :-(
> 
> 
> 
> * this target platform is already chosen, I can't change it, I'd like to
> switch to RHEL7 but sadly can't.
> ___
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> 
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Paul Mansfield]

On 22/09/15 17:46, Jason Dillaman wrote:
> As a background, I believe LTTng-UST is disabled for RHEL7 in the Ceph 
> project only due to the fact that EPEL 7 doesn't provide the required 
> packages [1].

interesting. so basically our program might only work on RHEL7 by accident!!


We got the EL7 lttng libraries from Efficios:
http://packages.efficios.com/

___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Jason Dillaman]

> On 22/09/15 17:46, Jason Dillaman wrote:
> > As a background, I believe LTTng-UST is disabled for RHEL7 in the Ceph
> > project only due to the fact that EPEL 7 doesn't provide the required
> > packages [1].
> 
> interesting. so basically our program might only work on RHEL7 by accident!!
> 

It's not the best answer, but it is the reason why it is currently disabled on 
RHEL 7.  Best bet for finding a long-term solution is still probably attaching 
with gdb and catching the abort function call.  Once the offending probe can be 
found, we can figure out how to fix it.

-- 

Jason Dillaman 
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Paul Mansfield]

On 18/09/15 17:15, Paul Mansfield wrote:
> LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
> registration of tracepoint probes having the same name is not allowed.
> /bin/sh: line 1: 61001 Aborted (core dumped) ./$test

I have made an interesting discovery. I was building my test program on
and for Red Hat Enterprise Linux version 6*, using the rpm files with
version -0.94.3-0.el6.x86_64. This gives me the lttng clash.


I then took a RHEL7.1 box and build my test program against the el7
versions of the packages (namely 0.94.3-0.el7.x86_64) and it works just
fine, no problems with lttng clashes at all.


When I examine the libraries for differences using ldd, I find that the
el7 versions don't need lttng at all, but the el6 do.


So it appears that the el6 libraries had -WITH-LTTNG enabled when they
were built, but the el7 don't.


I've tried building ceph from sources on centos6 to get a copy of the
libraries without lttng. I've tried both git cloning the hammer branch,
or downloading the .tar.bz2 and using rpmbuild as per the wiki, but
neither work, something always fails critically along the way :-(



* this target platform is already chosen, I can't change it, I'd like to
switch to RHEL7 but sadly can't.
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Paul Mansfield]

Thanks. I read the notes about mixing dynamic and static libraries, but
at the moment I can't see why that affects me as I'm not doing anything
clever with linking, my makefile simply has "-lrados -lradosstriper" in
it, and I'm using gcc in a standard way.

If I used "ldd" and "nm" on the .o and executables it looks normal to me.

That said, we have a unique and special build system here which could be
doing something odd, but I have delved through the logs and the compiler
and linker options look sane.

thanks for your time


On 21/09/15 18:14, Jason Dillaman wrote:
> This is usually indicative of the same tracepoint event being included by 
> both a static and dynamic library.  See the following thread regarding this 
> issue within Ceph when LTTng-ust was first integrated [1].  Since I don't 
> have any insight into your application, are you somehow linking against Ceph 
> static libraries?
> 
> [1] http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/20353
> 
> - Original Message -
>> From: "Nick Fisk" <n...@fisk.me.uk>
>> To: "Paul Mansfield" <paul.mansfi...@alcatel-lucent.com>, 
>> ceph-users@lists.ceph.com
>> Sent: Saturday, September 19, 2015 3:10:02 AM
>> Subject: Re: [ceph-users] lttng duplicate registration problem when using 
>> librados2 and libradosstriper
>>
>> Hi Paul,
>>
>> I hit the same problem here (see last post):
>>
>> https://groups.google.com/forum/#!topic/bareos-users/mEzJ7IbDxvA
>>
>> If I ever get to the bottom of it, I will let you know. Sorry I can't be of
>> any more help.
>>
>> Nick
>>
>>> -Original Message-
>>> From: ceph-users [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of
>>> Paul Mansfield
>>> Sent: 18 September 2015 17:16
>>> To: ceph-users@lists.ceph.com
>>> Subject: [ceph-users] lttng duplicate registration problem when using
>>> librados2 and libradosstriper
>>>
>>> Hello,
>>> thanks for your attention.
>>>
>>> I have started using rados striper library, calling the functions from a C
>>> program.
>>>
>>> As soon as I add libradosstriper to the linking process, I get this error
>> when
>>> the program runs, even though I am not calling any functions from the
>> rados
>>> striper library (I commented them out).
>>>
>>> LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
>>> registration of tracepoint probes having the same name is not allowed.
>>> /bin/sh: line 1: 61001 Aborted (core dumped) ./$test
>>>
>>>
>>> I had been using lttng in my program but removed it to ensure it wasn't
>>> causing the problem.
>>>
>>> I have tried running the program using gdb but the calls to initialise
>> lttng occur
>>> before main() is called and so I cannot add a break point to see what is
>>> happening.
>>>
>>>
>>> thanks
>>> Paul
>>> ___
>>> ceph-users mailing list
>>> ceph-users@lists.ceph.com
>>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>
>>
>>
>>
>> ___
>> ceph-users mailing list
>> ceph-users@lists.ceph.com
>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
>>

-- 
Paul Mansfield
DevOps Engineer

___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Jason Dillaman]

You can run the program under 'gdb' with a breakpoint on the 'abort' function 
to catch the program's abnormal exit.  Assuming you have debug symbols 
installed, you should hopefully be able to see which probe is being 
re-registered.

-- 

Jason Dillaman 


- Original Message -
> From: "Paul Mansfield" <paul.mansfi...@alcatel-lucent.com>
> To: "Jason Dillaman" <dilla...@redhat.com>, "Nick Fisk" <n...@fisk.me.uk>
> Cc: ceph-users@lists.ceph.com
> Sent: Tuesday, September 22, 2015 5:28:51 AM
> Subject: Re: [ceph-users] lttng duplicate registration problem when using 
> librados2 and libradosstriper
> 
> 
> Thanks. I read the notes about mixing dynamic and static libraries, but
> at the moment I can't see why that affects me as I'm not doing anything
> clever with linking, my makefile simply has "-lrados -lradosstriper" in
> it, and I'm using gcc in a standard way.
> 
> If I used "ldd" and "nm" on the .o and executables it looks normal to me.
> 
> That said, we have a unique and special build system here which could be
> doing something odd, but I have delved through the logs and the compiler
> and linker options look sane.
> 
> thanks for your time
> 
> 
> On 21/09/15 18:14, Jason Dillaman wrote:
> > This is usually indicative of the same tracepoint event being included by
> > both a static and dynamic library.  See the following thread regarding
> > this issue within Ceph when LTTng-ust was first integrated [1].  Since I
> > don't have any insight into your application, are you somehow linking
> > against Ceph static libraries?
> > 
> > [1] http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/20353
> > 
> > - Original Message -
> >> From: "Nick Fisk" <n...@fisk.me.uk>
> >> To: "Paul Mansfield" <paul.mansfi...@alcatel-lucent.com>,
> >> ceph-users@lists.ceph.com
> >> Sent: Saturday, September 19, 2015 3:10:02 AM
> >> Subject: Re: [ceph-users] lttng duplicate registration problem when using
> >> librados2 and libradosstriper
> >>
> >> Hi Paul,
> >>
> >> I hit the same problem here (see last post):
> >>
> >> https://groups.google.com/forum/#!topic/bareos-users/mEzJ7IbDxvA
> >>
> >> If I ever get to the bottom of it, I will let you know. Sorry I can't be
> >> of
> >> any more help.
> >>
> >> Nick
> >>
> >>> -Original Message-
> >>> From: ceph-users [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of
> >>> Paul Mansfield
> >>> Sent: 18 September 2015 17:16
> >>> To: ceph-users@lists.ceph.com
> >>> Subject: [ceph-users] lttng duplicate registration problem when using
> >>> librados2 and libradosstriper
> >>>
> >>> Hello,
> >>> thanks for your attention.
> >>>
> >>> I have started using rados striper library, calling the functions from a
> >>> C
> >>> program.
> >>>
> >>> As soon as I add libradosstriper to the linking process, I get this error
> >> when
> >>> the program runs, even though I am not calling any functions from the
> >> rados
> >>> striper library (I commented them out).
> >>>
> >>> LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
> >>> registration of tracepoint probes having the same name is not allowed.
> >>> /bin/sh: line 1: 61001 Aborted (core dumped) ./$test
> >>>
> >>>
> >>> I had been using lttng in my program but removed it to ensure it wasn't
> >>> causing the problem.
> >>>
> >>> I have tried running the program using gdb but the calls to initialise
> >> lttng occur
> >>> before main() is called and so I cannot add a break point to see what is
> >>> happening.
> >>>
> >>>
> >>> thanks
> >>> Paul
> >>> ___
> >>> ceph-users mailing list
> >>> ceph-users@lists.ceph.com
> >>> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >>
> >>
> >>
> >>
> >> ___
> >> ceph-users mailing list
> >> ceph-users@lists.ceph.com
> >> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> >>
> 
> --
> Paul Mansfield
> DevOps Engineer
> 
> 
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Jason Dillaman]

This is usually indicative of the same tracepoint event being included by both 
a static and dynamic library.  See the following thread regarding this issue 
within Ceph when LTTng-ust was first integrated [1].  Since I don't have any 
insight into your application, are you somehow linking against Ceph static 
libraries?

[1] http://comments.gmane.org/gmane.comp.file-systems.ceph.devel/20353

- Original Message -
> From: "Nick Fisk" <n...@fisk.me.uk>
> To: "Paul Mansfield" <paul.mansfi...@alcatel-lucent.com>, 
> ceph-users@lists.ceph.com
> Sent: Saturday, September 19, 2015 3:10:02 AM
> Subject: Re: [ceph-users] lttng duplicate registration problem when using 
> librados2 and libradosstriper
> 
> Hi Paul,
> 
> I hit the same problem here (see last post):
> 
> https://groups.google.com/forum/#!topic/bareos-users/mEzJ7IbDxvA
> 
> If I ever get to the bottom of it, I will let you know. Sorry I can't be of
> any more help.
> 
> Nick
> 
> > -Original Message-
> > From: ceph-users [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of
> > Paul Mansfield
> > Sent: 18 September 2015 17:16
> > To: ceph-users@lists.ceph.com
> > Subject: [ceph-users] lttng duplicate registration problem when using
> > librados2 and libradosstriper
> > 
> > Hello,
> > thanks for your attention.
> > 
> > I have started using rados striper library, calling the functions from a C
> > program.
> > 
> > As soon as I add libradosstriper to the linking process, I get this error
> when
> > the program runs, even though I am not calling any functions from the
> rados
> > striper library (I commented them out).
> > 
> > LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
> > registration of tracepoint probes having the same name is not allowed.
> > /bin/sh: line 1: 61001 Aborted (core dumped) ./$test
> > 
> > 
> > I had been using lttng in my program but removed it to ensure it wasn't
> > causing the problem.
> > 
> > I have tried running the program using gdb but the calls to initialise
> lttng occur
> > before main() is called and so I cannot add a break point to see what is
> > happening.
> > 
> > 
> > thanks
> > Paul
> > ___
> > ceph-users mailing list
> > ceph-users@lists.ceph.com
> > http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> 
> 
> 
> 
> ___
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com
> 
___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com

Re: [ceph-users] lttng duplicate registration problem when using librados2 and libradosstriper

[Nick Fisk]

Hi Paul,

I hit the same problem here (see last post):

https://groups.google.com/forum/#!topic/bareos-users/mEzJ7IbDxvA

If I ever get to the bottom of it, I will let you know. Sorry I can't be of
any more help.

Nick

> -Original Message-
> From: ceph-users [mailto:ceph-users-boun...@lists.ceph.com] On Behalf Of
> Paul Mansfield
> Sent: 18 September 2015 17:16
> To: ceph-users@lists.ceph.com
> Subject: [ceph-users] lttng duplicate registration problem when using
> librados2 and libradosstriper
> 
> Hello,
> thanks for your attention.
> 
> I have started using rados striper library, calling the functions from a C
> program.
> 
> As soon as I add libradosstriper to the linking process, I get this error
when
> the program runs, even though I am not calling any functions from the
rados
> striper library (I commented them out).
> 
> LTTng-UST: Error (-17) while registering tracepoint probe. Duplicate
> registration of tracepoint probes having the same name is not allowed.
> /bin/sh: line 1: 61001 Aborted (core dumped) ./$test
> 
> 
> I had been using lttng in my program but removed it to ensure it wasn't
> causing the problem.
> 
> I have tried running the program using gdb but the calls to initialise
lttng occur
> before main() is called and so I cannot add a break point to see what is
> happening.
> 
> 
> thanks
> Paul
> ___
> ceph-users mailing list
> ceph-users@lists.ceph.com
> http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com




___
ceph-users mailing list
ceph-users@lists.ceph.com
http://lists.ceph.com/listinfo.cgi/ceph-users-ceph.com