NOAA Reports showing back to 1969

115 views
Skip to first unread message

weather list

unread,
Jan 22, 2021, 11:40:43 AM1/22/21
to weewx...@googlegroups.com
I’m pretty sure I have missed a basic setting about when my station was installed or similar. My NOAA page is displaying years back to 1969, where of course there is no data. This is a site-in-progress.

Is there a known fix for this?

  • Station hardware: WeatherFlow
  • Server uptime: 18 days, 17 hours, 43 minutes
  • WeeWX uptime: 1 day, 12 hours, 46 minutes
  • WeeWX version: 4.1.1
  • Belchertown Skin Version: 1.2
  • Debian Raspian Desktop running in a VM on Mac High Sierra

Tom Keffer

unread,
Jan 22, 2021, 11:51:57 AM1/22/21
to weewx-user
This is probably caused by a record in your database with a very old timestamp. 

Take a look at this thread and see if it answers your question.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/AE58767F-D0C1-463F-B325-D2BD8317DF5C%40gmail.com.

vince

unread,
Jan 22, 2021, 12:56:32 PM1/22/21
to weewx-user
Any time you see 1969 it means your VM came up with a time of zero seconds (or close) since the unix epoch of 1/1/1970 midnight UTC.   You're seeing 1969 because you are a few hours behind UTC in your timezone.     I've never seen this in bringing up many os in VM in VirtualBox/Vagrant on my MacBook Air, but if you want me to try to recreate it, I'd need to know how exactly you're bringing up the VM on the Mac.   Did you perhaps do something custom in your virtualization setup ?

weather list

unread,
Jan 23, 2021, 4:54:54 PM1/23/21
to weewx...@googlegroups.com
The first record in weewx.sdb had a value of 300 in the dateTime field; all the other fields look correct. I removed that, and dropped/rebuilt the dailies. Problem persists.

Tom Keffer

unread,
Jan 23, 2021, 5:58:56 PM1/23/21
to weewx-user
If all the other records have a timestamp (field 'dateTime') that truly looks correct (check!), then the problem may be as simple as waiting for new files to be regenerated. Or, try deleting all generated files. They will be automatically regenerated at the next reporting cycle

If you used the setup.py method, this would be 

rm -r /home/weewx/public_html

If you used a package installer,

sudo rm -r /var/www/html/weewx

If the problem still persists, then you still have some old data.

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/10775DA8-F53A-4D52-B086-C1E6C1216E7B%40gmail.com.

weather list

unread,
Jan 23, 2021, 8:32:01 PM1/23/21
to weewx...@googlegroups.com
On 22 Jan, 2021, at 12:56, vince <vince...@gmail.com> wrote:

Any time you see 1969 it means your VM came up with a time of zero seconds (or close) since the unix epoch of 1/1/1970 midnight UTC.   You're seeing 1969 because you are a few hours behind UTC in your timezone.     I've never seen this in bringing up many os in VM in VirtualBox/Vagrant on my MacBook Air, but if you want me to try to recreate it, I'd need to know how exactly you're bringing up the VM on the Mac.   Did you perhaps do something custom in your virtualization setup ?

Not sure I follow all your points. This is Raspian desktop, Buster, is a stock, follow-the-prompts Parallels VM. WeeWx install using setup.py. Parallels starts on boot up, and I launch the VM from the Parallels window. The VM is displaying the correct time for EST.



--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

vince

unread,
Jan 24, 2021, 1:48:55 AM1/24/21
to weewx-user
I think if you look at all your VM logs you'll find firstboot started at 1969 or 1970 and then shortly thereafter it got time from either the host os or from an internet ntp site.  There's really no other explanation.

weather list

unread,
Jan 24, 2021, 8:34:06 AM1/24/21
to weewx...@googlegroups.com
On 24 Jan, 2021, at 01:48, vince <vince...@gmail.com> wrote:

I think if you look at all your VM logs you'll find firstboot started at 1969 or 1970 and then shortly thereafter it got time from either the host os or from an internet ntp site.  There's really no other explanation.

Thanks, I will do that. Meanwhile an rm * of all the generated files has cured the issue.


On Saturday, January 23, 2021 at 5:32:01 PM UTC-8 weatherl...@gmail.com wrote:
On 22 Jan, 2021, at 12:56, vince <vince...@gmail.com> wrote:

Any time you see 1969 it means your VM came up with a time of zero seconds (or close) since the unix epoch of 1/1/1970 midnight UTC.   You're seeing 1969 because you are a few hours behind UTC in your timezone.     I've never seen this in bringing up many os in VM in VirtualBox/Vagrant on my MacBook Air, but if you want me to try to recreate it, I'd need to know how exactly you're bringing up the VM on the Mac.   Did you perhaps do something custom in your virtualization setup ?

Not sure I follow all your points. This is Raspian desktop, Buster, is a stock, follow-the-prompts Parallels VM. WeeWx install using setup.py. Parallels starts on boot up, and I launch the VM from the Parallels window. The VM is displaying the correct time for EST.



--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.

--
You received this message because you are subscribed to the Google Groups "weewx-user" group.
To unsubscribe from this group and stop receiving emails from it, send an email to weewx-user+...@googlegroups.com.
Reply all
Reply to author
Forward
0 new messages