FAQs
From CometWiki
(Created page with "== FAQs == '''Where are all the various log files?'''<br> When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log fil...") |
|||
| Line 11: | Line 11: | ||
'''The CosP Log'''<br> | '''The CosP Log'''<br> | ||
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In order to get the log you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings. | For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In order to get the log you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings. | ||
| + | |||
| + | '''The Comet Services Logs'''<br> | ||
| + | Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder.<br> | ||
| + | |||
| + | The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6.<br> | ||
| + | |||
| + | The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance.<br> | ||
Revision as of 17:58, 13 February 2015
FAQs
Where are all the various log files?
When troubleshooting problems with your Comet installation, a good first place to start is with the appropriate log file. Here is a list of the log files and where you'll find them:
The Comet Log
The easiest way to find the Comet log is to click on the "System Logs" button on the QMONITOR screen. This will open Windows Explorer to the folder containing the log. It will have all of the log information since the last time the log file was either erased or truncated. If you only need to see the log for the current Comet session just click on View->Comet log at the top of your Comet window (full Comet sessions only).
Another way to find the path to the Comet log file is to look at the value assigned to your LOGS alias. Click on Edit->Directory Aliases at the top of your Comet window to view the path.
The CosP Log
For printing problems this is the first place to look. You'll find it in the same folder as the Comet log (above). In order to get the log you must turn on the logging option in your CosW.ini. See info below about where to find CosW.ini and where to find a list of the settings.
The Comet Services Logs
Both the Security Server and the File Server produce logs which may be helpful in troubleshooting problems. You'll find the logs in a folder called LOGS in your Comet Services folder.
The current Security Server log is called CSecSrv.log. Each time you restart the Security Server a new log is started so that seven generations of logs are kept. They are named CSecSrvN.log, where N is a number from 1 to 6.
The current file server log is called CometSrv.log. Each time you restart the File Server a new log is started so that seven generations of logs are kept. They are named CometSrvN.log, where N is a number from 1 to 6. The log is only created if you have logging turned on. You'll need administrative privileges to turn logging on. From the file server console, click on View->Properties. Check the "Log Messages" box under "Diagnostic Logging". Select the "All Messages" radio button. The top half of the properties dialog lets you choose which functions will generate log entries. Unless you are troubleshooting a particular function we recommend you choose the "Show None" button. This will restrict logging to just logins and logouts and any error messages that occur. Adding additional functions to the logging can impact file server performance.
