NetWorker:NetWorker 伺服器服務未出現「NetWorker 無法繼續其啟動順序」

Summary: NetWorker 伺服器軟體部署在 Red Hat Enterprise Linux Pacemaker (PCS) 叢集上。將 NetWorker 從 19.6.1.x (或更早版本) 升級至 19.7.0.0-19.7.0.3 或 19.8.0.0-19.8.0.1 後,NetWorker 伺服器服務不會啟動。

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.

Symptoms

NetWorker 伺服器部署在 Red Hat Enterprise Linux Pacemaker (PCS) 叢集上。

NetWorker 伺服器從 19.6.1.x (或更早版本) 升級到其中一個受影響的版本:

  • 19.7.0.0 至 19.7.0.3
  • 19.8.0.0 至 19.8.0.3
  • 19.9.0.0 至 19.9.0.1

升級後,NetWorker 伺服器服務不會啟動。

  • 作用節點的 /nsr_share/nsr/logs/daemon.raw
84419 MM/DD/YYYY HH:mm:SS AM  5 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR critical NetWorker is unable to continue its startup sequence due to a server hostname change to "CLUSTER_VIRTUAL_IP". Please verify that the server's hostname and its aliases are properly represented in the local host database (eg. /etc/hosts)and DNS.
78366 MM/DD/YYYY HH:mm:SS AM  1 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Beginning check of client attributes
78367 MM/DD/YYYY HH:mm:SS AM  1 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Finished check of client attributes
83273 MM/DD/YYYY HH:mm:SS AM  1 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Startup in process (step 3 of 5); checking resource types in the RAP database...
198264 MM/DD/YYYY HH:mm:SS AM  1 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Populating InactiveClientsCache.
198266 MM/DD/YYYY HH:mm:SS AM  1 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Populating InactiveClientsCache completed in 16 microseconds
202656 MM/DD/YYYY HH:mm:SS AM  1 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Populating DNS cache...
203404 MM/DD/YYYY HH:mm:SS AM  1 5 0 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Checking resource types in the RAP database...
95297 MM/DD/YYYY HH:mm:SS AM  5 3 17 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd RAP critical Error encountered while re-signing lockbox '/nsr/lockbox/CLUSTER_HOSTNAME_FQDN/clb.lb': The Lockbox file was not found.
88783 MM/DD/YYYY HH:mm:SS AM  2 3 17 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd RAP warningAttempt to allocate server storage node 'CLUSTER_HOSTNAME_FQDN' again.
199164 MM/DD/YYYY HH:mm:SS AM  1 5 0 3039790848 1735039 0 CLUSTER_NODE_HOSTNAME nsrd NSR notice Filling DNS cache with the active clients only.
95297 MM/DD/YYYY HH:mm:SS AM  5 3 17 3128739648 1735039 0 CLUSTER_NODE_HOSTNAME nsrd RAP critical Error encountered while re-signing lockbox '/nsr/lockbox/CLUSTER_VIRTUAL_IP/clb.lb': The Lockbox file was not found.

Cause

在受影響版本中套用的變更使 NetWorker 服務無法在 VIRTUAL_CLUSTER_IP 設定用於設定 NetWorker 的主機名稱。在服務啟動期間,服務會看到IP位址而不是主機名,從而導致與伺服器資源中的“name”值不匹配。它還會嘗試開啟 /nsr/lockbox 使用 IP,而非先前設定的完整網域名稱 (FQDN)。

root@NWrhelNode1:~# lcmap
type: NSR_CLU_TYPE;
clu_type: NSR_LC_TYPE;
interface version: 1.0;

type: NSR_CLU_VIRTHOST;
hostname: 192.1xx.xx.30;
local: TRUE;
owned paths: /nsr_share;

root@NWrhelNode1:~# nsradmin
NetWorker administration program.
Use the "help" command for help, "visual" for full-screen mode.
nsradmin> show name
nsradmin> p type: nsr
                        name: nwrhelclus.emclab.local;
nsradmin> q
root@NWrhelNode1:~# nslookup nwrhelclus.emclab.local
Server:         192.1xx.xx.2
Address:        192.1xx.xx.2#53

Name:   nwrhelclus.emclab.local
Address: 192.1xx.xx.30

加密箱和 NetWorker 伺服器資源 (NSR) 的「名稱」欄位會用於靜態指派,而非位址解析。

Resolution

此問題已在 NetWorker 19.8.0.4 中解決;但是,19.8 是截至 2025 年 11 月 11 日的支援壽命終止 (EOSL)。升級至 19.9.0.2 或更新版本以取得程式碼修正: https://www.dell.com/support/home/product-support/product/networker/drivers

 

請參閱:NetWorker:Red Hat Pacemaker 叢集如何升級 NetWorker 伺服器和最佳實務

 
注意:NetWorker 版本的支援終止日期會列在 NetWorker 產品頁面的概觀標籤中。
 

Additional Information

Products

NetWorker Family, NetWorker, NetWorker Series
Article Properties
Article Number: 000212566
Article Type: Solution
Last Modified: 04 Nov 2025
Version:  10
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.