NetWorker: nws resource on RHEL pacemaker cluster fails to start "nsrd NSR critical Can't start nsrd..." (NSrd NSR-kritisk kan ikke starte nsrd...)
Summary: NetWorker implementeres på en RedHat High Availability-klynge ved hjelp av pacemaker. NetWorker-servertjenesten (nsrd) kan ikke begynne å si at /nsr er lokal og må administreres av Cluster Manager. ...
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
- Loggene /nsr_share/nsr/logs/daemon.raw logger følgende feil under oppstart av tjenesten:
73248 01/31/2023 12:57:48 PM 5 5 0 926312256 966299 0 nwrhelnodef.emclab.local nsrd NSR critical Can't start nsrd because /nsr/res (/nsr) is local, and NetWorker is configured as a cluster server. Use cluster manager to check NetWorker service status.
144354 01/31/2023 12:57:48 PM 1 5 0 130900160 963225 0 nwrhelnodef.emclab.local nsrctld NSR notice Daemon nsrd terminated.
- Noden kan se klyngeressursene med: lcmap
root@NWrhelNodeF:~# lcmap
type: NSR_CLU_TYPE;
clu_type: NSR_LC_TYPE;
interface version: 1.0;
type: NSR_CLU_VIRTHOST;
hostname: 192.168.25.28;
local: FALSE;
owned paths: /nsr_share;
- Lcmap-utdataene samsvarer med pc-ens ressurskonfigurasjon: ressurskonfigurasjon for PC-er
root@NWrhelNodeF:~# pcs resource config Group: NW_group Resource: fs (class=ocf provider=heartbeat type=Filesystem) Attributes: device=/dev/sdb1 directory=/nsr_share fstype=ext4 Operations: monitor interval=20 timeout=300 (fs-monitor-interval-20) start interval=0s timeout=60s (fs-start-interval-0s) stop interval=0s timeout=60s (fs-stop-interval-0s) Resource: ip (class=ocf provider=heartbeat type=IPaddr) Attributes: cidr_netmask=24 ip=192.168.25.28 nic=ens192 Operations: monitor interval=15 timeout=120 (ip-monitor-interval-15) start interval=0s timeout=20s (ip-start-interval-0s) stop interval=0s timeout=20s (ip-stop-interval-0s) Resource: nws (class=ocf provider=EMC_NetWorker type=Server) Meta Attrs: is-managed=true Operations: meta-data interval=0 timeout=10 (nws-meta-data-interval-0) migrate_from interval=0 timeout=120 (nws-migrate_from-interval-0) migrate_to interval=0 timeout=60 (nws-migrate_to-interval-0) monitor interval=100 timeout=1000 (nws-monitor-interval-100) start interval=0 timeout=300 (nws-start-interval-0) stop interval=0 timeout=300 (nws-stop-interval-0)
Cause
IP-adressen løser ikke navnet som brukes av NetWorker-klyngekonfigurasjonen:
root@NWrhelNodeF:~# nslookup 192.168.25.28
** server can't find 28.25.168.192.in-addr.arpa: NXDOMAIN
IP-en skal løse problemet med NSR_SERVERHOST verdien i /usr/lib/ocf/resource.d/EMC_NetWorker/Server-filen:
root@NWrhelNodeF:~# cat /usr/lib/ocf/resource.d/EMC_NetWorker/Server | grep SERVERHOST
echo "q" | nsradmin -s ${NSR_SERVERHOST} -i - > /dev/null 2>&1
echo "q" | nsradmin -s ${NSR_SERVERHOST} -i - > /dev/null 2>&1
NSR_SERVERHOST=NWrhelClusD.emclab.local
Denne verdien angis når du kjører skriptet /usr/sbin/networker.cluster.Resolution
Løs navneløsing for VIP. Dette kan korrigeres av AD-administrator i DNS-konfigurasjon eller ved hjelp av /etc/hosts-filoppføringer på hver node som er involvert i klyngen.
root@NWrhelNodeF:~# nslookup 192.168.25.28
28.25.168.192.in-addr.arpa name = NWrhelClusD.emclab.local.
Når navnet løses på riktig måte, kan NetWorker-tjenester startes:
root@NWrhelNodeF:~# pcs resource cleanup nws
Cleaned up fs on NWrhelNodeF.emclab.local
Cleaned up fs on NWrhelNodeE.emclab.local
Cleaned up ip on NWrhelNodeF.emclab.local
Cleaned up ip on NWrhelNodeE.emclab.local
Cleaned up nws on NWrhelNodeF.emclab.local
Cleaned up nws on NWrhelNodeE.emclab.local
root@NWrhelNodeF:~# pcs resource
* Resource Group: NW_group:
* fs (ocf::heartbeat:Filesystem): Started NWrhelNodeF.emclab.local
* ip (ocf::heartbeat:IPaddr): Started NWrhelNodeF.emclab.local
* nws (ocf::EMC_NetWorker:Server): Started NWrhelNodeF.emclab.local
Additional Information
Hvis lcmap ikke returnerer vertsnavnet eller de eide baneverdiene, kan du se:
Affected Products
NetWorkerProducts
NetWorker Family, NetWorker SeriesArticle Properties
Article Number: 000208093
Article Type: Solution
Last Modified: 30 Apr 2025
Version: 5
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.