Just to clarify my previous post about the HTML_ROOT entry in
/etc/weewx/weewx.conf
My extract shows
# Where the generated reports should go, relative to WEEWX_ROOT
HTML_ROOT = /var/www/html/weewx
and that is correct for my setup
Your entry should point to the location of *your* working webserver.
On 3 October 2016 at 08:45, Glenn McKechnie <[email protected]> wrote:
> Hi Bob,
>
> There's nothing in that snippet that indicates why you have no html output.
>
>
>> Oct 2 14:17:01 raspberrypi rsyslogd-2007: action 'action 17' suspended,
>> next retry is Sun Oct 2 14:17:31 2016 [try http://www.rsyslog.com/e/2007 ]
>
>
> that action 7 info message is more a nuisance than anything. It can be
> eliminated by commenting out the last couple of lines of your config
> file, /etc/rsyslog.conf , as per the following snippet
>
> #
> #daemon.*;mail.*;\
> # news.err;\
> # *.=debug;*.=info;\
> # *.=notice;*.=warn>······|/dev/xconsole
>
>> Oct 2 14:17:01 raspberrypi CRON[1511]: (root) CMD ( cd / && run-parts
>> --report /etc/cron.hourly)
>> Oct 2 14:34:08 raspberrypi vncserver-x11[498]: Connections: connected:
>> 10.0.1.35::50737
>
> and those are unrelated info messages, one from CRON: (that particular
> one you'll get every hour!) and the other from a vncserver:. You are
> looking for messages from weewx: and there are none there.
>
> You're best to turn on debugging in /etc/weewx/weewx.conf
> [...]
> # Set to 1 for extra debug info, otherwise comment it out or set to zero
> debug = 0
>
> and then restart weewx. If nothing obvious is revealed then post the
> whole log - or at least an extract large enough to show what weewx is
> doing over a longer time period.
>
> Questions...
>
> Is your webserver running, does it return pages.
>
> Does the actual www file location match what's in /etc/weewx/weewx.conf?
>
> ie:-
> [StdReport]
> [...]
> # Where the generated reports should go, relative to WEEWX_ROOT
> HTML_ROOT = /var/www/html/weewx
>
> After that I'm out of ideas, but I'm unfamiliar with an AcuRite 02064C
> and they all have their quirks. Perhaps its taking a while to generate
> data because of its archive interval? and that's where a more verbose
> syslog extract will be helpful.
>
> So, best to make the changes and checks outlined above, then post your
> weewx.conf file and syslog for others to make more informed
> responses.
>
> --
>
> Cheers
> Glenn
--
Cheers
Glenn
--
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.
