NetWorker: la risorsa nws sul cluster pacemaker RHEL non riesce ad avviare "nsrd NSR critical Can't start nsrd..."

Summary: NetWorker viene implementato in un cluster RedHat High Availability utilizzando pacemaker. Il servizio server NetWorker (nsrd) non riesce ad affermare che /nsr è locale e deve essere gestito da 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.
Check out other resources

Symptoms

  • Il file /nsr_share/nsr/logs/daemon.raw registra il seguente errore durante l'avvio del servizio:
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.
  • Il nodo può visualizzare le risorse del cluster con: 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;
  • L'output lcmap corrisponde alla configurazione delle risorse pcs: configurazione delle risorse pcs
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

L'indirizzo IP non risolve il nome utilizzato dalla configurazione del cluster NetWorker: 
root@NWrhelNodeF:~# nslookup 192.168.25.28
** server can't find 28.25.168.192.in-addr.arpa: NXDOMAIN
L'IP deve essere risolto nel valore NSR_SERVERHOST nel file /usr/lib/ocf/resource.d/EMC_NetWorker/Server: 
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
Questo valore viene impostato durante l'esecuzione dello script /usr/sbin/networker.cluster.

Resolution

Correggere la risoluzione dei nomi per il VIP. Ciò può essere corretto dall'amministratore di ACTIVE Directory nella configurazione DNS o utilizzando le voci di file /etc/hosts su ogni nodo coinvolto nel cluster. 
root@NWrhelNodeF:~# nslookup 192.168.25.28
28.25.168.192.in-addr.arpa      name = NWrhelClusD.emclab.local.

Una volta che il nome viene risolto correttamente, è possibile avviare i servizi NetWorker:

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

Se lcmap non restituisce il nome host o i valori del percorso di proprietà, consultare: 

Affected Products

NetWorker

Products

NetWorker Family, NetWorker Series
Article 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.