There is an update to app-system-database now available for testing.

yum update app-system-database --enablerepo=clearos-updates-testing

It will restart system-mariadb on any time zone change. It you have an affected report screen open it the time it may look odd (it the time jumps later) or frozen (if the time jumps earlier). All you will need to do is a screen refresh. It will be fine if you don't have the reports screen open when you do the time zone change.

I am waiting to hear back if I should add a system-mariadb restart to one of the packages, but I am not totally sure which one to use. There is more than one option.

Nick Howitt wrote:

It looks like the reports get corrected following a "systemctl restart system-mariadb". Then you have to wait until the next event fires for each report type. These happen every 5 minutes and sequentially so one report gets fixed a few seconds before the other one.

Good deal! I'll do the install and check it out

It looks like the reports get corrected following a "systemctl restart system-mariadb". Then you have to wait until the next event fires for each report type. These happen every 5 minutes and sequentially so one report gets fixed a few seconds before the other one.

The Network Report and Resource Report seem to be very different and I think they work but there is browser/PHP caching at play somewhere. If you are view one without having viewed the other, it will appear in local time. If you then change the timezone, nothing appears to change with the report you are viewing. However, if you view the other one, the report will appear in your new local time.

It also appears like a restart of system-mariadb may be required. If I view both reports then change the TZ, the reports stay on the old TZ until I restart system-mariadb. At that point the Resource report corrects itself but not the Network report. That takes a few minutes longer. I'll play around with inserting a condrestart on system-mariadb into the Date/Time screen.

Sorry. It is in contribs-testing:

yum install app-bandwidth-viewer --disablerepo=* --enablerepo=clearos-contribs-testing

In the next few minutes there should be an updates app-bandwidth-viewer available for testing:

yum update app-bandwidth-viewer --enablerepo=clearos-updates-testing

It may take a couple of hours to sync to your mirror depending on which mirrors you use. It should fix the graph timezone issue.

I'll have a look at the other reports over the next couple of days.

I see the issue. I wonder when it started. I know I fixed the Bandwidth Viewer a while ago. I wonder if something like a later update to the Webconfig version of PHP broke it? I'm not sure that I can fix it so I'll have to raise an issue.

The Resource Report, the Network Report, and the bandwidth viewer are all 5+ hrs ahead in the graphics on my system.

I fixed the Bandwidth Viewer a few months ago. I am currently on UTC so all my reports show correctly whatever. Perhaps I'll have to try changing timezones and then check. Which graphs in particular are you talking about? The Network Report? Resource report? Any others? The Bandwidth Viewer was a two line fix, but there is no guarantee that the others will be.