Troubleshooting Data Communication Stoppage

Objective

To identify and resolve issues causing data communication failure by:

Verifying the status of Cormatix services
Restarting services that are stopped or not responding
Collecting relevant application and system logs for further analysis
Reviewing system event logs (Windows Event Viewer or Linux system logs) for related errors

Open Run → Press Windows + R, type services.msc, and press Enter.
Locate services starting with Cormatix_* and check whether the status is Running or Stopped.
If the service is Running, open Properties, note the Path to Executable, navigate to the installation/log directory, collect the latest log files, and create a support ticket with the IBM Support Team, attaching the collected logs for further investigation
If Stopped, right-click and select Start.
If the service fails to start or stops again, open Event Viewer → Windows Logs → Application, check for Error or Critical events related to Cormatix, and record the Event ID, error description, and timestamp. Share the details with your IT support team for initial analysis, and if the issue appears to be related to the application, create a support ticket with the IBM Support Team and attach the necessary logs for further investigation.

Open Terminal.
Run the command:

sudo supervisorctl status
Check for services starting with Cormatix* and verify their status.
If the service is stopped, start it using:

sudo supervisorctl start <service_name>
If it fails to start, review application logs or supervisor logs (for example /var/log/supervisor/) and share the error details with the IBM Support Team.