peteoheat
commented
1 year ago So I've tried again with this. I created a new fleet, and added a new device to it by flashing an SD card. Then from the CLI I recloned the github repository and did a balena push to my new fleet and everything installed ok.
I previous had not set TZ in the device variables, this this time I set LAT, LON, ALT and TZ and rebooted. I got to the stage where I have services in the following states:
Running services: dump1090-fa (seeing gain messages etc in the logs) dump978-fa (Even though it says it's disabled in the logs) frontend-proxy kiosk (but no screen is attached) wifi connect.
Everything else is 'Installed'
I added the device variable FLIGHTAWARE_FEEDER_IF using my ID for my established feeder (which is now switched off). I see a log message saying 'starting service piaware...' but then nothing further in the logs.
drhanke
ketilmo
The most common when services keep looping and not start is when the device variables for LAT, LON, ALT, TZ and all services specifics are not in valid format or not present.
Have you done all steps as per the documentation on each service? Or as you already have been a sharer you probably already have keys for each service. You just need to add them, you can simply copy them out of you old installation.
Please don´t try to fix everything at once, start to check if your device variables are present. Start with LAT, LON, ALT and TZ. Then make sure dump1090-fa starts.
For each service you need the following device variables for it to start up: dump1090-fa LAT, LON, ALT, TZ
The following services requires LAT, LON, ALT, TZ (global values can be reused no need to add per service) and their own keys as specified: adsb-exchange, ADSB_EXCHANGE_SITENAME and ADSB_EXCHANGE_UUID fre24feed, FR24KEY planefinder, PLANEFINDER_SHARECODE opensky, OPENSKY_USERNAME flightaware, FLIGHTAWARE_FEEDER_ID radarbox, RADARBOX_KEY