Hello richardthis has nothing todo with any drivers, but only the syntax of your OS when using this command:

ifconfig eth0 | grep 'inet '

On all Linux versions I had so far it is displaying this as a result line for exmaple on a Suse enterprise system:inet addr:192.168.123.123 Bcast:192.168.123.255 Mask:255.255.255.0Of this way on my german Debian Jessie:inet Adresse:192.168.193.6 Bcast:192.168.193.255 Maske:255.255.255.0My query in the script is now trying to seperate the IP Address and the Netmask from this line ifconfig eth0 | grep 'inet ' | cut -d: -f2 | awk '{ print $1}'by searching for the line which contain the word "inet " deleting the first part of characters in front of the : and removing everything after the result.

As you can see, on all my systemems I am using independent which language the ifconfig result replies always with inet addr:192.168.123.123 Bcast:192.168.123.255 Mask:255.255.255.0but your OS is replying with out a : in the resultinet 192.168.1.4 netmask 255.255.255.0 broadcast 192.168.1.255with the result that my "cut" command is not working anymore

This is why always INET is being displayed.

Question, if you type this command, what are you getting as a result ?

What is this doing. It is CD into the /tmp folder, downloading a bash scriptrenaming this bash scriptMake the bash Scirpt executablestarting the bash script.

It is very simple, it is trying to retrieve some network parameters from your Linux system.Please have a look into it before you start it: cat network_check.shDon't trust any bash script you are downloading from the internet !

Please paste the result.....maybe this is working for all languages and for all linux systems

I have two weather stations. Second here at home with Davis Vantage Pro2 hardware and another at our summer home with Fine offset hardware. Both stations work with Raspberry 3 model B and are powered with CumulusMX. They also work with that start / stop script. Everything works well. Thanks to the script author and thanks to Steve for this CumulusMX.

I'm curious about the assertion that CumulusMX cannot be "deamonized" ( or "daemonized" if you will). What is getting in the way?

I finally ported from Windows box running 3038 to a Pi 3 running 3043 today and it was surprisingly painless. It appears all my data came across intact, and I haven't yet come across anything that needs to be reconfigured. (I essentially ran a "diff" to find all the files the previous installation added or changed relative to the 3038 package, and overlayed those file on the 3043 install. I was a little nervous from some of what I had read...)

I looked at the interactive script (1100+ lines) and it's quite rich and the output is slick for a shell script. I had in mind to start with something considerably simpler; something that might be accessible through the service or systemctl commands. Somewhere in this thread someone mentioned different runlevels, and I'd be just as happy to run headless without the desktop started by default. (Maybe that's a separate thread I've not found yet.)

radilly wrote:I looked at the interactive script (1100+ lines) and it's quite rich and the output is slick for a shell script. I had in mind to start with something considerably simpler; something that might be accessible through the service or systemctl commands. Somewhere in this thread someone mentioned different runlevels, and I'd be just as happy to run headless without the desktop started by default. (Maybe that's a separate thread I've not found yet.)

Hello BobYes this script grew over the past month day by day and there are a lot of functions build in. (use the ./cumulusmx.sh -h to see whats possible)Regarding your "headless" question.

there are several possibillities to run this script headless.Normally headless means, no keyboard and no mouse. You don't need to run your raspberry into the graphical mode, it's just fine when you start it directly into a ssh session. once the raspi is up, make a ssh connecitons using putty from one of your windows boxes and start cumulusmx.Login as root and start the script by command line.

If you want to start the script (and cumulus) automatically when your raspberry reboots (Like startup folder or autoexec.bat on your windows computer) , there are 2 options.

Thanks for the feedback. Seems like the direction of Debian (and thus Raspbian) is systemd (https://wiki.debian.org/systemd). Its been (quite) a few years since I wrote code to launch daemons, but it was init.d-based as I recall. I believe that is the now dated System V approach, which uses runlevel which seems simpler (or maybe more familiar) than the systemd startup approach.

Oh, boy... As I typed "systemd" I just realized I never searched the forum for that word. I found viewtopic.php?f=27&t=16087 (which you commented on Jan). I've read enough about systemd now, that the thread looks somewhat familiar in what it describes.

As an aside, I have the habit of running code I want to disconnect the terminal from under nohup (https://en.wikipedia.org/wiki/Nohup) - which is ancient (like me ). It also redirects the output to nohup.out which can be helpful in debugging. I'm using that for a python script which monitors my web cam (and power cycles it when needed) at the moment. Because CumulusMX.exe generates so little output, I thought it would be a good fit for nohup.... pretty ideal actually, because the config is handled through a browser.

Not that Cumulus hadn't been very reliable, but SysV had a respawn option intended to cover the case where the daemon crashed. In the aforementioned post, I spotted "Restart=always" which appears to be the equivalent. I'll post here ... and maybe there if I learn anything interesting.

It might be interesting to see if your script could be modified to interact with Cumulus running as a service under systemd. Without having spent much time looking at it, I would guess it is doable.

I am running Cumulus MX on Raspberry Pi Raspbian Jessie. On my first go at this, I downloaded and installed this cumulusmx.sh script, but then once I learnt about systemd I realised that (as far as I can see) this script is not needed at all as the daemon is easily handled natively by systemd. There is also no need to install the "screen" utility.

All I did to get Cumulus MX to run as a service on Raspbian Jessie was the following:

Step 1 - Create a file "/lib/systemd/system/CumulusMX.service" with the following contents:

And that's it! Cumulus MX will now be running as a service on your Raspberry Pi . If it ever fails, systemd will automatically attempt to restart it due to the "Restart=on-failure" line in the above file. To check on the service, you can issue the following command:

weathersoft wrote:I am running Cumulus MX on Raspberry Pi Raspbian Jessie. On my first go at this, I downloaded and installed this cumulusmx.sh script, but then once I learnt about systemd I realised that (as far as I can see) this script is not needed at all as the daemon is easily handled natively by systemd. There is also no need to install the "screen" utility.

All I did to get Cumulus MX to run as a service on Raspbian Jessie was the following:

[CUT]

thanks for your instructions, work perfectly under jessie (and i agree with you, with systemd there is no reason to use cumulusmx.sh anymore - however thanks to the author!).

Hi Folks,I don't seem to be able to get this systemd service to run CumulusMX as it denies access to the root files (serial.txt realtime.txt etc).Do I need to change permissions or should this service run as a sudo?Cheers Steve S