To identify errors, platform crashes, tune performance, and perform other analysis of 1C:Enterprise 8, a technical log is used. Every 1C:Enterprise administrator eventually encounters the need to use this log. In this note, we will look at how to enable the technical log, configure it to collect the necessary information, and review practical examples of the most useful technical logs.
Starting the technical log.
So, to start collecting log data, place logcfg.xml in the bin\conf directory of a specific release of 1C:Enterprise 8.2, for example, c:\Program Files\1cv82\8.2.18.104\bin\conf\ on the machine where the 1C:Enterprise server is running. The server checks this file once per minute. The file format is as follows:
<config xmlns="http://v8.1c.ru/v8/tech-log">
<dump create="true" location="c:\dumps" prntscrn="true" type="2"/>
<log history="72" location="c:\logs">
<event>
<eq property="name" value="EXCP"/>
</event>
<property name="all"/>
</log>
</config>
where c:\dumps and c:\logs are directories for dumps and logs, respectively, and history is the log retention time in hours. (Dumps are needed if you plan to send them directly to 1C; for other cases, this tag is not required).
Attention! To correctly start the technical log, ensure the following:
- The user under which the 1C:Enterprise server runs must have write permissions to these directories; the history parameter specifies the log retention time in hours;
- Case sensitivity matters in directory names in the logcfg.xml file; C:\LOGS and c:\Log are different directories;
- In the same file, do not end the path with a slash; c:\logs\ will not work.
A sign of successful startup of the technical log is the appearance of rphost_XXXX, rmng_XXXX, and ragent_XXXX directories in c:\logs.
Configuring the log.
Log configuration in most cases involves describing the events necessary for analysis (EVENTS tag) and specifying the required attributes. The list of allowed values for VALUE is provided in the table below.
| ALL | All events | All events from the technical log |
| ADMIN | Administrative action | Actions performed by a cluster administrator in 1C:Enterprise 8.2 |
| CALL | Incoming call | Incoming remote call (remote call on the receiver side) |
| CONN | Server connection | Establishment or termination of a TCP connection between 1C:Enterprise system processes |
| CLSTR | Cluster activity | Execution of operations that change the behavior of the server cluster |
| EDS | External data source | All events from external data sources |
| DB2 | IBM DB2 | Execution of SQL statements in the IBM DB2 DBMS |
| DBMSSQL | Microsoft SQL Server | Execution of SQL statements in the Microsoft SQL Server DBMS |
| DBPOSTGRS | PostgreSQL | Execution of SQL statements in the PostgreSQL DBMS |
| DBORACLE | Oracle Database | Execution of SQL statements in the Oracle Database DBMS |
| DBV8DBEng | SQL, File-based DBMS | Execution of SQL statements in the file-based DBMS |
| EXCP | Exception | An exceptional situation in the 1C:Enterprise application that is not handled normally and may cause the server process or an attached client process to terminate abnormally |
| EXCPCNTX | Exception context | An event that started but did not complete at the moment an abnormal situation occurred |
| HASP | HASP access | Access to the hardware protection key (HASP) |
| LEAKS | Memory leak | An event related to a memory leak, which may be caused by errors in the configuration code |
| MEM | Server memory leak | An event related to an increase in memory usage by server processes (ragent, rmngr, rphost). |
| PROC | Process | An event that affects the entire process and its further operability. For example: start, completion, abnormal termination, etc. |
| QERR | Query error | An event related to the detection of query compilation errors or restrictions at the database record and field levels |
| SCALL | Outgoing call | Outgoing remote call (outgoing call on the caller side). |
| SCOM | Server context | An event of creating or deleting a server context, usually associated with an information base. |
| SDBL | Database query | Execution of queries against the 1C:Enterprise 8.2 database model |
| SESN | Session | An action related to a user session. For example: session start, session end, etc. |
| SRVC | Cluster services | Events related to the start, stop, and notifications of cluster server services |
| TLOCK | Lock | Management of transaction locks in Managed mode |
| TDEADLOCK | Deadlock | A deadlock detected in Managed mode |
| TTIMEOUT | Timeout | The maximum wait time for a transaction lock has been exceeded |
| VRSCACHE | HTTP cache | Operation of the server call cache |
| VRSREQUEST | Server request | A request to the server for a specific resource |
| VRSRESPONSE | Server response | Server response |
| SYSTEM | System events | System events of the platform mechanisms intended for analysis by 1C company employees |
Examples of logs
- Long-running queries.
We will collect data on queries that take more than 10 seconds to execute. Example for an MSSQL database server.
<config xmlns="http://v8.1c.ru/v8/tech-log"> <log location="C:\Temp\1cv8logs\2" history="1"> <event> <eq property="Name" value="DBMSSQL" /> </event> <property name="sql"> <event> <eq property="Name" value="DBMSSQL" /> <gt property="Duration" value="10000" /> </event> </property> </log> </config>
- All errors, including dumps.
<config xmlns="http://v8.1c.ru/v8/tech-log"> <dump create="true" location="d:\dumps" prntscrn="true" type="2"/> <log history="72" location="d:\logs"> <event><eq property="name" value="EXCP"/></event> <event><eq property="name" value="EXCPCNTX"/></event> <event><eq property="name" value="PROC"/></event> <event><eq property="name" value="ADMIN"/></event> <event><eq property="name" value="MEM"/></event> <event><eq property="name" value="LEAKS"/></event> <property name="all"/> </log> </config> Если ваше предпр
If your pre