Steve Edwards wrote:
I must have missed the memo, but the repos vanished on 2016-09-25
causing all of my 'yum update's to fail.
Am I'm the only one using the repos?
You are not, there's been multiple reports about it being broken
currently. There's an issue open[1] to look at it but most
I must have missed the memo, but the repos vanished on 2016-09-25 causing
all of my 'yum update's to fail.
Am I'm the only one using the repos?
--
Thanks in advance,
-
Steve Edwards sedwa...@sedwards.com Voice:
You won't see anything in the Asterisk logs because there's nothing to log.
The error happens in the freeradius-client library and returns an integer.
On 29 Sep 2016 17:44, "Willem Offermans" wrote:
Hello Andrew and asterisk friends,
I suspect that asterisk has
You don't get anything in the Asterisk logs because freeradius-client
(formerly radiusclient-ng) returns a single failure code for any failure
when building a radius request.
Andrew
On 29 September 2016 at 15:55, Willy Offermans wrote:
> Hi Ahmed and asterisk
Hi Ahmed and asterisk friends,
So asterisk cannot contact the radius server.
The radiusclient __can__ contact the radius server.
Check in the asterisk log files why asterisk cannot contact the radius
server! Be also aware of the user, who is running the daemons. This user
might need read