ECS:OBS: xDoctor:手動升級程序
Summary: 從命令列手動升級 xDoctor。
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Instructions
xDoctor 是一種支援和診斷工具,可識別並幫助解決可能對 ECS 和 OBS 系統產生負面影響的已知配置、軟體和硬體問題。重要功能包括:
- 故障診斷:協助支援團隊和客戶識別 ECS 問題的根本原因。
- 主動式監控:偵測問題的早期跡象
- 支援參與:某些動作和解決方案需要 Dell 的支持參與。
Dell 技術支援部門建議您對所有 VDC 機架進行最新的 xDoctor 執行狀況檢查。與每個版本一樣,xDoctor 的更新包含改良的執行狀況檢查和自動修復程式。在後來的 xDoctor 版本中引入了自動修復程式。
判斷安裝的 ECS/OBS 和 xDoctor 版本:
admin@node1:~> sudo xdoctor -x .................... ECS Version: 3.8.1.6 ----------------------- xDoctor Version: 4.8-104.0 -----------------------
判斷所有節點是否都具有相同的 xDoctor 版本:
admin@node1:~> sudo xdoctor -s
xDoctor Uniform on all nodes: 4.8-104.0
手動 xDoctor 升級:
- 根據上述 ECS/OBS 版本,下載最新版本的 xDoctor。請注意,下載 xDoctor 套件時,這取決於您在 ECS 和 OBS 中的代碼版本,並請記下以下檔案格式:
- 需要登入以下載最新版本:
- ECS (3.8 及以下版本):xDoctor 套件從 4.x 開始。(範例:4.8-105.0 - ECS 產品支援網頁
- OBS (3.9 及以上版本):xDoctor 套件從 5.x 開始 (例如:5.1-105.0) - OBS產品支援網頁
- 已下載版本的 xDoctor 版本資訊有升級 xDoctor 的專屬區段。
- 需要登入以下載最新版本:
- 上傳 最新的 xDoctor RPM 檔案至
/home/admin機架上某節點的目錄 - 以下範例涵蓋 ECS,請按照與 OBS 變更檔案名相同的步驟操作):
admin@node1~> ls -l | grep xDoctor
-rw-r--r-- 1 admin users 20057045 Jul 6 2025 xDoctor4ECS-4.8-104.0.noarch.rpm
-rw-r--r-- 1 admin users 31927626 Aug 26 15:11 xDoctor4ECS-4.8-105.0.noarch.rpm
- 執行 xDoctor 升級命令。可基於每個機架或每個 VDC 執行升級。
機架升級命令 - 輸入 A:
# sudo xdoctor --upgrade --local=/home/admin/xDoctor4ECS-4.8-105.0.noarch.rpm
admin@node1:~> sudo xdoctor --upgrade --local=/home/admin/xDoctor4ECS-4.8-105.0.noarch.rpm
This new xDoctor RPM has the following Auto Healers:
┌──────────────┐
│ Auto Healers │
└───┬──────────┘
│
│ time_zone = Enabled
│ pmon_crontab_check = Disabled
│ pmon_swapiness_check = Disabled
│ rsyslogd_check = Disabled
│ task_md_cleanup_status = Disabled
│ ntpd_not_running (New) = Disabled
│ cron_not_running (New) = Disabled
│ machines_file_error (New) = Disabled
│ non_uniform_psnt (New) = Disabled
│ racadm_stale_pid (New) = Disabled
│ obj_control_svc_check (New) = Disabled
In order to have them active, they need to be enabled ...
You can do this during this upgrade or later post upgrade via `xdoctor --config`
Would you like to enable (A)ll, only the (N)ew ones or (I)gnore them [I]: A
2025-10-09 11:36:15,663: xDoctor_4.8-104.0 - INFO : User selected to enable all Auto Healers ...
2025-10-09 11:36:15,663: xDoctor_4.8-104.0 - INFO : Local Upgrade (/home/admin/xDoctor4ECS-4.8-105.0.noarch.rpm)
2025-10-09 11:36:15,696: xDoctor_4.8-104.0 - INFO : Current Installed xDoctor version is 4.8-104.0
2025-10-09 11:36:15,712: xDoctor_4.8-104.0 - INFO : Requested package version is 4.8-105.0
2025-10-09 11:36:15,713: xDoctor_4.8-104.0 - INFO : Updating xDoctor RPM Package (RPM)
2025-10-09 11:36:15,935: xDoctor_4.8-104.0 - INFO : - Distribute package
2025-10-09 11:36:17,402: xDoctor_4.8-104.0 - INFO : - Install new rpm package
2025-10-09 11:36:33,562: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: pmon_crontab_check ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: pmon_swapiness_check ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: rsyslogd_check ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: task_md_cleanup_status ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: ntpd_not_running ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: cron_not_running ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: machines_file_error ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: non_uniform_psnt ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: racadm_stale_pid ...
2025-10-09 11:36:33,563: xDoctor_4.8-104.0 - INFO : Enabling Auto Healer: obj_control_svc_check ...
2025-10-09 11:36:33,828: xDoctor_4.8-104.0 - INFO : Auto Healer Settings saved and distributed ...
┌──────────────────────┐
│ Updated Auto Healers │
└───┬──────────────────┘
│
│ time_zone = Enabled
│ pmon_crontab_check = Enabled
│ pmon_swapiness_check = Enabled
│ rsyslogd_check = Enabled
│ task_md_cleanup_status = Enabled
│ ntpd_not_running (New) = Enabled
│ cron_not_running (New) = Enabled
│ machines_file_error (New) = Enabled
│ non_uniform_psnt (New) = Enabled
│ racadm_stale_pid (New) = Enabled
│ obj_control_svc_check (New) = Enabled
2025-10-09 11:36:33,829: xDoctor_4.8-104.0 - INFO : xDoctor successfully updated to version 4.8-105.0
VDC 升級命令 - 輸入 A:
# sudo xdoctor --upgrade --vdc-upgrade --local=/home/admin/xDoctor4ECS-4.8.105.0.noarch.rpm
xDoctor 在所有節點上並不統一:
如果節點在 xDoctor 更新期間重新安裝或處於離線狀態,其最終可能會得到與叢集其餘部分不同的版本:
admin@node1:~> sudo xdoctor -s xDoctor not uniform across all nodes ... Trying xDoctor Resync ... Resync failed: No xDoctor package found for re-installation [4.8-104.0] -> ['169.254.1.2'] [4.8-105.0] -> ['169.254.1.6', '169.254.1.5', '169.254.1.4', '169.254.1.3', '169.254.1.1']
xDoctor 輸出警示機架的所有節點不統一:
admin@node1:~> sudo xdoctor --report --archive=2022-06-26_101004 -WEC xDoctor 4.8.105.0 CKM00xxxxxxxx - ECS 3.8.1.2 Displaying xDoctor Report (2022-06-26_101004) Filter:['CRITICAL', 'ERROR', 'WARNING'] ... -------------------------------------------- ERROR - xDoctor not uniform across all nodes -------------------------------------------- Extra = Not allowed to use the SYSTEM scope, use LOCAL scope instead or reinstall xDoctor -> xdr_versions={'4.8-104.0': ['169.254.1.2'], '4.8-105.0': ['169.254.1.1', '169.254.1.6', '169.254.1.4', '169.254.1.3', '169.254.1.5']} RAP = RAP099 Solution = KB 91703 Timestamp = 2022-06-26_101004 PSNT = CKM00xxxxxxxx @ 4.8.105.0
嘗試 xDoctor 升級將會失敗,因為 xDoctor 偵測到其他節點具有您嘗試安裝的版本:
admin@node1:~> sudo xdoctor --upgrade --local=/home/admin/xDoctor4ECS-4.8.105.0.noarch.rpm 2022-06-28 15:11:40,101: xDoctor_4.8-105.0 - INFO : xDoctor Upgrader Instance (2:FTP_SFTP) 2022-06-28 15:11:40,101: xDoctor_4.8-105.0 - INFO : Local Upgrade (/home/admin/xDoctor4ECS-4.8-105.0.noarch.rpm) 2022-06-28 15:11:40,134: xDoctor_4.8-105.0 - INFO : Current Installed xDoctor version is 4.8-105.0 2022-06-28 15:11:40,174: xDoctor_4.8-105.0 - INFO : Requested package version is 4.8-105.0 2022-06-28 15:11:40,174: xDoctor_4.8-105.0 - INFO : xDoctor is up-to-date, only newer versions allowed ...
如果有最新版本的節點,但您想要在機架上重新套用相同的 xDoctor 版本,請使用 xDoctor 重新安裝選項:
admin@node1:~> sudo xdoctor --upgrade --local=/home/admin/xDoctor4ECS-4.8-105.0.noarch.rpm --reinstall
2022-06-28 15:12:53,079: xDoctor_4.8-105.0 - INFO : xDoctor Upgrader Instance (2:FTP_SFTP)
2022-06-28 15:12:53,079: xDoctor_4.8-105.0 - INFO : Local Upgrade (/home/admin/xDoctor4ECS-4.8-105.0.noarch.rpm)
2022-06-28 15:12:53,112: xDoctor_4.8-105.0 - INFO : Current Installed xDoctor version is 4.8-105.0
2022-06-28 15:12:53,147: xDoctor_4.8-105.0 - INFO : Requested package version is 4.8-105.0
2022-06-28 15:12:53,148: xDoctor_4.8-105.0 - WARNING : (Re)installing requested xDoctor package ...
2022-06-28 15:12:53,148: xDoctor_4.8-105.0 - INFO : Updating xDoctor RPM Package (RPM)
2022-06-28 15:12:53,244: xDoctor_4.8-105.0 - INFO : - Distribute package
2022-06-28 15:12:54,115: xDoctor_4.8-105.0 - INFO : - Install new rpm package
2022-06-28 15:13:08,544: xDoctor_4.8-105.0 - INFO : xDoctor successfully updated to version 4.8-105.0
2020-09-01 09:04:30,184: xDoctor_4.8-105.0 - INFO : xDoctor Activation skipped. Only tested on Rack Master
判斷是否所有節點現在都具有相同的 xDoctor 版本:
admin@node1:~> sudo xdoctor -s
xDoctor Uniform on all nodes: 4.8-105.0.
重新檢查 xDoctor 版本:
admin@node1:~> sudo xdoctor -x ........ ECS Version: 3.8.1.6 ----------------------- xDoctor Version: 4.8-105.0 -----------------------
判斷所有節點是否都具有相同的 xDoctor 版本:
admin@node1:~> sudo xdoctor -s
xDoctor Uniform on all nodes: 4.8-105.0
執行 xDoctor 執行狀況檢查:
若要執行 xDoctor 執行狀況檢查,請先清除快取,然後執行 xDoctor:
admin@node1:~> sudo xdoctor --clear You are about to clear all xDoctor Cache files. Are you sure you want to proceed? [No]: yes 2020-09-07 14:03:34,263: xDoctor_4.8-105.0- INFO : xDoctor Cache files successfully cleared.
若要執行 xDoctor 執行狀況檢查:
admin@node1:~> sudo xdoctor --hr
可使用
xDoctor 從單個節點作為主節點運行,並將其他節點的 xDoctor 報告一起提取到該節點上。因此,請在該節點上執行 xDoctor,預設為機架上的第一個節點。如果節點未回應 VDC,下一個節點將成為 “主節點” ,即節點 2。請參閱上述 xDoctor 升級中的「已略過 xDoctor 啟用」, 僅在主要節點上作用中。
xDoctor 執行結束時,xDoctor 會產生工作階段報告,「警告」、「錯誤」或「嚴重」是 xDoctor 報告中要檢查的項目:
--hr 選項會嘗試傳送 ECS 支援最新的 xDoctor 執行狀況檢查報告,因為連線可能遭到封鎖。
xDoctor 從單個節點作為主節點運行,並將其他節點的 xDoctor 報告一起提取到該節點上。因此,請在該節點上執行 xDoctor,預設為機架上的第一個節點。如果節點未回應 VDC,下一個節點將成為 “主節點” ,即節點 2。請參閱上述 xDoctor 升級中的「已略過 xDoctor 啟用」, 僅在主要節點上作用中。
xDoctor 執行結束時,xDoctor 會產生工作階段報告,「警告」、「錯誤」或「嚴重」是 xDoctor 報告中要檢查的項目:
admin@node1:~> sudo xdoctor --hr .................... 2020-09-07 13:58:33,520: xDoctor_4.8-105.0 - INFO : PSNT: CKM00xxxxxxxxxx 2020-09-07 13:58:33,520: xDoctor_4.8-105.0 - INFO : -------------------- 2020-09-07 13:58:33,520: xDoctor_4.8-105.0 - INFO : Number of CRITICAL: 0 2020-09-07 13:58:33,520: xDoctor_4.8-105.0 - INFO : Number of FIXED: 0 2020-09-07 13:58:33,520: xDoctor_4.8-105.0 - INFO : Number of ERROR: 0 2020-09-07 13:58:33,520: xDoctor_4.8-105.0 - INFO : Number of WARNING: 1 .................... .................... 2020-09-07 13:58:42,910: xDoctor_4.8-105.0 - INFO : -------------------------- 2020-09-07 13:58:42,910: xDoctor_4.8-105.0 - INFO : Session Report - xdoctor --report --archive=2020-09-07_135109
若要查看 xDoctor 報告:
sudo xdoctor --report --archive=2022-xxxxxxxxxxxxx -WEC
範例:
admin@node1:~> sudo xdoctor --report --archive=2XXX-0X-01_0XXXX9 -WEC xDoctor 4.8-105.0 CKM00xxxxxxxxx - ECS 3.8 Patch 2 (??) - 3.8.0.2 Displaying xDoctor Report (2XX0-0X-01_0XXXX9) Filter:['CRITICAL', 'ERROR', 'WARNING'] ... Timestamp = 2XX0-0X-01_0XXXX9 Category = Health Source = Disk Severity = ERROR Node = 169.254.1.1 Message = Boot device is not accessible Extra = {'1XX.2XX.X.5': ['/dev/sdl']} RAP = RAP004 Solution = 46306
結果可能會產生建議行動計劃 (RAP) 代碼。這些對於搜索可能與警報代碼相關的連結知識文章非常有用。
Affected Products
ECS ApplianceProducts
ECS Appliance, ECS Appliance Hardware Gen1 U-Series, ECS Appliance Software with Encryption, ECS Appliance Software without EncryptionArticle Properties
Article Number: 000021704
Article Type: How To
Last Modified: 07 نوفمبر 2025
Version: 14
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.