Graphs have wrong time on the x axis

[geoff]

I have the following problem, all of the daily graphs have the wrong
time on the x axis for the data, but the the data is otherwise graphed
correctly and the graphs to have the correct time that it was
generated. Right not at 9:34PM, the graph only goes to 17:20 even
thought the data for 17:20 is actually for the current time. Curiously
the rain graph has the scale to 18:00 while all of the other graphs
are 17:20. The ~4:20 lag time between the true time and the graph axis
seems to be pretty consistent. I am running wview 5.5.1, Debian Lenny
on a Slug. The system time on the slug is correct when I do 'Date' at
the command line. I've rebooted and this has not helped. Any ideas?

-Geoff

[Mark S. Teel]

I have seen this occasionally and it always ends up being a caching
issue with the browser. The only way to be sure is look at the generated
html files on your wview server.

Mark

[geoff]

Hi Mark,

I upgraded to 5.5.2 and have now somewhat figured out what the problem
was. For some reason wview was not entering the 10 minute data into
the archive database for some period of time. When I would restart
wview it would add 10 old, but yet to be recorded entries from the
vpro to the database and then try to graph the data for the various
graphs. At the next 10 minute interval, wview would again add 10
entries to the database and make a partially filled graph. Over the
next ~ 3 hours the data for a previous day would be serially added to
the graph in 1:40 minute (10 entry) chunks. Since the graph was
produced by the htmlgen process at the current time, the time stamp
at the bottom of each graph would have the current correct time. Once
the graph for the day was made, wview stopped adding entries in chunks
of 10 to the database, but would add a single missing entry and the
graph would be updated as if it was the current data. I looked into
the archive database and determined that ~3-4 days of data was
missing. I started and stopped wview, but it would only load data in
chunks of 10 every 10 minutes until it had added ~ 150 entries and
then would resume single entry updates every 10 minutes. I started and
stopped wview until it had added all of the data into the database.
Once I restarted wview after all of the data was current, it drew a
complete graph with the current time and everything has been running
fine now for a couple of days. I have no idea if this behavioral
description makes and sense based upon the under the hood design of
wview. It would see that somehow when wview starts up, determines the
current date and the date of the latest database entry and then
doesn't add all of the missing database entries prior to making the
graphs it exhibits this odd behavior. I have no idea what would be the
optimal solution - erasing all of the vpro data, starting and stopping
wview to load the data, other ideas?

Anyway, thanks for the help and the great product.

Cheers,

Geoff

> > -Geoff- Hide quoted text -
>
> - Show quoted text -

[Mark S. Teel]

Very unusual, never heard of such a thing!
If the wview archive table is behind the VPro archive record buffer in
time, it will try to extract all records up to the last archive record.
The fact it is only extracting 10 records at a time makes me think the
VP console is acting strangely. If it were me, I would wait until my
archive table is up to date, then shut it all down, unplug the console
power, remove the batteries, wait 5 minutes, then add batteries, AC
power, wait a few minutes, run vpconfig (clearing the archive buffer),
wait a few minutes, then start up wview. The waiting steps are annoying
but the VP console is temperamental around power loss and barometric
pressure resets.

I am assuming all your data was collected with a 10 minute archive
interval. wview does not support mixed archive interval data (yet).
The new database was constructed to support that and metric data (also
not yet supported).

Mark

[geoff]

I'll reset the vpro and let you know what happens.

Cheers,

Geoff