I have a completely generic install. Using Raspberry Pi 3, etcher works flawlessly, devices log in but can’t get any video output. Tried with USB and RPi camera… tried various images… all same result… Rebooting, restarting… below is log…
Tried searching the archives and could not find anything related (sorry if I missed it)
Any direction GREATLY appreciated…
18.04.21 18:55:08 (-0400) Rebooting
18.04.21 18:55:48 (-0400) Supervisor starting
18.04.21 18:55:36 (-0400) main Config files are available.
18.04.21 18:55:36 (-0400) main Config files are available.
18.04.21 18:55:40 (-0400) main 2021-04-18 22:55:40,972 CRIT Set uid to user 0
18.04.21 18:55:41 (-0400) main Unlinking stale socket /var/run/supervisor.sock
18.04.21 18:55:41 (-0400) main 2021-04-18 22:55:41,404 INFO RPC interface ‘supervisor’ initialized
18.04.21 18:55:41 (-0400) main 2021-04-18 22:55:41,405 CRIT Server ‘unix_http_server’ running without any HTTP authentication checking
18.04.21 18:55:41 (-0400) main 2021-04-18 22:55:41,407 INFO supervisord started with pid 29
18.04.21 18:55:42 (-0400) main 2021-04-18 22:55:42,412 INFO spawned: ‘nginx’ with pid 32
18.04.21 18:55:42 (-0400) main 2021-04-18 22:55:42,419 INFO spawned: ‘machinery’ with pid 33
18.04.21 18:55:43 (-0400) main 2021-04-18 22:55:43,419 INFO success: nginx entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
18.04.21 18:55:43 (-0400) main 2021-04-18 22:55:43,420 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
18.04.21 18:55:43 (-0400) main 2021-04-18 22:55:43,533 INFO exited: machinery (terminated by SIGSEGV (core dumped); not expected)
18.04.21 18:55:44 (-0400) main 2021-04-18 22:55:44,542 INFO spawned: ‘machinery’ with pid 43
18.04.21 18:55:45 (-0400) main 2021-04-18 22:55:45,733 INFO success: machinery entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)
18.04.21 18:55:45 (-0400) main 2021-04-18 22:55:45,734 INFO exited: machinery (terminated by SIGSEGV (core dumped); not expected)
18.04.21 18:55:46 (-0400) main 2021-04-18 22:55:46,739 INFO spawned: ‘machinery’ with pid 49
18.04.21 18:55:46 (-0400) main 2021-04-18 22:55:46,904 INFO exited: machinery (terminated by SIGSEGV (core dumped); not expected)
18.04.21 18:55:47 (-0400) main 2021-04-18 22:55:47,911 INFO spawned: ‘machinery’ with pid 55
18.04.21 18:55:48 (-0400) main 2021-04-18 22:55:48,063 INFO exited: machinery (terminated by SIGSEGV (core dumped); not expected)
18.04.21 18:58:03 (-0400) main 2021-04-18 22:58:03,646 INFO exited: machinery (terminated by SIGSEGV (core dumped); not expected)
18.04.21 18:58:06 (-0400) main 2021-04-18 22:58:06,659 INFO spawned: ‘machinery’ with pid 67
18.04.21 18:58:06 (-0400) main 2021-04-18 22:58:06,794 INFO exited: machinery (terminated by SIGSEGV (core dumped); not expected)
18.04.21 18:58:07 (-0400) main 2021-04-18 22:58:07,797 INFO gave up: machinery entered FATAL state, too many start retries too quickly
Hi Joe, I just tested a Kerberos node last week and it was fine, so let’s see whats going on here. First, how did you deploy it, was it through balenaHub?
Next, is there any chance you can try another SD Card? I’m just curious if the SD Card is starting to fail.
Also, does the application itself start up? Can you browse to your local IP address, login, and click on “Settings”?
Finally, the RPi camera certainly should have worked, but what type of USB camera are you using?
Thank you VERY much for the reply. I must be missing some very basic step. Everything is new and generic / out of the box. The Raspberry 3 boxes and SD Cards are all new (I have several of each). Same results with a RaPi 4 or 3. .
.
To your questions…
How did you deploy….
I used the BalenaCloud application / dashboard.
I’m downloaded the Balena Etcher app (on macOS), imaging the SD card… The RaPi boots up and I can “see” it attach and initialize to the cloud app. Everything seems to go swimmingly… no errors or hitches…
Try another SD Card?
I tried several (about 4), different brands and sizes (16-64)
Does the application start up?
Yes.
I can attach to the RaPi Box / camera using BOTH the cloud system path OR the local IP address (http://192.168.1.72) and log into the Kerberos screen.
When I go to the systems tab on the web page it shows:
Web 2.8.0 Running
Machinery 2.8.0 Not Running
Everything on the Summary page over in the cloud app looks great… all info is there - Except for the log entry that states
“…machinery (terminated by SIGSEGV (core dumped); not expected”
What type of camera?
I tried 2, a RaPi camera AND a HP USB camera.
Same results with a RaPi cam or a usb cam.
I know the camera works because I can insert a the Debian RaPi OS SD Card in the same hardware and run raspistill -o /home/pi/Desktop/mpicture.jpg
I get a picture every time.
Everything is GENERIC and out of the box… I’ve deleted all my cameras and tried to do new deployments the same way but all seem to work perfectly except for the Machinery service not running…,
OK, this is interesting … I let the camera run for about a day… I just now went to the cloud dashboard screen and manually restarted the main service using the web app. The camera came RIGHT up… no other configuration changes were made. Before doing this I manually rebooted the cameras several times… Problem solved? Maybe?
Making progress… looks like the problem is with the camera. When I did the system refresh I happened to have the USB camera attached… When I switched back to the RaPi camera the machinery service failed. Switch back to usb, all is well…
So now the problem is why is there an issue with the camera? I again switched back to the stock Debian/Linux chip and tried the RaPi camera… it shows video and takes pictures. Swap the Balena chip, boots up but can’t get the machine service to run, switch back to the usb camera… it works…
The camera chip is stamped “Raspberry Pi Camera” AND “Rev 1.3”
Any issues with this camera? Below is a link to where I purchased them on Amazon…
Also, just to add… I repurposed another RaPi camera a had on a straight Debian system (that was working) and plugged it into the Balena box… same problem… machinery service fails… Is there a list of approved cameras?
Hi Joe, glad to hear you are making progress. I’d have to defer those camera questions to the Kerberos team, as they built the App…we just containerize and deploy to the Pi in our repo. I don’t see anything specific in their Documentation about the camera requirements, but it might be worth double checking in case I missed it: https://doc.kerberos.io/opensource/get-started#settings