[weewx-user] Re: rsync does not work after upgrade to v5
remember the permissions of files on the remote machine! Mario Wesolek schrieb am Freitag, 1. März 2024 um 10:59:16 UTC+1: > problem here: since weewx 5 the deamon runs no more as root. The new user > "weewx" hat his homedir under "/var/lib/weewx/" so i create the ssh config > there. this is a workaround, but it works... > teq...@gmail.com schrieb am Freitag, 1. März 2024 um 10:36:32 UTC+1: > >> Hello, >> first I messed up with the normal upgrade from 4 to 5 via apt upgrade. >> After that I created a complete new installation but keep my weewx.conf >> file. >> >> So, weewx 5 works now and generated all information. Unfortunately the >> rsync "skin" does not do anything. If I execute the rsync command manually >> it works fine. >> >> After that I enabled the debug mode and saw that the command seems to be >> executed, but without any output. >> >> 2024-03-01T10:30:35.062186+01:00 weewx weewxd[392]: DEBUG >> weewx.reportengine: Running report 'RSYNC' >> 2024-03-01T10:30:35.062694+01:00 weewx weewxd[392]: DEBUG >> weewx.reportengine: Found configuration file >> /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC' >> 2024-03-01T10:30:35.065311+01:00 weewx weewxd[392]: DEBUG >> weewx.reportengine: Running generators for report 'RSYNC' in directory >> '/etc/weewx/skins/Rsync' >> 2024-03-01T10:30:35.065483+01:00 weewx weewxd[392]: DEBUG >> weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', '--stats', >> '-e', 'ssh', '/var/www/html/weewx/', >> 'us...@vps01.example.com:/home/user/webseiten/website/html']] >> >> Because of the working weewx.conf in version 4 I don't see any issues. I >> read many comments about host key verification, but I don't have this issue >> here. So maybe someone could help. >> >> Thanks. >> > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/200d498b-373a-43ab-898f-7a031286b317n%40googlegroups.com.
[weewx-user] Re: rsync does not work after upgrade to v5
problem here: since weewx 5 the deamon runs no more as root. The new user "weewx" hat his homedir under "/var/lib/weewx/" so i create the ssh config there. this is a workaround, but it works... teq...@gmail.com schrieb am Freitag, 1. März 2024 um 10:36:32 UTC+1: > Hello, > first I messed up with the normal upgrade from 4 to 5 via apt upgrade. > After that I created a complete new installation but keep my weewx.conf > file. > > So, weewx 5 works now and generated all information. Unfortunately the > rsync "skin" does not do anything. If I execute the rsync command manually > it works fine. > > After that I enabled the debug mode and saw that the command seems to be > executed, but without any output. > > 2024-03-01T10:30:35.062186+01:00 weewx weewxd[392]: DEBUG > weewx.reportengine: Running report 'RSYNC' > 2024-03-01T10:30:35.062694+01:00 weewx weewxd[392]: DEBUG > weewx.reportengine: Found configuration file > /etc/weewx/skins/Rsync/skin.conf for report 'RSYNC' > 2024-03-01T10:30:35.065311+01:00 weewx weewxd[392]: DEBUG > weewx.reportengine: Running generators for report 'RSYNC' in directory > '/etc/weewx/skins/Rsync' > 2024-03-01T10:30:35.065483+01:00 weewx weewxd[392]: DEBUG > weeutil.rsyncupload: rsyncupload: cmd: [['rsync', '--archive', '--stats', > '-e', 'ssh', '/var/www/html/weewx/', > 'us...@vps01.example.com:/home/user/webseiten/website/html']] > > Because of the working weewx.conf in version 4 I don't see any issues. I > read many comments about host key verification, but I don't have this issue > here. So maybe someone could help. > > Thanks. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/2602729b-e3a1-40ed-8506-ce298d3b276en%40googlegroups.com.
[weewx-user] Re: Since I upgrade to the 5.0.1 version : NO_PUBKEY E788768B9CB16E10
https://weewx.com/docs/4.10/debian.htm Reimport the Key Valerian Mezieres schrieb am Montag, 19. Februar 2024 um 11:07:34 UTC+1: > Hello > I Have been using Weewx on a raspberry pi 3 model B rev 1.2 for several > years, and it works well for me. > But since I upgraded to version 5.0.1, I got an error message when I try > to update the raspberry. > "sudo apt update" returns Err :3 http://weewx.com/apt/python3 buster > InRelease > .../... : NO_PUBKEY E788768B9CB16E10 > My Pi works under Raspbian Bullseye but in weewx.list there is > "deb [arch=all] http://weewx.com/apt/python3 buster main" > Does somebody know how to fix this ? > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/1df17751-a35f-4ca4-8105-33a357eb365cn%40googlegroups.com.
[weewx-user] Re: Repository Error
https://weewx.com/docs/4.10/debian.htm Reimport the Key Dave McCreath schrieb am Donnerstag, 15. Februar 2024 um 22:16:53 UTC+1: > Hi > > Weewx installed on a RPI 4 (Debian - Bullseye), version 5.0.1, working > fine, no issues. > > Just tried to update to version 5.0.2 via sudo apt update && sudo apt > full-upgrade and received the following error: > > $ sudo apt update && sudo apt full-upgrade > Hit:1 http://security.debian.org/debian-security bullseye-security > InRelease > Hit:2 http://deb.debian.org/debian bullseye InRelease > Hit:3 http://deb.debian.org/debian bullseye-updates InRelease > Hit:4 http://archive.raspberrypi.org/debian bullseye InRelease > Hit:5 http://repository.picockpit.com/raspbian bullseye InRelease > Get:6 http://weewx.com/apt/python3 buster InRelease [4,252 B] > > Err:6 http://weewx.com/apt/python3 buster InRelease > The following signatures couldn't be verified because the public key is > not available: NO_PUBKEY E788768B9CB16E10 > Fetched 4,252 B in 2s (1,789 B/s) > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > All packages are up to date. > W: An error occurred during the signature verification. The repository is > not updated and the previous index files will be used. GPG error: > http://weewx.com/apt/python3 buster InRelease: The following signatures > couldn't be verified because the public key is not available: NO_PUBKEY > E788768B9CB16E10 > W: Failed to fetch http://weewx.com/apt/python3/dists/buster/InRelease > The following signatures couldn't be verified because the public key is > not available: NO_PUBKEY E788768B9CB16E10 > W: Some index files failed to download. They have been ignored, or old > ones used instead. > Reading package lists... Done > Building dependency tree... Done > Reading state information... Done > Calculating upgrade... Done > 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > > I've read through the WeeWX 5 help guide and, even though I'm on Bullseye, > it does state that the repository should point to Buster (which it does). > > Any help for noob much appreciated. > > Many thanks. > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/24e02d50-594c-4956--763834f2e2c4n%40googlegroups.com.
[weewx-user] purge / clean mysql database?
hi there, i use weewx 5.0.2 with belchertown skin 1.3.1 with mysql database. over the time there are tousends of entrys in the database. is there a good / easy way to purge them without lost of alltime records statistik? i think the min/max values came from table archives, so i can select them and delete the other - so i think this is not a good way to do that like this. does anybody knows a better way or is a tool for that job include? thank you mario dg1fi -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/757cf9a9-13df-40a6-8169-dd987317c3b7n%40googlegroups.com.
[weewx-user] Re: MQTT publish time after upgrade to weewx 5.0.1
After update to 5.0.1-4 the MQTT publish data every 2-5 seconds ... have anyone an explanation or can tell me where i can setup the publish time? Feb 9 12:04:08 weewx chronyd[522]: Selected source 217.197.91.176 (de.pool.ntp.org) Feb 9 12:04:09 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:10 CET (1707476650) Feb 9 12:04:12 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:12 CET (1707476652) Feb 9 12:04:14 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:15 CET (1707476655) Feb 9 12:04:17 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:17 CET (1707476657) Feb 9 12:04:19 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:20 CET (1707476660) Feb 9 12:04:22 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:22 CET (1707476662) Feb 9 12:04:24 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:25 CET (1707476665) Feb 9 12:04:27 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:27 CET (1707476667) Feb 9 12:04:29 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:30 CET (1707476670) Feb 9 12:04:32 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:32 CET (1707476672) Feb 9 12:04:34 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:35 CET (1707476675) Feb 9 12:04:37 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:37 CET (1707476677) Feb 9 12:04:39 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:40 CET (1707476680) Feb 9 12:04:42 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:42 CET (1707476682) Feb 9 12:04:44 weewx weewxd[716]: INFO weewx.restx: MQTT: Published record 2024-02-09 12:04:45 CET (1707476685) thank you very much! mario dg1fi Mario Wesolek schrieb am Dienstag, 6. Februar 2024 um 10:42:58 UTC+1: > hi there! > > i use weewx with belchertown skin and publish the data via mqtt. in > versions < 5.0.1 mqtt publish the data to every full minute, like 10:01:00, > 10:02:00 and so on... after upgrade the time is uneven, like: > > Feb 6 09:56:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published > record 2024-02-06 09:56:50 CET (1707209810) > Feb 6 09:57:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published > record 2024-02-06 09:57:50 CET (1707209870) > Feb 6 09:58:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published > record 2024-02-06 09:58:51 CET (1707209931) > Feb 6 09:59:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published > record 2024-02-06 09:59:51 CET (1707209991) > Feb 6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published > record 2024-02-06 10:00:00 CET (170721) > Feb 6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published > record 2024-02-06 10:00:52 CET (1707210052) > > this is not really a problem but i will understand the reason. have > anybody a explanation? > > thank you very much! > mario > -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/e5072808-4bf1-44dc-b0d6-c24c32986a5fn%40googlegroups.com.
Re: [weewx-user] Re: rsync: host key verification failed - problem
some problem.. weewx homedir is /var/lib/weewx ... copy the hostkey and
config file to /var/lib/weewx/.ssh and chown it to weewx:weewx
Kalju schrieb am Donnerstag, 8. Februar 2024 um 11:22:46 UTC+1:
> Hi Dominic!
>
> Thanks for the tip. Indeed, the user was changed from *root* to *weewx*
> That solved the issue
> Thanks!
>
> On Thursday, February 8, 2024 at 11:49:48 AM UTC+2 Dominic Reich wrote:
>
>> Kalju wrote:
>>
>> >Hi all,
>> >
>> >Facing same issue with ERROR weeutil.rsyncupload: Host key
>> verification
>> >failed error.
>> >However, it's really strange...
>> >I can ssh to remote site as both root as well as pi user
>> >I can do manual rsync with no problems but weewx builtin rsync returns
>> above
>> >error
>> >At the moment my weewx installation is syncing using cron with no
>> problems but
>> >I want to understand why builtin rsync fails
>> >Problem started after upgrade from weewx 5.0.0 to 5.0.1
>> >
>> >Any ideas?
>>
>> Adding the debug info should output the actual rsync command initiated by
>> weewx to the logs. That's what I assume when looking at line 104 in
>> `src/weeutil/rsyncupload.py` from the sources of 5.0.1.
>>
>> Maybe that gives a clue in which the actual rsync commands differ and
>> why it might fail within Weewx.
>>
>> Somewhere around 5.0.1 or 5.1.x the user got switched to weewx (not root
>> anymore) so maybe there is a problem? (I can't remember when the switch
>> was (it was mentioned on the list somwhere) and haven't found it in the
>> docs yet)
>>
>> I'd always suggest looking as what weewx is running so you may not have
>> to play the guessing game on which user to look at.
>>
>> sudo ps ux | grep weewxd
>>
>> should return the user that actually runs the (python) daemon like on my
>> old Raspberry this runs still as root with 4.10.2.
>>
>> root 690 2.8 1.5 647360 60428 ? Sl Feb06 75:38 python3
>> /usr/share/weewx/weewxd --daemon --pidfile=/var/run/weewx.pid
>> /etc/weewx/weewx.conf
>>
>> As it was a package-installation I never messed with it, though I
>> welcome the change to a non-root package installation per default :)
>>
>> In case host keys have changed on the server a deletion of the
>> known_hosts
>> file within ~/.ssh could also help, probably.
>>
>> -dominic
>>
>> >Thank you forward :-)
>> >On Friday, July 21, 2023 at 1:14:24 PM UTC+3 Tomasz Lewicki wrote:
>> >
>> > Thank you for replies.
>> >
>> > @Warren Gill: yes, I was thinking about crontab but wanted to use
>> built-in
>> > solution. Of course crontab is good as backup solution.
>> >
>> > @vince: you're right, I didn't think about it from this side. Just for
>> > record for future seekers:
>> >
>> > 1. I logged as root ('sudo -i' from 'pi' account)
>> > 2. generated SSH keys ('ssh-keygen')
>> > 3. copied them to external server ('ssh-copy-id
>> ace...@external.domain.com
>> > -p 222')
>> > 4. copied /home/pi/.ssh/config to /root/.ssh/config
>> > 5. changed owner of 'config' ('chown root:root /root/.ssh/config')
>> > 6. waited for next synchronization
>> > 7. smiled because everything worked as expected :)
>> >
>>
>> --
>> Educating the mind without educating the heart is no education at all.
>> - Aristotle
>>
>
--
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.
To view this discussion on the web visit
https://groups.google.com/d/msgid/weewx-user/619884db-8d65-4b83-a462-f46a923f7776n%40googlegroups.com.
[weewx-user] MQTT publish time after upgrade to weewx 5.0.1
hi there! i use weewx with belchertown skin and publish the data via mqtt. in versions < 5.0.1 mqtt publish the data to every full minute, like 10:01:00, 10:02:00 and so on... after upgrade the time is uneven, like: Feb 6 09:56:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published record 2024-02-06 09:56:50 CET (1707209810) Feb 6 09:57:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published record 2024-02-06 09:57:50 CET (1707209870) Feb 6 09:58:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published record 2024-02-06 09:58:51 CET (1707209931) Feb 6 09:59:50 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published record 2024-02-06 09:59:51 CET (1707209991) Feb 6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published record 2024-02-06 10:00:00 CET (170721) Feb 6 10:00:51 weewx weewxd[4654]: INFO weewx.restx: MQTT: Published record 2024-02-06 10:00:52 CET (1707210052) this is not really a problem but i will understand the reason. have anybody a explanation? thank you very much! mario -- 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. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-user/84563b0d-0e91-4e65-91e6-65691d6685c6n%40googlegroups.com.
