9 Mar
2020
9 Mar
'20
7:20 p.m.
Hmm, quite strange, the function exists, defined in src/core/basex.c:
$ ag --cc base64url_dec
src/core/basex.h
868:int base64url_dec(char *in, int ilen, char *out, int osize);
src/core/basex.c
465:int base64url_dec(char *in, int ilen, char *out, int osize)
src/modules/pv/pv_trans.c
552: i = base64url_dec(val->rs.s, val->rs.len,
597: i = base64url_dec(st.s, st.len,
600: i = base64url_dec(val->rs.s, val->rs.len,
What operating system are you using and is the version of the c compiler?
Cheers,
Daniel
On 09.03.20 16:17, Stefan Mititelu wrote:
Indeed, "journalctl -xe" truncated the error msg... sorry for not
checking that.
Here it is from syslog:
Mar 9 17:13:05 LXBU-GRPF8S2 kamailio: ERROR: <core>
[core/sr_module.c:512]: load_module(): could not open module
</usr/local/lib64/kamailio/modules/pv.so>:
/usr/local/lib64/kamailio/modules/pv.so: *undefined symbol: base64url_dec*
Just as a double check I did:
~/kamailio-upstream$ ls -lah /usr/local/lib64/kamailio/modules/pv.so
-rwxr-xr-x 1 root root 1,2M mar 9 17:13
/usr/local/lib64/kamailio/modules/pv.so
~/kamailio-upstream$ sudo cat /etc/systemd/system/kamailio.service
...
ExecStart=/sbin/kamailio -P /var/kamailio.pid -f
/etc/kamailio/kamailio.cfg -m 64 -M 128 -u root -g root
...
So the file exists and has proper access rights.
On 09.03.2020 17:01, Daniel-Constantin Mierla wrote:
> The error message doesn't show the real reason of not being able to load
> pv.so file, like a missing symbol (which was the case for the initial
> report in this thread). Maybe it is due to file permissions or file not
> being at that location for what so ever reason, can you check it?
--
Daniel-Constantin Mierla -- www.asipto.com
www.twitter.com/miconda -- www.linkedin.com/in/miconda
Kamailio Advanced Training - March 9-11, 2020, Berlin - www.asipto.com
Kamailio World Conference - April 27-29, 2020, in Berlin -- www.kamailioworld.com