Debug mode and logs

From PlcWiki

Current revision as of 13:08, 11 October 2013

From october 2013 we change logic of debug mode and logs files. Until that, there was main parameter for control of debug mode

workplace.DebugLevel = 0

From october 2013 is this parameter optional, because debug level 0 is the same like debug level 2 before. We log in detail for complete overview of client behavior. Every log is automatically rotated after 50MB. We recommend don't change debug lebel to any other value than 0. Structure of new client's log files is this:

install.log (plc client installation log)

plc.service.log (main log for services. For example start of sqlsender)

plc_XX.log (Main client info log, where XX is workplace ID. The text between {# and #} is the original untranslated text in English. It's there so that even people not speaking German, Spanish, Czech, Portuguese, Turkish, ... can understand these logs/emails. Name of that file is old one, just for task who still need it. There is one more name for that file, and that is plc_client_XX.info.log, which is the same log)

plc_client_XX.cnp.log (this is log file of communication between client and kernel in case of new Clever Network Protocol is used)

plc_client_XX.debug.log (main debug log with highly detailed information about client processes)

plc_client_XX.device.log (log for devices like tightening machines or racks, you can see results of tightres here)

plc_client_XX.error.log (system errors can be find here)

plc_client_XX.info.log (the info log should approx. contain the same amount of information as the old plc_XX.log)

plc_screen_XX.log (screen log contain a information what was written on screen and what worker can see in main window of our client. There is untranslated text in english between {# and #} as well)

In /usr/local/plc/log/ can be found more log files regarding of processes what running on specific machine. For example plc_radion.log, plc_trolley2vin_lineRFID.log, workers.log and others.