Page 1 of 1
How to start WCCOAtoolLogViewer within only 1 specific log file
Posted: Thu Aug 08, 2019 10:46 am
by sblancha
Hello,
How to start WCCOAtoolLogViewer within only 1 specific log file. I know that once open I can unselect files but for large project there are so many....
Cheers,
Sebastien
Re: How to start WCCOAtoolLogViewer within only 1 specific log file
Posted: Fri Aug 09, 2019 3:31 pm
by leoknipp
What is the use case of opening a log viewer with only 1 file?
Normally only the pmon.<hostname> and PVSS_II.log file contain data.
All other log files are empty. Only if debugging options are used content is written to the files.
Best Regards
Leopold Knipp
Senior Support Specialist
Re: How to start WCCOAtoolLogViewer within only 1 specific log file
Posted: Mon Aug 12, 2019 11:16 am
by sblancha
in my use case, PVSS_II.log is polluted by some third party uis or control managers and I have a new script launched by a control manager num X and I want to see only the messages and errors coming from this script. I can change the setting only elected the file WCCOActrlX.log or read it with any editor but I wondering if there is an option launching WCCOAtoolLogViewer within only 1 file (that will be very convenient).
Re: How to start WCCOAtoolLogViewer within only 1 specific log file
Posted: Wed Aug 14, 2019 10:59 am
by leoknipp
If your script returns an error this information will be written to the PVSS_II.log file as all other standard errors for every WinCC OA manager.
The manager log file will only contain information written by Debug* functions or by activated debug flags.
When your PVSS_II.log file contains too many errors you should get rid of them.
The PVSS_II.log file is used for analysis if a problem in WinCC OA shall be checked. When there are many lines of errors some standard information (e.g. startup of the project) is not available anymore which makes it maybe impossible to detect why a problem in WinCC OA occured.
Best Regards
Leopold Knipp
Senior Support Specialist
Re: How to start WCCOAtoolLogViewer within only 1 specific log file
Posted: Wed Aug 14, 2019 1:54 pm
by gschijndel
To monitor file(s) you could also use the command 'tail -f <logfile (pattern)>' instead of the log viewer.