For any reason people reported that they are having problems using this method in Debian 8 (Debian Jessie)I was able to insert such a command in the system crontab successfully, but others reported further problemssudo nano /etc/crontab

This was the reason why I created a small system startup script which can be placed in /etc/init.d to start the CumulusMX Start|Stop Script at system boot without irritate with cron jobs probably not working anymore

Here is the instruction what you need to do.

1. Removing autostarts from cronYou can ignore this step, if you never had a cron based startup entry and proceed with Step 2Please make sure, that all cron's are being checked not to start cumulusmx.sh anymorePlease use these commands and search for lines probably containing the start|stop script at reboot

Copy the Script (using WINSCP) to your /tmp folderOnce the zip file is copied, login as pi or root using SSH (Putty) and insert these commandsunzip /tmp/cumulusmx.zip - will unzip the zip filesudo cp /tmp/cumulusmx /etc/init.d/cumulusmx - will copy the startup script cumulusmx to /etc/init.dsudo chmod +x /etc/init.d/cumulusmx - will make the scirpt executablesudo update-rc.d cumulusmx defaults - will insert the Startup Script into the runlevels(the command to remove it from the runlevels again is: sudo update-rc.d -f cumulusmx remove)

3. Changing some settings in this init scriptsudo nano /etc/init.d/cumulusmx

Please only change one of these lines if necesarry (for most poeple nothing needs to be changed)

CumulusMX_HOME= the folder where the cumulusmx.sh Start|Stop Script is located. Normally it is in the same folder as CumulusMX.exeCumulusMX_USER this is the user, who should start CumulusMX at system boot. It might user pi or rootSave changes by pressing CTRL-o and CTRL-xsudo reboot - to reboot system

After the system has being rebooted check if CumulusMX is being started.sudo grep -i cumulusmx /var/log/syslogyou should see a line like this:Jan 7 13:31:11 raspberrypi systemd[1]: Started LSB: Start cumulusmx.sh (CumulusMX) at boot time

But now you have more optionstype: /etc/init.d/cumulusmxUsage: /etc/init.d/cumulusmx {start|stop|force-reload|status}Possible commands should be

So you are free to start stop CumulusMX by using the start Stop Script itself1) /home/pi/CumulusMX/cumulusmx.sh -{options}or using2) /etc/init.d/cumulusmx {options}

however option 1) has more options than option 2)

for me it works so feel free to play around wit this init script.I know, real linux admins maybe can do this much better then me, but this was my first attempt to write a init.d script.

EDIT: 11.10.2016For all who have trouble strating CumulusMX with the init.d Startup Script at system boot, here is a command to check, if the init.d startup scirpt is correctly inserted into the runlevel of your system.1) install a small program called: chkconfigsudo apt-get install chkconfig2) run the command to check if the startup script should be started at system bootchkconfig |grep cumuas a result you should see:

cumulusmx on

If you did not see this result, you missed to enter the following command to insert the startup script into the runlevels

sudo update-rc.d cumulusmx defaults

You do not have the required permissions to view the files attached to this post.

Last edited by jank on Tue Oct 11, 2016 11:53 am, edited 15 times in total.

The error in the documentation is fixed...this was easy the bigger problem seem to be that it is not workiong for you.

In the screenshot, I can see that you tried it with the CRON method.If you look into your screenshot, 6 January 17:33 cron is reporting (root) CMD (sudo /CumulusMX/cumulusmx.sh >> /dev/null) But this seem not to be your path to the CumulusMX folder, becasue the Enviroment check some line above is saying that CumulusMX is installed in /home/pi/CumulusMX folder

Also the errors at 10 January 00:12:21 when it is being started with the init.d script the error is:systemd[1]: [/lib/systemd/system/cumulus.service:5] Executable path is not absolute, ignoring: sudo ./CumulusMX/cumulusmx.sh

Unfortunately, I have no idea which version of my CumulusMX Start|Stop Script you are using. but I remember, that I had a previous version of my script online, where I had my path hardcoded instead of using variables. this was some month ago and I replaced this script version with a correct one after one day.So I have no Idea, where you get this path from: /CumulusMX/cumulusmx.sh but it looks like this is not your installation path. PLease do the following: can you please doublecheck the init script for the path in the top area of the script ?What is the path for CumulusMX_HOME= ?you can use this commandgrep "CumulusMX_HOME=" /etc/init.d/cumulusmxIn your case it should be CumulusMX_HOME=/home/pi/CumulusMXCan you also tell me which version of the CumulusMX Start|Stop Script you are using ? /home/pi/CumulusMX/cumulusmx.sh -vMaybe you have one of the buggy version where my hardcoded path is in there.also the result output from this command would help me:grep "CumulusMX/cumulusmx.sh" /home/pi/CumulusMX/cumulusmx.sh

I have no idea what you did, or what you did with /etc/rc.local./etc/init.d is a directory where you can put scripts wich are able to start/stop/ Programs or in my case other scripts.It is a kind of autostart with the difference that you can tell the Linux system when these programs should be started or stopped.Normally, you need to put this script into this folder make some basic settings like, folder of the start|stop script and user who should start the Start|Stop Script.Once this is done, you need to tell the system at which runlevel the Start|Stop Script should be started at system boot (sudo update-rc.d cumulusmx defaults)So there is no need to modify /etc/rc.local which has nothing to do with /etc/init.dHowever, when you are okay as it is, fine.....and if this solved the problem with the not working cron starts....greatThanks for using it.JAn

Well, i've tried about every method suggested in the forum to get CumulusMX to start on a reboot, but nothing has worked thus far. I tried the method in this thread and after reboot sudo grep -i cumulusmx /var/log/syslog looks as it should but CumulusMX never seems to start. When I sudo ./CumulusMX.sh manually, then it starts CumulusMX and things run as normal. It is an important thing to be able to automatically start CumulusMX on a reboot as the power goes out here on a regular basis.

any other ideas?

You do not have the required permissions to view the files attached to this post.

If they decided to start CumulusMX with sudo, the owner of many files in this CumulusMX folder is user root.When they now try to start the Script at boot time as user pi, this user might not have enough rights to write into some files, which are being created/modified when called as sudo.Most users are starting the script with sudo with the result, that the owner of all files is root.When they now want to use the init.d script, they also need to start it as root --> CumulusMX_USER=root

Alternatively, they can call the script as ./cumulusmx.sh without sudo and they were told that they have to change permissions first, when calling without sudo.Then, they are able to start the script again without using sudo and using CumulusMX_USER=pi in the init.d script from now on.