Hi Ludovic, Thank you for getting back to me regarding this issue. I checked our LDAP/AD, and they were working. Unfortunately, we could not recover from this behavior, and we restored from the previous night's backup. Radius is working now. However, we did not create a realm with our domain name springfield.edu yet because Radius stopped working after we established that realm.
I am wondering if anyone ran into this issue before. Best, Nadim On Thu, Jan 30, 2020 at 8:19 AM Ludovic Zammit <lzam...@inverse.ca> wrote: > Hello, > > Check if all your LDAP / AD source are working. Freeradius checks LDAP > source availability at the start. > > Thanks, > > > Ludovic zammitlzam...@inverse.ca :: +1.514.447.4918 (x145) :: www.inverse.ca > Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence > (http://packetfence.org) > > > > > > On Jan 29, 2020, at 11:53 AM, Nadim El-Khoury via PacketFence-users < > packetfence-users@lists.sourceforge.net> wrote: > > Hi Everyone, > > The FreeRadius server is no longer starting after adding a new realm with > the name springfieldcollege.edu. Deleting the realm does not help either. > The Radius server was starting with no issues before that. > The error message is > > *radiusd*: Failed resolving "" to IPv4 address: Name or service not known > We are running CentOS Linux release 7.7.1908 (Core) > > Has anyone run into this problem? > > Best, > > Nadim > _______________________________________________ > PacketFence-users mailing list > PacketFence-users@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/packetfence-users > > >
_______________________________________________ PacketFence-users mailing list PacketFence-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/packetfence-users
