4.2 to 4.3 RPi not running anymore - installed on RPi with Deb

[miso k]

Here the errors when debug=1

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Finished loading service weewx.engine.StdConvert

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Loading service weewx.engine.StdCalibrate

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Finished loading service weewx.engine.StdCalibrate

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Loading service weewx.engine.StdQC

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Finished loading service weewx.engine.StdQC

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.engine: Loading service weewx.wxservices.StdWXCalculate

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.manager: Daily summary version is 2.0

Jan  8 13:57:16 WeeWX weewx[5067] INFO weewx.manager: Daily summaries at V2.0. Patching to V3.0

Jan  8 13:57:16 WeeWX weewx[5067] INFO weewx.manager: recalculate_weights: Using database 'weewx.sdb'

Jan  8 13:57:16 WeeWX weewx[5067] DEBUG weewx.manager: recalculate_weights: Tranche size 100

Jan  8 13:57:31 WeeWX weewx[5067] DEBUG user.interceptor: GET: ID=observer&PASSWORD=XXXX&indoortempf=72.3&tempf=32.5&dewptf=29.7&windchillf=32.5&indoorhumidity=55&humidity=89&windspeedmph=0.0&windgustmph=0.0&winddir=73&absbaromin=28.890&baromin=29.944&rainin=0.000&dailyrainin=0.000&weeklyrainin=0.492&monthlyrainin=0.520&solarradiation=81.97&UV=0&dateutc=2021-01-08%2012:57:28&softwaretype=EasyWeatherV1.5.6&action=updateraw&realtime=1&rtfreq=5

Jan  8 13:58:01 WeeWX CRON[5088]: (root) CMD (/usr/bin/wget "http://192.168.1.54/webcapture.jpg?command=snap&channel=1&user=pi&password=XXXX" -O /var/www/html/wordpress/wp-content/uploads/onlinecam.jpg)

Jan  8 13:58:01 WeeWX CRON[5087]: (CRON) info (No MTA installed, discarding output)

Jan  8 13:58:07 WeeWX systemd[1]: Starting Cleanup of Temporary Directories...

Jan  8 13:58:07 WeeWX systemd[1]: systemd-tmpfiles-clean.service: Succeeded.

Jan  8 13:58:07 WeeWX systemd[1]: Started Cleanup of Temporary Directories.

Jan  8 13:58:34 WeeWX weewx[5067] DEBUG user.interceptor: GET: ID=observer&PASSWORD=XXXX&indoortempf=72.1&tempf=32.5&dewptf=29.7&windchillf=32.5&indoorhumidity=55&humidity=89&windspeedmph=0.0&windgustmph=0.0&winddir=73&absbaromin=28.893&baromin=29.947&rainin=0.000&dailyrainin=0.000&weeklyrainin=0.492&monthlyrainin=0.520&solarradiation=86.24&UV=0&dateutc=2021-01-08%2012:58:32&softwaretype=EasyWeatherV1.5.6&action=updateraw&realtime=1&rtfreq=5

During the upgrading using DEB package I chose Y to rewrite my weewx.conf. After I have checked if it was updated, only few lines was mine, the rest was brand new weewx.conf with for example no credentials to weather services.

So I rewrote it with 4.2 conf file, made few changes to it according to http://weewx.com/docs/upgrading.htm#Upgrading_to_V4.3

But it seems that it is still the same... WeeWX is not running correctly.

If I restart it, it is the same. Looks like the Daily summaries are updating again after restart. Not only once, as in the upgrading guide.

Thanks for any help!

[Tom Keffer]

Most likely, the patch is not running to completion. It will let you know when it is done. Don't be deceived by the message from the interceptor driver: it is running in another thread.

I don't know what type of RPi you have, but the patch typically takes a couple minutes. Slowest we have seen is 17 minutes on Vince's 128MB Dockster.

--
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/77c8702a-0606-493e-bd06-937f40b5c566n%40googlegroups.com.

[miso]

Hi Tom,

thanks for the answer. This is probably not my case, as I have a dedicated RPi 3B+ and it was running more than 30 minutes.

Can we check somehow how the Daily summaries v2 -> v3 process is running?

Thanks,

Michal.

miso

pi 8. 1. 2021 o 14:54 Tom Keffer <tke...@gmail.com> napísal(a):

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/uCY_K9_gAqw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEA%3DW8nJijqKpG18gGiwsDvjnV1APbh7f6cNU_0vehwRpg%40mail.gmail.com.

[Tom Keffer]

We can look in the database. I don't know what install method you used, but assuming it was a package install (using apt-get):

sqlite3 /var/lib/weewx/weewx.sdb

sqlite> select * from archive_day__metadata;

sqlite> select * from archive_day_outTemp order by dateTime desc limit 10;

sqlite> .quit

You may have to install sqlite3 first:

sudo apt-get sqlite3

If you used setup.py instead of apt-get, then substitute /home/weewx/archive/weewx.sdb for /var/lib/weewx/weewx.sdb.

This will tell us the version of the daily summary, as well as give us a look at whether the patch process did its work or not.

-tk

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAJ0Y92Dv9YRQx_5vCApegKEczvrwSH5b7xJEwJ9NU4WX2c6uYA%40mail.gmail.com.

[miso k]

thanks,

this is the result:

1610060400|30.7|1610090851|32.4|1610111352|3065.1|99|183906.0|5940

1609974000|32.7|1609981063|34.7|1610016711|21169.4999999999|631|1270170.0|37860

1609887600|32.9|1609930871|36.3|1609940679|43137.6999999998|1235|2588262.0|74100

1609801200|33.3|1609880806|39.6|1609803685|42521.9999999999|1165|2551320.0|69900

1609714800|37.2|1609800933|44.2|1609762485|46542.4000000003|1153|2792544.0|69180

1609628400|39.2|1609658133|45.1|1609670773|48666.9|1148|2920014.0|68880

1609542000|33.6|1609555220|43.2|1609592229|46473.7|1177|2788422.0|70620

1609455600|27.5|1609473475|37.6|1609540660|39747.8999999998|1254|2384874.0|75240

1609369200|30.2|1609454771|39.0|1609420411|42054.6|1202|2523276.0|72120

1609282800|37.4|1609362626|42.1|1609328738|47054.2000000001|1165|2823252.0|69900

Michal

Dátum: piatok 8. januára 2021, čas: 15:13:28 UTC+1, odosielateľ: tke...@gmail.com

[miso k]

Btw, I have installed weewx through DEB package, I updated it through DEB package too.

M

Dátum: piatok 8. januára 2021, čas: 15:36:09 UTC+1, odosielateľ: miso k

[Tom Keffer]

You didn't show the results of the first sqlite command

sqlite> select * from archive_day__metadata;

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2764c9c6-92ee-4d95-8a62-657f9dee2bbdn%40googlegroups.com.

[miso k]

So what? after sudo apt-get upgrade I restarted RPi gain and! Its running :)

You have golden hands, Tom!

sqlite> select * from archive_day__metadata;

Version|3.0

lastUpdate|1610117160

the only thing what is not running now is AQI index. 

https://jastrabie.online/weewx/

$aqi($current($data_binding='aqi_binding').aqi_pm10_0_category).category  

can it be something with the update?

M

Dátum: piatok 8. januára 2021, čas: 15:37:27 UTC+1, odosielateľ: miso k

[miso k]

Solved this issue too:

in skin.conf for Seasons was missing in stanza:

[CheetahGenerator]

search_list_extensions = user.aqi.service.AqiSearchList  

Tom, many thanks for quick support from Slovakia!

Michal

Dátum: piatok 8. januára 2021, čas: 15:50:03 UTC+1, odosielateľ: miso k

[vince]

Tom - for dpkg installations there might be some confusion regarding how to answer the question regarding keeping/not-keeping weewx.conf that was previously in place especially if you've added extensions, and what the user might need to do manually to upgrade a customized system.

I've been running setup.py versions forever (which just magically always upgrade correctly) but I was super confused trying to upgrade one dpkg installation that I have.   Fortunately that one is very simple with just a trivial skin added so taking the defaults worked for me, but I basically hit returned and hoped.

The upgrade guide is certainly accurate in depicting what the person upgrading will see, but perhaps a bit more explanation with a couple examples might help.  Just a thought.

[Tom Keffer]

I've had the same experience. But, as I understand it, the script that runs the "keep your weewx.conf" file is supplied by Debian. It's not something that we can control. Matthew is the expert on this.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2cf307b4-d717-4e9f-bc98-b599f22403d1n%40googlegroups.com.

[vince]

On Friday, January 8, 2021 at 10:48:50 AM UTC-8 Tom Keffer wrote:

I've had the same experience. But, as I understand it, the script that runs the "keep your weewx.conf" file is supplied by Debian. It's not something that we can control. Matthew is the expert on this.

Thanks.  Just to clarify, I'm not asking for any code change, just a bit more explanation in the docs re: what happens if you answer each way.

Maybe somebody other than Matthew could work it if so inclined.

How'bout I add an issue to get it on a to-do list for possibily someday ?  

[miso]

I had this issue already before. As inexperienced user, I reinstalled the whole Raspberry again. What about making a python script to make the dpkg update work?

miso

pi 8. 1. 2021 o 20:41 vince <vince...@gmail.com> napísal(a):

--
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/uCY_K9_gAqw/unsubscribe.
To unsubscribe from this group and all its topics, send an email to weewx-user+...@googlegroups.com.

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/edb7a7ba-2565-417d-9b7a-471c8bbd3b87n%40googlegroups.com.

[Tom Keffer]

Not sure what you mean. Upgrades should be done through apt-get, not dpkg.

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/CAJ0Y92B0%3DLO4bfFnSjyr81yPh3Lyg-HOC2FuZfzgQjH93LVivw%40mail.gmail.com.

[Nate Bargmann]

* On 2021 09 Jan 06:50 -0600, Tom Keffer wrote:
> Not sure what you mean. Upgrades should be done through apt-get, not dpkg.

Actually, since Stretch and especially with Buster (Debian 10), 'apt'
should be used in favor of 'apt-get' which is more low level.

apt can even be used to install a manually downloaded package, e.g.
'apt install ./foo-1.2.3.deb' and it will handle installing the
dependencies assuming they are available in the configured archives.

- Nate

--

"The optimist proclaims that we live in the best of all
possible worlds. The pessimist fears this is true."

Web: https://www.n0nb.us
Projects: https://github.com/N0NB
GPG fingerprint: 82D6 4F6B 0E67 CD41 F689 BBA6 FB2C 5130 D55A 8819

[miso]

Tom, I meant apt-get. My mistake.

miso

so 9. 1. 2021 o 13:49 Tom Keffer <tke...@gmail.com> napísal(a):

To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/CAPq0zEBKb-QjhTOxy8vnE9x3owpudiCK67RzUUKC4%2BRYjpchJg%40mail.gmail.com.

[vince]

On Friday, January 8, 2021 at 10:02:38 PM UTC-8 misk...@gmail.com wrote:

What about making a python script to make the [apt-get] update work?

I'd suggest simply following the Upgrade Guide which says which 'two' commands to issue.

I think we're over-optimizing at this point.

There are lots of ways to get there equally well.

Same thing happens on the RHEL-compatible side with yum vs. rpm commands that install/upgrade packages.

 

[gjr80]

And it’s worth pointing out no matter how you do the install a copy of the old (pre-upgrade) config file is retained (refer to the Upgrade Guide for naming details) so it is a simple matter to compare/update config files if any extras don’t seem to be working post upgrade.

Gary

[didier belin]

Good evening,

since an update of weewx, here is a problem:

n 10 23:04:14 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:14 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:16 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:16 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:19 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:21 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:25 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting poll packet

Jan 10 23:04:25 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:26 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:29 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:29 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:31 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:31 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:34 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:34 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting push (broadcast) packet

Jan 10 23:04:36 weewx3 weewx [12717] INFO user.weatherlink_live: Emitting poll packet

at a (random) moment the poll packet stops and therefore no more data, I have to restart. any idea where the problem may come from? weewx or the WeatherLive Link?

Likewise for the belchertown skin, the almanac has disappeared and the graph representing the solar radiation only represents the measured value and no longer the predicted value (calculated via the pyepehem module) the two elements functioning before the update.