PS will not start on Unraid.
P-C-R opened this issue · comments
Here is the Log
2022-02-03 11:46:51,897 INFO supervisord started with pid 1 2022-02-03 11:46:52,899 INFO spawned: 'x11' with pid 16 2022-02-03 11:46:52,900 INFO spawned: 'easy-novnc' with pid 17 2022-02-03 11:46:52,901 INFO spawned: 'prusaslicer' with pid 18 2022-02-03 11:46:52,902 INFO spawned: 'openbox' with pid 19 2022-02-03 11:46:53,043 INFO exited: prusaslicer (terminated by SIGFPE; not expected) 2022-02-03 11:46:54,169 INFO success: x11 entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-02-03 11:46:54,170 INFO success: easy-novnc entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-02-03 11:46:54,170 INFO spawned: 'prusaslicer' with pid 41 2022-02-03 11:46:54,171 INFO success: openbox entered RUNNING state, process has stayed up for > than 1 seconds (startsecs) 2022-02-03 11:46:54,203 INFO exited: prusaslicer (terminated by SIGFPE; not expected) 2022-02-03 11:46:56,206 INFO spawned: 'prusaslicer' with pid 46 2022-02-03 11:46:56,238 INFO exited: prusaslicer (terminated by SIGSEGV; not expected) 2022-02-03 11:46:59,241 INFO spawned: 'prusaslicer' with pid 51 2022-02-03 11:46:59,274 INFO exited: prusaslicer (terminated by SIGFPE; not expected) 2022-02-03 11:47:00,275 INFO gave up: prusaslicer entered FATAL state, too many start retries too quickly
Thanks for the report, @P-C-R .
Can you confirm if you're using the latest build that was pushed to Docker and GitHub last night? The issue presented here (SIGFPE -> SIGSEGV) was resolved on https://forums.unraid.net/topic/119329-support-prusaslicer-novnc/ per another users confirmation.
The solution was to create a /configs/.config/ directory if it doesn't already exist otherwise the symbolic link failed (to hold the Prusaslicer configs between image changes).
The Docker container does this now in the latest push FWIW, but you could also launch the terminal from OpenBox and create that directory, restart, and it would in theory start working.
Let me know if you're on the latest version and still experiencing issues.
Additionally, there was another push this evening that might have resolved this due to stable/beta dependencies: https://forums.unraid.net/topic/119329-support-prusaslicer-novnc/?do=findComment&comment=1093533
Let me know if you're still experiencing issues with the latest image.
For me worked creating the directory. But I always was at the latest.
For me worked creating the directory. But I always was at the latest.
Thanks for the update. Just to confirm the directory you had to create was /configs/.config/ or something more specific? I'm curious if for some reason that directory isn't being generated properly in the Dockerfile.
just .config
There have been some additional changes to the mechanism for creating these files and folders, so hopefully this is a bit more resilient. Additionally, longer term I might consider moving to binding /home/$USER/ instead of /configs/ FWIW similar to my Cura container approach.