NetOps Portal web server services fail to start
search cancel

NetOps Portal web server services fail to start

book

Article ID: 402475

calendar_today

Updated On:

Products

Network Observability CA Performance Management

Issue/Introduction

Portal Installation on RHEL 9 Issues where the installation log shows a Non Fatal Error.

After installation, all portal services can not be started. there is no log in PC/EM/DM directories.

Portal is installed using a non root user with proper sudo user configuration in place.

Checking service status using systemctl command we see a permissions error.

Jun 24 14:32:14 <hostName> systemd[1]: Starting DX NetOps Portal SSO...
Jun 24 14:32:14 <hostName> caperfcenter_sso[48287]: Starting DX NetOps Portal SSO...
Jun 24 14:32:14 <hostName> caperfcenter_sso[48287]: CEF:0|Broadcom|DX NetOps Portal SSO|24.3.10|100|STARTING SERVICE|1|user=<nonRootUser>
Jun 24 14:32:14 <hostName> caperfcenter_sso[48357]: /opt/CA/PerformanceCenter/sso/bin/caperfcenter_sso: line 1941: /opt/CA/PerformanceCenter/sso/bin/PerfCenter-sso: Operation not permitted
Jun 24 14:32:29 <hostName> caperfcenter_sso[48287]: Waiting for DX NetOps Portal SSO..................
Jun 24 14:32:29 <hostName> caperfcenter_sso[48287]: WARNING: DX NetOps Portal SSO may have failed to start.
Jun 24 14:32:29 <hostName> caperfcenter_sso[48408]: /opt/CA/PerformanceCenter/sso/bin/caperfcenter_sso: line 1425: /opt/CA/PerformanceCenter/sso/bin/PerfCenter-sso: Operation not permitted
Jun 24 14:32:29 <hostName> systemd[1]: caperfcenter_sso.service: Control process exited, code=exited, status=1/FAILURE
Jun 24 14:32:29 <hostName> systemd[1]: caperfcenter_sso.service: Failed with result 'exit-code'.
Jun 24 14:32:29 <hostName> systemd[1]: Failed to start DX NetOps Portal SSO.

The same messages are seen for the Event Manager and Device Manager services.

Jun 24 13:05:23 <hostName> systemd[1]: Starting DX NetOps Portal EM...
Jun 24 13:05:23 <hostName> caperfcenter_eventmanager[40553]: Starting DX NetOps Portal EM...
Jun 24 13:05:23 <hostName> caperfcenter_eventmanager[40553]: CEF:0|Broadcom|DX NetOps Portal EM|24.3.10|100|STARTING SERVICE|1|user=<nonRootUser>
Jun 24 13:05:23 <hostName> caperfcenter_eventmanager[40623]: /opt/CA/PerformanceCenter/EM/bin/caperfcenter_eventmanager: line 1941: /opt/CA/PerformanceCenter/EM/bin/PerfCenter-EM: Operation not permitted
Jun 24 13:05:38 <hostName> caperfcenter_eventmanager[40553]: Waiting for DX NetOps Portal EM..................
Jun 24 13:05:38 <hostName> caperfcenter_eventmanager[40553]: WARNING: DX NetOps Portal EM may have failed to start.
Jun 24 13:05:38 <hostName> caperfcenter_eventmanager[40683]: /opt/CA/PerformanceCenter/EM/bin/caperfcenter_eventmanager: line 1425: /opt/CA/PerformanceCenter/EM/bin/PerfCenter-EM: Operation not permitted
Jun 24 13:05:38 <hostName> systemd[1]: caperfcenter_eventmanager.service: Control process exited, code=exited, status=1/FAILURE
Jun 24 13:05:38 <hostName> systemd[1]: caperfcenter_eventmanager.service: Failed with result 'exit-code'.
Jun 24 13:05:38 <hostName> systemd[1]: Failed to start DX NetOps Portal EM.

Jun 24 13:05:38 <hostName> systemd[1]: Starting DX NetOps Portal  DM...
Jun 24 13:05:38 <hostName> caperfcenter_devicemanager[40693]: Starting DX NetOps Portal DM...
Jun 24 13:05:38 <hostName> caperfcenter_devicemanager[40693]: CEF:0|Broadcom|DX NetOps Portal DM|24.3.10|100|STARTING SERVICE|1|user=<nonRootUser>
Jun 24 13:05:38 <hostName> caperfcenter_devicemanager[40763]: /opt/CA/PerformanceCenter/DM/bin/caperfcenter_devicemanager: line 1941: /opt/CA/PerformanceCenter/DM/bin/PerfCenter-DM: Operation not permitted
Jun 24 13:05:53 <hostName> caperfcenter_devicemanager[40693]: Waiting for DX NetOps Portal DM..................
Jun 24 13:05:53 <hostName> caperfcenter_devicemanager[40693]: WARNING: DX NetOps Portal DM may have failed to start.
Jun 24 13:05:53 <hostName> caperfcenter_devicemanager[40801]: /opt/CA/PerformanceCenter/DM/bin/caperfcenter_devicemanager: line 1425: /opt/CA/PerformanceCenter/DM/bin/PerfCenter-DM: Operation not permitted
Jun 24 13:05:53 <hostName> systemd[1]: caperfcenter_devicemanager.service: Control process exited, code=exited, status=1/FAILURE
Jun 24 13:05:53 <hostName> systemd[1]: caperfcenter_devicemanager.service: Failed with result 'exit-code'.
Jun 24 13:05:53 <hostName> systemd[1]: Failed to start DX NetOps Portal  DM.

The console service fails as follows due to it's dependence on the DM service which failed to start.

Jun 24 12:35:40 <hostName> systemd[1]: Dependency failed for DX NetOps Portal Console.
Jun 24 12:35:40 <hostName> systemd[1]: caperfcenter_console.service: Job caperfcenter_console.service/start failed with result 'dependency'.
Jun 24 13:05:53 <hostName> systemd[1]: Dependency failed for DX NetOps Portal Console.
Jun 24 13:05:53 <hostName> systemd[1]: caperfcenter_console.service: Job caperfcenter_console.service/start failed with result 'dependency'.

 

Environment

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

Cause

Running "systemctl status fapolicyd" shows it running. Stopping this service allows the Portal web server services to start properly.

The fapolicyd system service was configured in a way that prevented the non root install owner from running the software services.

Resolution

Options to resolve this?

  • Shut down the fapolicyd service. Do not restart it.
  • Set the fapolicyd service to be masked or disabled so it's not usable and won't restart.
  • Configure it to allow the non root install owner to operate the software services.

Additional Information

Ensure the solution used meets your environments requirements. In this instance the solution implemented was adding this line to the fapolicyd configuration where the /opt/CA path represents the default install home. Set it to your home path if using a path different from the default.

  • allow perm=any all : dir=/opt/CA
Powered by Wolken Software