janvda
December 22, 2018, 9:57am
107
krital:
I have rebooted the fin and the problem is occurring again, currently stuck in the restart loop. I have granted support access to the device so perhaps this would be easier because my code never gets a chance to run all I see is:
12.12.18 15:49:01 (+0200) Killing service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:06 (+0200) Service exited ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:08 (+0200) Killed service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:08 (+0200) Installing service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:39 (+0200) Installed service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:39 (+0200) Starting service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:41 (+0200) Started service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:42 (+0200) Killing service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:46 (+0200) Service exited ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:49 (+0200) Killed service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
12.12.18 15:49:49 (+0200) Installing service ‘signalk sha256:2b440092bb4e77941ffa4f47231aaedf0c6863d91160624e93a768d5fa77162a’
Can you access it?
I have recently encountered a similar pattern of installing starting installing stopping
with a certain container: see Container in endless installing - starting - installing - stopping loop since upgrade from Resin Os 2.15.1+rev2 to balenaOS 2.27.0+rev1
Maybe your problem has the same root cause as mine. I have just reported my problem, so also now solution is yet known for that problem.
krital
December 22, 2018, 6:32pm
110
Hello, before I had the time to create a simpler project I tried a similar one that I found here: https://github.com/cape-io/signalk-server-balena
I pushed it on my fin and got the same problem. This time though the problem occurs in influxdb container instead of the signalk container, and the only pattern I see is that in both cases the problem occurs on the last container to be defined in the compose file.
Hi there,
We would need the device dashboard url for a device inspection.
What version of BalenaOS are you using?
krital
December 24, 2018, 2:58pm
118
Hello, do you mean this ?
https://dashboard.balena-cloud.com/devices/858fb1da2f687dfb15142b6841479a9d/summary
The device runs fincm3-2.26.0+rev1-dev-v8.0.0
I have enabled the public URL but as the container for port 80 is in the bounce loop it doesn’t work. I have granted support access for a week also.
Let me know if something else is required.
Thanks,
Alex
@krital Thanks, we’re having a look at it.
It looks like the container keeps restarting because of config changes and in the application you listed above, the server closes the process when there’s an error, so it might be for example a missing dependency in the Fin image (which would also explain the fact that it works on a Rpi3).
We’ll keep you posted
@krital Meanwhile, could you please verify that you’re not running into this issue?
krital
December 25, 2018, 10:12am
133
Hi @thundron ,
many thanks for this. I don’t have time to look in detail but ordering ports as ascending seems to stop the loop and my container starts! Will examine in more detail in the next few days…
Alex
2 Likes