| EventCode | Context | EventMessage | Description / Solution |
|---|
| everywhere | Several | Code used for multi purposes: Mostly for debug messages below level warn, where no fixed message is needed. |
| everywhere | Several | Default code used for old error messages, which are not converted yet to the new error code system. |
| everywhere | Log HTTP Request | The HTTP request to the server and its parameters are logged. Generally for debugging only. |
| entities | Duplicate Key | A database key for the entity to be saved does already exist. |
| entities | Integrity Constraint Violation | An entity can not be added or updated since a referenced entity does not exist (anymore). Or an entity can not be updated or deleted since it is referenced by other entities. |
| everywhere | HTTP Status 404 | The requested URL / page was not found, the API endpoint in the application does not exist. |
| everywhere | HTTP Status 422 | The PUT / POST request to that URL could not be processed due invalid given data.
The invalid fields are listed in the result from the server. |
| everywhere | HTTP Status 422 | The File Upload did not succeed PUT / POST request to that URL could not be processed due invalid given data. The invalid fields are listed in the result from the server. |
| everywhere | HTTP Status 409 | The PUT / POST request to that URL could not be processed due the given data would produce an invalid state of the entity on the server. If possible, the causing fields are listed in the result from the server, or the error message is self explaining. |
| everywhere | PHP Fatal Error | PHP Fatal error, see error message for details. |
| everywhere | PHP Warning | PHP Warning, see error message for details. |
| everywhere | PHP Info | PHP Info, see error message for details. |
| Worker | Can not trigger worker URL: {host}:{port} Error: {errorName} ({errorNumber}) | The triggered worker URL is technically not available. Local firewall problems? Is the configured "runtimeOptions.server.name" available and callable from the translate5 instance? If not, it can help to configure "runtimeOptions.worker.server" with the local host name or the localhost IP, basicly the server adress which points to the local server and is available for the translate5 instance. |
| Worker | Worker URL result is no HTTP answer!: {host}:{port} | This can only happen if the worker URL is not pointing to an translate5 instance, or if there is an error on the translate5 instance. In the latter case investigate the log for further errors. |
| Worker | Worker HTTP response state was not 2XX but {state}. | This should happen only if there is an error on the translate5 instance. In the latter case investigate the log for further errors. |
| Worker | Worker HTTP response state was 404, the worker system requests probably the wrong server! | Check the server URL configuration values. Either runtimeOptions.worker.server or runtimeOptions.server.protocol and runtimeOptions.server.name are pointing to a wrong server / translate5 installation! |
| DB | Still producing a DB DeadLock after {retries} retries. | A transaction was repeated X times after a deadlock and it is still producing a deadlock.
The original dead lock exception is contained in this exception. |
| DB | A transaction could be completed after {retries} retries after a DB deadlock. | This is just a info / debug message to track if a deadlock occured, an that it could be successfully executed after X retries. |