Hi, new user desperately trying not to ask dumb questions but struggling to get CumulusMX running on a RPi3. Many apologies if I missed something trawling this helpful forum for the answer.
I flashed the pre-built image to an SD card. The instructions say wait 5 minutes, but I waited 30 without the Pi becoming visible on my network (i wonder if this is a clue to my issue?). I restarted and it popped up almost immediately. I can ssh in just fine but the service isn't running with the error I see a few people have experienced:
sudo systemctl status cumulusmx
● cumulusmx.service - CumulusMX service
Loaded: loaded (/etc/systemd/system/cumulusmx.service; enabled; vendor preset
Active: failed (Result: exit-code) since Mon 2020-12-07 12:28:29 GMT; 4 month
Docs: https://cumuluswiki.org/a/Main_Page
Main PID: 348 (code=exited, status=1/FAILURE)
Dec 07 12:28:27 cumulusmx systemd[1]: Starting CumulusMX service...
Dec 07 12:28:27 cumulusmx systemd[1]: Started CumulusMX service.
Dec 07 12:28:29 cumulusmx systemd[1]: cumulusmx.service: Main process exited, co
Dec 07 12:28:29 cumulusmx rm[440]: /bin/rm: cannot remove '/tmp/CumulusMX.exe.lo
Dec 07 12:28:29 cumulusmx systemd[1]: cumulusmx.service: Control process exited,
Dec 07 12:28:29 cumulusmx systemd[1]: cumulusmx.service: Failed with result 'exi
pi@cumulusmx:~ $ mono -V
Mono JIT compiler version 6.12.0.90 (tarball Fri Sep 4 14:21:54 UTC 2020)
Copyright (C) 2002-2014 Novell, Inc, Xamarin Inc and Contributors. www.mono-project.com
TLS: __thread
SIGSEGV: normal
Notifications: epoll
Architecture: armel,vfp+hard
Disabled: none
Misc: softdebug
Interpreter: yes
LLVM: yes(610)
Suspend: preemptive
GC: sgen (concurrent by default)
....I also checked that mono is installed.
So I ran "sudo apt update" and "sudo apt upgrade" and noticed some issues during the latter part. These messages appeared throughout:
dpkg: warning: old mono-devel package pre-removal script subprocess returned error exit status 2
dpkg: trying script from the new package instead ...
dpkg: ... it looks like that went OK
Unpacking mono-devel (6.12.0.122-0xamarin1+raspbian10b1) over (6.12.0.90-0xamarin1+raspbian10b1) ...
dpkg: error processing archive /tmp/apt-dpkg-install-XkpNYq/02-mono-devel_6.12.0.122-0xamarin1+raspbian10b1_all.deb (--unpack):
trying to overwrite '/etc/mono', which is also in package libmono-security4.0-cil 6.12.0.90-0xamarin1+raspbian10b1
dpkg-deb: error: paste subprocess was killed by signal (Broken pipe)
dpkg (subprocess): unable to execute installed mono-devel package post-installation script (/var/lib/dpkg/info/mono-devel.postinst): Permission denied
...then at the end a long list of the packages with which issues were encountered (just the first few shown).
Errors were encountered while processing:
/tmp/apt-dpkg-install-XkpNYq/02-mono-devel_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/04-libmono-accessibility4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/05-libmono-cairo4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/06-libmono-security4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/07-libmono-system-numerics4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/08-libmono-system-xml4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/09-libmono-system-security4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/10-libmono-system-configuration4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/11-mono-mcs_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/12-mono-utils_6.12.0.122-0xamarin1+raspbian10b1_armhf.deb
/tmp/apt-dpkg-install-XkpNYq/13-mono-roslyn_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/14-libmono-corlib4.5-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/15-libmono-tasklets4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
/tmp/apt-dpkg-install-XkpNYq/16-libmono-system4.0-cil_6.12.0.122-0xamarin1+raspbian10b1_all.deb
I have tried twice to reflash the card, with identical results.
Can anyone point me in the right direction?
Welcome to the Cumulus Support forum.
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Latest Cumulus MX V3 release 3.28.6 (build 3283) - 21 March 2024
Cumulus MX V4 beta test release 4.0.0 (build 4019) - 03 April 2024
Legacy Cumulus 1 release 1.9.4 (build 1099) - 28 November 2014
(a patch is available for 1.9.4 build 1099 that extends the date range of drop-down menus to 2030)
Download the Software (Cumulus MX / Cumulus 1 and other related items) from the Wiki
Pi - Getting started issue
Moderator: mcrossley
-
- Posts: 19
- Joined: Mon 19 Apr 2021 6:32 am
- Weather Station: Davis Vantage Pro2 Plus
- Operating System: RPi3 Buster
- mcrossley
- Posts: 12770
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Pi - Getting started issue
I'll try to flash an SD card from the latest image and see if I get the same issues - it may be the image has been corrupted somehow...
This may take me a day... Meanwhile you could try the previous image? - https://cumuluswiki.org/Downloads/rpi-CMX-3.10.4.zip
This may take me a day... Meanwhile you could try the previous image? - https://cumuluswiki.org/Downloads/rpi-CMX-3.10.4.zip
-
- Posts: 19
- Joined: Mon 19 Apr 2021 6:32 am
- Weather Station: Davis Vantage Pro2 Plus
- Operating System: RPi3 Buster
Re: Pi - Getting started issue
Thanks for getting back to me. I went back to basics, installed Rasbian and then Mono and CumulusMX on top of that and it's all working fine. Apart, that is, from me being able to get it to run as a service, but I consider it a challenge so won't be asking for help, yet at least!
Marc
Marc
- mcrossley
- Posts: 12770
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Pi - Getting started issue
I installed the image from the Wiki today, ran apt update/upgrade - there were lots! - and they all installed OK
I will use that as the new base image, so at least the next release will not need them all.
I will use that as the new base image, so at least the next release will not need them all.
-
- Posts: 19
- Joined: Mon 19 Apr 2021 6:32 am
- Weather Station: Davis Vantage Pro2 Plus
- Operating System: RPi3 Buster
Re: Pi - Getting started issue
Thank you for checking on this. I am now up and running with the system running as a service on a Pi3.....all good.
I am struggling a little with weatherlink.com not updating when Cumulus is running. I have the station refresh and cumulus refresh set to the same thing, 5 mins, and the "DavisIPResponseTime=500" set up in the ini file per the cumulus.ini Wiki page. Is there another idiot's guide somewhere I can refer to rather than bother everyone here with already answered questions?
Marc
I am struggling a little with weatherlink.com not updating when Cumulus is running. I have the station refresh and cumulus refresh set to the same thing, 5 mins, and the "DavisIPResponseTime=500" set up in the ini file per the cumulus.ini Wiki page. Is there another idiot's guide somewhere I can refer to rather than bother everyone here with already answered questions?
Marc
- mcrossley
- Posts: 12770
- Joined: Thu 07 Jan 2010 9:44 pm
- Weather Station: Davis VP2/WLL
- Operating System: Bullseye Lite rPi
- Location: Wilmslow, Cheshire, UK
- Contact:
Re: Pi - Getting started issue
So you are using a Davis IP logger?
Have you set the disconnect period setting to something other than zero in Station settings?
That disconnect period is what allows the logger a brief period of time to perform the wl.com upload.
Have you set the disconnect period setting to something other than zero in Station settings?
That disconnect period is what allows the logger a brief period of time to perform the wl.com upload.