First time installing Ignition on linux / raspberry pi using download " [Ignition Edge - Linux AARCH64.zip"
Followed all instructions until starting ignition: “WARNING: Ignition-Gateway may have failed to start”
Wrapper log, inter alia, states “License error.: A valid license was not found in the Wrapper configuration file. The Java Service Wrapper requires a License Key to activate the software. …”
Do I need to install Java? I understood that was no longer required.
More than likely, you’re running the 32-bit version of Raspberry Pi OS (64-bit is still in “beta” so you have to dig a little to find it on their website). In that case, you’d need our 32-bit ARMHF install.
If you can post the output of uname -a from your terminal along with the info @Kevin.Herron mentioned, it would be useful for helping troubleshoot.
Or, since you’re on an 8GB Rasp Pi 4 (NICE ), unless you’ve got a lot of other things setup on there already, you might try installing the 64-bit beta that @dkhayes117 mentioned above…
Hmm, I just downloaded the client launcher for Linux on 64bit RPi, and executing the clientlauncher.sh file yields
clientlauncher.sh: 4: clientlauncher.sh: Bad substitution
clientlauncher.sh: 7: clientlauncher.sh: [[: not found
clientlauncher.sh: 13: clientlauncher.sh: [[: not found
OOPS
My first post stated the incorrect Ignition download
I actually downloaded “Ignition-linux-armhf-8.1.3.zip”.
I only want Gateway on the Pi. The designer will be elsewhere.
I prefer to stick with 32bit as there will be other stuff on it and I don’t want beta 64
So the original problem remains:
“WARNING: Ignition-Gateway may have failed to start”!
… and error log appears to blame Java
One thing I have noticed is that on a fresh unzip, if you first attempt to run the gateway in the console with ./ignition.sh console, it does not decompress the JRE and you’ll end up with some errors related to java. You can force the JRE unpack with ./ignition.sh checkRuntimes. If you’re installing as a service with systemd (to run on startup), then it takes care of this automatically.
Here is a little run-through of an install on a Pi 4 (Raspberry Pi OS, 32-bit) that hopefully can provide you some helpful insights. This includes making the gateway run as the pi user instead of root.