pcs status fails with ERROR RUN_EXTERNAL_PROCESS_ERROR: {'reason': 'No such file or directory', 'command': 'crm_mon --one-shot --inactive'}

Solution Verified - Updated -


  • pcs status fails if /usr/sbin is not part of the PATH environment variable.
  • pcs commands fail when run as cron jobs.
  • Non-root user cannot execute pcs status without setting root environment. pcs cluster status works fine.
[testuser1@fastvm-rhel-7-5-22 ~]$ su -c '/usr/sbin/pcs status'
Traceback (most recent call last):
  File "/sbin/pcs", line 9, in <module>
    load_entry_point('pcs==0.9.165', 'console_scripts', 'pcs')()
  File "/usr/lib/python2.7/site-packages/pcs/app.py", line 212, in main
  File "/usr/lib/python2.7/site-packages/pcs/app.py", line 176, in <lambda>
  File "/usr/lib/python2.7/site-packages/pcs/status.py", line 28, in status_cmd
  File "/usr/lib/python2.7/site-packages/pcs/status.py", line 74, in full_status
    stdout, stderr, retval = utils.cmd_runner().run(monitor_command)
  File "/usr/lib/python2.7/site-packages/pcs/lib/external.py", line 428, in run
    reports.run_external_process_error(log_args, e.strerror)
pcs.lib.errors.LibraryError: ERROR RUN_EXTERNAL_PROCESS_ERROR: {'reason': 'No such file or directory', 'command': 'crm_mon --one-shot --inactive'} forceable: None


  • Red Hat Enterprise Linux (RHEL) 7, 8 with the High Availability Add-on
  • pcs-0.9.165-6.el7 or newer

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase of over 48,000 articles and solutions.

Current Customers and Partners

Log in for full access

Log In