Upgraded to 5.0.1, DB is updating but not reflecting

252 views
Skip to first unread message

Matt Johnson

unread,
Mar 5, 2024, 11:08:51 PM3/5/24
to weewx-user
I've been at this hours. I updated my WeeWx from 4.10.2 to 5.0.1. I am running Belchertown and have MQTT setup. That is all working. 

The issue is I don't see the archive data updating the charts or reflecting when you refresh the page. The database file itself does appear to be updated every 5 minutes as the modified date is updating every 5 minutes.

Any ideas to troubleshoot?

michael.k...@gmx.at

unread,
Mar 5, 2024, 11:28:35 PM3/5/24
to weewx-user
Maybe this thread helps you solving your issue: https://groups.google.com/g/weewx-user/c/yfqGGuFw-L8/m/8Ba9Kd86AAAJ

gjr80

unread,
Mar 5, 2024, 11:40:14 PM3/5/24
to weewx-user
The first thing to do is to post a log extract so we can see exactly what is/is not going on. This wiki page will help you to get a good log extract to post here.

Gary

Matt Johnson

unread,
Mar 6, 2024, 7:02:35 AM3/6/24
to weewx-user
So 12 hours later it seems my site's Belchertown skin is not updating any of the data, it is all stuck in time at 6:20pm last night when I did the update - forecast, almanac, charts all frozen there. MQTT shows real time data for some elements. Database is still updating leading me to believe the skin is simply not reflecting any updates. I'll generate a log to see if it helps.

Matt Johnson

unread,
Mar 10, 2024, 11:15:19 PM3/10/24
to weewx-user
Ok, update. I did a clean install of weewx 5.0.2 on new hardware, as it was time and if I am going to set this up for several more years of trouble free service this is the right way to do it. 

Anyway, I have everything working with Belchertown and mqtt EXCEPT I can't get WeeWx to publish Belchertown skin to var/www/html so it is accessible on port 80 for my website. For http://shakerweather.com I just get the NGINX confirmation page, which is in that folder as well as the weewx folder that has belchertown. 

I followed Pat's instructions to modify the weewx.conf so that HTML_ROOT = var/www/html but it simply won't generate the files there. In fact, I'm not sure where it publishes when I change the HTML_ROOT to var/www/html. According to Pat's instructions they should just generate at the next archive interval. When I make this change the directory at /weewx/belchertown stops updating as well unless I put the HTML_ROOT = var/www/html/weex/belchertown

The only way I can see everything is by going to http://shakerweather.com/weewx/belchertown

There must be something simple I am missing here. Anyone have any ideas?

Here is my weewx conf that works publishing to http://shakerweather.com/weewx/belchertown. Again, if I make Pat's modifications to set the Belchertown HTML_ROOT to /var/www/html/ nothing happens.


--
#   This section specifies what reports, using which skins, to generate.

[StdReport]
   
    # Where the skins reside, relative to WEEWX_ROOT
    SKIN_ROOT = skins
   
    # Where the generated reports should go, relative to WEEWX_ROOT
    HTML_ROOT = /var/www/html/weewx
   
    # Uncomment and change to override logging for reports.
    # log_success = True
    # log_failure = True
   
    # The database binding indicates which data should be used in reports.
    data_binding = wx_binding
   
    # Each of the following subsections defines a report that will be run.
    # See the customizing guide to change the units, plot types and line
    # colors, modify the fonts, display additional sensor data, and other
    # customizations. Many of those changes can be made here by overriding
    # parameters, or by modifying templates within the skin itself.
   
    [[SeasonsReport]]
        # The SeasonsReport uses the 'Seasons' skin, which contains the
        # images, templates and plots for the report.
        skin = Seasons
        enable = true
   
    [[SmartphoneReport]]
        # The SmartphoneReport uses the 'Smartphone' skin, and the images and
        # files are placed in a dedicated subdirectory.
        skin = Smartphone
        enable = false
        HTML_ROOT = /var/www/html/weewx/smartphone
   
    [[MobileReport]]
        # The MobileReport uses the 'Mobile' skin, and the images and files
        # are placed in a dedicated subdirectory.
        skin = Mobile
        enable = false
        HTML_ROOT = /var/www/html/weewx/mobile
   
    [[StandardReport]]
        # This is the old "Standard" skin. By default, it is not enabled.
        skin = Standard
        enable = false
   
    [[Belchertown]]
        skin = Belchertown
        HTML_ROOT = /var/www/html/weewx/belchertown
        enable = true




Tom Keffer

unread,
Mar 11, 2024, 9:02:09 AM3/11/24
to weewx...@googlegroups.com
If I'm understanding correctly, you wish to publish to /var/www/html directly, not /var/www/html/weewx. Without a log, it's hard to say what the problem is, but I would guess it's  a permissions issue. On the theory that it is, try this:

1. You've asked the report engine to generate both SeasonsReport and Belchertown. I doubt this is what you want. Disable the Seasons skin by setting "enable=false" under [[SeasonsReport]].

2. Under [Belchertown], set

HTML=/var/www/html

3. Change permissions. By default, user 'weewx' owns /var/www/html/weewx, not /var/www/html. To change:

sudo chown -R weewx:weewx /var/www/html

4. Restart weewx

If that doesn't work, you will have to include a log. See the wiki article Help! Posting to weewx-user for how to get a good log.

--
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/96db740a-3462-46a9-b50f-5fcc71047964n%40googlegroups.com.

Matt Johnson

unread,
Mar 11, 2024, 9:46:43 AM3/11/24
to weewx-user
Tom - Fantastic! It was a permissions issue, and your solution resolved it. That actually crossed my mind but wasn't sure how to resolve it. I am adding this to my notes for future reference. These notes certainly saved me when reinstalling, I remember the initial config of this and doing it all self hosted behind a reverse proxy took days!
Reply all
Reply to author
Forward
0 new messages