Like CET log files, Catalogues also create log files for logging error messages and other valuable information for debugging.
Each log entry is timestamped. The logs are also rotated like CET logs.
There should be 5 log files with the first one named Catalogue.cmtxt, followed by Catalogue1.cmtxt and so on. They are ordered by the time they are created.
The logs can be found at
- C:\Users\user\AppData\Local\CET Data\VersionNumber
What the logs contain.
- The date the log was started
- Setup of connection and if the relevant ports are open.
- The list of registered catalogue database files along with their id.
The status of the background sync task used to sync the catalogues
- This can include information such as the duration between the current and previous sync.
- If the download queue is busy
- The number of files queued to download for each catalogue, with some names of the files that are downloaded
- The catalogues that are being registered locally in CET as the system loads up.
Similar to error navigation for CET log. Clicking in CET Studio on an error or warning should bring you to the location of where the error/warning occurred.
Couldn’t find available ports for connection
RpcClient::parseResponse - Error: 502 Bad Gateway
There was a problem with communication with the server. There are a few variations of this, and they all start with RpcClient::parseResponse - Error: followed by a more descriptive error message.
errorOccured: [error message]
This happens if a general error occurs. The following text should have a more descriptive error message. Some common errors that would use this format (below are examples, the actual error message would be more specific to the situation)
- Error while logging in.
- Error while creating, deleting, catalogue.
- Error while adding, deleting files to catalogue.
- Error while deleting file from catalogue.
- Error while updating catalogue settings.
- Error while getting user catalogue data.
- Error while determining if the catalogue is turned on for the user.
Many more errors can occur, but generally, it would appear for various catalogue-related communication with the server.
If you are able to reproduce the error locally and want more information, there are a few trace flags that might come in handy. Find them in cm/abstract/dataSymInterface/communication/dsConfig.cm
This is for tracing async http events.
For tracing ZMQ related events.
For tracing events related to foreground/background sync tasks.