Cmon is now working OK with Weewx V5.0.0.a25 on Debian 10 Buster. Below are the steps to got it working.
*Upgrading to weewx v5.0.0a25 (debian) on Debian 10 (Buster)* Linux pi11 5.4.72+ #1356 Thu Oct 22 13:56:00 BST 2020 armv6l model name: ARMv6-compatible processor rev 7 (v6l) Model: Raspberry Pi Model B Rev 2 apt update apt install python3-pip apt install gcc python3-dev python3-pip pip3 install wheel pip3 install weewx weectl station create --no-prompt *Read weewx-data to windows* *Change the Service part of file weewx_cmon.service* [Service] ExecStart=/usr/bin/python3 /usr/local/lib/python3.7/dist-packages/weewxd.py /root/weewx-data/weewx_cmon.conf *Read back weewx_cmon/conf of version V4.5.1 to weewx-data* *Write the old weewx-data back to linux* *Create daemon voor cmon* cd ~/weewx-data cp util/systemd/weewx_cmon.service /etc/systemd/system chmod -wx /etc/systemd/system/weewx_cmon.service systemctl daemon-reload systemctl enable weewx_cmon *Start cmon* systemctl restart weewx_cmon *The webpage reports the version of weewx and python* station: ComputerMonitor server: 64178 seconds weewx: 281 seconds version: 5.0.0a25 python: 3.7.3 Conclusion: the reported error has to do with the latest version of PI OS (bullseye) which can't be used on RPI 1B (or RPI 2B?) Op zondag 26 maart 2023 om 18:09:10 UTC-3 schreef Vince Skahan: > Which precise model are you having problems with ? > My old one is: > > pi@raspberrypi:~ $ cat /sys/firmware/devicetree/base/model && echo "" > Raspberry Pi Model B Rev 2 > > > I wonder if your new os is what is broken. Do you have an old SD card > with an old image you can try ? > > On Sunday, March 26, 2023 at 10:27:07 AM UTC-7 Lucas Heijst wrote: > >> Thanks Vince. >> >> I got similar problems on my RPI 2b model, (both loaded with the latest >> Raspberry PI OS lite (32-bit), so for now I'm back to the old >> configurations. >> >> On my RPI 3b+ weewx V5.0.0.a25 and cmon both work fine with the latest >> Raspberry PI OS lite (64-bit) or ubuntu 22.10 server (64-bit). >> >> Op zondag 26 maart 2023 om 13:07:11 UTC-3 schreef Vince Skahan: >> >>> On Sunday, March 26, 2023 at 8:34:15 AM UTC-7 Lucas Heijst wrote: >>> >>> On PI 3b+ with weewx V5.0.0a25 cmon runs without errors >>> On PI 1 with weewx V4.5.1 cmon also worked ok. >>> On PI 1 with weewx V5.0.0a25 cmon got the following error: >>> >>> Mar 26 12:17:55 pi11 systemd[1]: weewx_cmon.service: Main process >>> exited, code=killed, status=4/ILL >>> Mar 26 12:17:55 pi11 systemd[1]: weewx_cmon.service: Failed with result >>> 'signal'. >>> Mar 26 12:17:55 pi11 systemd[1]: weewx_cmon.service: Consumed 3.183s CPU >>> time. >>> ====== >>> >>> Any idea what "'code=killed, status=4/ILL" and "Failed with result >>> 'signal'." mean? >>> I have no idea where to search for errors. >>> >>> >>> Some googling for status=4/ILL has a lot of hits for problems trying to >>> run armv7 binaries (pi3) on armv6 boxes (model-B), but that does not >>> explain how it worked before. Did you perhaps copy your cmon stuff from >>> the pi3 onto your old pi ? Maybe delete the .pyc files associated with >>> cmon on the old model pi ? >>> >>> >>> >> -- You received this message because you are subscribed to the Google Groups "weewx-development" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/weewx-development/8fc05bfd-c374-4a8b-8504-71003e3b39b3n%40googlegroups.com.
