Barco DP2K SLP Series Service Manual page 379

Dec 31 17:00:18 localhost local0.info dp60[233]: main - projector type is ...
Dec 31 17:00:21 localhost local0.info dp60[233]: ti-icp - wait until ready
Dec 31 17:00:34 localhost local0.info dp60[233]: system - synchronize date to ...
Apr 6 12:49:25 localhost local0.info dp60[233]: system - ti-link-decryptor ...
Apr 6 12:49:41 localhost local0.info dp60[233]: system - ti-link-decryptor ...
Apr 6 12:49:41 localhost local0.info dp60[233]: system - load lens encoder file ...
Apr 6 12:49:41 localhost local0.info dp60[233]: command (port = internal) - ...
...
Format :
'Time' localhost 'facility code'.'severity code' 'component name' ['pid']: 'message'
Where :
• 'Time' = the time when the event occurred
• 'facility code' = component level that generates a log message
• 'severity code' = the severity can be : info – debug – warning – alert – err.
•
'component name' = component name that generates a log message.
- dp60 = main process
- kernel = Linux kernel
- router = component which manages the router
- TI_marriage = component which handles the marriage
- clo = component which handles Light Sensor logic
- license-manager = internal license manager
- crypto memory = process which handles communication with crypto memory module (ID card)
• 'pid' = Process identifier. The internal process identifier, of the component generating the log message.
• 'message' = The actual error message.
The Barco controller inserts every hour an unique entry in the Barco log file and in the TI log file. This is done
to be able to synchronize events in both log files, when the clocks are not aligned. It will also be used for a
tool, that is still to be implemented, that will merge both log files, to make better analysis.
Example of such an entry :
Feb 3 02:41:16 localhost local0.info dp60[233]: log mark - 0000003c1b84 - 8
Each Barco entry into a TI log is proceeded with a B.
What does the id means (as in the example) :
•
0000003c
- the first 4 bytes give a hex interpretation of how many time the system has been booted.
- 3c hex is 60 in decimal. It means that this system has been booted 60 times. Every boot cycle
increases the timer with 1.
• 1b84 = the last two bytes, are random unique 2 bytes.
• 8 = the last digit indicates the number of hours passed in this boot cycle (in a decimal value). Every boot
cycle resets this number to 0.
Ethernet connection messages in log file (some examples).
Apr 6 14:05:19 localhost local0. info dp60 [233]: main - closing connection of
150.158.197.64:43680 (keep-alive time expired)
→ after 15 minutes of inactivity projector will close connection.
Apr 6 14:08:55 localhost local0. info dp60 [233]: main - accepted connection from
150.158.192.133:43680
→ connection from communicator, from pc with ip address 150.158.192.133
Apr 6 14:08:58 localhost local0.info dp60[233]: log (port = 150.158.192.133:43680:1e)
- logon-phmt-barco-default
→ communicator inserts in log file, who logged on to projector
Apr 6 14:09:07
150.158.192.133:43680:1e) - set lamp on
localhost local0. info dp60 [233]:
R5906848 /04
Troubleshooting
command (port =
DP2K SLP Series 379