Loading...
Loading...
xDoctor fails to run and quits after one second: admin@ecs1node1:~> sudo xdoctor --hr 2025-11-19 10:44:03,765: 5.1-106.1 - INFO : Adding Work - Job:1763549043 (P9) [* * * * * *] (--scope=SYSTEM --suite=default): From CLI 2025-11-19 10:44:03,766: 5.1-106.1 - INFO : Executing Job:1763549043 - session_1763549043.766 2025-11-19 10:44:03,798: 1763549043.766 - INFO : Initializing xDoctor v5.1-106.1 ... 2025-11-19 10:44:03,809: 1763549043.766 - INFO : xDoctor Composition - Full Diagnostic Suite for ECS 2025-11-19 10:44:03,814: 1763549043.766 - INFO : Starting xDoctor session_1763549043.766 ... (SYSTEM) 2025-11-19 10:44:03,814: 1763549043.766 - INFO : Primary Node Control Check ...Traceback (most recent call last): File "/opt/emc/xdoctor/lib/xdoctor/lib/cli.py", line 526, in __execute engine = Engine(session_id) ^^^^^^^^^^^^^^^^^^ File "/opt/emc/xdoctor/lib/xdoctor/core/engine.py", line 281, in __init__ if self.system.is_primary() == False: ^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/emc/xdoctor/lib/xdoctor/lib/system.py", line 799, in is_primary return self.config['hosts'][self.host]['state'].startswith('M') ~~~~~~~~~~~~~~~~~~~~~^^^^^^^^^^^ KeyError: '169.254.2.1'2025-11-19 10:44:04,106: 5.1-106.1 - ERROR : Failures in Job:1763549043 Exit Code:1 (Internal Failure) admin@ecs1node1:~>
xDoctor must be started from the control node. Usually this is the first node in the rack. If this error occurs, xDoctor is unable to determine the control node and stops running. This error can likely happen after a node expansion.
Contact Dell technical support for assistance by opening a service request and refer to this knowledge base article.
Click on a version to see all relevant bugs
Dell Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.