Thanks Fabrice,

I have the expiration settings setup and have rebooted the pfmon service but I 
haven't notice any reduction in the number of nodes in our database. I looked 
at the database-and-maintenance.sh script and the locationlog cleanup looks at 
the end_time column but all of my entries show NULL so nothing gets removed. 
That is why I wondered if end_time was the unregistered date of the node 
possibly. Most our nodes have unreg dates of five years since we don't replace 
systems until they break most of the time. However we would like for them to be 
removed if they never touch the network in two months because we do get rid of 
equipment.


I'm thinking of modifying the script to look at the start_time since I can see 
nodes have multiple times a day recorded in the locationlog. No need to keep 
more that 30 days of start times it seems. Would this cause any issues that you 
are aware of? Thanks.


Jeremy Plumley
ITS Network Technician
Guilford Technical Community College, www.GTCC.edu<http://www.gtcc.edu/>
601 High Point Road, Jamestown, NC 27282
Office - 336.334.4822 ext 50428
________________________________
From: Fabrice DURAND <[email protected]>
Sent: Monday, July 7, 2014 8:27 AM
To: [email protected]
Subject: Re: [PacketFence-users] Expiring Nodes and Database Maintenance script

Hello Jeremy,

setting expiration to 60 days for nodes and 30 for location log is a good idea.
What you have to take care is what technology you are using for the access 
(Port-Sec, mac-auth ...)
In the case of the port-securty, you have be sure that the expiration on the 
location log is a little bit more than the maximum access duration of a node.
Of course don´t forget to restart pfmon to use the new values you defined.

Other thing use database-backup-and-maintenance.sh for maintenance.

Regards
Fabrice

Le 2014-07-06 16:53, Jeremy Plumley a écrit :

Hello,


I have been trying to research on how to do maintenance on our packetfence 
database. Wanted to delete out nodes from our database that hasn't connected to 
the network in two months. I tried setting the expiring dates of 60 days for 
nodes and 30 days for the location log but nothing seems to be getting cleared 
out. At this moment I see some people use a cron job to delete nodes based on 
the last dhcp date which I will probably work on. However there is already a 
script in addons for locationlog maintenance but it goes by end_date. What is 
the end_date? All of my entries show NULL and the script only deletes those 
that are 1 month old. Is this the deregistration date? Thanks.

Jeremy Plumley
ITS Network Technician
Guilford Technical Community College, www.GTCC.edu<http://www.gtcc.edu/>
601 High Point Road, Jamestown, NC 27282
Office - 336.334.4822 ext 50428



------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft



_______________________________________________
PacketFence-users mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/packetfence-users




--
Fabrice Durand
[email protected]<mailto:[email protected]> ::  +1.514.447.4918 (x135) ::  
www.inverse.ca<http://www.inverse.ca>
Inverse inc. :: Leaders behind SOGo (http://www.sogo.nu) and PacketFence 
(http://packetfence.org)
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
PacketFence-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/packetfence-users

Reply via email to