How to use vxpbxserviceusercmd(Unix) and pbxserviceusercmd(Windows) CLI for switching to/from service user for Private Branch Exchange.
Description
Everything you need to know about switching Private Branch Exchange (PBX) service to/from service user.
This article also contains troubleshooting steps if you fall into issues regarding switching to/from service user and also contains solution for the same.
Command Usage for all platforms:
Windows:
Command Usage:
[VERITAS PBX INSTALLDIR]\bin\pbxserviceusercmd.bat LocalService | LocalSystem
Note :
Before running this command make sure VRTSpbx service is stopped, you can stop the service using the command sc stop VRTSpbx and start the service later using the command sc start VRTSpbx
Non Windows:
Command Usage:
/opt/VRTSpbx/bin/vxpbxserviceusercmd <username>
Note :
1. username - Can be a root or it should be same non-root user as configured for NetBackup.
2. Before running this command make sure pbx_exchange process is not running, you can stop the daemon using the command /opt/VRTSpbx/bin/vxpbx_exchanged stop and start the daemons later using the command /opt/VRTSpbx/bin/vxpbx_exchanged start
Troubleshooting:
- While running nbserviceusercmd CLI if we get following warning:
Windows :
WARNING: pbx_exchange process needs to be stopped. Skipping the service user configuration for now.
You can do the configuration later using the command: pbxserviceusercmd.bat.
Non Windows :
WARNING: pbx_exchange process needs to be stopped. Skipping the service user configuration for now.
You can do the configuration later using the command: vxpbxserviceusercmd.
For changing service user configuration, stop the PBX exchange service\daemon using following steps :
Windows:
sc stop VRTSpbx
[VERITAS PBX INSTALLDIR]\bin\pbxserviceusercmd.bat LocalService | LocalSystem
Non Windows:
/opt/VRTSpbx/bin/vxpbx_exchanged stop
/opt/VRTSpbx/bin/vxpbxserviceusercmd <username>
2. For Non Windows, if you get "ACL is not supported on the system. PBX exchange will be run with the root user permissions.
" error while running vxpbxserviceusercmd CLI:
Try to check ACL functionality by running ACL commands (e.g. setfacl, getfacl on file present in /var) on the system, Check if RPM for ACL functionality is missing or disabled on file system level.
If the RPM for ACL functionalities are missing then install ACL RPM on the system, in case RPM are present then enable the ACL support for the file system.