ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.
Service Manager : ucybsmcl unable to stop a Process started from a different user
Article ID: 187659
Updated On:
Products
CA Automic Workload Automation - Automation Engine
Issue/Introduction
The service manager command (ucybsmcl) cannot stop a process which has been started with a different user.
For example, if a customer user (e.g awaadmin) is the owner of the ucybsmcl script and the process (JWP, JCP, or any other) has been started by root, ucybsmcl "stop" won't work.
For example, if a customer user (e.g awaadmin) is the owner of the ucybsmcl script and the process (JWP, JCP, or any other) has been started by root, ucybsmcl "stop" won't work.
The corresponding process need to be killed using the root user.
Cause
Different owner between the Service Manager scripts and the Automation Engine process.
Environment
Service Manager (all versions)
Resolution
The Service Manager must be installed & started with the same account.
Every WP/CP processes must also be started using this account.
Additional Information
-
Feedback
Yes
No
Powered by
