Thank you. Even if you indicate that url in station_url CSS fails. But I will continue investigating.
El martes, 4 de septiembre de 2018, 14:13:04 (UTC+2), Pat escribió: > > This is because your CSS styles aren't loading due to the station_url > setting being wrong in weewx.conf. > > In weewx.conf change station_url to " > http://www.meteomontaos.es/belchertown"; and let me know. > > > > On Tuesday, September 4, 2018 at 6:39:18 AM UTC-4, Juan Antonio Mosquera > wrote: > > I have re-tried today to reinstall the extension and everything works OK. > But when showing the web it seems that there is a problem with styles > (surely by routes). > > http://www.meteomontaos.es/belchertown/ > > Greetings. > > El martes, 4 de septiembre de 2018, 2:46:44 (UTC+2), Pat escribió: > > That's what looks like is going on. Your reports are stepping on each > other and the database is locked. > > You can either disable the highcharts portion by setting highcharts_enabled > = 0 <https://github.com/poblabs/weewx-belchertown#general-options> in > options or disable the skin all together. I'm going to be tinkering around > with the chart generations this week. I'll keep you updated on anything > that needs some testing > > > On Monday, September 3, 2018 at 8:04:07 PM UTC-4, Philip Kutzenco wrote: > > Pat > > It actually may be running a bit better now, though the Belchertown web > page update time is behind my SteelSeries web page. And both are behind my > archive period. I'm not using mqtt at this point. Just want to get this > running. > > So maybe it's now just that report generation is extremely slow. I hope > there is a way to resolve that without buying a new box to run weewx on. > > It looks like it's taking about 575 seconds to generate the files for the > Belchertown report. I am also still seeing notes about report thread launch > being aborted as one is already running. My archive period is 300 seconds. > > > Best, > Phil > > On Monday, September 3, 2018 at 7:46:07 PM UTC-4, Philip Kutzenco wrote: > > Pat, > > I installed WeeWX with install.py. So everything lives underneath > /home/weewx/. > > I replaced the file in /Belchertown/records folder with the one you gave > me. Then I re-enabled the Belchertown skin in weewx.conf, restarted WeeWX > and ran wee_reports. Per the log extract below, after about 8 minutes, > weewx hung with the database locked. WeeWX automatically restarted 2 > minutes later. > > In between my efforts to run Belchertown, I've been disabling the > Belchertown extension by commenting out the three lines in weewx.conf > starting with [[Belchertown]] and then stopping and then starting weewx > again. I re-enable it to test the next change. > > I wonder if locking the file is also the cause of the complaints that > header.html.tmpl doesn't exist in earlier efforts. I noticed that a > report thread couldn't be started as one was already running. Maybe that > running report thread locked the file as it (or something) locked the > archive database? > > Also, it seems that typing sudo /etc/init.d/weewx stop doesn't always stop > weewx when Belchertown is running. Even though I return to the prompt, when > I looked at ps, WeeWX was still running. I ended up rebooting once and > Killing the PID the last time. > > Will the Belchertown report generation time decrease after the initial run > through the database? Or will it take the same time each report generation > cycle? > > Thoughts? I saw a note on disabling the charts to speed things up, but I'd > really hate to do that. > > Best, > Phil > > Sep 3 19:02:38 Weather-pi wee_reports[3281]: cheetahgenerator: Generated > 14 files for report StandardReport in 19.27 seconds > Sep 3 19:02:51 Weather-pi systemd[1]: Started Session c7 of user pi. > Sep 3 19:02:53 Wea > > ... -- 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. For more options, visit https://groups.google.com/d/optout.
