Andrew, you may be right - and that's why I mentioned I was confused 
earlier - quite a few generators that do different things. :) 

Still - I'm not sure where the issue lies with this particular issue yet. I 
don't think it's a CopyGenerator problem as initially reported. That was 
what my testing was trying to rule out. 



On Tuesday, November 27, 2018 at 10:57:52 AM UTC-5, Andrew Milner wrote:
>
> Pat
> If I am understanding correctly it is the report generator which is 
> putting the .json files in the correct place - not the copy generator.
>
>
>
> On Tuesday, 27 November 2018 16:44:52 UTC+2, Pat wrote:
>>
>> Gary, understood on all counts. My belief is that the copy generator will 
>> copy the newly generated files by the report generator. In this case, it's 
>> the 4 json files. This is how it's working in Belchertown 0.7, as well as 
>> in 0.8rc1,2,3. I don't think I need to explicitly specify copy_always = 
>> *.json. If this were the case, then the Standard skin would have copy_always 
>> = *.html - which is does not. Further, my skin would have been broken 
>> since 0.1. 
>>
>> Aside from all of that, I did perform an install with the install.py, and 
>> my syslog did return an error of a missing file. It doesn't seem to be 
>> related, but still something I just fixed in a recent commit. 
>>
>> Back to this issue: From an install using setup.py, I have installed the 
>> Belchertown skin using /home/weewx/bin/wee_extension --install. My 
>> weewx.conf is below:
>>
>>     [[Highcharts_Belchertown]]
>>         HTML_ROOT = public_html/belchertown
>>         skin = Highcharts_Belchertown
>>     [[Belchertown]]
>>         HTML_ROOT = public_html/belchertown
>>         skin = Belchertown
>>
>>
>> Upon issuing a /home/weewx/bin/wee_reports, I get the following:
>>
>> Nov 27 14:32:09 setuppy wee_reports[1473]: cheetahgenerator: Generated 4 
>> files for report Highcharts_Belchertown in 2.52 seconds
>> Nov 27 14:32:09 setuppy wee_reports[1473]: copygenerator: copied 0 files 
>> to /home/weewx/public_html/belchertown
>>
>>
>> However, within /home/weewx/public_html/belchertown/json I have 4 json 
>> files with a timestamp of 14:32. So it seems it IS copying them, but it's 
>> saying it is NOT. 
>>
>> The charts on the website are updated as well. 
>>
>> And again at 9:40 (note my system is in UTC, so it shows 14:40):
>>
>> Nov 27 14:40:18 setuppy weewx[1689]: cheetahgenerator: Generated 4 files 
>> for report Highcharts_Belchertown in 2.70 seconds
>> Nov 27 14:40:18 setuppy weewx[1689]: copygenerator: copied 0 files to /
>> home/weewx/public_html/belchertown
>>
>> root@setuppy:/home/weewx# ls -al /home/weewx/public_html/belchertown/json
>> total 3320
>> drwxr-xr-x  2 root root    4096 Nov 27 14:40 .
>> drwxr-xr-x 11 root root    4096 Nov 27 14:40 ..
>> -rw-r--r--  1 root root    4150 Nov 27 *14:40 day.**json*
>> -rw-r--r--  1 root root    1035 Nov 27 14:32 earthquake.json
>> -rw-r--r--  1 root root      14 Nov 27 14:40 index.html
>> -rw-r--r--  1 root root    1961 Nov 27 *14:40 month.**json*
>> -rw-r--r--  1 root root    2157 Nov 27 *14:40 week.**json*
>> -rw-r--r--  1 root root    9995 Nov 27 14:40 weewx_data.json
>> -rw-r--r--  1 root root 3353388 Nov 27 *14:40 year.**json*
>>
>>
>> And the charts have updated as well for 9:40. 
>>
>> At this time I don't see anything wrong with Belchertown. Maybe a slight 
>> cosmetic bug with the output of the copygenerator?
>>
>>
>> *Rich*, when you see the archive interval run and it says 0 files 
>> copied, please confirm the timestamps on the files in bold above. Do they 
>> update?
>>
>> If you have MQTT disabled on your Belchertown skin, you will need to 
>> refresh the page to see the updated charts. 
>>
>> Let me know what happens. 
>>
>>
>>
>> On Monday, November 26, 2018 at 9:25:34 PM UTC-5, gjr80 wrote:
>>>
>>>
>>> On Tuesday, 27 November 2018 12:09:05 UTC+10, Pat wrote:
>>>>
>>>> Ok your explanation is my understanding as well. Understood on Rich's 
>>>> report of 0 files copied - which is why I'm lost as to why it's failing 
>>>> since it should have 4 files to copy. The Belchertown highcharts skin 
>>>> should create new json files every archive interval, which should be a 
>>>> fresh copy to the HTML_DIR. 
>>>>
>>>
>>> Now you are confusing me. You say 'it should have 4 files to copy', that 
>>> implies to me you are expecting the report generator to generate 4 files 
>>> then you are expecting them to be copied somewhere. Given the conversation 
>>> centres on the copy generator I take it you are expecting the copy 
>>> generator to copy these 4 .json files. The 4 files are in fact 
>>> generated by the report generator, this is evidenced by:
>>>
>>> Nov 25 17:35:44 raspberrypi weewx[1619]: cheetahgenerator: Generated 4 
>>> files for report Highcharts_Belchertown in 6.84 seconds
>>>
>>> but the copy generator will never copy these files, the copy generator 
>>> file specs in Highcharts_Belchertown skin config file do not match 
>>> *.json files and as I said earlier a properly configured skin does not need 
>>> such files to be copied.
>>>
>>> I'm sorry if this seems to be pedantic but when you start talking about 
>>> copying files and copy generators etc you need to quite specific.
>>>  
>>>
>>>> Unless there's a typo in a config, or something else, that's preventing 
>>>> that from happening. My comment of "first I'm hearing of it" is in regards 
>>>> to the 3 or so beta testers of 0.8 who haven't reported this issue. 
>>>>
>>>
>>> In this case I think a bit of sleuthing might be needed on Rich' system 
>>> to ensure the generated files content looks correct (do they have data), 
>>> are saved (not copied) to the correct directory and then suitably made 
>>> available (copied or via symlink) to the web server. Then make sure the JS 
>>> is looking in the correct location for the .json files.
>>>  
>>> Gary
>>>
>>

-- 
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].
For more options, visit https://groups.google.com/d/optout.

Reply via email to