Please Help: "Firewall Logs" Dashboard Widget Not Updating
-
@johnpoz said in Please Help: "Firewall Logs" Dashboard Widget Not Updating:
@sissy - good find. But I just set mine to 5 seconds and not seeing any issues.. So its not something generic in pfsense.. Running on sg4860..
Mine works at 5 seconds or greater. Setting it to four or less causes it to not update.
This may be performance-based, so someone with faster hardware, or a less compute-intensive pfSense configuration, might be able to use a shorter update interval (maybe even 1 second). There are things I could do, such as turning off PowerD CPU throttling, simplifying my firewall configuration, experimenting with RAM disks. But I'm lazy, so I probably won't.
Perhaps it could be fixed in pfSense by changing the update interval to a delay between updates; the Firewall Log update finishes and then it waits however many seconds is specified before starting the next one. I'm looking at this as a black box rather than looking at source code, so I could be completely wrong.
-
Yeah, good catch, that's interesting. The widget should have a 5s minimum interval at least if it won't update faster.
https://redmine.pfsense.org/issues/12673
-
So I set it to 3, and from just quick test of sending some traffic to wan from outside.. Yeah its not updating.
I commented on the redmine with a link to this thread.
-
@johnpoz - TL;DR Mine stopped updating after some hours with a 5 second Update Interval. The problem may be load-dependent.
I just returned to my iMac Pro at 3:10AM, where I had left the pfSense dashboard displayed. The Firewall Logs widget, with a 5 second interval setting, had ceased updating about 7 hours ago.
Perhaps it stopped because my WAN port received a whole lot of unsavory, logged traffic at once -- more than the widget could process and display within one Update Interval timer cycle? Or maybe some other series of processes were depleting available CPU cycles, preventing the widget from completing the update fast enough?
I have now set the Update Interval to 10 seconds. I will see if updates cease at that setting.
I believe that the problem could be resolved by changing the Update Interval to a "rest" period after each update completes. That would free up CPU cycles (which is the raison d'être of the setting, after all) while not creating some sort of race condition between the Update Interval timer and the widget update display process.
Note: The Update Interval isn't really an interval. On my system, when it is set to five seconds, the updates are each several seconds "late" relative to five seconds (maybe coming every 7-9 seconds). That's not a problem, but it might be a clue.
-
Yeah, it 'feels' like something that takes too long to process which would be load dependent. Anything less that 5s always seems to fail though.
Add anything that might be relevant to the bug there.Steve
