I agree. The iplog_history table needs to be reworked. IMHO, we don't need a single record for the same ip again and again and again for every renewal, the renewal should extend the end time and keep it as one record. Iplog_history is the single biggest performance problem in my pf setup.
Sent from my iPhone On Oct 22, 2015, at 8:35 PM, Thomas, Gregory A <thom...@uwp.edu> wrote: I have found a temporary fix for this issue. The user’s device was not in the node table of the database and thus a correct error. However the device was given an address from the dhcp server but the database slow to update the node table with the information. In my case the iplog_history table was what was causing the problems. I have an instance of phpMyAdmin installed and when I tried to browse the table it was extremely slow to respond. I assumed this was causing problems with writing to the node table as it has to work on pulling info from the iplog and placing it into iplog_history. The history table was well over 3,000,000 records at 7 weeks of use and close to 300 MB all unindexed. I backed up iplog_history, truncated the table and rebooted the server. This time the load never got over 2 and has settled to .7 at peak time. I will be working on some process to do this type of truncation for me on a weekly basis to help keep the system running. -- Gregory A. Thomas Computer Professional University of Wisconsin-Parkside thom...@uwp.edu </owa/redir.aspx?C=PJoLX1MXo0SU0MLM7GrPmwxJzaMkdtAIgi4jkK-AXpCwJ307G0bt2lvFPw4WGoqQ06Tt1qwrKAA.&URL=mailto%3athomasg%40uwp.edu> 262.595.2432 *From:* Thomas, Gregory A [mailto:thom...@uwp.edu <thom...@uwp.edu>] *Sent:* Thursday, October 22, 2015 6:31 PM *To:* packetfence-users@lists.sourceforge.net *Subject:* [PacketFence-users] Device not found in Database So, I am run 5.4 in complete Inline mode. CentOS 6.7 64bit 6 GB RAM with 6 Processors Running on an EXi server This afternoon, the server began a death spiral where the free RAM was getting to 500 MB free (yeah I know there is still a ton there) and the load was starting to creep from .8 to 7 and eventually at reboot time stuck at 20 + for 5 minutes straight. That is not the problem (right now). I rebooted the server with the managed NIC disabled, know that once enable the load would jump to handle all of the “new” requests for access. After about 5 minutes, the load fell to the evening average of 2-3. So I decide to see how the network is running. I fire up my phone, which is registered and I get the error: Your device in not in the Database, please reboot to solve this problem. Of course I don’t as I know better and renew the lease and everything else under the sun and eventually reboot all to no avail. After about 10 minutes and trying to calm residents down who are also getting this error, I get a connection and can register my phone. What causes this error and is there a way to somewhat eliminate it? -- Gregory A. Thomas Computer Professional University of Wisconsin-Parkside thom...@uwp.edu </owa/redir.aspx?C=PJoLX1MXo0SU0MLM7GrPmwxJzaMkdtAIgi4jkK-AXpCwJ307G0bt2lvFPw4WGoqQ06Tt1qwrKAA.&URL=mailto%3athomasg%40uwp.edu> 262.595.2432 ------------------------------------------------------------------------------ _______________________________________________ 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
