NCPA 3 -- has_error is not handled well
Opened this issue · 0 comments
ne-bbahn commented
When there is an error at startup time for NCPA 3 (i.e. the has_error variable is true), we don't get any logging for what's going wrong and it's just a huge disaster.
This can be shown by going into systemctl edit --full ncpa.service and modifying -n to --start (which is not intended and will break things), and then restarting NCPA several times.