-
-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] FileNotFoundError, wdc tries to pull files from the wrong skin dir? #267
Comments
Hello and thank you for reaching out! Very strange behaviour, I have never encountered this before. What changes did you make to One thing you could do is reset all your changes, does the error also occur with default configs? |
Hi, so this is what I did now:
I rely on changing these two things to not get in trouble with my other skin outputs. The other skins (Belchertown, Bootstrap, neowx) are installed in their normal places and output to /var/www/weewx/Belchertown etc. This is my entire WdcReport config:
I should also say that I have >10 years of data, so initial output generation takes a looong time. And after cleaning up everything and starting from scratch, now also I don't see any graphs being created. (EDIT: the missing graphs topic was solved, I noticed that the |
In your first comment your wrote 4 templates causing this error:
Is it the same error for all four templates? The Can you verify that the file |
Hi, yes, skins/weewx-wdc/includes/combined-diagram-tile.inc exists:
And it gets weirder: After some hours and a few restarts and essentially no relevant changes (just tried to reorder skin related lines in weewx.conf and removed a few commented lines) wdc suddenly started to create the missing files. However, the errors are still there, just not anymore with every wdc run as before. The output files get also updated as they should. And error also appear for other templates now, e.g. year-%Y.html.tmpl What is even more funny - I now see these skin crossfire errors also for other skin templates directing towards wdc or e.g. Bootstrap. As you can see they are more or less all the same, wildly trying to find files in the wrong skin's directory. I checked, and before the installation of wdc I have no such log entries at all in my syslog. I'm attaching a longer log snippet with all the log entry types I see (hopefully better to read). By now, as finally all the output files are there, it has turned more into a cosmetic "weird errors" issue, but still really strange. Thank you very much for looking into this! :-) |
Could this be a permission problem? Under which user is weewx running? Does it make a difference if you run the I am asking because
|
well, I had a similar suspicion - weewx runs as user weewx since the v5 upgrade. I chowned the wdc skin dir to weewx now, as all the other skins already were, but this hasn't had any impact. I also noticed that the Belchertown skin was missing The situation now is as follows:
It looks to me as if twice a day the cheetahgenerator decides to go a little wild and tries to mix things up a little bit. :-) |
This could be the statistics.html page - it gets generated every 12 hours per default config, see: https://github.com/Daveiano/weewx-wdc/blob/3.x/skins/weewx-wdc/skin.conf#L647 Could you try to comment out the |
I have re-enabled wdc skin and disabled statistics yesterday, and so far no issues/errors. So yes, it looks like the statistics page is the culprit here. (For the record, also no issues when wdc is entirely disabled) As far as it got generated, the statistics page looks okay to me (no glitches) and also the data make sense. As mentioned before, I have >11 years worth of data in weewx DB, so I assume the processing will be a bit stressful.... Will play with it some more. Thanks a lot! 👍 |
Good news, but would be great if all pages could be generated. I guess it takes too long and generation of the other reports starts in the background and things start to mess up... WeeWX supports the scheduling of reports via the
Another question: On which hardware are you running WeeWX? |
Hello, sorry for the late response and thanks for your hints. I have now scheduled all my reports in a way to allow for an 1 hour window at night where only wdc reports are is running and that matches the stale timer of the statistics file (24hours). This has removed the crossfire into other skins, predictably, the only error messages I see are related to the other wdc templates. See attached, these are all the errors I saw last night. The timestamp of the output file statistics.html is also showing 02:44 (same as when the errors are happening), but the timestamp shown inside ($alltime.end) is 02:31:00. I'm running weewx with MySQL on an Intel Xeon E-2276G server (6-Core, 16GB RAM). It also does some other things, but I wouldn't call it resource challenged... |
Very similar situation here. It loosely coincides with the other problem I posted about statistics.html failing due to database locking issues. |
Hope there's something here that helps:
My weewx.conf is very straightforward, almost no customization. |
So I did some research and stumbled upon this posts:
Belchertown has a very similar issue: poblabs/weewx-belchertown#924 Also related to weewx: https://github.com/weewx/weewx/wiki/v5-performance-troubleshooting I currently do not have the time to go through all the info provided but it could be related to the old db schema (v3 and earlier) vs the new db schema (v4 and later) and missing types in the database. When the data is not in the DB, it needs to be calculated at report run time - with a lot of years of data and a lot of types, this can take some time. Possible fixes from the posts:From poblabs/weewx-belchertown#924 (comment):
From https://groups.google.com/g/weewx-user/c/6rl2FIbqVp4/m/vNJ_bwjEBwAJ:
Would be great if somebody could test this out and report back! |
I have checked in my database, and most of these columns were existing and populated. The ones missing were: visibility I have created those columns and tested the backfill for some recent data (complete backfill for all data would take A LONG time). However, these columns are only filled with NULL at the moment, both by the service and by backfill. So I guess there is no module currently calculating these observations. |
Ok, so this wont make any difference I guess. What you could do to clarify if this is a general performance issue or related to some observations: You could try to remove observations in skin.conf from stat_tile_observations , table_tile_observations and diagrams: https://github.com/Daveiano/weewx-wdc/blob/3.x/skins/weewx-wdc/skin.conf#L563 Would be interesting if you can get to the point where no more errors appear and all files are generated. Sorry, but I am missing ideas here on how to solve this. I also think your hardware should be easily capable of handling this. |
Adding the columns to the database seems to have resolved the problem for me!
|
Just an FYI - I followed
Just an FYI - I followed these steps exactly, and then had to run "sudo weectl report run" and it completely fixed this issue on my install after it finished. |
Hi,
I just newly installed your skin on top of a weewx 5.0.2 installation that already runs Belchertown and some other skins. I did not change much yet in the config, apart from changing base_path and HTML_dir and trying to activate forecasting.
Overall I managed to create content, but some stuff (e.g. statistics page) I can't get to generate.
I see these errors below in the log. They are coming from the following 4 templates
statistics.html.tmpl,
celestial.html.tmpl
offline.html.tmpl
about.html.tmpl
and they are all trying to get includes from the Belchertown skin dir! Why is that? Why is it not looking in its own skin dir instead?
Thanks a lot, otherwise really a great looking skin!
The text was updated successfully, but these errors were encountered: