Perhaps related: the error reported in time-segment 08:21:58 is strange, because the file index.html.tmpl is actually present at the indicated location.
Op zondag 2 mei 2021 om 08:35:33 UTC+2 schreef Ton vanN: > Tom, > ;-) That was a really good advice! > Turned to running WeeWX as daemon, started the logging and got a different > read-out which now includes a reference to the HWA-template. > That confirms my 'nagging feeling' that something is not OK with the > handling of that HWA-template: see time-segment 08:21:59 > Next step is finding a soulution ..... > > Op zaterdag 1 mei 2021 om 20:02:10 UTC+2 schreef tke...@gmail.com: > >> This is most likely being caused by the terminal session detaching from >> the process. This can happen when you ssh into a computer, start a process, >> then exit the ssh session. >> >> Either run weewxd as a daemon, or keep the terminal window open. >> >> That's the best I can come up with. >> >> >> >> On Sat, May 1, 2021 at 4:24 AM Anton vanNwnhzn@GMail <ton...@gmail.com> >> wrote: >> >>> Addition to description of *Sequence1*. >>> >>> Once weewx has been started, at Putty's CLI appears the expected stream >>> of print-out. >>> At the keyboard break that stream ends with an error report. >>> Perhaps that error report also provides some relevant info? >>> See below the last printout from the loop and the error report mentioned >>> above. >>> >>> LOOP: 2021-05-01 13:17:59 CEST (1619867879) altimeter: >>> 31.165113295698216, appTemp: 28.451970776082117, barometer: >>> 31.09999991633433, cloudbase: 1300.0558352360692, consBatteryVoltage: >>> 12.743352544782736, dateTime: 1619867879, dewpoint: 27.19647824994742, >>> heatindex: 32.6713164908827, heatingVoltage: 11.71583632592742, humidex: >>> 32.6713164908827, inDewpoint: 31.079532540856405, inHumidity: >>> 29.99999665337326, inTemp: 63.00000167331337, inTempBatteryStatus: 0, >>> maxSolarRad: 812.0133117257177, outHumidity: 79.99999749002984, outTemp: >>> 32.6713164908827, outTempBatteryStatus: 0, pressure: 31.09999991633433, >>> radiation: 888.7102401456455, rain: 0, rainBatteryStatus: 0, rainRate: 0.0, >>> referenceVoltage: 12.0, rxCheckPercent: 45.10949739082836, supplyVoltage: >>> 12.0, txBatteryStatus: 0, usUnits: 1, UV: 12.441943362039037, >>> windBatteryStatus: 0, windchill: 32.6713164908827, windDir: >>> 359.99998494017905, windGust: 5.019940321204786e-07, windGustDir: >>> 359.99998494017905, windSpeed: 4.1832835950827985e-07 >>> ^CTraceback (most recent call last): >>> File "./bin/weewxd", line 264, in <module> >>> main() >>> File "./bin/weewxd", line 157, in main >>> engine.run() >>> File "/home/weewx/bin/weewx/engine.py", line 208, in run >>> for packet in self.console.genLoopPackets(): >>> File "/home/weewx/bin/weewx/drivers/simulator.py", line 162, in >>> genLoopPackets >>> time.sleep(sleep_time) >>> KeyboardInterrupt >>> pi@Raspberry8:/home/weewx $ >>> Op 1-5-2021 om 12:28 schreef Ton vanN: >>> >>> As requested, a leaner realisation. >>> In attached file the results of 2 sequences executed: >>> - in both cases 'clean restart' of the raspberry to ensure that no >>> unintended process running, followed by 1 direct switch-on of weewx >>> - the sequences differ in the way going to logging, as described in the >>> file >>> - in sequence1 apparently oneshot run before weewx stops. Exit of >>> logging is by keyboard break. >>> - in sequence2 stream of repeating logging info. Also terminated the >>> logging by keyboard break. >>> >>> Op vrijdag 30 april 2021 om 17:34:47 UTC+2 schreef tke...@gmail.com: >>> >>>> You have many instances of weewxd all running simultaneously. Kill them >>>> all, then start one. >>>> >>>> On Fri, Apr 30, 2021 at 7:56 AM Ton vanN <ton...@gmail.com> wrote: >>>> >>>>> As requested. >>>>> >>>>> Scanning the logging see repeated reporting of loading of StdReport, >>>>> but no text clearly pointing to errors in execution of StandardReport, >>>>> nor >>>>> any results. >>>>> But as explained in the first message of this thread, have 'limited' >>>>> experience with weewx ... >>>>> >>>>> Op vrijdag 30 april 2021 om 11:28:53 UTC+2 schreef gjr80: >>>>> >>>>>> The config files and template tell us what should be happening but >>>>>> the log will tell us what is actually happening. Have you looked in the >>>>>> log? Are there any errors? You already have debug = 1 in weewx.conf so >>>>>> you >>>>>> should be able to work out from the log what is being generated and what >>>>>> is >>>>>> not. Post at least 10 minutes of log here and we can see what is going >>>>>> on. >>>>>> >>>>>> Gary >>>>>> On Friday, 30 April 2021 at 19:00:29 UTC+10 ton...@gmail.com wrote: >>>>>> >>>>>>> Tom, >>>>>>> Puzzled/baffled, because following the hints from you and taking >>>>>>> into account also the hints from the much earlier discussion between >>>>>>> you >>>>>>> and Franklin Bockstael, but still no file openweerdata.htm appearing in >>>>>>> folder /home/weewx/public_html. >>>>>>> >>>>>>> Have attached the (probably) relevant setup-files: >>>>>>> - weewx.conf which in folder /home/weewx enables Standard-skin and >>>>>>> sets the related HTML_Root to /home/weewx/public_html >>>>>>> (*on purpose*, to get a different output from 'basic' etc.) >>>>>>> - skin.conf which in folder /home/weewx/skins/Standard in the >>>>>>> [ToDate]-segment at the first lines enables/sets the template for owd >>>>>>> (and >>>>>>> disables the 'later', other templates) >>>>>>> - the template openweerdata.htm.tmpl as located in >>>>>>> /home/weewx/skins/Standard >>>>>>> >>>>>>> The adapted conf-files seem OK, but now the nagging feeling that the >>>>>>> template has an inhibiting error. >>>>>>> But that is contradicted by the fact that Franklin Bockstael has it >>>>>>> in operation since long time without problems. >>>>>>> >>>>>>> During testing not running WeeWx as daemon, but 'discrete start' by >>>>>>> command ./bin/weexd >>>>>>> >>>>>>> Do you see a solution? >>>>>>> >>>>>>> >>>>>>> Op woensdag 28 april 2021 om 15:40:06 UTC+2 schreef tke...@gmail.com >>>>>>> : >>>>>>> >>>>>>>> I should add that the template must also be listed in the >>>>>>>> corresponding skin.conf, in the [[ToDate]] section. >>>>>>>> >>>>>>>> On Wed, Apr 28, 2021 at 6:31 AM Tom Keffer <tke...@gmail.com> >>>>>>>> wrote: >>>>>>>> >>>>>>>>> Yes, the skin has to be enabled for any of the templates in the >>>>>>>>> skin's folder to be processed. So, if you put your "HWA" template in >>>>>>>>> ./Standard, then the report StandardReport must be enabled. >>>>>>>>> >>>>>>>>> Or, you can put HWA in your "./basic" folder, then enable your >>>>>>>>> basic report. >>>>>>>>> >>>>>>>>> Either way will work. >>>>>>>>> >>>>>>>>> On Wed, Apr 28, 2021 at 1:07 AM Ton vanN <ton...@gmail.com> wrote: >>>>>>>>> >>>>>>>>>> *Brainwave?* >>>>>>>>>> Aiming at a first, basic realisation the folder >>>>>>>>>> /home/weewx/skins/Standard seeming the 'obvious' place, the template >>>>>>>>>> for >>>>>>>>>> generation of the HWA-file was put in that folder. >>>>>>>>>> Considering similarity with generation of other html-files the >>>>>>>>>> call to the HWA-template was put in skin.conf in same folder >>>>>>>>>> /home/weewx/skins/Standard >>>>>>>>>> >>>>>>>>>> Looking in /home/weewx at the below setting in weewx.conf, >>>>>>>>>> starting to doubt that such choice is correct. >>>>>>>>>> >>>>>>>>>> [[StandardReport]] >>>>>>>>>> # This is the old "Standard" skin. By default, it is >>>>>>>>>> not enabled. >>>>>>>>>> skin = Standard >>>>>>>>>> enable = false >>>>>>>>>> [[basic]] >>>>>>>>>> skin = basic >>>>>>>>>> HTML_ROOT = /var/weewx/reports >>>>>>>>>> [[[Extras]]] >>>>>>>>>> current = INST_SKIN_ROOT/basic/current.inc >>>>>>>>>> hilo = INST_SKIN_ROOT/basic/hilo.inc >>>>>>>>>> >>>>>>>>>> If enable=false, *it looks as if* 'Standard'will not be called >>>>>>>>>> and (as consequence no call to the HWA-template at it's present >>>>>>>>>> location). >>>>>>>>>> But if that assumption is correct, where should I alternatively >>>>>>>>>> put the template and call to the HWA-template to stay in line with >>>>>>>>>> 'normal >>>>>>>>>> practise'? >>>>>>>>>> *[Or simple enabling of 'Standard'?]* >>>>>>>>>> Op woensdag 28 april 2021 om 08:30:52 UTC+2 schreef Ton vanN: >>>>>>>>>> >>>>>>>>>>> As requested, attached is the repeating segment of the syslog >>>>>>>>>>> with debug=1 >>>>>>>>>>> >>>>>>>>>>> Op dinsdag 27 april 2021 om 13:21:12 UTC+2 schreef >>>>>>>>>>> tke...@gmail.com: >>>>>>>>>>> >>>>>>>>>>>> Please try again, but this time set debug=1 first. >>>>>>>>>>>> >>>>>>>>>>>> Stop weewx >>>>>>>>>>>> Set debug=1 (in weewx.conf) >>>>>>>>>>>> Restart weewx >>>>>>>>>>>> Post the log from startup. >>>>>>>>>>>> >>>>>>>>>>>> -tk >>>>>>>>>>>> >>>>>>>>>>>> On Fri, Mar 26, 2021 at 5:41 AM Ton vanN <ton...@gmail.com> >>>>>>>>>>>> wrote: >>>>>>>>>>>> >>>>>>>>>>>>> Related syslog-segment from RPI_CLI obtained with PuttySSH >>>>>>>>>>>>> >>>>>>>>>>>>> Op vrijdag 26 maart 2021 om 10:00:19 UTC+1 schreef Ton vanN: >>>>>>>>>>>>> >>>>>>>>>>>>>> Novice to WeeWX. >>>>>>>>>>>>>> Have the main progam as simulator up and running (= see files >>>>>>>>>>>>>> updating in folder public_html ). >>>>>>>>>>>>>> Now trying to implement a template to generate an uploadfile >>>>>>>>>>>>>> for HetWeerActueel. >>>>>>>>>>>>>> [has been discussed earlier in this forum, but that >>>>>>>>>>>>>> discussion apparently not ending with working solution] >>>>>>>>>>>>>> >>>>>>>>>>>>>> Template [attached in zip-file] should generate a htm-file. >>>>>>>>>>>>>> For activation of the template I inserted the following text >>>>>>>>>>>>>> in >>>>>>>>>>>>>> /home/weewx/skins/Standard/skin.conf at the end of the >>>>>>>>>>>>>> section CheetahGenerator >>>>>>>>>>>>>> >>>>>>>>>>>>>> [[HWA]] >>>>>>>>>>>>>> # Report that generates an uploadfile for >>>>>>>>>>>>>> HetWeerActueel. >>>>>>>>>>>>>> [[[OWD]]] >>>>>>>>>>>>>> template = openweerdata_wx.htm.tmpl >>>>>>>>>>>>>> >>>>>>>>>>>>>> Would expect the generated htm-file to appear in folder >>>>>>>>>>>>>> public_html >>>>>>>>>>>>>> When running WeeWX no errors (which is OK), but also nowhere >>>>>>>>>>>>>> the expected htm-file: >>>>>>>>>>>>>> what needs to be done to activate file-generation? >>>>>>>>>>>>>> >>>>>>>>>>>>> -- >>>>>>>>>>>>> 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/d6591a4a-09d9-41f7-8092-5e0fcbc113ccn%40googlegroups.com >>>>>>>>>>>>> >>>>>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/d6591a4a-09d9-41f7-8092-5e0fcbc113ccn%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/33bd4fee-48c9-42dd-9e1e-ce04ba727dddn%40googlegroups.com >>>>>>>>>> >>>>>>>>>> <https://groups.google.com/d/msgid/weewx-user/33bd4fee-48c9-42dd-9e1e-ce04ba727dddn%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/9446dcc8-ebd9-4d63-9198-c501af3b1988n%40googlegroups.com >>>>> >>>>> <https://groups.google.com/d/msgid/weewx-user/9446dcc8-ebd9-4d63-9198-c501af3b1988n%40googlegroups.com?utm_medium=email&utm_source=footer> >>>>> . >>>>> >>>> -- >>> You received this message because you are subscribed to a topic in the >>> Google Groups "weewx-user" group. >>> To unsubscribe from this topic, visit >>> https://groups.google.com/d/topic/weewx-user/_KTQ9XcGIRo/unsubscribe. >>> To unsubscribe from this group and all its topics, send an email to >>> weewx-user+...@googlegroups.com. >>> To view this discussion on the web visit >>> https://groups.google.com/d/msgid/weewx-user/fc4aac6f-befe-48f5-b8c8-da7d757dcfd1n%40googlegroups.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/fc4aac6f-befe-48f5-b8c8-da7d757dcfd1n%40googlegroups.com?utm_medium=email&utm_source=footer> >>> . >>> >>> -- >>> >>> =============================================================== >>> Contactinfo voor Anton van Nieuwenhuijzen: >>> Email = ton...@gmail.com >>> Fax2Mail = (+31/0)84.8397303 <+31%2084%20839%207303> [ook Voice2Mail] >>> =============================================================== >>> Deze E-mail en eventuele aanhangende files zijn >>> alleen bestemd voor de geadresseerde(n). >>> Als je deze E-mail ten onrechte hebt ontvangen, >>> dan aub verwijderen en de afzender informeren. >>> >>> -- >>> 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/dcf553de-16de-a99b-58d1-77897a1e8d5f%40gmail.com >>> >>> <https://groups.google.com/d/msgid/weewx-user/dcf553de-16de-a99b-58d1-77897a1e8d5f%40gmail.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/f4f1ee6e-84c1-48a2-b597-6e0813e4c0a7n%40googlegroups.com.
