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) 的“name”字段使用静态分配,而不是地址解析。

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.