UM3 http interface service crashed?

[peteruithoven 4]

I noticed that my Ultimaker 3's camera stopped being available a couple of times.

Looking into it it seems like it's the http interface (http server?) that stopped?

Some observations:

- I can still ssh into the ultimaker

- "systemctl status griffin.camera.service" indicated that the camera service was active (running) and showed no warnings or errors.

- "systemctl status griffin.interface.http.service" indicated it failed.

Full output:

 

# systemctl status griffin.interface.http.service -l● griffin.interface.http.service - Griffin HTTP service  Loaded: loaded (/etc/systemd/system/griffin.interface.http.service; enabled)  Active: failed (Result: exit-code) since Thu 2017-02-09 22:11:17 CET; 50s ago Process: 2261 ExecStart=/usr/bin/python3.4 /usr/share/griffin/main.py griffin.interface.http.um3server UM3Server (code=exited, status=1/FAILURE)Main PID: 2261 (code=exited, status=1/FAILURE)Feb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,573 INFO     server          adding rule: /api/v1/system/hardware/typeidFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,576 INFO     server          adding rule: /api/v1/system/hardware/revisionFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,579 INFO     server          adding rule: /api/v1/camera/feedFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,581 INFO     server          adding rule: /api/v1/print_job/nameFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,584 INFO     server          adding rule: /api/v1/print_job/time_elapsedFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,586 INFO     server          adding rule: /api/v1/print_job/time_totalFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,589 INFO     server          adding rule: /api/v1/print_job/progressFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,593 INFO     server          adding rule: /api/v1/print_job/stateFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,596 INFO     server          adding rule: /StableWSDiscoveryEndpoint/schemas-xmlsoap-org_ws_2005_04_discoveryFeb 09 22:11:17 ultimakersystem-ccbdd3000627 python3.4[2261]: 2017-02-09 22:11:16,600 INFO     server          adding rule: /WSPrintEndpointFeb 09 22:11:17 ultimakersystem-ccbdd3000627 systemd[1]: griffin.interface.http.service: main process exited, code=exited, status=1/FAILUREFeb 09 22:11:17 ultimakersystem-ccbdd3000627 systemd[1]: Unit griffin.interface.http.service entered failed state.

 

I restarted the interface.http service (systemctl restart griffin.interface.http.service), after which it's status shortly indicated that it active, but when checking it again a few seconds later it failed again.

 

# systemctl status griffin.interface.http.service   ● griffin.interface.http.service - Griffin HTTP service  Loaded: loaded (/etc/systemd/system/griffin.interface.http.service; enabled)  Active: failed (Result: exit-code) since Thu 2017-02-09 22:21:17 CET; 2min 53s ago Process: 2894 ExecStart=/usr/bin/python3.4 /usr/share/griffin/main.py griffin.interface.http.um3server UM3Server (code=exited, status=1/FAILURE)Main PID: 2894 (code=exited, status=1/FAILURE)Feb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,350 INFO     server          adding rule: /api/v1/camera/feedFeb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,352 INFO     server          adding rule: /api/v1/print_job/nameFeb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,355 INFO     server          adding rule: /api/v1/print_job/time_elapsedFeb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,358 INFO     server          adding rule: /api/v1/print_job/time_totalFeb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,361 INFO     server          adding rule: /api/v1/print_job/progressFeb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,365 INFO     server          adding rule: /api/v1/print_job/stateFeb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,368 INFO     server          adding rule: /StableWSDiscoveryEndpoint/schemas-xmlsoap-org_ws_2005_04_discoveryFeb 09 22:21:16 ultimakersystem-ccbdd3000627 python3.4[2894]: 2017-02-09 22:21:16,372 INFO     server          adding rule: /WSPrintEndpointFeb 09 22:21:17 ultimakersystem-ccbdd3000627 systemd[1]: griffin.interface.http.service: main process exited, code=exited, status=1/FAILUREFeb 09 22:21:17 ultimakersystem-ccbdd3000627 systemd[1]: Unit griffin.interface.http.service entered failed state.

 

I need to do a reboot the internal computer (sudo reboot) or the whole printer for it to start working again.

Let me know if I can share more information.

Edited February 9, 2017 by Guest

[Daid 306]

The actual camera feed is provided by mjpg-streamer, which crashes occasionally.

We've updated the service script to restart this service better. Not a perfect solution, but it would put an end to the camera stopping to work.

 

root@ultimakersystem-ccbdd3000d97:~# cat /etc/systemd/system/mjpg-streamer.service[unit]Description=mjpg-streamer, Webcam streaming for all[install]WantedBy=multi-user.target[service]Type=simpleUser=ultimakerEnvironment=LD_LIBRARY_PATH=/usr/lib/mjpg-streamerExecStart=/usr/bin/mjpg-streamer -i "input_uvc.so -r SVGA -d /dev/video0" -o "output_http.so"Restart=alwaysRestartSec=3TimeoutSec=1

 

[peteruithoven 4]

Thanks! I'll apply those tweaks. They make it wait a few seconds before restarting it and waits a second before checking it started successfully?

Got that from: https://www.freedesktop.org/software/systemd/man/systemd.service.html

That service isn't prefixed with griffin because it's an existing service?

[peteruithoven 4]

Won't changes like this disappear on an updates? Is it likely that this tweak is included in the next firmware update?

[Daid 306]

The fix is already included for the next update. We've improved on it even more :-)

[peteruithoven 4]

Thanks!