As far as I can see, the new version of Kamailio requires radiusclient-ng,
although the current one old worked with freeradius-client.
Maybe there is a reason?


чт, 11 мая 2023 г. в 11:35, Denys Pozniak <[email protected]>:

> Hello!
>
> >Is it the same radius client library used for the two test cases?
> >It is the same operating system?
> >In other words, have you tried with the two version on exactly the same
> system?
>
> That's exactly what it is, in two cases the operating system and the
> radius library are the same, only the difference is in the version of
> Kamailio.
>
> CentOS Linux release 7.9.2009 (Core)
> freeradius-utils-3.0.13-15.el7.x86_64
> freeradius-3.0.13-15.el7.x86_64
> freeradius-client-1.1.7-16.el7.centos.x86_64
>
> I connected via strace to kamailio 5.6.4, maybe this output will somehow
> clarify the situation:
>
> ...
> write(2, " 0(20677) INFO: auth [auth_mod.c"..., 107 0(20677) INFO: auth
> [auth_mod.c:346]: mod_init(): qop set, but nonce-count (nonce_count)
> support disabled
> ) = 107
> write(2, " 0(20677) DEBUG: <core> [core/sr"..., 72 0(20677) DEBUG: <core>
> [core/sr_module.c:969]: init_mod(): auth_radius
> ) = 72
> open("/etc/radiusclient/radiusclient.conf", O_RDONLY) = 4
> fstat(4, {st_mode=S_IFREG|0644, st_size=487, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7f2df0119000
> read(4, "auth_order      radius,local\nlog"..., 4096) = 487
> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
> ENOENT (No such file or directory)
> close(5)                                = 0
> socket(AF_UNIX, SOCK_STREAM|SOCK_CLOEXEC|SOCK_NONBLOCK, 0) = 5
> connect(5, {sa_family=AF_UNIX, sun_path="/var/run/nscd/socket"}, 110) = -1
> ENOENT (No such file or directory)
> close(5)                                = 0
> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7f2df0118000
> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
> read(5, " 74/udp                         "..., 4096) = 4096
> read(5, "     # Quick Mail Transfer Proto"..., 4096) = 4096
> read(5, "    636/udp                     "..., 4096) = 4096
> read(5, "          # Microsoft-SQL-Monito"..., 4096) = 4096
> close(5)                                = 0
> munmap(0x7f2df0118000, 4096)            = 0
> open("/etc/services", O_RDONLY|O_CLOEXEC) = 5
> fstat(5, {st_mode=S_IFREG|0644, st_size=670293, ...}) = 0
> mmap(NULL, 4096, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS, -1, 0) =
> 0x7f2df0118000
> read(5, "# /etc/services:\n# $Id: services"..., 4096) = 4096
> read(5, " 74/udp                         "..., 4096) = 4096
> read(5, "     # Quick Mail Transfer Proto"..., 4096) = 4096
> read(5, "    636/udp                     "..., 4096) = 4096
> read(5, "          # Microsoft-SQL-Monito"..., 4096) = 4096
> close(5)                                = 0
> munmap(0x7f2df0118000, 4096)            = 0
> socket(AF_UNIX, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 5
> connect(5, {sa_family=AF_UNIX, sun_path="/dev/log"}, 110) = 0
> sendto(5, "<11>May 11 10:20:50 kamailio: /e"..., 113, MSG_NOSIGNAL, NULL,
> 0) = 113
> close(4)                                = 0
> munmap(0x7f2df0119000, 4096)            = 0
> write(2, " 0(20677) ERROR: auth_radius [au"..., 97 0(20677) ERROR:
> auth_radius [auth_radius.c:123]: mod_init(): failed to open configuration
> file
> ) = 97
> write(2, " 0(20677) ERROR: <core> [core/sr"..., 149 0(20677) ERROR: <core>
> [core/sr_module.c:975]: init_mod(): Error while initializing module
> auth_radius (/usr/lib64/kamailio/modules/auth_radius.so)
> ) = 149
> write(2, "ERROR: error while initializing "..., 40ERROR: error while
> initializing modules
> ) = 40
> rt_sigaction(SIGALRM, {sa_handler=0x41f3af, sa_mask=[ALRM],
> sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f2def23b400},
> {sa_handler=SIG_DFL, sa_mask=[], sa_flags=0}, 8) = 0
> alarm(60)                               = 0
> wait4(-1, NULL, 0, NULL)                = -1 ECHILD (No child processes)
> rt_sigaction(SIGALRM, {sa_handler=0x41f3c6, sa_mask=[ALRM],
> sa_flags=SA_RESTORER|SA_RESTART, sa_restorer=0x7f2def23b400},
> {sa_handler=0x41f3af, sa_mask=[ALRM], sa_flags=SA_RESTORER|SA_RESTART,
> sa_restorer=0x7f2def23b400}, 8) = 0
> write(2, " 0(20677) DEBUG: <core> [core/sr"..., 98 0(20677) DEBUG: <core>
> [core/sr_module.c:835]: destroy_modules(): starting modules destroy phase
>
>
>
>
>
> чт, 11 мая 2023 г. в 09:50, Daniel-Constantin Mierla <[email protected]>:
>
>> Hello,
>>
>> On 10.05.23 22:40, Victor Seva wrote:
>> > Hi,
>> >
>> > On 10/5/23 16:36, Denys Pozniak wrote:
>> >> Hello!
>> >>
>> >> After a major upgrade of Kamailio (5.1 -> 5.6), an error appears that
>> >> it is not possible to open configuration file (I think this is about
>> >> /etc/radiusclient/radiusclient.conf), although it exists with the
>> >> necessary access rights:
>> >> /0(27075) DEBUG: <core> [core/sr_module.c:969]: init_mod(): auth_radius
>> >> 0(27075) ERROR: auth_radius [auth_radius.c:123]: mod_init(): failed
>> >> to open configuration file
>> >> 0(27075) ERROR: <core> [core/sr_module.c:975]: init_mod(): Error
>> >> while initializing module auth_radius
>> >> (/usr/lib64/kamailio/modules/auth_radius.so)
>> >> ERROR: error while initializing modules
>> >> /
>> >> For the test, I made Kamailio downgrade back to 5.1 and the problem
>> >> went away.
>> >> Shortened the Kamailio config to the minimum for reproducing the
>> >> problem:
>> >>
>> >> /#!KAMAILIO
>> >> memdbg=5
>> >> memlog=5
>> >> children=1
>> >> log_stderror=no
>> >> listen=udp:127.0.0.1:5060 <http://127.0.0.1:5060>
>> >> loadmodule "kex.so"
>> >> loadmodule "corex.so"
>> >> loadmodule "tm.so"
>> >> loadmodule "sl.so"
>> >> loadmodule "rr.so"
>> >> loadmodule "pv.so"
>> >> loadmodule "maxfwd.so"
>> >> loadmodule "auth.so"
>> >> loadmodule "auth_radius.so"
>> >> modparam("auth_radius", "radius_config",
>> >> "/etc/radiusclient/radiusclient.conf")
>> >>
>> >> request_route {
>> >>          return;
>> >> }
>> >> /
>> >>
>> >> Could the commit below somehow affect the acceptance of the
>> >> radius_config module parameter?
>> >>
>> https://github.com/kamailio/kamailio/commit/f33ba318b20cbd2b34d278a7e2c4e64129b9e68d
>> >> <
>> https://github.com/kamailio/kamailio/commit/f33ba318b20cbd2b34d278a7e2c4e64129b9e68d
>> >
>> >>
>> >>
>> >
>> > No, I don't think so.
>>
>>
>> Indeed, that commit should not change anything.
>>
>> Looking at the code, it is rc_read_config() that fails -- this is not a
>> function implemented inside kamailio, being from radius client library.
>>
>> Is it the same radius client library used for the two test cases? It is
>> the same operating system? In other words, have you tried with the two
>> version on exactly the same system?
>>
>> Cheers,
>> Daniel
>>
>> --
>> Daniel-Constantin Mierla -- www.asipto.com
>> www.twitter.com/miconda -- www.linkedin.com/in/miconda
>> Kamailio World Conference - June 5-7, 2023 - www.kamailioworld.com
>>
>> __________________________________________________________
>> Kamailio - Users Mailing List - Non Commercial Discussions
>> To unsubscribe send an email to [email protected]
>> Important: keep the mailing list in the recipients, do not reply only to
>> the sender!
>> Edit mailing list options or unsubscribe:
>>
>
>
> --
>
> BR,
> Denys Pozniak
>
>
>

-- 

BR,
Denys Pozniak
__________________________________________________________
Kamailio - Users Mailing List - Non Commercial Discussions
To unsubscribe send an email to [email protected]
Important: keep the mailing list in the recipients, do not reply only to the 
sender!
Edit mailing list options or unsubscribe:

Reply via email to