DM service starts but does not function with permission errors in logs after upgrade - DX NetOps Portal

Products

• Network Observability
• CA Performance Management

Issue/Introduction

You see 503 errors when you attempt to access the Portal UI. While the Device Manager (DM) service starts, it does not function correctly.

Symptoms

You find the following error in the DMService.log file:

ERROR | WrapperSimpleAppMain | #### | com.ca.im.portal.api.services.repository.RepositoryService | Application does not have write permission for $PORTAL_HOME/CA/PerformanceCenter/DM/repository directory.

com.ca.im.portal.api.services.interfaces.repository.RepositoryException: Application does not have write permission for $PORTAL_HOME/CA/PerformanceCenter/DM/repository directory.

Environment

All supported Network Observability DX NetOps Performance Management Portal web server releases

Cause

This issue occurs because the Repository.Root.Directory attribute in the netqosportal.general database table points to an incorrect or legacy installation directory (e.g., ####/app1 instead of ####/app). This typically happens if the server was migrated between hosts in the past. The upgrade scripts do not automatically update this specific database value to match the current installation path.

Resolution

You must manually update the database to reflect the correct home directory.

1. You log into the MySQL database on the Portal host.

2. You execute the following command to update the path (replace $PORTAL_HOME with your actual installation home):

   sql

    

   REPLACE INTO netqosportal.general (Attribute, Value) VALUES ('Repository.Root.Directory', '$PORTAL_HOME/CA/PerformanceCenter/DM/repository');

3. You restart the Performance Center services:

   • systemctl restart caperfcenter_sso
   • systemctl restart caperfcenter_devicemanager
   • systemctl restart caperfcenter_console

4. You verify that the DMService.log no longer reports permission errors and the service functions as expected.

Note: If 503 errors persist in the UI after this fix, you should also verify the log4j appender configuration for the Console service.