David,
Looking at a generated web page is looking at the end product, there are a
whole pile of intermediate steps before you get there. Best to work through
from the beginning to locate where the issue is.
>From your log extract it appears that your system is obtaining data from
your station, saving it to archive and running reports as expected. So no
problems there. Looking at your [StdReport] stanza in weewx.conf you have:
[StdReport]
# Where the skins reside, relative to WEEWX_ROOT
SKIN_ROOT = skins
[[Belchertown]]
skin = Belchertown
HTML_ROOT = /home/weewx/public_html/weewx
[[[Extras]]]
footer_copyright_text = "BelchertownWeather.com"
forecast_enabled = 1
forecast_api_id = "obfuscated"
forecast_api_secret = "obfuscated"
earthquake_enabled = 1
earthquake_server = USGS
twitter_enabled = 0
belchertown_debug = 1
# Where the generated reports should go, relative to WEEWX_ROOT
# HTML_ROOT = /home/weewx/public_html/weewx
# The database binding indicates which data should be used in reports.
data_binding = wx_binding
# Whether to log a successful operation
log_success = True
# Whether to log an unsuccessful operation
log_failure = True
# 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
The issue I can see is that you have the Belchertown skin and the Seasons
skin both sending their generated output to the same directory. Not a
problem in itself but if there are any files of the same name generated by
both skins then the Seasons skin version will overwrite the Belchertown
version (skins are processed in the order they appear in [StdReport]). In
your case both skins produce index.html so the Belchertown index.html will
always be overwritten. Depending on how your web server is setup you either
won't be able to view the Belchertown main page or you will see an old
version; you definitely will not see a current Belchertown index.html. You
have two options; (1) turn off the Seasons skin with enable = False or (2)
send the output of each skin to a different directory. To do the latter
change the HTML_ROOT setting under [[Belchertown]], perhaps to
/home/weewx/public_html/weewx/belchertown.
The other side of the equation is your web server. You are not having WeeWX
FTP or Rsync any files so I presume your web server is on your WeeWX
machine. In that case you should be able to configure your web server to
serve files from /home/weewx/public_html. Depending on how you set the web
server up and where you have WeeWX save your Belchertown files you should
be able to access both the Seasons skin and Belchertown skin files from
browser using an address like http://web_server_address/weewx and
http://web_server_address/weewx/belchertown. Exactly what goes after the
web server address depends on how you configure WeeWX HTML_ROOT and how you
setup your web server.
See how you go and get back to us if you have problems.
In terms of numbers of files generated and copied, use that as a guide
only. The number of files generated can vary depending on settings in
skin.conf, if analysed in conjunction with the skin.conf settings you can
draw some detailed conclusions but otherwise just treat it as an indication
that 'the skin is being run'. Likewise copied files, it can be quite normal
to have zero files copied even though the skin is generating numerous
files. It all depends on how the copy generator is configured; the main
purpose of the copy generator is not for copying skin generated files it is
more for copying static or non-WeeWX generated files.
Gary
On Tuesday, 9 March 2021 at 07:30:30 UTC+10 david.a....@gmail.com wrote:
> I've been running debug since the beginning! Attached is a text file with
> 200 line extract of syslog, 100 lines of "/var/log/debug", 100 lines of
> "/var/log/messages"; next is a copy of my weewx.conf. Let me know if you'd
> like to have skin.conf and graphs.conf.
> /David
>
> On Monday, March 8, 2021 at 12:28:19 AM UTC-8 gjr80 wrote:
>
>> Hi,
>>
>> I suggest as a start you edit weewx.conf, set debug=1, save weewx.conf
>> and the restart WeeWX. Let WeeWX run for at least two report cycles and
>> then post a log extract here showing the entire WeeWX startup and the two
>> report cycles. Then we can see what WeeWX and the skins are doing.
>>
>> Gary
>>
>> On Monday, 8 March 2021 at 15:30:41 UTC+10 david.a....@gmail.com wrote:
>>
>>> lecoqacr - i can access the belchertown link from my mobile, which is
>>> sharing the same meshed net. Interesting, both Belchertown homepages show a
>>> "last updated" date as yesterday noon; i've restarted all aspects of this
>>> machine (Debian 10 on a Dell laptop), from the laptop thru weewx (three
>>> times) and wee-reports (atleast 10 times). but all of the Belchertown pages
>>> show yesterday noon as the last update. However, the Weewx default skin
>>> updates and shows current data. That's why i think its an issue with my
>>> weewx.conf/skin.conf/graphs.conf files - and/or their location...
>>>
>>>
>>> On Sunday, March 7, 2021 at 7:23:41 PM UTC-8 lecoqacr...@gmail.com
>>> wrote:
>>>
>>>> Maybe this thread is what you are having a problem with.
>>>>
>>>> https://groups.google.com/g/weewx-user/c/qUt0XdqREqk/m/O-wO1GiVAwAJ
>>>> Try going to another computer on the network and enter the address of
>>>> the weewx belchertown address computer.
>>>>
>>>> On Sun, Mar 7, 2021 at 7:12 PM David Prellwitz <david.a....@gmail.com>
>>>> wrote:
>>>>
>>>>> More info - looking at syslog, i notice that 8, 11, 15 season files
>>>>> generated, but are written to /home/weewx/public_html. Sometimes i'll
>>>>> get
>>>>> 2 files written to /home/weewx/public_html/weewx. But, still no updates
>>>>> on
>>>>> belchertown web page. I'm now officially confused as to where skin.conf,
>>>>> graphs.conf need to be in relationship to /home/weewx.
>>>>> /David
>>>>> On Sunday, March 7, 2021 at 1:36:35 PM UTC-8 David Prellwitz wrote:
>>>>>
>>>>>> New issue; i can't get graphs.conf to work, irrespective of where i
>>>>>> put it. It's now in /home/weewx/skins/belchertown directory with
>>>>>> graphs.conf.example file. I've even changed example filename - still
>>>>>> can't
>>>>>> get belchertown skin to use the minor changes i made to the graphs. It
>>>>>> has
>>>>>> to be a configuration issue, something i've overlooked. help!
>>>>>> /David
>>>>>>
>>>>>> On Saturday, March 6, 2021 at 3:35:15 PM UTC-8 David Prellwitz wrote:
>>>>>>
>>>>>>> kool! thanks!
>>>>>>>
>>>>>>> On Saturday, March 6, 2021 at 3:23:04 PM UTC-8 kb1...@gmail.com
>>>>>>> wrote:
>>>>>>>
>>>>>>>> Try localhost/weewx/belchertown
>>>>>>>>
>>>>>>>> Dave - KB1PVH
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>>
>>>>>>>> Sent from my Galaxy S21
>>>>>>>>
>>>>>>>> On Sat, Mar 6, 2021, 6:12 PM David Prellwitz <david.a....@gmail.com>
>>>>>>>> wrote:
>>>>>>>>
>>>>>>>>> I installed the Belchertown skin; configured weewx.conf and
>>>>>>>>> skin.conf; stopped and started weewx; corrected duplication error in
>>>>>>>>> weewx.conf and stopped/restarted weews - no errors. Checked file
>>>>>>>>> date/times
>>>>>>>>> in /home/weewx/public_html/Belchertown_html directory and files are
>>>>>>>>> being
>>>>>>>>> updated. However, when i look at 'localhost/weewx' i get the
>>>>>>>>> original
>>>>>>>>> skin. when i enter 192.168.82.24 (url of this machine) i get the
>>>>>>>>> nginx
>>>>>>>>> welcome screen.
>>>>>>>>>
>>>>>>>>> I believe it's a config or a setup issue on my part, but i don't
>>>>>>>>> know where to look. I'm sure i've failed to link the Belchertown skin
>>>>>>>>> to
>>>>>>>>> the web engine, just not sure how that link is setup. Suggestions as
>>>>>>>>> to
>>>>>>>>> where to look?
>>>>>>>>> /David
>>>>>>>>>
>>>>>>>>> --
>>>>>>>>> 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/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com
>>>>>>>>>
>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/0032546b-89c0-4176-9b58-0cf14a698635n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>>>>>> .
>>>>>>>>>
>>>>>>>> --
>>>>> 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/929bfde0-c860-4105-9fcd-89551acdfa88n%40googlegroups.com
>>>>>
>>>>> <https://groups.google.com/d/msgid/weewx-user/929bfde0-c860-4105-9fcd-89551acdfa88n%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>>
>>>>
--
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+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/287c28a7-f6bb-4d59-aa04-2397b7383394n%40googlegroups.com.
