Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Link copied. Please paste this link to share this article on your social media post.
📖 Home Back
All ClearSCADA log entries follow the same pattern as below:
Here is an example log excerpt:
The Identifier may indicate the component of DBServer that logged the message, [DBFILE] below:
Server Links.pngServer Links.png
Amongst other things the client connection id can be used to identify:
In this example we can follow the activity associated with a new client link that connected to the server.
All ClearSCADA log entries follow the same pattern as below:
15-FEB-2010 15:27:59.683 0224 [OPCAEEVENTMGT] 1:05 GetState( IN )
UTC Date Time
Thread Id (HEX)
Identifier
Message
Here is an example log excerpt:
15-FEB-2010 15:27:59.683 0224 [OPCAEEVENTMGT] 1:05 GetState( IN )
15-FEB-2010 15:27:59.683 0224 [OPCAEEVENTMGT] 1:05 GetState( OUT: hr 0 -> Ok.)
15-FEB-2010 15:27:59.684 0464 [OPCAE] 2:02 GetStatus( OUT: hr 0 -> Ok.)
15-FEB-2010 15:28:00.003 0C7C Perform DoMinuteOp() on objects
15-FEB-2010 15:28:00.003 0C7C DoMinuteOp() on objects complete
15-FEB-2010 15:28:00.003 0C7C Calculate object memory usage (starting offset 0)
15-FEB-2010 15:28:00.003 0C7C Calculate object memory usage complete
15-FEB-2010 15:28:00.003 06C8 [DBFILE] PerformSave next state Metadata.
15-FEB-2010 15:28:00.003 06C8 [DBFILE] About to save metadata
15-FEB-2010 15:28:00.003 06C8 [DBFILE] PerformSave next state Structure.
15-FEB-2010 15:28:00.003 06C8 [DBFILE] About to save structure
15-FEB-2010 15:28:00.003 06C8 [DBFILE] PerformSave next state Permit.
15-FEB-2010 15:28:00.003 06C8 [DBFILE] About to save permit
15-FEB-2010 15:28:00.003 06C8 [DBFILE] PerformSave next state Config.
15-FEB-2010 15:28:00.003 06C8 [DBFILE] About to save config
15-FEB-2010 15:28:00.004 06C8 [DBFILE] Config save (no changes)
15-FEB-2010 15:28:00.004 06C8 [DBFILE] PerformSave next state Data.
15-FEB-2010 15:28:00.004 06C8 [DBFILE] About to save data
15-FEB-2010 15:28:00.004 06C8 [DBFILE] Data save (no changes)
15-FEB-2010 15:28:00.004 06C8 [DBFILE] No database changes detected, nothing saved
15-FEB-2010 15:28:00.004 06C8 [DBFILE] PerformSave next state Idle.
15-FEB-2010 15:28:02.375 0270 [SVRADVTHR] 1 Timeout
15-FEB-2010 15:28:02.375 1280 [SVRTHR] 1 Timeout
15-FEB-2010 15:28:02.376 0464 [SVRTHR] 2 Timeout
15-FEB-2010 15:28:02.376 0D7C [SVRADVTHR] 2 Timeout
15-FEB-2010 15:28:02.398 13C8 [DATAFILE] Beginning flush cycle
15-FEB-2010 15:28:02.398 13C8 [DATAFILE] Flush cycle complete, flushed 0 files (0 bytes), time taken 0.000000 milliseconds
15-FEB-2010 15:28:02.532 0F0C [ICMP] Poll Timer Callback
15-FEB-2010 15:28:02.532 0F0C [ICMP] Tx 0: Addr 172.24.1.204 (172.24.1.204), Len 40, Ident 256, Seq 143
15-FEB-2010 15:28:03.745 1280 [SCXIcon] 1:01 Poll()
15-FEB-2010 15:28:11.739 1194 [SVR] Accepted connection 14 from 127.0.0.1:50880 to 127.0.0.1:5481...
15-FEB-2010 15:28:11.739 1194 [SVR] ... Connection 14: Type 1, client version 0x6450E64 (6.69.3684), (Uncompressed,Floating Licence,ViewX,Include Checksums)
15-FEB-2010 15:28:11.739 1194 [SVR] ... Connection 14 confirmed, link version 6.69.3684, client name 'IP 127.0.0.1, Session 1'
15-FEB-2010 15:28:11.740 1194 [SVRTHR] 1 AddClient from 127.0.0.1:50880, link is [SCX] 1:10
15-FEB-2010 15:28:11.740 1194 [SCX] 1:10 QP Created
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( IN: LoggedOn 0, User (null), Workstation Name , Client Name Unknown )
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( OUT: Hr 0 -> Ok. )
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( IN: Lcid 0x809, ClientName STEFAN-W7::CSCXObject)
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( OUT: Features 19727, hr 0 -> Ok. )
15-FEB-2010 15:28:11.741 0224 [SCX] 1:10 FindObject( IN: Name 'New Analogue Point' )
15-FEB-2010 15:28:11.741 0224 [SCX] 1:10 FindObject( OUT: Id 1, Hr 0 -> Ok. )
15-FEB-2010 15:28:11.752 0224 [SCX] 1:10 ReadObject( IN: Id 1 )
15-FEB-2010 15:28:11.766 0224 [SCX] 1:10 ReadObject( OUT: hr 0 -> Ok., Version 1, Count 7 )
Thread ID
The Thread ID can be used to identify which thread created the log entry.
A list of all threads indexed by Thread ID can be found in
- Server Status, General/Threads tab
- The 'General Threads' section of DB_SNAPSHOT file
Identifier
The Identifier may indicate the component of DBServer that logged the message, [DBFILE] below:
15-FEB-2010 15:28:00.003 06C8 [DBFILE] PerformSave next state Metadata.
15-FEB-2010 15:28:00.003 06C8 [DBFILE] About to save metadata
15-FEB-2010 15:28:00.003 06C8 [DBFILE] PerformSave next state Structure.
15-FEB-2010 15:28:00.003 06C8 [DBFILE] About to save structure
15-FEB-2010 15:28:00.003 06C8 [DBFILE] PerformSave next state Permit.
It may also indicate the link used by a remote client to communicate with the server. The following message were raised from link '[SCX] 1:10', link type 'SCX' and id '1:10':
15-FEB-2010 15:28:11.741 0224 [SCX] 1:10 FindObject( IN: Name 'New Analogue Point' )
15-FEB-2010 15:28:11.741 0224 [SCX] 1:10 FindObject( OUT: Id 1, Hr 0 -> Ok. )
15-FEB-2010 15:28:11.752 0224 [SCX] 1:10 ReadObject( IN: Id 1 )
15-FEB-2010 15:28:11.766 0224 [SCX] 1:10 ReadObject( OUT: hr 0 -> Ok., Version 1, Count 7 )
Details about the system's active links can be accessed via
- Server Status, On the Server/Links tab
Server Links.pngServer Links.png
- The 'Server Links' section of DB_SNAPSHOT files
Amongst other things the client connection id can be used to identify:
- Source, IP Address
- Client Version/Effective Link Version, ClearSCADA Version
- Client Name, Name of the machine (or driver)
- User Name, ClearSCADA user
Example Analysis
In this example we can follow the activity associated with a new client link that connected to the server.
15-FEB-2010 15:28:11.739 1194 [SVR] Accepted connection 14 from 127.0.0.1:50880 to 127.0.0.1:5481...
15-FEB-2010 15:28:11.739 1194 [SVR] ... Connection 14: Type 1, client version 0x6450E64 (6.69.3684), (Uncompressed,Floating Licence,ViewX,Include Checksums)
15-FEB-2010 15:28:11.739 1194 [SVR] ... Connection 14 confirmed, link version 6.69.3684, client name 'IP 127.0.0.1, Session 1'
'[SVR]' logs the new incomming connection recording the connection details (source and destination IP addresses and ports).
The client version, licensing details and client name are identified.
15-FEB-2010 15:28:11.740 1194 [SVRTHR] 1 AddClient from 127.0.0.1:50880, link is [SCX] 1:10
'[SVRTHR] 1' adds the client and assignes it the link identifier '[SCX] 1:10'. (For details on links and link threads see Links, Advises and Associated Server Threads)
15-FEB-2010 15:28:11.740 1194 [SCX] 1:10 QP Created
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( IN: LoggedOn 0, User (null), Workstation Name , Client Name Unknown )
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( OUT: Hr 0 -> Ok. )
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( IN: Lcid 0x809, ClientName STEFAN-W7::CSCXObject)
15-FEB-2010 15:28:11.740 1280 [SCX] 1:10 SetClientDetails( OUT: Features 19727, hr 0 -> Ok. )
15-FEB-2010 15:28:11.741 0224 [SCX] 1:10 FindObject( IN: Name 'New Analogue Point' )
15-FEB-2010 15:28:11.741 0224 [SCX] 1:10 FindObject( OUT: Id 1, Hr 0 -> Ok. )
15-FEB-2010 15:28:11.752 0224 [SCX] 1:10 ReadObject( IN: Id 1 )
15-FEB-2010 15:28:11.766 0224 [SCX] 1:10 ReadObject( OUT: hr 0 -> Ok., Version 1, Count 7 )
We now see details about the activity of '[SCX] 1:10' as its connection is initialised and client details registered.
The client then finds the object 'New Analogue Point' to determine its Object Id, in this case '1'.
The client then reads the details of Object Id 1.
Go: Home Back
Author
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.