Comments (15)
On CentOS 6.5, I have xmlrpc-c-1.16.24-1210.1840.el6.x86_64 installed and it works just fine with that version. It doesn't have a "libxmlrpc_xmlparse" library though, and I don't see a newer version of xmlrpc-c available in the repository.
Note that on my installation, it looks in /usr/lib64/ for .so files, not /usr/lib/ (which is used for 32-bit libs)
You can run "ldd" on the compiled rtpengine binary to see where it's trying to pull libraries from, and which ones.
from rtpengine.
Hi,
Thank you very much for the response.
I followed your advice and ldd rtpengine was great, however I still have the following library missing and cant see it anywhere;
libxmlrpc_xmltok.so.3 is n
Will try and find it, thanks for the help!
Jon
Date: Wed, 25 Jun 2014 06:24:00 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [rtpengine] Installing rtpengine on Centos 6.5 (#7)
On CentOS 6.5, I have xmlrpc-c-1.16.24-1210.1840.el6.x86_64 installed and it works just fine with that version. It doesn't have a "libxmlrpc_xmlparse" library though, and I don't see a newer version of xmlrpc-c available in the repository.
Note that on my installation, it looks in /usr/lib64/ for .so files, not /usr/lib/ (which is used for 32-bit libs)
You can run "ldd" on the compiled rtpengine binary to see where it's trying to pull libraries from, and which ones.
—
Reply to this email directly or view it on GitHub.
from rtpengine.
hi Guys
Sorry to bother you again, Im still struggling with;
libxmlrpc_xmltok.so.3
I can see its not installed when doing an ldd rtpengine.
Is it associated with an old version of xmlrpc?
Thanks
Jon
ldd rtpengine linux-vdso.so.1 => (0x00007fff40777000) libdl.so.2 => /lib64/libdl.so.2 (0x0000003392200000) libm.so.6 => /lib64/libm.so.6 (0x0000003392a00000) libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x0000003393600000) libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x0000003394600000) librt.so.1 => /lib64/librt.so.1 (0x0000003392e00000) libz.so.1 => /lib64/libz.so.1 (0x0000003392600000) libssl.so.10 => /usr/lib64/libssl.so.10 (0x0000003397e00000) libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x0000003394a00000) libpcre.so.0 => /lib64/libpcre.so.0 (0x0000003399e00000) libxmlrpc_client.so.3 => /usr/lib64/libxmlrpc_client.so.3 (0x000000323de 00000) libxmlrpc.so.3 => /usr/lib64/libxmlrpc.so.3 (0x000000323ce00000) libxmlrpc_util.so.3 => /usr/lib64/libxmlrpc_util.so.3 (0x000000323f20000 0) libxmlrpc_xmlparse.so.3 => /usr/lib/libxmlrpc_xmlparse.so.3 (0x00007f0c1 b8f6000) libxmlrpc_xmltok.so.3 => not found libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x000000323e600000) libpthread.so.0 => /lib64/libpthread.so.0 (0x0000003391e00000) libc.so.6 => /lib64/libc.so.6 (0x0000003391a00000) /lib64/ld-linux-x86-64.so.2 (0x0000003391600000) libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x0000003396200000) libkrb5.so.3 => /lib64/libkrb5.so.3 (0x0000003395a00000) libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f0c1b6f0000) libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x0000003395200000) libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x0000003396e00000) libxmlrpc_xmltok.so.3 => not found libidn.so.11 => /lib64/libidn.so.11 (0x0000003398e00000) libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x000000323d600000) libssl3.so => /usr/lib64/libssl3.so (0x000000323d200000) libsmime3.so => /usr/lib64/libsmime3.so (0x000000323e200000) libnss3.so => /usr/lib64/libnss3.so (0x000000323da00000) libnssutil3.so => /usr/lib64/libnssutil3.so (0x000000323ca00000) libplds4.so => /lib64/libplds4.so (0x000000323c200000) libplc4.so => /lib64/libplc4.so (0x000000323ee00000) libnspr4.so => /lib64/libnspr4.so (0x000000323ea00000) libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x0000003399600000) libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x0000003395600000) libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x0000003396600000) libresolv.so.2 => /lib64/libresolv.so.2 (0x0000003393a00000) liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x000000323c600000) libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x0000003398a00000) libselinux.so.1 => /lib64/libselinux.so.1 (0x0000003393200000) libcrypt.so.1 => /lib64/libcrypt.so.1 (0x0000003393e00000) libfreebl3.so => /lib64/libfreebl3.so (0x0000003394200000)
Date: Wed, 25 Jun 2014 06:24:00 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [rtpengine] Installing rtpengine on Centos 6.5 (#7)
On CentOS 6.5, I have xmlrpc-c-1.16.24-1210.1840.el6.x86_64 installed and it works just fine with that version. It doesn't have a "libxmlrpc_xmlparse" library though, and I don't see a newer version of xmlrpc-c available in the repository.
Note that on my installation, it looks in /usr/lib64/ for .so files, not /usr/lib/ (which is used for 32-bit libs)
You can run "ldd" on the compiled rtpengine binary to see where it's trying to pull libraries from, and which ones.
—
Reply to this email directly or view it on GitHub.
from rtpengine.
Have you compiled rtpengine yourself on that same system, or did you copy the binary from a different system?
from rtpengine.
On the same system, shall I look to recompile again?
Many thanks
Date: Wed, 2 Jul 2014 06:33:47 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [rtpengine] Installing rtpengine on Centos 6.5 (#7)
Have you compiled rtpengine yourself on that same system, or did you copy the binary from a different system?
—
Reply to this email directly or view it on GitHub.
from rtpengine.
That's what I would suggest. I can't really help much because on my CentOS system, I have a different version of the xmlrpc-c package and it works fine with that.
from rtpengine.
Perhaps you have conflicting versions of the xmlrpc-c and the respective devel package? Check the output of
rpm -qa | grep xmlrpc
from rtpengine.
Hi Richard,
Thanks again for the suggestions, appreciate your time.output of rpm -qa | grep xmlrpc.
xmlrpc-c-1.16.24-1210.1840.el6.x86_64xmlrpc-c-client++-1.16.24-1210.1840.el6.x86_64xmlrpc-c-client-1.16.24-1210.1840.el6.x86_64xmlrpc-c-c++-1.16.24-1210.1840.el6.x86_64xmlrpc-c-devel-1.16.24-1210.1840.el6.x86_64
Ive also tried running make in relevant directories of rtpengine.
No look as yet, will keep digging.
Date: Wed, 2 Jul 2014 06:41:16 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [rtpengine] Installing rtpengine on Centos 6.5 (#7)
Perhaps you have conflicting versions of the xmlrpc-c and the respective devel package? Check the output of
rpm -qa | grep xmlrpc
—
Reply to this email directly or view it on GitHub.
from rtpengine.
This is the exact same version of xmlrpc-c that I have installed, but previously you mentioned that you're trying with a different version ("I have tried with xmlrpc-c-1.25.27 and .28"). Where did that come from? Did you install any libraries from sources other than the package management?
from rtpengine.
i tried to look for other versions but when it came to installing these required other dependencies so didn't want to go down that path.
I will look to remove xmlrpc, then re-install from packages.
Can I ask which repository you got xmlrpc from?
Mine is from base repository but I will check it again as this OS is from a vendor image.
And does it contain the libraries libxmlrpc_xmltok.so.3?
Date: Wed, 2 Jul 2014 07:48:45 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [rtpengine] Installing rtpengine on Centos 6.5 (#7)
This is the exact same version of xmlrpc-c that I have installed, but previously you mentioned that you're trying with a different version ("I have tried with xmlrpc-c-1.25.27 and .28"). Where did that come from? Did you install any libraries from sources other than the package management?
—
Reply to this email directly or view it on GitHub.
from rtpengine.
I installed it through yum from the official CentOS repo, and no it doesn't contain that file. Here's the status from my system:
[root@centos ~]# rpm -qa | grep xmlrpc
xmlrpc-c-c++-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-client-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-client++-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-devel-1.16.24-1210.1840.el6.x86_64
[root@centos ~]#
[root@centos ~]# find / -iname xmltok
[root@centos ~]#
[root@centos daemon]# ldd rtpengine
linux-vdso.so.1 => (0x00007fff71c3f000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f181c801000)
libm.so.6 => /lib64/libm.so.6 (0x00007f181c57d000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f181c277000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f181c073000)
librt.so.1 => /lib64/librt.so.1 (0x00007f181be6b000)
libz.so.1 => /lib64/libz.so.1 (0x00007f181bc54000)
libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f181b9e8000)
libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007f181b608000)
libpcre.so.0 => /lib64/libpcre.so.0 (0x00007f181b3db000)
libxmlrpc_client.so.3 => /usr/lib64/libxmlrpc_client.so.3 (0x00007f181b1d0000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f181afb3000)
libc.so.6 => /lib64/libc.so.6 (0x00007f181ac1e000)
libxmlrpc.so.3 => /usr/lib64/libxmlrpc.so.3 (0x00007f181aa0a000)
libxmlrpc_util.so.3 => /usr/lib64/libxmlrpc_util.so.3 (0x00007f181a806000)
/lib64/ld-linux-x86-64.so.2 (0x00007f181ca11000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f181a5c1000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f181a2db000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f181a0d7000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f1819eaa000)
libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f1819c56000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f1819902000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f18196f7000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f18194f4000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f18192da000)
libidn.so.11 => /lib64/libidn.so.11 (0x00007f18190a7000)
libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x00007f1818e5a000)
libssl3.so => /usr/lib64/libssl3.so (0x00007f1818c1c000)
libsmime3.so => /usr/lib64/libsmime3.so (0x00007f18189ef000)
libnss3.so => /usr/lib64/libnss3.so (0x00007f18186b1000)
libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007f1818485000)
libplds4.so => /lib64/libplds4.so (0x00007f1818280000)
libplc4.so => /lib64/libplc4.so (0x00007f181807b000)
libnspr4.so => /lib64/libnspr4.so (0x00007f1817e3e000)
libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007f1817c15000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f18179f6000)
liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f18177e6000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f18175cc000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f1817394000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007f181711d000)
[root@centos daemon]#
from rtpengine.
Weird, I wonder why I keep getting;
rtpenginertpengine: error while loading shared libraries: libxmlrpc_xmltok.so.3: cannot open shared object file: No such file or directory
Have I installed incorrect version?
I just did;
git clone https://github.com/sipwise/rtpengine.git
And make in relevant sub directories.
Thanks
Jon
Date: Wed, 2 Jul 2014 08:13:58 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [rtpengine] Installing rtpengine on Centos 6.5 (#7)
I installed it through yum from the official CentOS repo, and no it doesn't contain that file. Here's the status from my system:
[root@centos ~]# rpm -qa | grep xmlrpc
xmlrpc-c-c++-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-client-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-client++-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-1.16.24-1210.1840.el6.x86_64
xmlrpc-c-devel-1.16.24-1210.1840.el6.x86_64
[root@centos ~]#
[root@centos ~]# find / -iname xmltok
[root@centos ~]#
[root@centos daemon]# ldd rtpengine
linux-vdso.so.1 => (0x00007fff71c3f000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f181c801000)
libm.so.6 => /lib64/libm.so.6 (0x00007f181c57d000)
libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f181c277000)
libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f181c073000)
librt.so.1 => /lib64/librt.so.1 (0x00007f181be6b000)
libz.so.1 => /lib64/libz.so.1 (0x00007f181bc54000)
libssl.so.10 => /usr/lib64/libssl.so.10 (0x00007f181b9e8000)
libcrypto.so.10 => /usr/lib64/libcrypto.so.10 (0x00007f181b608000)
libpcre.so.0 => /lib64/libpcre.so.0 (0x00007f181b3db000)
libxmlrpc_client.so.3 => /usr/lib64/libxmlrpc_client.so.3 (0x00007f181b1d0000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f181afb3000)
libc.so.6 => /lib64/libc.so.6 (0x00007f181ac1e000)
libxmlrpc.so.3 => /usr/lib64/libxmlrpc.so.3 (0x00007f181aa0a000)
libxmlrpc_util.so.3 => /usr/lib64/libxmlrpc_util.so.3 (0x00007f181a806000)
/lib64/ld-linux-x86-64.so.2 (0x00007f181ca11000)
libgssapi_krb5.so.2 => /lib64/libgssapi_krb5.so.2 (0x00007f181a5c1000)
libkrb5.so.3 => /lib64/libkrb5.so.3 (0x00007f181a2db000)
libcom_err.so.2 => /lib64/libcom_err.so.2 (0x00007f181a0d7000)
libk5crypto.so.3 => /lib64/libk5crypto.so.3 (0x00007f1819eaa000)
libcurl.so.4 => /usr/lib64/libcurl.so.4 (0x00007f1819c56000)
libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f1819902000)
libkrb5support.so.0 => /lib64/libkrb5support.so.0 (0x00007f18196f7000)
libkeyutils.so.1 => /lib64/libkeyutils.so.1 (0x00007f18194f4000)
libresolv.so.2 => /lib64/libresolv.so.2 (0x00007f18192da000)
libidn.so.11 => /lib64/libidn.so.11 (0x00007f18190a7000)
libldap-2.4.so.2 => /lib64/libldap-2.4.so.2 (0x00007f1818e5a000)
libssl3.so => /usr/lib64/libssl3.so (0x00007f1818c1c000)
libsmime3.so => /usr/lib64/libsmime3.so (0x00007f18189ef000)
libnss3.so => /usr/lib64/libnss3.so (0x00007f18186b1000)
libnssutil3.so => /usr/lib64/libnssutil3.so (0x00007f1818485000)
libplds4.so => /lib64/libplds4.so (0x00007f1818280000)
libplc4.so => /lib64/libplc4.so (0x00007f181807b000)
libnspr4.so => /lib64/libnspr4.so (0x00007f1817e3e000)
libssh2.so.1 => /usr/lib64/libssh2.so.1 (0x00007f1817c15000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f18179f6000)
liblber-2.4.so.2 => /lib64/liblber-2.4.so.2 (0x00007f18177e6000)
libsasl2.so.2 => /usr/lib64/libsasl2.so.2 (0x00007f18175cc000)
libcrypt.so.1 => /lib64/libcrypt.so.1 (0x00007f1817394000)
libfreebl3.so => /lib64/libfreebl3.so (0x00007f181711d000)
[root@centos daemon]#
—
Reply to this email directly or view it on GitHub.
from rtpengine.
Yes, that's the correct version. Rtpengine doesn't link to that library directly, it goes by whatever the xmlrpc-c-config script tells it. If you run
xmlrpc-c-config client --libs
you can see the compile flags it will use for xmlrpc-c. This script comes out of the devel package.
It's also possible that it's not the rtpengine binary which links to this lib, but rather one of the other libs (recursive linking/dependency). You can check that by running ldd on the listed library files and see if this xmltok file pops up in one of them.
from rtpengine.
Thanks Richard, got it!
Its was in /usr/local/lib and the xmlrpc-c-config client --libs let me locate.
Thanks for that, the error have now cleared as I copied it into the /lib64
One last thing, then will leave you in peace!
if I now run rtpengine -v I get;
undefined.
Does this indicate I need to re-install again?
Sorry for taking up your valuable time.
Thanks
Jon
Date: Wed, 2 Jul 2014 08:34:42 -0700
From: [email protected]
To: [email protected]
CC: [email protected]
Subject: Re: [rtpengine] Installing rtpengine on Centos 6.5 (#7)
Yes, that's the correct version. Rtpengine doesn't link to that library directly, it goes by whatever the xmlrpc-c-config script tells it. If you run
xmlrpc-c-config client --libs
you can see the compile flags it will use for xmlrpc-c. This script comes out of the devel package.
It's also possible that it's not the rtpengine binary which links to this lib, but rather one of the other libs (recursive linking/dependency). You can check that by running ldd on the listed library files and see if this xmltok file pops up in one of them.
—
Reply to this email directly or view it on GitHub.
from rtpengine.
No, that's alright. The version is set automatically in the build scripts, but this only works if you're on a Debian system. We don't have any similar mechanism in place for other systems.
from rtpengine.
Related Issues (20)
- Sometimes DTLS cannot be negotiated HOT 2
- A code problem HOT 1
- Geting SIGFPE when trying restore calls from redis with enabled: "poller-per-thread"
- RTCP packets failing to be processed properly after starting a recording on a call. HOT 4
- RTP Engine two interfaces with private IPs HOT 2
- dtls-mtu param does not have any effect on RTPEngine HOT 5
- Codec / Transcoding information returned by ng query
- How to determine the multi-channel sequence of recording
- cannot compile mr8.5.12 HOT 2
- RFC 2833 issue - tripling of digits due to final 2 payloads getting new timestamp HOT 3
- Proposal to change this log from ERR to WARN HOT 1
- UBSAN: array-index-out-of-bounds in /var/lib/dkms/rtpengine/12.2.1.5/build/xt_RTPENGINE.c:5156:32
- compile rtpengine failed on ubuntu 22.04 with error "undefined reference to `av_channel_layout_default'" HOT 4
- SRTP output wanted, but no crypto suite was negotiated HOT 1
- rtpengine mr10.5 crashed in __dtx_send_later HOT 2
- `silent-timeout` not working HOT 1
- for rhel 8.9 mr11.5 there is an compilation issue HOT 1
- rtpengine not support H264 HOT 3
- call.h:921:7: error: unknown type name ‘__auto_type
- kamailio rtpengine re-INVITE HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from rtpengine.