Location of trace logs

Question

Hi,
Can any one tell where the trace logs,audits etc are stored in content server's file system
Thanks in advance
Amit

Answer 1

Content Server logs are written to:
<cs_dir>/weblayout/groups/secure/logs and are named IdcLog01.htm - IdcLog30.htm. The file IdcnLog.htm keeps track of the log number to date relationship and is the page the web GUI resolves to.
Archiver logs are written to:
<cs_dir>/weblayout/groups/secure/logs/archiver and are named ArchiveLog01.htm - ArchiveLog30.htm. The file ArchiveLnLog.htm keeps track of the log number to date relationship and is the page the web GUI resolves to.
Verity log is written to:
<cs_dir>/weblayout/groups/secure/logs/verity and is called search.log. This log is a single text file and will grow as entries are written to it - this different behaviour is because this log file is created by the licensed Verity indexing application.
NOTE: By default the verity debug level is set to none - so no logs will be created. Verity debug levels are set in the repository manager indexer setup screen and can vary from verbose to all. Be aware that high levels of debug information from verity will create a very large log file very quickly. There will also be a processor and disk I/O overhead from the processing and writing of verbose log file entries.
Server output log is written to:
Windows:
<cs_dir>/bin/IdcServerNT.log if UseRedirectedOutput=true is set in the config.cfg file. This file should be purged occasionally as it can grow to a fairly large size. However this can be cleared form the admin server web GUI interface and should be checked regularly for major errors and warnings that are written to the file.
Unix:
<cs_dir>/etc/log regardless of whether or not UseRedirectedOutput=true is set.
Web Server Filter logs:
Windows:
<cs_dir>/idcplg/idc_cgi_isapi-<instance>.dll.log
Unix:
<cs_dir>/data/users/authfilter.log
These are accessed through the Filter Administration link from the administration page. Options can be set from here and the filter viewed and output cleared. Because this is primarily a debugging tool, it is not normal practice to save or archive these logs. There is also substantial performance overhead involved with writing these logs, so they should not be left running in normal production mode.