CumulusMX - RaspberyPi - Start|Stop|Restart Script V2.5.5.3

[richard_newberry]

i have only took out Raspberry pi bit because mines not a Raspberry Pi

Please see attached the files as requested.

I have deleted the old file and still the same error message.

[jank]

Hello Richard
I downloaded your file and started it on my Raspberry PI and it worked as expected.
Some posts ago, you wrote about this error message:

error is: ./cumulusmx.sh: line 1131: syntax error: unexpected end of file
But in the attached docx file I can see, that the command: ./cumulusmx.sh -s is correctly showing the status information without the above error.
The only error is on top of the status page:

./cumulusmx.sh: line 633: [: 3043: unary operator expected

And this error is "normal" because the variable: $MXVERSIONONLINE is pointing to "http://sandaysoft.com/forum/" and must be changed to
"https://cumulus.hosiene.co.uk/" .......

So I am a little bit confused where, and when you get the error error is: ./cumulusmx.sh: line 1131: syntax error: unexpected end of file ?

Jan

[richard_newberry]

I dont know.

I will alter the script to point to the right url.

Thanks Jank.

[jank]

I dont know.
I will alter the script to point to the right url.
Thanks Jank.

Okay you can find it in line 170
and replace this line with
MXVERSIONONLINE=$(curl -s https://cumulus.hosiene.co.uk/ -o /tmp/version.txt | grep -i "Latest Cumulus MX release" /tmp/version.txt | sed 's/^.*v3.0.0/>v3.0.0/' |cut -c2-18)


So I assume, I can ignore this error (post) from you?

i am getting error on kernel on 4.18

error is: ./cumulusmx.sh: line 1131: syntax error: unexpected end of file

An thing would be appreciated.

[richard_newberry]

Thanks Jank, that's sorted it out.

Sorry to waste your time.

[billy]

Recently I upgraded to V2.5.5.0 and now when I check the status with "sudo ./cumulusmx.sh -s" I get errors that are probably due to the first one reported "nc: port number invalid".

Capture.PNG

If I use "/etc/init.d/cumulusmx" status to check status I get:

Capture2.PNG

None of this seems significant because everything else apparently functions as expected despite what the script reports (or doesn't). The script is started at boot using init.d.

This has been reported previously in this thread but I can't find any solutions - at least that I understand and can work out how to implement. The reason I would like to solve it is the "nc: port number invalid " seems to be causing a cron job, that does a daily backup, to issue an email each time - but the backup works.

So, is there a "simple" solution to its irritating consequence?

[jank]

Hello

if you have a look into your first screenshot, you can see, that there is not an IPv4 IP Address listed, but an IPv6 IP address.

Background:
An IPv4 address with Port 8998 looks like 192.168.3.222:8998
an IPv6 Address looks like: xxxx:xxxx:xxxx:xxxx (Hexdecimal characters)

You can do me a favour....I just looked into the code and I can see, that I determine the IP Address with the command: hostname -I
Can you pleasecheck this command on your PI:
hostname -I

I assume, you are getting the IPv6 IP address instead of an IPv4 IP address ?

If you see an IPv6 Address, you can temporary disable IPv6 with this command

echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6

After the next reboot, IPv6 is still enabled, or insert
echo 0 > /proc/sys/net/ipv6/conf/all/disable_ipv6 to enable it immidiately

I assume, you are still using an IPv4 Network ?
If you think it is safe to turn IPv6 permanently off, follow this:
nano /etc/sysctl.d/01-disable-ipv6.conf to create an empty file and insert this line:

net.ipv6.conf.all.disable_ipv6 = 1
Save.
This will permanently disable IPv6 (If you need IPv6 sometime in the future, remove this file......

Would this be an option for you ?

Jan

[billy]

hostname -I does indeed give the IPv6 IP address

echo 1 > /proc/sys/net/ipv6/conf/all/disable_ipv6 results in:
"-bash: /proc/sys/net/ipv6/conf/all/disable_ipv6: Permission denied"
(prefixing sudo does not change this)

However, I have successfully made /etc/sysctl.d/01-disable-ipv6.conf
And after a reboot sudo ./cumulusmx.sh -s no longer produces the error.

My network seems to have both an IPv4 and an IPv6 address - when checking network settings on a windows 10 pc. But I don't really know what I'm doing in that area so may not be looking at the correct part.

The daily cron job doing the backup happens early tomorrow morning, so I await the outcome.

It's looking promising - thank you!

[billy]

Jan, just confirming that seems to have sorted it out. Thanks for your help.

[richard_newberry]

This is what I receive on my status page but I can't find version V2.5.5.2.

can you point me in the right direction please.

[jank]

This is what I receive on my status page but I can't find version V2.5.5.2.
can you point me in the right direction please.

Hello Richard....I am so sorry, I missed to put the 2.5.5.2 on this website. The change between 2.5.5.0 and 2.5.5.2 is just small. I corrected the URLs in the script from *sandaysoft* to
https://cumulus.hosiene.co.uk .....The most current version is now on the first page of this post, available for download,,,,,
Jan

[HansR]

Hi,

I just updated the start/stop script to 2.5.5.2 version. All is OK, but I took the opportunity to run the -c option and I noticed the FTP check went wrong. As CumulusMX is running fine I checked the script and found a small error: in the lines where you parse the cumulus.ini at the FTP section, the passwordline goes wrong if there is an '=' character in the password (which is legal) and which happens to be the case in my situation.

Code: Select all

 FTPPASS=$(grep -A 5 "FTP site" $INSTPATH/Cumulus.ini | grep Password | cut -d = -f 2)

The problem is the delimiter character in the cut command.
Not a very big problem but thought I ought to inform you.

Best,

[jank]

.....found a small error: in the lines where you parse the cumulus.ini at the FTP section, the passwordline goes wrong if there is an '=' character in the password (which is legal) and which happens to be the case in my situation.

Hello Hans
thank you very much for reporting this error.

A new Script Version is in the first post where this error is being fixed (2.5.5.3)
The change is

Code: Select all

 FTPPASS=$(grep -A 5 "FTP site" $INSTPATH/Cumulus.ini | grep Password | cut -d = -f 2-10)

PLease let me know if this doesn ot work for you......
Jan

[HansR]

Thnx Jan, quick reply, works perfectly
Best,