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 | HTTP client logging - SEND | The raw connection content of a internal used HTTP client is logged for debugging purposes. |
| everywhere | HTTP client logging - RECEIVE | The raw connection content of a internal used HTTP client is logged for debugging purposes. |
| everywhere | Several | Default code used for old error messages, which are not converted yet to the new error code system. |
| everywhere | No access to requested URL | The currently authenticated user is not allowed to access the requested resource. Since this is normally a misconfiguration of ACL rules or programming error in the GUI (missing isAllowed check) this error is locked as error. |
| 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 | HTTP Status 502 Bad Gateway | A requested service is not available, or answers with an error. |
| 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! This can also happen, if the server name is resolving to multiple IPs on the server it self (multiple entries in the /etc/hosts for example). |
| Worker | Worker "{worker}" failed on initialisation. | Check other errors , this message is just for debugging. |
| 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. |
| DB | A transaction was rejected after a DB deadlock. | This is just a info / debug message to track if a deadlock occured, an that it was intentionally rejected. |
| API Filter | Errors in parsing filters Filterstring: "{filter}" | The given JSON filter string can not parsed. Is the given JSON valid? |
| API Filter | Illegal type "{type}" in filter | The given filter type does not exist. |
| API Filter | Illegal chars in field name "{field}" | There were invalid characters in the field name. Only Alphanumeric characters and dash "-" and underscore "_" are allowed. |
| API Filter | Illegal field "{field}" requested | The requested field does not exist. |
| API Filter | Unkown filter operator "{operator}" from ExtJS 5 Grid Filter! | The given filter operator is invalid. |
| API Filter Join | Given tableClass "{tableClass}" is not a subclass of Zend_Db_Table_Abstract! | The given tableClass in the join filter must be a sub class of Zend_Db_Table_Abstract |
| Installation & Update | The following file does not exist or is not readable and is therefore ignored: {path} | Check the existence and access rights of the mentioned file. |
| Installation & Update | Errors on calling database update - see details for more information. | This are the errors happend on calling the alter SQLs. |
| Installation & Update | Result of imported DbUpdater PHP File {path}: {result} | The output of a PHP update file is logged as info. |
| Http Client | Request time out in {method}ing URL {url} | The requested service did not respond in a reasonable time. |
| Http Client | Requested URL is DOWN: {url} | The requested service is either not available or not reachable. |
| Http Client | Empty response in {method}ing URL {url} | The requested service returns an empty response, this may indicate a problem (crash) on the service side. |