IoT2000, IS ONLINE = false

openBalena
1

Hello, I have the following doubt, it turns out that I have configured the image for my IoT2000, which I have seen is in BETA, when I flashed the image and I connect the IoT to the network, it finds the device but I get IS ONLINE = false, I have tried with the image development, production and nothing.

Finally I did a test with a RaspBerry Pi 3, to see if it was that I was doing something wrong and it turns out that I connect the RaspBerry and when I detect the device IS ONLINE = true, does anyone know how I can modify this?

My company wants to work with the IoT2000 and this is being a real wall that I can not overcome, thank you very much for your time

4

Hello, the latest balenaOS release (v2.12) for IoT2000 is too old for openBalena. This sounds like an omission on our part. I’ll see if the balenaOS team plans a new release for that device and post back.

How many devices do you plan to roll out? IoT is properly supported on balenaCloud and it is free to use for up to 10 devices. That might let you get started in the meantime.

9

Hi. The IOT2000 needs some work to get it up to date. Will start work on it this week and keep you updated

13

Hello, thank you very much for the answers, my company wants to connect more than 100 devices that is why it is important to want to do it with IoT Siemens, because they have already made the investment in the devices. His idea is to start with openBalena to do the tests and see how it works and how it adapts and later on and change the paid version.

19

Hi, last version of balenaos (2.31) for iot2000 seems to keep restarting containers (supervisor and app) every 10/15 minutes. Any update on this issue?
Thanks

20

tried again yesterday with the image available on balenacloud (v2.31 supervisor:9.9.0), every now and then balenad crash with this log:

May 04 09:51:20 b80bddc balenad[6005]: panic: sync: negative WaitGroup counter
May 04 09:51:20 b80bddc balenad[6005]: goroutine 62 [running]:
May 04 09:51:20 b80bddc balenad[6005]: sync.(*WaitGroup).Add(0x19dac1e0, 0xffffffff)
May 04 09:51:20 b80bddc balenad[6005]: /usr/lib/go/src/sync/waitgroup.go:75 +0x124
May 04 09:51:20 b80bddc balenad[6005]: sync.(*WaitGroup).Done(0x19dac1e0)
May 04 09:51:20 b80bddc balenad[6005]: /usr/lib/go/src/sync/waitgroup.go:100 +0x29
May 04 09:51:20 b80bddc balenad[6005]: github.com/docker/docker/daemon.(*Daemon).restore.func1(0x19dac1e0, 0x19ee4900, 0x19dac1b8, 0x1a05d340, 0x1a05d320, 0x1a05d300, 0x19caa000)
May 04 09:51:20 b80bddc balenad[6005]: /yocto/resin-board/build/tmp/work/i586-nlp-32-poky-linux/balena/17.12.0-dev+gitfe78e2c9a69313007c53c83fff4b5525fbc2ba45-r0/git/src/import/.gopath/src/github.com/docker/docker/daemon/daemon.go:364 +0x596
May 04 09:51:20 b80bddc balenad[6005]: created by github.com/docker/docker/daemon.(*Daemon).restore
May 04 09:51:20 b80bddc balenad[6005]: /yocto/resin-board/build/tmp/work/i586-nlp-32-poky-linux/balena/17.12.0-dev+gitfe78e2c9a69313007c53c83fff4b5525fbc2ba45-r0/git/src/import/.gopath/src/github.com/docker/docker/daemon/daemon.go:218 +0xbce
May 04 09:51:20 b80bddc systemd[1]: balena.service: Main process exited, code=exited, status=2/INVALIDARGUMENT
May 04 09:51:20 b80bddc systemd[1]: Failed to start Balena Application Container Engine.
May 04 09:51:20 b80bddc systemd[1]: balena.service: Unit entered failed state.
May 04 09:51:20 b80bddc systemd[1]: balena.service: Failed with result ‘exit-code’.
May 04 09:51:20 b80bddc systemd[1]: Starting Resin supervisor…
May 04 09:51:20 b80bddc systemd[1]: balena.service: Service hold-off time over, scheduling restart.

any idea on what could be? Thanks

23

Hi,

Thanks for the update. We’ve involved the relevant engineers; we’ll let you know when we have some more information.

25

Hi again,

Just to clarify, having looked at this a bit more, you appear to be using the latest release from balean-staging.com and not balena-cloud.com. Staging images are not guaranteed to work correctly, as they are still ‘in flux’. Still, the relevant engineers have been contacted who will be looking into this issue.