# Having some issues with the audit log or loading something with PropertiesFactory **URL:** \ **Category:** Ignition\ **Created:** [June 30, 2023, 1:50pm UTC](https://forum.inductiveautomation.com/t/having-some-issues-with-the-audit-log-or-loading-something-with-propertiesfactory/75772 "2023-06-30T13:50:21Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\ **Post date:** [June 30, 2023, 1:50pm UTC](https://forum.inductiveautomation.com/t/having-some-issues-with-the-audit-log-or-loading-something-with-propertiesfactory/75772/1 "2023-06-30T13:50:21Z")
**Short version** Is there an issue with the audit log causing some kind of cpu usage loop? Is PropertiesFactory loading a properties files from jar files on the gateway something my company added or something native to Ignition? What is that? My CPU utilization cranked up to 80% for hours and hasn't gone below 50% since. I will probably restart soon, but I want to do some investigating first. * * * I am using Ignition 8.1.19 I was trying to look at audit logs on the gateway. I did a search for a target using `%machineName%` for example over the last 6 months. The gateway started to hang. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/8/18127fe9f88203bb81f562dfd13b93360984fbe9.png) I thought hanging would be the end of it. However, instead the CPU utilization went to 80%, stayed there for hours, and still has not gone back down since. The timestamps seem to line up with the first audit search hanging. 29Jun2023 16:53:22 is when I had the first issue with the audit. From the diagnostics log, I had these repeating issues from that one audit that hung. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/7/77fc6c869a3725a0bda4ab19e9a7d1a94b10c305.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/9/c906df89ab70a75cdd0f47d4ae00383b9baae7aa.png) The other event that happened just before were an internal database ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/2/e/2e1d3e46cb1c40e327d54b4a4346cf31dc8a12bf.png) The propertiesfactory items happened at the same time, a double loading of the same properties files. Then the InternalDatabase items were a double creation of auto-backup of internal database config.idb. It is kind of hard to tell which of these events are the causal one for the CPU going high, and then I don't know why it has remained high ever since, ranging from 50-90,instead of hovering around 10%. I suspect that the double call of loading properties files from jar files in the gateway from a wicket extension something apache might be the issue. Looking at the timestamps and the curve, it seems like it might be the audit search caused a looping issue that has not gone away, but I think that is definitely native to Ignition. I thought the other thing happened 2 times simultaneously which seems like a bug somewhere. ---
**Author:** ![zacharyw.larson](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/zacharyw.larson/32/23749_2.png) [@zacharyw.larson](https://forum.inductiveautomation.com/u/zacharyw.larson)\ **Post date:** [June 30, 2023, 3:28pm UTC](https://forum.inductiveautomation.com/t/having-some-issues-with-the-audit-log-or-loading-something-with-propertiesfactory/75772/2 "2023-06-30T15:28:25Z")
Upon restart, I am back to 5-10% cpu. The automated PropertiesFactory event triggered before I could manually test the audit use impact. CPU went up a little then returned to base levels 5-10%. On the 5th I will test the audit. (So the authorized person who restarts the gateway service is available.) **Has using the audit logs in the gateway been an issue for anyone else?** Right now it seems like that might the issue. **Is the PropertyFactory event supposed to double trigger?**