Hi Jason, we had a similar issue, and after some searching on the mailing list i read that this could be a MySQL socket timeout.
The default timeout is AFAIK 8 hours. I.e. if there is absolutely nothing going on on PF for more than 8 hours, MySQL stops listening on the socket. Although I have no idea how it can happen that PF does not use the DB for so many hours. Maybe when pfmon is not running for some reason? We never had this issue again, but nevertheless I set wait_timeout in my.cf to 43200 = 12 hours. Maybe this helps in you, too. Regards, Till On 29.09.2016 19:34, Jason 'XenoPhage' Frisvold wrote: > On 9/16/16 10:01, Louis Munro wrote: >> Hi Jason, > Man, it's been a month.. sorry for the delay here.. > >> Are you running this as a cluster or a single node? > Single Node. > >> And are there other database errors in the logs? > No, those are pretty much the only ones.. > >> Any sign that mysql may be restarted (by systemd perhaps)? > You mean that mysql was being restarted when these errors occurred? No, > it was up and running ... > >> Regards, >> -- >> Louis Munro > > > ------------------------------------------------------------------------------ > > > _______________________________________________ > PacketFence-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/packetfence-users
------------------------------------------------------------------------------
_______________________________________________ PacketFence-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/packetfence-users
