Hi Brian, When the "group_radius" module was integrated into "group", a debug print message accidentally became an error print message . So your hunch was correct, the Failure was actually the result for the query, not an actual error. I committed the fix on trunk and also the 1.6 branch. Please update and let me know if there are any other problems.
Regards, Irina Stanescu opensipsl...@encambio.com wrote: > Hello List, > > On tues., dec 08, 2009, opensipsl...@encambio.com wrote: > >> In my config file I have (a few times): >> >> # check if user is suspended >> if (aaa_is_user_in("From", "suspended")) { >> send_reply("403", "Forbidden"); >> exit; >> } >> >> ...and I see in the log: >> >> Dec 08 23:03:47 name.host.tld <error> opensips[14400]: >> ERROR:group:aaa_is_user_in: Failure >> >> I'm using: >> >> Radiusclient-ng 0.5.6 >> Freeradius 2.1.3 >> OpenSIPS 1.6.0 with TLS >> >> > ...on Solaris 11 x86 (nv-b91). > > >> I'm trying to migrate from 1.3.X to 1.6.0, but don't see what I'm >> doing wrong. Any ideas? >> >> > Can it be that 'ERROR' and 'Failure' in the log file describe the > result of the aaa_is_user_in query instead of its exit status? I > can't imagine it, but maybe the module writer decided that this > function reports errors when it simply finds no user in the group? > > Thanks, > Brian > > _______________________________________________ > Users mailing list > Users@lists.opensips.org > http://lists.opensips.org/cgi-bin/mailman/listinfo/users > > _______________________________________________ Users mailing list Users@lists.opensips.org http://lists.opensips.org/cgi-bin/mailman/listinfo/users