Bug
Exceptional job execution not finished
Issue description
When a job does not terminate successfully, but results in an exception, the job page does show the start of the execution, but not the end, like the job is still running. Normally an exception would still write the end of the job into the MySQL database and it will show up with status ERROR.
Developer comments
This is caused by unusing the store which switches the log from the store log to the Topincs log, but the respective directory is not in the open_basedir.
Access to the general conf dir is avoided and thus it works.
|
Work sessions
Start |
2022-12-14T09:00:00
|
End |
2022-12-14T12:37:11
|
Participant |
Robert Cerny
|
|
We are sorry
This page cannot be displayed in your browser. Use Firefox, Opera, Safari, or Chrome instead.