|
Hi Ivy team Is there a switch or something to keep the container running even if there was a (fatal) exception at boot time of Ivy ? Currently it's slightly painful to debug ... Thanks & Regards John Moser |
|
It's better to not start the engine at all if a problem like this occur, this can lead to very unexpected behaviors. If the engine can not access the And in fact everything is said when you got the message 'Permission denied'. E.g. you can't start an apache http server if it can not access its configuration files. In your case now, please check the file permissions (chown/chmod) of your |
Once you sign in you will be able to subscribe for any updates here
By RSS:Markdown Basics
Tags:
Asked: 15.05.2019 at 11:54
Seen: 1,889 times
Last updated: 17.05.2019 at 02:46
What do you mean with a fatal exception in ivy. A fatal exception is something like OutOfMemory and there is no way out. This is not specific to ivy.
The problem is, you can't connect to the container anymore if something like this ...
Caused by: java.io.FileNotFoundException: /etc/axonivy-engine-7x/ivy.yaml (Permission denied)... happens. It would be nice to keep the container up and running in order to connect and investigate, what went wrong.