So close... (new DEB Install)

[Bob Breck]

New installation on a clear Raspberian install; configured for an AcuRite 02064C. When I run, i get this in the log file (over and over again), and no results in the weewx HTML file.

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 ]

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

Any help much appreciated!

[Glenn McKechnie]

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

[Glenn McKechnie]

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.

--

Cheers
Glenn

[Bob Breck]

Thanks, Glenn. Still puzzled. Set the debug to 1, and restarted; even did a manual start of weewx and not other messages from weewx in the file. Still nothing in file:///var/www/weewx/index.html either.

pi@raspberrypi:~ $ sudo tail -f /var/log/syslog

Oct  2 20:01:48 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Sun Oct  2 20:02:48 2016 [try http://www.rsyslog.com/e/2007 ]

Oct  2 20:12:53 raspberrypi vncserver-x11[499]: Connections: connected: 10.0.1.35::52163

Oct  2 20:12:53 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Sun Oct  2 20:13:53 2016 [try http://www.rsyslog.com/e/2007 ]

Oct  2 20:13:01 raspberrypi vncserver-x11[499]: Connections: authenticated: 10.0.1.35::52163, as pi (f permissions)

Oct  2 20:13:02 raspberrypi vncserver-x11[499]: SPrintConnMgr: Failed to add printer: server-error-service-unavailable

Oct  2 20:17:01 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Sun Oct  2 20:18:01 2016 [try http://www.rsyslog.com/e/2007 ]

Oct  2 20:17:01 raspberrypi CRON[1894]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

Oct  2 20:19:35 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Sun Oct  2 20:20:35 2016 [try http://www.rsyslog.com/e/2007 ]

Oct  2 20:19:54 raspberrypi systemd[1]: Started LSB: weewx weather system.

Oct  2 20:37:52 raspberrypi rsyslogd-2007: action 'action 17' suspended, next retry is Sun Oct  2 20:38:52 2016 [try http://www.rsyslog.com/e/2007 ]

[Andrew Milner]

You really need to find where weewx log messages are going to!!

try tail -100 /var/log/weewx.log and see if they are there ....

[vince]

Do you mean Raspbian ?  Which version ?

Which version of weewx did you install ?

Did you try to start it as the unprivileged user 'pi' or did you remember to preface your command with 'sudo' ?

Have you tried running weewx in the foreground to see if it runs at all ?

 

[Bob Breck]

The weewx.log file isn't there--can't seem to locate it.

[Bob Breck]

Sorry--yes, Raspbian (v. 8 Jessie), and weewx 3.5.0-1. I know this is brand-new version of Raspbian--might this be the issue? One other odity is that the istaller, when I can it, did not ask for parameters--I had to manually edit the .conf file.

I did run it with sudo, but am logged in as pi overall. Not sure how to run it in the foreground, unless it's what I've already tried: sudo /etc/init.d/weewx start

Thanks!

[mwall]

On Monday, October 3, 2016 at 3:01:54 PM UTC-4, Bob Breck wrote:

The weewx.log file isn't there--can't seem to locate it.

on debian systems, log output from weewx goes to /var/log/syslog

it would only go to /var/log/weewx.log if you reconfigured rsyslog

[mwall]

On Monday, October 3, 2016 at 3:09:15 PM UTC-4, Bob Breck wrote:

Sorry--yes, Raspbian (v. 8 Jessie), and weewx 3.5.0-1. I know this is brand-new version of Raspbian--might this be the issue? One other odity is that the istaller, when I can it, did not ask for parameters--I had to manually edit the .conf file.

I did run it with sudo, but am logged in as pi overall. Not sure how to run it in the foreground, unless it's what I've already tried: sudo /etc/init.d/weewx start

to run weewx in the foreground:

sudo weewxd /etc/weewx/weewx.conf

see the 'running weewx' section of the user guide

if you are not seeing weewx log messages in /var/log/syslog, then there is something about your system configuration that is swallowing the weewx log output.  it might be your systemd configuration, it might be your rsyslog configuration.

m

[mwall]

On Monday, October 3, 2016 at 3:09:15 PM UTC-4, Bob Breck wrote:

Sorry--yes, Raspbian (v. 8 Jessie), and weewx 3.5.0-1. I know this is brand-new version of Raspbian--might this be the issue? One other odity is that the istaller, when I can it, did not ask for parameters--I had to manually edit the .conf file.

how did you install weewx?

[vince]

On Monday, October 3, 2016 at 12:09:15 PM UTC-7, Bob Breck wrote:

Sorry--yes, Raspbian (v. 8 Jessie), and weewx 3.5.0-1. I know this is brand-new version of Raspbian--might this be the issue? One other odity is that the istaller, when I can it, did not ask for parameters--I had to manually edit the .conf file.

I did run it with sudo, but am logged in as pi overall. Not sure how to run it in the foreground, unless it's what I've already tried: sudo /etc/init.d/weewx start

ok, lets spin back to square one a little:

 - did you install Raspbian 'lite' or the 'full' one ?

 - was it 9/23 raspbian one that just came out, or the older May-2016 version ?

 - did you install a webserver ?

reason I ask is I have a couple raspi here, so I could try to recreate your issue if I had more data on exactly what you did....

[Bob Breck]

OK, running in foreground gives:

pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf

Traceback (most recent call last):

  File "/usr/bin/weewxd", line 64, in <module>

    weewx.engine.main(options, args)

  File "/usr/share/weewx/weewx/engine.py", line 853, in main

    engine = EngineClass(config_dict)

  File "/usr/share/weewx/weewx/engine.py", line 69, in __init__

    self.setupStation(config_dict)

  File "/usr/share/weewx/weewx/engine.py", line 87, in setupStation

    driver = config_dict[stationType]['driver']

  File "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__

    val = dict.__getitem__(self, key)

KeyError: 'AcuRite 02064C'

System Log then says:

sudo tail -f /var/log/syslog

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****      engine = EngineClass(config_dict)

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****    File "/usr/share/weewx/weewx/engine.py", line 69, in __init__

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****      self.setupStation(config_dict)

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****    File "/usr/share/weewx/weewx/engine.py", line 87, in setupStation

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****      driver = config_dict[stationType]['driver']

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****    File "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****      val = dict.__getitem__(self, key)

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****  KeyError: 'AcuRite 02064C'

Oct  3 19:42:53 raspberrypi weewx[8114]:     ****  Exiting.

Oct  3 19:44:02 raspberrypi wpa_supplicant[461]: wlan0: WPA: Group rekeying completed with 20:c9:d0:24:c8:35 [GTK=CCMP]

As to the install, I used PiBakery, which I believe uses the full Rapbian install. I then downloaded the .deb install file from the weewx site and ran it from the graphical interface. Since the config tool didn't run, I edited it with nano to add my parameters. Restarted, tried to run it manually, and in checking for the HTML output it couldn't find any HTML generated.

Only thing I found confusing, which loking at the log above may be an issue, is that the instructions ask for a driver and model for AcuRites (see below), but don't give a clear idea of the syntax to add the model. I added it on one line, which seems in line with other config instructions, since there is not a seperate variable for "model".

[AcuRite]

This section is for options relating to the AcuRite 5-in-1 series of weather stations with USB connectors.

model

Set to the station model. For example, "AcuRite 01035", "AcuRite 01036", or "02032C"

Thanks again, and virtual beers, to all of you!

--Bob

On Sunday, October 2, 2016 at 2:50:03 PM UTC-5, Bob Breck wrote:

[gjr80]

Hi,

So what do you have in weewx.conf? Looking at the User's Manual under The configuration file weewx.conf you should have (amongst other things) something like:

[Station]
    station_type = AcuRite

[AcuRite]
    model = 2064C

Reading the acurite code it seems the model setting is optional, it merely returns '2064C' to anything that asks for the model number.

Gary

[Bob Breck]

My weewx.conf file does not have a model variable:

    # Set to type of station hardware. There must be a corresponding stanza

    # in this file with a 'driver' parameter indicating the driver to be used.

    station_type = AcuRite 02064C

and that's it. There isn't a separate section for driver-specific information, either.

I'm attaching the whole conf file (it's got a .txt extention in this copy, but not in the actual file).

Thanks again.

[gjr80]

You want

station_type = AcuRite

not
station_type = AcuRite 02064C

Make the change, save weewx.conf then stop/start weewx. As I said the model = 2064C appears optional. You can add:

[AcuRite]
    model = 2064C

to weewx.conf if you want.

Gary

[Bob Breck]

OK, changed to just AcuRite (no model), and it seems to still be choking on that:

pi@raspberrypi:~ $ sudo weewxd /etc/weewx/weewx.conf

Traceback (most recent call last):

  File "/usr/bin/weewxd", line 64, in <module>

    weewx.engine.main(options, args)

  File "/usr/share/weewx/weewx/engine.py", line 853, in main

    engine = EngineClass(config_dict)

  File "/usr/share/weewx/weewx/engine.py", line 69, in __init__

    self.setupStation(config_dict)

  File "/usr/share/weewx/weewx/engine.py", line 87, in setupStation

    driver = config_dict[stationType]['driver']

  File "/usr/lib/python2.7/dist-packages/configobj.py", line 554, in __getitem__

    val = dict.__getitem__(self, key)

KeyError: 'AcuRite'

[gjr80]

My bad, you need to have an [AcuRite] section in weewx.conf with a driver setting. Something like this:

[AcuRite]
    # This section is for AcuRite weather stations.
   
    # The station model, e.g., 'AcuRite 01025' or 'AcuRite 02032C'
    model = AcuRite 2064C
   
    # The driver to use:
    driver = weewx.drivers.acurite

Gary

[Bob Breck]

No bad—you’re being helpful. Unfortunately, I don’t have an Accurate section in my file; only station-specific section I have is for [Simulator]. Can I just add it manually?

--
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/7j5TAf5oV8s/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gjr80]

Yes you can add it manually. It is normally added automatically when you install (if you tell it you are using an AcuRite station) or later on if you reconfigure using wee_config.

[Bob Breck]

Yea! Looks like it's working. Thanks so very much, Gary and all. I had run the installer manually at an earlier point and it did't ask for a model then, either but looks lie it's humming right along now.