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/b05c57dd-8f8f-468a-b391-e8daa1023ee4n%40googlegroups.com.
