installation of Weewx

[Parsoli 69]

Just amazed.  I've built many websites from template from many folks.  Whether that's Meteotemplate, Weather26, or many others.  Setup linux ubuntu or redhat myself following instructions by these developers and always had a functional website, IF, I followed the instructions.

I've built 4 virtual servers on Ubuntu using the multiple DIFFERENT instructional sets from weewx whether that's using the DEB installation method of the Python installation script method.  Can't get one to function properly without having to go hard core into Apache is make changes on what path is serving up web pages. I can get close and get a webpage to show, but it will be a snapshot in time.  wont' update, even setting up init.d, etc.....

I have read other posts here about people complaining about too many instructions and nothing working 100% if you follow any of them.  Any suggestions on a solid installation method/resource?  Whether that's following a .deb install, python or whatever?  This stuff it pretty simple.  You either cut it into a "from scratch" method or a 'adding a new service for weewx to an existing webserver".  At least in my mind.

Thanks in advance for any direction

Steve

[gjr80]

Hi,

I thought for a while about how I might respond to your post and then I thought, this is a good question. Other than upgrading, my on-line WeeWX install (setup.py) has not been touched for years; when i want to test something on WeeWX I create a VirtualBox VM, install the latest Debian and run a short script I have that installs WeeWX via setup.py, so I seldom look at the instructions.

So just now I downloaded the latest Debian net ISO and installed on a VirtualBox VM. When asked if I wanted a web server installed I checked the box. VM created and Debian running.

Next I went to the WeeWX User's Guide, specifically the Installing WeeWX page and then selected the link Installing from DEB package. I followed the Configure apt, Install and Status instructions on this page selecting simulator as the weather station. All worked, no problems. WeeWX is running.

Then I went back to the WeeWX User's Guide and went to the Integrating with a web server page. I skipped step 1 as Apache2 was installed as part of my Debian install. Step 2 told me that since I had installed from a DEB package I should not have to do a thing to setup Apache. So I opened a browser on another computer on my network, entered the IP address of my newly installed WeeWX machine followed by /weewx (ie w.x.y.z/weewx) and straight way up came my WeeWX page with data and plots. It was timestamped 15:35. I waited 5 minutes and refreshed the page and now had data timestamped 15:40.

Great, clearly everything is working, and no need to do anything with Apache, not even type its name anywhere. You mentioned Ubuntu and I installed on Debian, granted Debian is not Ubuntu but I think the lineage is pretty close. Notwithstanding, I took the time to download the Ubuntu 18.04 netinst ISO and installed on a new VM, though noticeably I was not asked about installing a web server (perhaps my fault, Ubuntu is not my distro of choice so not that familiar with the vagaries of Ubuntu). I then followed the exact same WeeWX install instructions as for my Debian VM though this time I needed to follow step 1 of the Integrating with a web server page and install Apache2. It was a straight up Apache2 install with no config needed on my behalf.  When I went to the address for the Ubuntu VM (with /weewx appended) in my browser up came the WeeWX page with current data and plots, five minutes later and a refresh showed updated data and plots.

So getting back to your question, you should find the necessary instructions in the links above. If Apache is on your WeeWX machine you need do nothing to configure Apache/WeeWX.Might I suggest that if you are having specific problems either configuring WeeWX to operate with your station, getting WeeWX to run in general or work with your web server you provide a little more detail rather than 'it doesn't work'.

Gary

[Parsoli 69]

Thanks Gary.  Frustration took over my fingers, as usual.  In essence, Apache wasn't aware of the conf.d config.  In one section for Apache installations, it says to create a weewx.conf file at /etc/apache2/conf.d/weewx.conf.  conf.d is not a directory so that step fails.

I ended up creating a sym link shown below to get [ip address]/weewx to show a page

 sudo ln -s /home/weewx/public_html /var/www/html/weewx

Now a page is shown and it stays static.  It says it's 12:30 whereas it was only 8:45am here in Chicago.  See below

Mar 11 08:49:40 weather weewx[1067]: vantage: Getting archive packets since 2020-03-11 12:30:00 CDT (1583947800)

Mar 11 08:49:40 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 08:49:41 weather weewx[1067]: vantage: Retrieving 1 page(s); starting index= 3

Mar 11 08:49:42 weather weewx[1067]: vantage: DMPAFT complete: page timestamp 2020-03-11 08:00:00 CDT (1583931600) less than final timestamp 2020-03-11 12:30:00 CDT (1583947800)

Mar 11 08:49:42 weather weewx[1067]: vantage: Catch up complete.

Mar 11 08:49:42 weather weewx[1067]: engine: Starting main packet loop.

Mar 11 08:49:42 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 08:49:43 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 08:49:43 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 08:49:43 weather systemd[1]: Started Session 3 of user sparsons.

Mar 11 08:50:04 weather systemd-timesyncd[555]: Synchronized to time server 91.189.91.157:123 (ntp.ubuntu.com).

The system time was accurate even before the sync of NTP showing on last line above.  Now, the webpage does not update at all.  During the time to write this, these next two lines show up in the tail of syslog.  I'm using a David Pro2 tied to a Meteobridge via serial and am accessing that via IP address using the vantage driver which will auto-hit port 22222 (even REM'd that port line out of .conf file as some folks have suggested).

Mar 11 08:56:19 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 08:56:19 weather weewx[1067]: vantage: Gentle wake up of console successful

Webpage still shows 12:30 and no statistics have updated.  Temp still the same, etc...reading more, I'm unsure if using meteobridge in this fashion will ever work.

Syslog Tail now shows:

Mar 11 08:56:19 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 08:56:19 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 09:00:15 weather weewx[1067]: vantage: Getting archive packets since 2020-03-11 12:30:00 CDT (1583947800)

Mar 11 09:00:15 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 09:00:16 weather weewx[1067]: vantage: Retrieving 2 page(s); starting index= 3

Mar 11 09:00:17 weather weewx[1067]: vantage: DMPAFT complete: page timestamp 2020-03-11 08:00:00 CDT (1583931600) less than final timestamp 2020-03-11 12:30:00 CDT (1583947800)

Mar 11 09:00:17 weather weewx[1067]: vantage: Catch up complete.

Mar 11 09:00:17 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 09:00:17 weather weewx[1067]: reportengine: Running reports for latest time in the database.

Mar 11 09:00:17 weather weewx[1067]: reportengine: Running report 'SeasonsReport'

Mar 11 09:00:17 weather weewx[1067]: reportengine: Found configuration file /home/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'

Mar 11 09:00:17 weather weewx[1067]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']

Mar 11 09:00:17 weather weewx[1067]: manager: Daily summary version is 2.0

Mar 11 09:00:17 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 09:00:18 weather weewx[1067]: cheetahgenerator: Generated 8 files for report SeasonsReport in 0.62 seconds

Mar 11 09:00:18 weather weewx[1067]: manager: Daily summary version is 2.0

Mar 11 09:00:18 weather weewx[1067]: imagegenerator: Generated 42 images for SeasonsReport in 0.60 seconds

Mar 11 09:00:18 weather weewx[1067]: copygenerator: copied 5 files to /home/weewx/public_html

Mar 11 09:00:18 weather weewx[1067]: reportengine: Report 'SmartphoneReport' not enabled. Skipping.

Mar 11 09:00:18 weather weewx[1067]: reportengine: Report 'MobileReport' not enabled. Skipping.

Mar 11 09:00:18 weather weewx[1067]: reportengine: Report 'StandardReport' not enabled. Skipping.

Mar 11 09:00:18 weather weewx[1067]: reportengine: Report 'FTP' not enabled. Skipping.

Mar 11 09:00:18 weather weewx[1067]: reportengine: Report 'RSYNC' not enabled. Skipping.

So the service is running correctly, but webpage still shows 12:30, same time/temp/wind/bar, etc....as if page is not updating.  Any thoughts?  Maybe a permissions issue?

[Parsoli 69]

....and now the driver starts to suffer trying to query the Davis thru the meteobridge.  I suspect even if we figured out how to get the realtime data to show, this problem with the driver to meteobridge combo will still peeter out.  I noticed some very smart folks trying to get meteobridge to write to a db so that Weewx could read from it, however didn't see it going 100 yds for a touchdown.

Mar 11 09:04:36 weather systemd[1]: Starting Cleanup of Temporary Directories...

Mar 11 09:04:36 weather systemd[1]: Started Cleanup of Temporary Directories.

Mar 11 09:06:53 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 09:06:53 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 09:11:47 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:11:47 weather weewx[1067]: vantage: LOOP try #1; error: timed out

Mar 11 09:11:47 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 09:11:51 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:11:51 weather weewx[1067]: vantage: Retry  #0 failed

Mar 11 09:11:56 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:11:56 weather weewx[1067]: vantage: Retry  #1 failed

Mar 11 09:12:01 weather weewx[1067]: vantage: Retry  #2 failed

Mar 11 09:12:06 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:12:06 weather weewx[1067]: vantage: Retry  #3 failed

Mar 11 09:12:06 weather weewx[1067]: vantage: Unable to wake up console

Mar 11 09:12:06 weather weewx[1067]: vantage: LOOP try #2; error: Unable to wake up Vantage console

Mar 11 09:12:06 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 09:12:06 weather weewx[1067]: vantage: Gentle wake up of console successful

Mar 11 09:14:25 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:14:25 weather weewx[1067]: vantage: LOOP try #3; error: timed out

Mar 11 09:14:25 weather weewx[1067]: vantage: Requesting 200 LOOP packets.

Mar 11 09:14:29 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:14:29 weather weewx[1067]: vantage: Retry  #0 failed

Mar 11 09:14:34 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:14:34 weather weewx[1067]: vantage: Retry  #1 failed

Mar 11 09:14:38 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:14:38 weather weewx[1067]: vantage: Retry  #2 failed

Mar 11 09:14:43 weather weewx[1067]: vantage: ip-read error: timed out

Mar 11 09:14:43 weather weewx[1067]: vantage: Retry  #3 failed

Mar 11 09:14:43 weather weewx[1067]: vantage: Unable to wake up console

Mar 11 09:14:43 weather weewx[1067]: vantage: LOOP try #4; error: Unable to wake up Vantage console

Mar 11 09:14:43 weather weewx[1067]: vantage: LOOP max tries (4) exceeded.

Mar 11 09:14:43 weather weewx[1067]: engine: Main loop exiting. Shutting engine down.

Mar 11 09:14:43 weather weewx[1067]: engine: Shutting down StdReport thread

Mar 11 09:14:43 weather weewx[1067]: engine: StdReport thread has been terminated

Mar 11 09:14:43 weather weewx[1067]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data.

Mar 11 09:14:43 weather weewx[1067]:     ****  Waiting 60 seconds then retrying...

Mar 11 09:15:43 weather weewx[1067]: engine: retrying...

Mar 11 09:15:43 weather weewx[1067]: engine: Using configuration file /home/weewx/weewx.conf

Mar 11 09:15:43 weather weewx[1067]: engine: Debug is 1

Mar 11 09:15:43 weather weewx[1067]: engine: Initializing engine

Mar 11 09:15:43 weather weewx[1067]: engine: Loading station type Vantage (weewx.drivers.vantage)

Mar 11 09:15:43 weather weewx[1067]: vantage: Driver version is 3.1.1

Mar 11 09:15:47 weather weewx[1067]: vantage: Socket error while opening port 22222 to ethernet host 192.168.1.20.

Mar 11 09:15:47 weather weewx[1067]: engine: Import of driver failed: timed out (<class 'weewx.WeeWxIOError'>)

Mar 11 09:15:47 weather weewx[1067]: engine: Unable to load driver: timed out

Mar 11 09:15:47 weather weewx[1067]:     ****  Exiting...

Mar 11 09:17:01 weather CRON[1609]: (root) CMD (   cd / && run-parts --report /etc/cron.hourly)

[mwall]

On Wednesday, March 11, 2020 at 10:02:59 AM UTC-4, Parsoli 69 wrote:

Thanks Gary.  Frustration took over my fingers, as usual.  In essence, Apache wasn't aware of the conf.d config.  In one section for Apache installations, it says to create a weewx.conf file at /etc/apache2/conf.d/weewx.conf.  conf.d is not a directory so that step fails.

not sure which instructions you are referring to by 'one section for Apache installations'.

the directory /etc/apache2/conf.d does exist for many apache installations, but it depends on how apache was packaged for the operating system and operating system version.

if you would like to understand some of the permutations, the weewx wiki has a page that explains strategies for configuring some of the web server variations:

https://github.com/weewx/weewx/wiki/webserver

 

I ended up creating a sym link shown below to get [ip address]/weewx to show a page

 sudo ln -s /home/weewx/public_html /var/www/html/weewx

that would be 'strategy 3' from the wiki page above.

 

Webpage still shows 12:30 and no statistics have updated.  Temp still the same, etc...reading more, I'm unsure if using meteobridge in this fashion will ever work.

it should work

 

Syslog Tail now shows:

Mar 11 09:00:17 weather weewx[1067]: vantage: DMPAFT complete: page timestamp 2020-03-11 08:00:00 CDT (1583931600) less than final timestamp 2020-03-11 12:30:00 CDT (1583947800)

So the service is running correctly, but webpage still shows 12:30, same time/temp/wind/bar, etc....as if page is not updating.  Any thoughts?  Maybe a permissions issue?

looks like you have data in the weewx database that have a timestamp that is more recent than the time reported by your system.

 

[mwall]

On Wednesday, March 11, 2020 at 10:32:33 AM UTC-4, Parsoli 69 wrote:

....and now the driver starts to suffer trying to query the Davis thru the meteobridge.  I suspect even if we figured out how to get the realtime data to show, this problem with the driver to meteobridge combo will still peeter out.  I noticed some very smart folks trying to get meteobridge to write to a db so that Weewx could read from it, however didn't see it going 100 yds for a touchdown.

Mar 11 09:14:43 weather weewx[1067]: engine: Caught WeeWxIOError: Max tries exceeded while getting LOOP data.

weewx tries repeatedly to connect to 192.168.1.20:22222, but those attempts fail.

is the meteobridge at ip address 192.168.1.20?

is the meteobridge listening at port 22222?

i do not have first-hand experience with the meteobridge port relay/forward/relay (not sure which approach the meteobridge uses).  i said that it *should* work, because boris seems to be a very competent developer, and i would be surprised if such a feature was not working, given all of the meteobridge users and boris' responsiveness to fixing bugs.

it is possible that the way that the weewx vantage driver probes the davis hardware somehow exposes a bug in meteobridge or a bug in the weewx vantage driver code.  if so, we should fix that.

however, doing that requires that you are certain that the problem is not your configuration.

can your weewx installation communicate directly with your vantage station?

m

[John Kline]

Ubuntu is like Debian in this regard (and others).

The script should go in conf-available and then a symlink should be created in conf-enabled.

To be clear:

/etc/apache2/conf-enabled/weewx.conf -> ../conf-available/weewx.conf

There is a script to create the symlink so you can just type:

a2enconf weewx

(That is, you can type that after you put the script in the conf-available directory.)

Of course, you could also just put the script in conf-enabled.

On Mar 11, 2020, at 7:39 AM, mwall <mw...@users.sourceforge.net> wrote:



--
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+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/bb1538bd-90ac-4e48-a5ab-2ef4abac3934%40googlegroups.com.

[Parsoli 69]

Yup, it's listening on that IP and that port.  When first running the weewx service on a new VM, it will communicate and pull down the last 2 or so months worth of data just fine.  Sits there dumping this data for quite a few minutes.  Then it goes thru whatever polling timeline to gather more data.  See below:

Mar 11 09:35:23 weather systemd[1395]: Reached target Paths.

Mar 11 09:35:23 weather systemd[1395]: Listening on GnuPG cryptographic agent and passphrase cache (access for web browsers).

Mar 11 09:35:23 weather systemd[1395]: Listening on GnuPG network certificate management daemon.

Mar 11 09:35:23 weather systemd[1395]: Listening on GnuPG cryptographic agent (ssh-agent emulation).

Mar 11 09:35:23 weather systemd[1395]: Reached target Sockets.

Mar 11 09:35:23 weather systemd[1395]: Reached target Basic System.

Mar 11 09:35:23 weather systemd[1]: Started User Manager for UID 1000.

Mar 11 09:35:23 weather systemd[1395]: Reached target Default.

Mar 11 09:35:23 weather systemd[1395]: Startup finished in 251ms.

Mar 11 09:35:28 weather systemd[1]: Started Session 3 of user sparsons.

Mar 11 09:40:01 weather weewx[1148]: vantage: Requesting 200 LOOP packets.

Mar 11 09:40:01 weather weewx[1148]: vantage: Gentle wake up of console successful

Mar 11 09:46:39 weather weewx[1148]: vantage: Requesting 200 LOOP packets.

Mar 11 09:46:39 weather weewx[1148]: vantage: Gentle wake up of console successful

Mar 11 09:48:18 weather systemd[1]: Starting Cleanup of Temporary Directories...

Mar 11 09:48:19 weather systemd[1]: Started Cleanup of Temporary Directories.

Mar 11 09:53:17 weather weewx[1148]: vantage: Requesting 200 LOOP packets.

Mar 11 09:53:17 weather weewx[1148]: vantage: Gentle wake up of console successful

This can go on for some time.  This is after a fresh reboot of the Ubuntu installation after the driver stopped working.  So when the driver states it's requesting 200 LOOP packets, I am unsure if that means it's pulling actual data.  Website still shows the same static data as it did after it's last full pull.  You can see this @ https://weather.parsoli.net/weewx

Any suggestion on how to tell if this is pulling data correctly?  It's as if after a few pulls, meteobridge will become unresponsive on that port.  however, it's still pushing weather data to WU via meteobridge internals...

[mwall]

On Wednesday, March 11, 2020 at 10:39:40 AM UTC-4, mwall wrote:

Syslog Tail now shows:

Mar 11 09:00:17 weather weewx[1067]: vantage: DMPAFT complete: page timestamp 2020-03-11 08:00:00 CDT (1583931600) less than final timestamp 2020-03-11 12:30:00 CDT (1583947800)

So the service is running correctly, but webpage still shows 12:30, same time/temp/wind/bar, etc....as if page is not updating.  Any thoughts?  Maybe a permissions issue?

looks like you have data in the weewx database that have a timestamp that is more recent than the time reported by your system.

on second look, i think i am mistaken - this looks like corrupt memory in the davis logger, not the weewx database.  you might have to clear the davis logger to fix it.  or use wee_device to dump the data first and diagnose it.  one of the vantage experts would have to give you more guidance.

you could try that directly with the davis (we *know* that works), or via the meteobridge.  that would give you more information about how well the meteobridge forward/mirror/relay implementation works.

also, since you are relaying through the meteobridge, you might want to take things one step at a time.  in your weewx configuration, set record_generation=software so that you collect only live 'loop' data.

once you verify that you can test the historical/logger stuff.

[Parsoli 69]

Yea, just ran thru that cycle again:  So I suppose best to just clear the davis as I don't believe any way for the meteobridge to do that.  It just pulls data from it.  Will look up instructions on how to do that and give it a whirl.  Thanks

Mar 11 09:59:55 weather weewx[1148]: vantage: Requesting 200 LOOP packets.

Mar 11 09:59:55 weather weewx[1148]: vantage: Gentle wake up of console successful

Mar 11 10:00:15 weather weewx[1148]: vantage: Getting archive packets since 2020-03-11 12:30:00 CDT (1583947800)

Mar 11 10:00:15 weather weewx[1148]: vantage: Gentle wake up of console successful

Mar 11 10:00:16 weather weewx[1148]: vantage: Retrieving 2 page(s); starting index= 3

Mar 11 10:00:17 weather weewx[1148]: vantage: DMPAFT complete: page timestamp 2020-03-11 08:00:00 CDT (1583931600) less than final timestamp 2020-03-11 12:30:00 CDT (1583947800)

Mar 11 10:00:17 weather weewx[1148]: vantage: Catch up complete.

Mar 11 10:00:17 weather weewx[1148]: vantage: Requesting 200 LOOP packets.

Mar 11 10:00:17 weather weewx[1148]: reportengine: Running reports for latest time in the database.

Mar 11 10:00:17 weather weewx[1148]: reportengine: Running report 'SeasonsReport'

Mar 11 10:00:17 weather weewx[1148]: reportengine: Found configuration file /home/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'

Mar 11 10:00:17 weather weewx[1148]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']

Mar 11 10:00:17 weather weewx[1148]: manager: Daily summary version is 2.0

Mar 11 10:00:17 weather weewx[1148]: vantage: Gentle wake up of console successful

Mar 11 10:00:18 weather weewx[1148]: cheetahgenerator: Generated 8 files for report SeasonsReport in 0.64 seconds

Mar 11 10:00:18 weather weewx[1148]: manager: Daily summary version is 2.0

Mar 11 10:00:18 weather weewx[1148]: imagegenerator: Generated 42 images for SeasonsReport in 0.60 seconds

Mar 11 10:00:18 weather weewx[1148]: copygenerator: copied 5 files to /home/weewx/public_html

Mar 11 10:00:18 weather weewx[1148]: reportengine: Report 'SmartphoneReport' not enabled. Skipping.

Mar 11 10:00:18 weather weewx[1148]: reportengine: Report 'MobileReport' not enabled. Skipping.

Mar 11 10:00:18 weather weewx[1148]: reportengine: Report 'StandardReport' not enabled. Skipping.

Mar 11 10:00:18 weather weewx[1148]: reportengine: Report 'FTP' not enabled. Skipping.

Mar 11 10:00:18 weather weewx[1148]: reportengine: Report 'RSYNC' not enabled. Skipping.

[mwall]

thank you john and steve - i updated the webserver instructions to include the conf-enabled/conf-available pattern:

https://github.com/weewx/weewx/wiki/webserver

[vince]

I just got done working this with a non-Linux new weewx user remotely via a zillion emails.  Painful for both sides.

FWIW, I don't want to remember apache vs. nginx syntax, config files, or the like.  I just want my blasted web pages :-)

So personally I always follow Strategy-3 in the wiki.  One symlink so weewx writes where the webserver expects things.  Done and done.   It would work with any webserver I'd expect.

That said, depending on which way you do the symlink (/var/www/html pointing to /home/weewx/public_html, or the other way), this can cause breakage if you have selinux in enabled mode because selinux still is a PITA this many years in.  It has its expectations.  Being creative is out of compliance for selinux unless you restorecon its brain.  Sigh.

[Parsoli 69]

Well, I wiped the historical data from the DVP2.  Fired everything back up.  Appears it's only reaching out to grab data at the top of every hour.  Website pulled the current temp and posted it and logged correct time of day as 4:00pm.  Any thoughts on why this is only polling every hour?

Mar 11 16:00:16 weather weewx[1109]: vantage: Getting archive packets since 2020-03-11 13:00:00 CDT (1583949600)

Mar 11 16:00:16 weather weewx[1109]: vantage: Gentle wake up of console successful

Mar 11 16:00:17 weather weewx[1109]: vantage: Retrieving 1 page(s); starting index= 0

Mar 11 16:00:18 weather weewx[1109]: manager: Added record 2020-03-11 16:00:00 CDT (1583960400) to database 'weewx.sdb'

Mar 11 16:00:18 weather weewx[1109]: manager: Added record 2020-03-11 16:00:00 CDT (1583960400) to daily summary in 'weewx.sdb'

Mar 11 16:00:18 weather weewx[1109]: vantage: Empty record page 0; index 1

Mar 11 16:00:18 weather weewx[1109]: vantage: Requesting 200 LOOP packets.

Mar 11 16:00:18 weather weewx[1109]: reportengine: Running reports for latest time in the database.

Mar 11 16:00:18 weather weewx[1109]: reportengine: Running report 'SeasonsReport'

Mar 11 16:00:18 weather weewx[1109]: reportengine: Found configuration file /home/weewx/skins/Seasons/skin.conf for report 'SeasonsReport'

Mar 11 16:00:18 weather weewx[1109]: cheetahgenerator: using search list ['weewx.cheetahgenerator.Almanac', 'weewx.cheetahgenerator.Station', 'weewx.cheetahgenerator.Current', 'weewx.cheetahgenerator.Stats', 'weewx.cheetahgenerator.UnitInfo', 'weewx.cheetahgenerator.Extras']

Mar 11 16:00:18 weather weewx[1109]: manager: Daily summary version is 2.0

Mar 11 16:00:18 weather weewx[1109]: vantage: Gentle wake up of console successful

Mar 11 16:00:18 weather weewx[1109]: cheetahgenerator: Generated 8 files for report SeasonsReport in 0.65 seconds

Mar 11 16:00:19 weather weewx[1109]: manager: Daily summary version is 2.0

Mar 11 16:00:19 weather weewx[1109]: imagegenerator: Generated 42 images for SeasonsReport in 0.58 seconds

Mar 11 16:00:19 weather weewx[1109]: copygenerator: copied 5 files to /home/weewx/public_html

Mar 11 16:00:19 weather weewx[1109]: reportengine: Report 'SmartphoneReport' not enabled. Skipping.

Mar 11 16:00:19 weather weewx[1109]: reportengine: Report 'MobileReport' not enabled. Skipping.

Mar 11 16:00:19 weather weewx[1109]: reportengine: Report 'StandardReport' not enabled. Skipping.

Mar 11 16:00:19 weather weewx[1109]: reportengine: Report 'FTP' not enabled. Skipping.

Mar 11 16:00:19 weather weewx[1109]: reportengine: Report 'RSYNC' not enabled. Skipping.

[gjr80]

The first thing I would look at is your archive interval setting, what archive interval are you using? Archive interval is set using the archive_interval setting under [StdArchive] in weewx.conf. With Davis stations the archive interval is also stored in the console memory, if these two values differ the console value is used (note that the console defaults to a 30 minute archive interval so if you have never changed the console value chances are it is still set at 30 minutes). This is logged during WeeWX startup so you can confirm what is being used by referring to the log. What does the startup log say?

If the setting being used is not what you want you need to set the correct value in the console either manually via the console buttons or programmatically via the wee_device utility (http://weewx.com/docs/utilities.htm#wee_device_utility).

Gary

[Parsoli 69]

Got it, thank you.  Did set for 30 and it did update at 4:30p.  Which is good.  But suppose I'm back to a potential issue with meteobridge and brokering the connection to the Davis.

Mar 11 16:39:59 weather wee_device[2230]: vantage: ip-read error: [Errno 104] Connection reset by peer

Mar 11 16:39:59 weather wee_device[2230]: vantage: ip-write error: [Errno 32] Broken pipe

Mar 11 16:39:59 weather wee_device[2230]: message repeated 3 times: [ vantage: ip-write error: [Errno 32] Broken pipe]

Mar 11 16:39:59 weather wee_device[2230]: vantage: Unable to wake up console

[gjr80]

I have no experience with the ip logger, so others might be best placed to help there. What might help is to get a clear picture of your current config; there have been various posts re changing record generation, archive interval etc. could I suggest you provide a startup debug log so we are all on the same sheet of music. To obtain a startup debug log edit weewx.conf, set debug = 1, save weewx.conf then restart WeeWX. Let WeeWX run for at least three archive intervals (if you are still running 30 minutes archive interval in the console that’s 90 minutes) then take a copy of and post the log from when you restarted WeeWX through until the three archive intervals have elapsed. Make sure you capture the entire startup sequence and don’t add/delete/change anything.

Gary