'pcs status' produces a traceback ending with error "UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 32: ordinal not in range(128)" in a RHEL 6 High Availability cluster

Solution In Progress - Updated -

Issue

  • after upgrading from pcs Version 0.9.148-7 to Version 0.9.155-2 we get error-like output from command "pcs status"
  • pcs status reports a traceback ending with an ASCII decode error
Daemon Status:
  cman: active/disabled
Traceback (most recent call last):
  File "/usr/sbin/pcs", line 9, in <module>
    load_entry_point('pcs==0.9.155', 'console_scripts', 'pcs')()
  File "/usr/lib/python2.6/site-packages/pcs/app.py", line 220, in main
    cmd_map[command](argv)
  File "/usr/lib/python2.6/site-packages/pcs/status.py", line 24, in status_cmd
    full_status()
  File "/usr/lib/python2.6/site-packages/pcs/status.py", line 109, in full_status
    utils.serviceStatus("  ")
  File "/usr/lib/python2.6/site-packages/pcs/utils.py", line 2142, in serviceStatus
    running = is_service_running(cmd_runner(), service)
  File "/usr/lib/python2.6/site-packages/pcs/lib/external.py", line 282, in is_service_running
    [_service, service, "status"]
  File "/usr/lib/python2.6/site-packages/pcs/lib/external.py", line 430, in run
    out_err=out_err
UnicodeDecodeError: 'ascii' codec can't decode byte 0xfc in position 32: ordinal not in range(128)

Environment

  • Red Hat Enterprise Linux (RHEL) 6 with the High Availability Add-On
  • pcs
    • Issue is suspected to affect all pcs releases, but it has been reported on pcs-0.9.155-2.el6
  • Issue is known to be possible on servers set with language settings that may use non-ASCII characters in service status output

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content