David, Apologies I have not had much time for WeeWX today. In any case it is good that you have it working.
Gary On Wednesday, 10 March 2021 at 11:14:29 UTC+10 [email protected] wrote: > Gary, more GOOD news, i changed HTML_ROOT statement in weewx.conf for > [[Belchertown]] to "HTML_ROOT = /home/weewx/public_html/belchertown" then > made some minor title changes to skin.conf in belchertown and it works! > > I think that nginx was looking at the base of /home/weewx/public_html for > all implementations of localhost. So, any calls to http://localhost/weewx > gets the basic pages found in /public_html; but calls to > http://localhost/weewx/belchertown will get the belchertown pages (off of > ../public_html/belchertown') instead of the ../public_html pages. > > I think it's now working! Thanks! > /David > On Tuesday, March 9, 2021 at 4:53:48 PM UTC-8 David Prellwitz wrote: > >> Gary, did one more test - i copied all of the files in >> "/home/weewx/public_html/weewx/belchertown" to >> "/home/weewx/public_html/belchertown" and ran the browser to >> 'localhost/weewx/belchertown' - i worked!!! that means i need to modify the >> conf file to point to "/home/weewx/public_html/belchertown" instead of >> "/home/weewx/public_html/weewx/belchertown" >> >> On Tuesday, March 9, 2021 at 3:58:32 PM UTC-8 David Prellwitz wrote: >> >>> Gary: >>> more - i've been studying the nginx package. I followed the >>> configuration file links. they start at /etc/nginx in the nginx.conf file. >>> It links /etc/nginx/sites-enabled; which redirects to >>> /etc/nginx/sites-avaialble. that configuration file links to 'default' >>> which has a declaration to include 'root' with /var/www/html which contains >>> the first mention of weewx; that links is a redirection to >>> /home/weewx/public_html directory. No mention of belchertown anywhere. >>> >>> I'm thinking that I need a reference to the >>> "/home/weewx/public_html/weewx/belchertown" somewhere in this chain, >>> otherwise nginx can't find the config, html and image files. what do you >>> think? attached is a text file of my findings on the nginx configuration >>> setup. >>> /David >>> >>> On Tuesday, March 9, 2021 at 12:56:47 PM UTC-8 David Prellwitz wrote: >>> >>>> Gary: >>>> yes to all. here's some examples. First file is a set of extracts from >>>> syslog; then annotated extracts from the index.html files in >>>> ../public_html >>>> and ../public_html/weewx/belchertown directories; then an annotated tree >>>> structure taken at /home/weewx/public_html; then screen shots from >>>> http://192.168.86.28/ - then screen shot from >>>> http://192.168.86.28/weewx and last from >>>> http://192.168.86.28/weewx/belchertown . as i noted in my extracts, >>>> both the index files show current info (i think). When i look in >>>> /home/weewx/public_html/weewx directory it's empty except for the >>>> /belchertown subdirectory. I also did "locate" commands for all >>>> occurrences of "index.html" and nothing seemed out of place. So, i'm not >>>> sure where weewx and belchertown execution put their respective web files. >>>> Nor am i aware of where nginx will pick up those files. It seems that the >>>> default weewx skin operates correctly, that means weewx is operational and >>>> correct (i think). the syslog shows that weewx generates reports for >>>> belchertown using the skin.conf in belchertown skins directory. almost all >>>> of the features of belchertown skin seem to be working... so i'm >>>> officially >>>> lost! thanks for the assistance. >>>> >>>> >>>> On Tuesday, March 9, 2021 at 2:21:19 AM UTC-8 gjr80 wrote: >>>> >>>>> Just to remove all possibility of misinterpretation with abbreviated >>>>> paths etc. You are saying /home/weewx/public_html/weewx/index.html >>>>> and /home/weewx/public_html/weewx/belchertown/index.html both exist >>>>> and appear to be current? And also when you put >>>>> http://192.168.86.28/weewx into your browser it displays the Seasons >>>>> skin main page and the data is current, but when you use >>>>> http://192.168.86.28/weewx/belchertown you get a 404 error? >>>>> >>>>> Gary >>>>> >>>>> On Tuesday, 9 March 2021 at 20:08:20 UTC+10 [email protected] >>>>> wrote: >>>>> >>>>>> Gary, they seem to be current. I read index.html files in >>>>>> ../public_html/weewx/ and /belchertown and they shows labels and some >>>>>> epoch >>>>>> time that appears to be current. All the files in /public_html, weewx >>>>>> and >>>>>> belchertown all seems to have current files. I still get a 404 error >>>>>> when >>>>>> trying to open. default skin/browser still works. >>>>>> /David >>>>>> On Tuesday, March 9, 2021 at 1:06:24 AM UTC-8 gjr80 wrote: >>>>>> >>>>>>> Yes, deleting while tired is to be avoided. Interrupting a reporting >>>>>>> cycle is not critical, just means you probably deleted some files that >>>>>>> WeeWX had just generated, WeeWX will get over it. >>>>>>> >>>>>>> So forgetting about the browser, does >>>>>>> /home/weewx/public_html/weewx/belchertown contain any files and >>>>>>> directories? Are they current, check the content with an editor. If >>>>>>> they >>>>>>> are current your issue is an nginx config issue, if they are not >>>>>>> current >>>>>>> then you have a really bizarre WeeWX/Belchertown skin problem. >>>>>>> >>>>>>> Gary >>>>>>> >>>>>>> On Tuesday, 9 March 2021 at 18:48:15 UTC+10 [email protected] >>>>>>> wrote: >>>>>>> >>>>>>>> Gary: >>>>>>>> well, i should not make major changes while tired.... I >>>>>>>> (unfortunately) wiped out my own user directory ("/home/david/...) so >>>>>>>> i'll >>>>>>>> have to live with that. Lost some files and copies of modified conf >>>>>>>> files, >>>>>>>> but not much else was lost... >>>>>>>> >>>>>>>> I did wipe out the contents of public_html directory and it's >>>>>>>> subdirectories. I must have interrupted a reporting cycle as syslog >>>>>>>> had >>>>>>>> some serious errors. once i restarted weewx it all ran successfully. >>>>>>>> However, still no joy. Now when i go to >>>>>>>> http://192,168.86.28/weewx/belchertown >>>>>>>> i get a 404 error (not found). the default skin >>>>>>>> (http://192,168.86.28/weewx) >>>>>>>> runs fine. Files all seem to have a current date/time, but i still >>>>>>>> don't >>>>>>>> get a belchertown page loaded. >>>>>>>> /David >>>>>>>> >>>>>>>> On Monday, March 8, 2021 at 10:11:54 PM UTC-8 gjr80 wrote: >>>>>>>> >>>>>>>>> OK. Let's forget about the browser for the time being and work >>>>>>>>> with the files in /home/weewx/public_html, get them right and the >>>>>>>>> browser will fall into place. Since you have made various changes to >>>>>>>>> where >>>>>>>>> WeeWX generated files are going, but seem to have that set correctly >>>>>>>>> now, >>>>>>>>> go ahead and delete everything in /home/weewx/public_html. >>>>>>>>> Everything includes files and directories. WeeWX will re-generate it >>>>>>>>> all on >>>>>>>>> the next report cycle, then next report cycle might take a little >>>>>>>>> longer >>>>>>>>> depending on how much historical data you have as WeeWX will >>>>>>>>> re-generate >>>>>>>>> all NOAA format files. No need to stop/start or restart WeeWX, just >>>>>>>>> make >>>>>>>>> sure that you get everything deleted before a report cycle starts and >>>>>>>>> not >>>>>>>>> during. >>>>>>>>> >>>>>>>>> Monitor the log and once that next report cycle has completed have >>>>>>>>> a look at what files/directories are where in >>>>>>>>> /home/weewx/public_html and when are they timestamped. >>>>>>>>> >>>>>>>>> Gary >>>>>>>>> >>>>>>>>> On Tuesday, 9 March 2021 at 15:53:24 UTC+10 [email protected] >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> Gary: >>>>>>>>>> no joy. changed weewx.conf to show Belchertown HTML_ROOT as you >>>>>>>>>> suggested ("/home/weewx/public_html/weewx/belchertown"), stopped >>>>>>>>>> weewx, >>>>>>>>>> started weewx, ran weewx status. waited for updates, browsed to >>>>>>>>>> http://192.168.86.28/weewx and got the original weewx skin with >>>>>>>>>> correct info. Then browsed to >>>>>>>>>> http://192.168.86.28/weewx/belchertown and got the old >>>>>>>>>> belchertown skin with March 6, 2021 at 1:55 pm. (Same problem i >>>>>>>>>> started >>>>>>>>>> with.) no errors or problems indicated on syslog, debug or messages. >>>>>>>>>> I >>>>>>>>>> checked the file/directory structure in /home/weewx/public_html and >>>>>>>>>> see >>>>>>>>>> that there is a belchertown and a weewx subdirectories. However, the >>>>>>>>>> files >>>>>>>>>> in /home/public_html/belchertown show a date of Mar 6, 2021 at 13:55 >>>>>>>>>> - same >>>>>>>>>> as the offending pages. When i checked the >>>>>>>>>> .../public_html/belchertown >>>>>>>>>> directory, However, there is NOT a >>>>>>>>>> /home/weewx/publich_html/weewx/belchertown subdirectory. >>>>>>>>>> >>>>>>>>>> More interesting stuff: i looked at the index.html file in >>>>>>>>>> "../public_html/weewx" directory and it has the correct belchertown >>>>>>>>>> date/time and it contains the corrected labels/headers and chart >>>>>>>>>> specifics >>>>>>>>>> i'd modified. When i looked at the index.html file in >>>>>>>>>> "../public_html/belchertown" directory it contains the March 6 >>>>>>>>>> layout >>>>>>>>>> (first modifications to only change the title name). Whatever is >>>>>>>>>> happening >>>>>>>>>> means wherever weewx is putting the html files for the newer >>>>>>>>>> Belchertown >>>>>>>>>> files is not the same place that the web engine (nginx) is not >>>>>>>>>> picking them >>>>>>>>>> up from. >>>>>>>>>> /D >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> 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 [email protected] >>>>>>>>>>> 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 >>>>>>>>>>>> [email protected] 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 < >>>>>>>>>>>>> [email protected]> 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 >>>>>>>>>>>>>>>> [email protected] wrote: >>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Try localhost/weewx/belchertown >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Dave - KB1PVH >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> Sent from my Galaxy S21 >>>>>>>>>>>>>>>>> >>>>>>>>>>>>>>>>> On Sat, Mar 6, 2021, 6:12 PM David Prellwitz < >>>>>>>>>>>>>>>>> [email protected]> 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 [email protected] >>>>>>>>>>>>>>>>>> . >>>>>>>>>>>>>>>>>> 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 [email protected]. >>>>>>>>>>>>>> >>>>>>>>>>>>> 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/4abca329-e6e1-4f2c-a88b-d61f4a17b390n%40googlegroups.com.
