Traffic widget crashing WebGUI?



  • I run 2.4 on a test node.  It doesn't do much at the moment other than sit there 99% of the time.  I've noticed that after leaving it alone for awhile, I'll check back and see After.png.  Normally it looks like Before.png.  Not much in the System log except a lot of strange cruft:

    [tt]Feb 28 08:49:47	check_reload_status		Linkup starting vmx0
    Feb 28 08:49:47	php-cgi		rc.bootup: Resyncing OpenVPN instances.
    Feb 28 08:49:47	check_reload_status		Linkup starting vmx1
    Feb 28 08:49:48	kernel		.done.
    Feb 28 08:49:48	kernel		done.
    Feb 28 08:49:48	php-cgi		rc.bootup: ROUTING: setting default route to 209.87.228.145
    Feb 28 08:49:48	kernel		done.
    Feb 28 08:49:49	kernel		done.
    Feb 28 08:49:49	php-cgi		rc.bootup: NTPD is starting up.
    Feb 28 08:49:49	kernel		done.
    Feb 28 08:49:50	check_reload_status		Updating all dyndns
    Feb 28 08:49:50	kernel		.done.
    Feb 28 08:49:54	php-cgi		rc.bootup: Creating rrd update script
    Feb 28 08:49:54	syslogd		exiting on signal 15
    Feb 28 08:49:54	syslogd		kernel boot file is /boot/kernel/kernel
    Feb 28 08:49:54	kernel		done.
    Feb 28 08:49:54	php-fpm	379	/rc.start_packages: Restarting/Starting all packages.
    Feb 28 08:49:54	kernel		done.
    Feb 28 03:48:28	login		login on ttyv0 as root
    Feb 28 03:48:28	kernel		done.
    Feb 28 03:48:28	sshlockout	59235	sshlockout/webConfigurator v3.0 starting up
    Feb 28 04:10:11	php-fpm	68497	/index.php: Successful login for user 'admin' from: 10.10.4.1
    Feb 28 13:51:05	php-fpm	4228	/ifstats.php: Session timed out for user 'admin' from: 10.10.4.1
    Feb 28 13:53:10	php-fpm	47115	/index.php: Successful login for user 'admin' from: 10.10.4.1[/tt]
    

    None of this appears relevant but it does show that some log messages do not seem to care about the timezone (+5 where I am).





  • Should probably try and open a network traffic tab in the browser, and see what responses came back for each of the requests for up to date information/statistics. Up to where they failed to get a expected response.. Might be a automatic logout after 2 hours or something.? and the the 'getstats.php' could return a login page instead of the requested statistics.?.



  • Could be an auto-logout.  When I refresh the view to clear the error, I'm back at the login screen.  I prefer 2.3's way that does not kick me after a time period expires.  Perhaps make it an option.

    I'll keep a separate tab open and see how it behaves when the main screen crashes.



  • b.t.w. what is this set to on your system?: System/User Manager/Settings "Session timeout"

    It looks to me only a 'empty' or a 0 will stay alive forever while displaying graphs/stats.. With a number of minutes set, the 'ajax requests' seem not to be tracked as 'activity'.



  • It's blank so I assume the default of 240 minutes?

    It was crashed again when I came in this morning, and this was the traffic graph:




  • I took another look at your logfile posted above..

    Feb 28 08:49:54	kernel		done.
    
    ```Time go's backward, not only the 5+ timezone but also like 1.5 minutes..
    

    Feb 28 03:48:28 login login on ttyv0 as root
    Feb 28 03:48:28 kernel done.
    Feb 28 03:48:28 sshlockout 59235 sshlockout/webConfigurator v3.0 starting up
    Feb 28 04:10:11 php-fpm 68497 /index.php: Successful login for user 'admin' from: 10.10.4.1
    Feb 28 13:51:05 php-fpm 4228 /ifstats.php: Session timed out for user 'admin' from: 10.10.4.1

    Feb 28 13:53:10 php-fpm 47115 /index.php: Successful login for user 'admin' from: 10.10.4.1

    So that seems to be a little above the 4 hours between login and timeout.. Probably first few minutes you did some clicking around and then 4 hours later it stopped working..?
    
    Anyhow it doesn't seem to make sense, ive changed the 4h timeout to like 30 seconds on my local box, and it keeps running after that time passes, unless i make the ajax requests not update the 'last_access'..
    
    https://github.com/pfsense/pfsense/blob/master/src/etc/inc/auth.inc#L1804
    
    Maybe you could try and check if indeed it stops working after the number of seconds set in above file?


  • I've deleted my 2.4 test instance so this won't be a concern for me any longer.  Thanks for your efforts though.  They were appreciated.