Hey,
From: Milosz Wasilewski milosz.wasilewski@foundries.io
On Tue, May 31, 2022 at 9:04 PM Westermann, Oliver Oliver.Westermann@cognex.com wrote:
Hey,
I've a device stuck in 'Running' state, but missing the usual appending of '#<123> <Job Name> [submitter]'.
Does somebody have some tips how to set/force the device state to 'Idle' manually?
I put my bet on lava-dispatcher crashing somewhere along the way. Please try to restart lava-dispatcher and all services around it (webserver, ser2net, etc.).
Did so before my mail request. We're running the docker-compose setup and I've already update (to 2022.05) and restarted (and rebuild) the containers with no success.
Once you've done this, you can mark the device "idle" in the admin interface. This should help.
Can you give me some guidance here? The admin interface (as well as the lava-server cli) allow me to set the health (good, bad, maintenance, retired), but not the state.
Unrelated sidenote: Rebuilding the docker containers failed me. The dispatcher requires a file from schneider electric [1], which is currently not available for me. I found the file on Remis Github [2] and fixed my Dockerfile locally, but I will try to create a Issue in the gitlab.
Best regards, Olli
[1] https://git.lavasoftware.org/lava/pkg/docker-compose/-/blob/master/dispatche... [2] https://github.com/ci-box/ci-box-lava-worker/blob/master/powernet428.mib