Descriptions for Log Messages
Marker
Information
- Markers are used in PLANTA Server for log message separation by topics.
- Messages can be "coloured" using markers; e.g. the marker "operative" is attached to log messages that are considered important for operators of PLANTA Server.
- Markers can contain references to other markers; when filtering for a marker (e.g. "operative"), markers with a reference to this marker match additionally.
- PLANTA Server has a static set of markers which is shown in the following.
- Markers that are shown as children of others in fact have references to the "parent" marker.
Static marker set
operativedatabaseschema_mapping
loggingsystem_customizingschema_mapping
module_customizinguser_adminproject_adminproject_data
Java
| Log Message ID | Level | Marker | Description | Cause(s) | TODO |
|---|---|---|---|---|---|
| 0100001 | ERROR | operative | exception came up that was not caught | contact PLANTA | |
| 0100002 | WARN | database | transaction handling failure | bug, database outages | check database connectivity |
| 0100003 | ERROR | operative | unexpected exception | bug, side effect of infrastructure problems | check exception stack trace |
| 0100004 | WARN | database | Database operation failure | (customizing) bug, database outages | check database connectivity, check customizing |
| 0100005 | ERROR | schema_mapping | severe differences betweeen system customizing and server | migration/update failure | check migration status |
| 0100006 | WARN | database | Query handling failure | (customizing) bug | check customizing |
| 0100007 | WARN | schema_mapping | problems while building the data dictionary | customizing bug (e.g. by migration/update failure) | check customizing/migration steps |
| 0100008 | WARN | schema_mapping | non-fatal failure while building the table mapping | customizing bug (e.g. by migration/update failure) | check customizing/migration steps |
| 0100009 | WARN | system_customizing | wrong db dialect was given when trying to start the schema export | customizing bug | provide legal db dialect |
| 0100010 | ERROR | operative | unexpected exception during schema export | contact PLANTA | |
| 0100011 | WARN | schema_mapping | foreign key customizing for the specified table broken | table customizing | check relation customizing |
| 0100012 | ERROR | database | DB connection/hibernate is wrongly cofigured | wrong configuration | check db/hibernate configuration |
| 0100013 | ERROR | schema_mapping | table definitions prevent successful (re)configuration of hibernate | system customizing | check table definitions |
| 0100014 | WARN | schema_mapping | differences between system customizing and server | system customizing | check migration/system customizing |
| 0100015 | WARN | system_customizing | column names are not unique | system customizing | check column name definition |
| 0100016 | WARN | schema_mapping | no primary key is given for thze specified table thus it is not usable in PLANTA | system customizing | add primary key if the table is needed |
| 0100017 | WARN | schema_mapping | unhandled object type | system customizing bug | check DI type definition |
| 0100018 | WARN | schema_mapping | incompatible object type (integer/string) | system customizing | check DI type definition (and value range) |
| 0100019 | ERROR | schema_mapping | fatal problem in generated table mapping | ? | contact PLANTA, provide stack trace |
| 0100020 | INFO | operative | started the servers monitoring interface | ||
| 0100021 | WARN | logging | Bug in native logging implementation | server bug | contact PLANTA |
| 0100022 | ERROR | operative | configuration errors exist, initialization of server will be stopped. | configuration error | check configuration files/additional arguments |
| 0100023 | INFO | operative | logging system was successfully initialized | ||
| 0100024 | WARN | database | Listeners for specific DB events were not successfully registered | DB configuration/server bug | contact PLANTA |
| 0100025 | INFO | database | Starting Initialization of the database/hibernate subsystem | ||
| 0100026 | INFO | operative | Loading native libraries succeeded | ||
| 0100027 | INFO | operative | Starting initialization of the native interface for DB access | ||
| 0100028 | INFO | database | (Re-) Starting initialization of the data dictionary which is needed for running client sessions | ||
| 0100029 | INFO | operative | Will create new session, e.g. for handling a new client connection | ||
| 0100030 | INFO | operative | indicates that the server is running w.r.t. handling (further) client connections | ||
| 0100031 | WARN | operative | the network socket the server needs for handling client connections has closed unexpectedly | network/OS failure | restart service |
| 0100032 | WARN | operative | an unsupported virtual memory limit is configured on the operating system the server runs on | OS restriction | remove the limit, more information |
| 0100033 | ERROR | database | hibernate initialization failed | db connection failure | check db connection |
| 0100034 | WARN | operative | monitoring interface could not be initialized/started | configuration/os | check monitoring configuration |
| 0100035 | INFO | operative | status messages regarding migration package execution | ||
| 0100036 | ERROR | operative | migration failure because of missing start script | installation failure | verify that the python folder is correctly installed |
| 0100037 | INFO | operative | connection to the kerberos service succeeded | ||
| 0100038 | ERROR | operative | connection to the kerberos service failed | kerberos configuration failure | check kerberos configuration (PLANTA Server and kerberos service) |
| 0100039 | INFO | operative | restarting the server; no handling of incoming client connections until restart has finished | ||
| 0100040 | INFO | operative | shutting down the server; running sessions will be stopped (client connections are closed) | ||
| 0100041 | INFO | operative | stopping the server; no handling of incoming connections, while running sessions stay functional | ||
| 0100042 | INFO | operative | indicates a session was started | ||
| 0100043 | ERROR | operative | an unexpected failure occured in a session | server bug | check exception, inform PLANTA |
| 0100044 | INFO | operative | indicates a session was closed regularly | ||
| 0100045 | WARN | operative | session lookup failed: the session could not be found in the session managment dictionary | server bug, lookup with wrong session key | check requested session key |
| 0100046 | WARN | operative | when trying to shutdown the server, not all sessions could be stopped | ||
| 0100047 | INFO | operative | User canceled query | User pressed escape while a huge query was running | |
| 0100048 | WARN | operative | System canceled huge query | A query, returning a very large number of records, which was canceled to reduce memory usage | See the exact message: Either update customizing to return fewer records, or raise the system variable that defines this limit (either G80109 or G80110) |
| 0100060 | INFO | logging | a planta service is starting up | ||
| 0100061 | INFO | logging | a planta service is shutting down | ||
| 0100062 | WARN | logging | non-critical unexpected behaviour in planta service | ||
| 0100063 | ERROR | operative | a planta service could not be started or a critical error occured that brought it down | check exception, inform PLANTA | |
| 0100070 | INFO | logging | a scheduling session is starting | ||
| 0100071 | INFO | logging | a scheduling session is ending | ||
| 0100072 | WARN | logging | non-critical unexpected behaviour in scheduling session | ||
| 0100073 | ERROR | operative | a scheduling session could not be started or a critical error occured that brought it down | check exception, inform PLANTA | |
| 0100074 | INFO | events | an interface function is called between Java and Jython | ||
| 0100075 | WARN | events | an interface function created a warning either in Java or in Jython | check log file, inform PLANTA | |
| 0100076 | ERROR | events | an interface function created a critical error | check exception, inform PLANTA | |
| 0100077 | INFO | operative | information about the license check | ||
| 0100078 | WARN | operative | the license check created a warning | check log file, inform PLANTA | |
| 0100079 | ERROR | operative | the license check created an error occured that brought it down | check exception, inform PLANTA | |
| 0100080 | INFO | operative | information about an thread | ||
| 0100081 | INFO | secure | information about the buildin secure interface | ||
| 0100082 | INFO | operative | information about schema creation | ||
| 0100083 | INFO | database | information about DB export | ||
| 0100084 | INFO | database | information about schema export | ||
| 0100085 | ERROR | secure | an error occured configuring secure | ||
| 0100086 | DEBUG | logging | a debug message |
Native
| Log Message ID | Level | Marker | Description | TODO |
|---|---|---|---|---|
| 0200001 | WARN | system_customizing | unable to load data items | make sure the system is properly set up |
| 0200002 | ERROR | operative | critical error during server startup | contact PLANTA |
| 0200003 | ERROR | operative | critical error during user session led to termination of the server | check EXIT_ON_EXCEPTION parameter in planta_server.conf, contact PLANTA |
| 0200004 | WARN | operative | critical error during user session left the server running | check EXIT_ON_EXCEPTION parameter in planta_server.conf, contact PLANTA |
| 0200005 | ERROR | operative | out of memory | check administrative limits wrt. memory consumption, add more RAM to the (physical or virtual) machine |
| 0200006 | ERROR | operative | the license number specified in planta_server.conf cannot be found in the database | make sure the database is properly set up, check PPMS_LICENSE parameter in planta_server.conf |
| 0200007 | WARN | operative | client connection: keepalive timeout exceeded | check network connectivity of the machine |
| 0200008 | WARN | operative | client connection: socket error | check network connectivity of the machine |
| 0200009 | WARN | operative | hibernate exception occurred due to database error | check exception message, database connectivity |
| 0200010 | INFO | operative | a session thread is exiting | |
| 0200011 | WARN | user_admin | user interface skin not found | check user account configuration |
| 0200012 | INFO | project_data | external link is being ignored since the referred project is not active | if the link is to be considered, the referred project needs to be activated |
| 0200013 | WARN | project_admin | multiple active models found, there should be only one | make sure the desired model is the only one set to 'active' |
| 0200014 | WARN | libz encountered an internal error while (de)compressing a client message | contact PLANTA | |
| 0200015 | WARN | libiconv encountered an internal error while transcoding text | contact PLANTA | |
| 0200016 | ERROR | libiconv encountered an internal error while looking up a required encoding | contact PLANTA | |
| 0200017 | WARN | system_customizing | auto number construction rule and maximum value do not match | fix auto number customizing |
| 0200018 | WARN | system_customizing | data item has illegal data type | fix data item customizing, assing proper data type |
| 0200019 | WARN | system_customizing | data item has illegal numeric type size | fix data item customizing, assing proper data type |
| 0200020 | WARN | system_customizing | data item has no data type set | fix data item customizing, assing proper data type |
| 0200021 | WARN | system_customizing | data table has invalid ACR position | fix data table customizing, check DB pos. of its data items, assign proper ACR position |
| 0200022 | WARN | module_customizing | aggregation type is incompatible with data item's data type | check data field customizing, assign sensible aggregation type or choose proper data item |
| 0200023 | WARN | system_customizing | chosen menu item not implemented | fix menu item customizing |
| 0200024 | INFO | user_admin | no OS user login requested by client | |
| 0200025 | INFO | user_admin | could not find user account with requested OS user set | if OS user logon is desired, check user account configuration |
| 0200026 | WARN | user_admin | found multiple user accounts with requested OS user set, must be unique | check user account configuration |
| 0200027 | WARN | module_customizing | scale-bound data field encountered without a corresponding horizontal scale | check data field customizing |
| 0200028 | INFO | could not find any record referring to hyperlink, resulting in orphaned hyperlink | ||
| 0200029 | WARN | error writing BLOB into database | check database error message, contact PLANTA | |
| 0200030 | WARN | error looking up BLOB by ID | contact PLANTA | |
| 0200031 | WARN | data item number out of bounds, must range from 1..999999 | fix python macro or value range | |
| 0200032 | WARN | data item with specified number does not exist | fix python macro or value range | |
| 0200033 | WARN | data item with specified python id does not exist in specified data table | fix python macro or value range | |
| 0200034 | WARN | data item with specified number belongs to another data table | fix python macro or value range | |
| 0200035 | WARN | error compiling python code | fix python macro or value range | |
| 0200036 | WARN | error running python code | fix python macro or value range | |
| 0200037 | WARN | while reenabling auto-commit behaviour, a missing commit was enforced | ensure all macros performing transactional database modifications do proper transaction handling | |
| 0200038 | WARN | while exiting a python context, the previous auto-commit state was restored | ensure all macros setting auto-commit behaviour restore the previous state prior to returning | |
| 0200039 | WARN | a commit statement was ignored since no transaction was running | check transactional behaviour of database-modifying macros | |
| 0200040 | WARN | a rollback statement was ignored since no transaction was running | check transactional behaviour of database-modifying macros | |
| 0200041 | WARN | unhandled python exception | fix python macro or value range | |
| 0200042 | WARN | error running python file while applying migration packages | contact PLANTA | |
| 0200043 | WARN | system_customizing | checkInput() method of python value range dit not return a boolean value | fix python value range |
| 0200044 | WARN | code assertion failed | contact PLANTA | |
| 0200045 | WARN | system_customizing | data table without a primary key relation | fix data table customizing |
| 0200046 | WARN | user_admin | login failed | |
| 0200047 | WARN | user_admin | mandatory password change failed | |
| 0200048 | ERROR | data dictionary initialization failed | check system customizing, contact PLANTA | |
| 0200049 | WARN | system_customizing | runtime check identified a problem in the area of system customizing | check system customizing, contact PLANTA |
| 0200050 | WARN | customizing | circular references in dynamic variables | check module and/or dynamic variable customizing |
| 0200051 | WARN | conversion to smaller numeric data type, value exceeds the destination's range | contact PLANTA | |
| 0200052 | WARN | system_customizing | error compiling value range | check data item customizing |
| 0200053 | INFO | user_admin | unable to load user roles | check user accounts and roles |
| 0200054 | INFO | user_admin | unable to load work fields | check work fields |
| 0200055 | INFO | user_admin | unable to load menu items | check menu items |
| 0200056 | WARN | module_customizing | panel layout configuration exceeds width of database column | |
| 0200057 | INFO | user_admin | unable to load user account | check user account |
| 0200058 | INFO | module_customizing | redundant aggregation on primary key column ignored | check module customizing, remove aggregation flag from data area |
| 0200059 | INFO | conflicting BLOB insertion | ||
| 0200060 | INFO | conflicting BLOB modification | ||
| 0200061 | INFO | operative | in response to a critical fault, a coredump will be written | check coredump settings in server configuration files, contact PLANTA |
| 0200062 | INFO | operative | coredump written successfully | check coredump settings in server configuration files, contact PLANTA |
| 0200063 | WARN | operative | failed to write coredump | check coredump settings in server configuration files, contact PLANTA |
| 0200064 | WARN | operative | failed to execute migration script | execute migration scripts manually, and contact PLANTA |
| 0200065 | WARN | operative | unable to parse XML message, contents will be ignored | contact PLANTA |
| 0200066 | WARN | operative | Could not cancel huge query because module assigned to query could not be determined | |
| 0200067 | WARN | operative | protocol feature ExecutePythonScript (client_exec()/server_exec()) is disabled | update customizing to use the secure rpc implementation |
| 0200068 | ERROR | operative | signal or SEH exception was caught, logged with stack trace if possible | contact PLANTA |
| 0200069 | WARN | module_customizing | encountered link DF without a matching DA to be linked | add DA or DF to be linked, or remove spurious link DF |
| 0200070 | WARN | system_customizing | reused data prevents destruction of the old session dictionary | close the current session and log in again |
| 0200071 | INFO | operative | Migration: Starting ... | |
| 0200072 | INFO | operative | Migration done | |
| 0200073 | WARN | Stale Protocol Buffer response with requestId equal to the one about to be sent | contact PLANTA | |
| 0200074 | ERROR | operative | Could not execute session binary | check server directory contents and permissions, esp. within 'dlls'; contact PLANTA |
Python
| Log Message ID | Level | Marker | Description | TODO |
|---|---|---|---|---|
| 0300001 | ERROR | migration | Migration failed because of Python error | Check the printed traceback for the Python error and fix it |
| 0300002 | INFO | migration | Summary of failed migration packets | Check the migration packets for manual tasks that need to be done |
PLANTA link Webservices
All PLANTA link webservice log messages have the marker "webservices"
| Log Message ID | Level | Description | TODO |
|---|---|---|---|
| 0600001 | INFO | New request incoming | |
| 0600002 | ERROR | An internal error has occured while processing a request | Check the log for further information |
| 0600003 | INFO | A request has completed | |
| 0600005 | ERROR | A request has concluded, but the logger for this request could not be cleaned up | |
| 0600006 | ERROR | The request header for the current request could not be found in the database. The request log in PLANTA won't be updated | |
| 0600007 | ERROR | A request has concluded, but the request header could not be cleaned up | |
| 0600008 | ERROR | An internal request was received, but the url is malformed | Check the calling code |
| 0600009 | INFO | The new request was identified as an internal request | |
| 0600010 | ERROR | An internal request was received, but no implementation exists | Check the calling code |
| 0600011 | ERROR | The given attributes of the request lack mandatory attributes | Provide the mandatory attributes in the request |
| 0600012 | ERROR | The given attributes of the request contain superfluous attributes | Remove the additional attributes from the request |
| 0600013 | INFO | Returning {} characters | |
| 0600014 | INFO | The request found no data | |
| 0600015 | ERROR | <Unused> | |
| 0600016 | INFO | <x> objects will be updated by this request | |
| 0600017 | ERROR | The data sent in this request could not be saved | |
| 0600018 | ERROR | The task referenced in the request is locked | |
| 0600019 | ERROR | The project referenced in the request is locked | |
| 0600020 | ERROR | The load record referenced in the request is locked | |
| 0600021 | ERROR | The resources maximum hours for that day have been reached | |
| 0600022 | ERROR | Load records can not be created past the current week | |
| 0600023 | ERROR | Load records can not be created outside the reporting period | |
| 0600024 | ERROR | The record specified in the request could not be updated as it is not synchronized with PLANTA pulse | |
| 0600025 | ERROR | The record specified in the request could not be deleted as it is not synchronized with PLANTA pulse | |
| 0600026 | INFO | Events initialized successfully | |
| 0600027 | ERROR | The project referenced in the request is finished | |
| 0600028 | ERROR | The task referenced in the request is finished | |
| 0600029 | ERROR | Load records can not be created with a negative actual load value | |
| 0600030 | ERROR | The resource assignment referenced in the request is finished | |
| 0600031 | ERROR | Could not delete entity {} | |
| 0600032 | INFO | Deleted entity {} | |
| 0600033 | ERROR | Transformation failed | Check the error message for details |
| 0600034 | ERROR | The request contains invalid json | Correct your json |
| 0600035 | ERROR | The attributes of the entity could not be set | Check your data |
| 0600036 | ERROR | The request contained a read only attribute | Check your data |