PrimeCenter Logging: How to Use calapisvc.log for Troubleshooting

The calapisvc.log file is a general-purpose log used by PrimeCenter to record background activity during a production session.

Log file locations:

• macOS: /var/calapisvc/calapisvc.log
• Windows: %USERPROFILE%\AppData\Local\calapisvc\calapisvc.log

Tip: The %USERPROFILE% variable refers to your specific Windows user folder (e.g., C:\Users\Caldera\). Note that the AppData folder is hidden by default; to see it, enable Hidden items under the View tab in File Explorer.

This log provides visibility into how PrimeCenter processes files and manages jobs behind the scenes.

What the log is used for

The calapisvc.log helps track the lifecycle of a job as it moves through PrimeCenter, including:

• File intake and preparation, such as when PDFs are loaded and analyzed
• Extraction of pages and assets used for layout
• Detection of duplicate files to avoid reprocessing
• Identification of key print elements like cut lines, bleed, and page dimensions
• Creation and management of production tasks (recipes, layouts, copies)

It also records general system activity, including session handling and communication between internal components.

Additional logging and troubleshooting

• Production reports (PrimeCenter 4.6 and newer):
  Can be enabled via Settings > Production Report to provide a higher-level overview of job processing.

• Live debugging of the PrimeCenter frontend (for the advanced user)
  When the PrimeCenter interface is open, the browser console can be used for real-time troubleshooting. The PrimeCenter frontend is built on an Electron web-tech framework, pressing Cmd + Option + J (macOS) or Ctrl + Shift + J (Windows/Linux) pulls up the standard Chromium developer drawer, select the Console tab.

   

• Start with a clean log:
  For troubleshooting, it can be helpful to start with a fresh log file to isolate recent events and errors. To do this, first remove or rename the existing calapisvc.log file, then restart the Caldera API Service. You can restart the service using:
  • CalderaDock (recommended):
    Go to CalderaDock > Tools > Services > PrimeCenter and restart the service.

Alternative ways to restart the Caldera API Service:

• macOS (Terminal):
  Stop the service:
  sudo launchctl unload /Library/LaunchDaemons/com.caldera.calapisvc.plist
  Start the service:
  sudo launchctl load /Library/LaunchDaemons/com.caldera.calapisvc.plist
• Windows (GUI):
  Open Task Manager > Details, locate calapisvc, stop it, then start it again by launching:
  C:\Program Files\CalApiSvc\bin\calapisvc.exe
• Windows (Command Line):
  Stop the service:
  taskkill /T /F /IM calapisvc.exe
  Start the service:
  "%PROGRAMFILES%\CalApiSvc\bin\calapisvc.exe"

When to check this log

Review the calapisvc.log when:

• Jobs are not processed as expected
• Layouts or assets are missing or incorrect
• Errors occur during automation or recipe execution
• Licensing or system communication issues are suspected

The log may include warnings or errors related to job validation, licensing checks, or device communication, which can help identify the root cause of issues.

For intermittent license related issues, check the following article: How to send Sentinel license log files to Support