NetWorker client does not start in a cloned virtual machine if a cloned machine has a different hostname.
SYMPTOMPS

NetWorker client works fine on an original virtual machine, but it does not start on a cloned one.

## Original VM 

root@original.net: service networker start
root@original.net: ps -fe |grep nsr
root     27102     1  0 Jan26 ?        00:00:24 /usr/sbin/nsrexecd
root     28597 28565  0 12:31 pts/0    00:00:00 grep nsr

## Cloned VM 

root@cloned.net: service networker start
root@cloned.net: ps -fe |grep nsr
root     23949 17304  0 15:22 pts/4    00:00:00 grep nsr

Both virtual machines have the same number of installed NetWorker client packages. Re-installation of NetWorker client packages does not fix the problem.

root@cloned.net: uname -ri
2.6.39-400.297.3.el5uek x86_64

root@cloned.net: rpm -qa --queryformat '%{NAME}-%{VERSION}-%{RELEASE} %{ARCH}\n'  |grep lgto
lgtoclnt-8.2.3.5-1 x86_64
lgtoman-8.2.3.5-1 x86_64
lgtonmda-8.2.3.0-1 x86_64

Executing the nsrexecd in a debug mode identified a problem related to the virtual machine hostname.

## Start nsrexecd in a debug mode
https://dbpilot.net/wp-admin/edit.php
root@cloned.net: export LD_LIBRARY_PATH=/usr/lib/nsr/lib64/cst:/usr/lib/nsr/lib64
root@cloned.net: nsrexecd -D9

...

Attributes '%s' and/or '%s' of the %s resource do not resolve to the machine's hostname '%s'. 
To correct the error, it may be necessary to delete the %s database.

...

The same debug information is found in the daemon.raw log

root@cloned.net: tail -8 /nsr/logs/daemon.raw

0 1516 1 5 0 328705776 9097 0 cloned.net nsrexecd NSR notice 2 %s 1 0 29 @(#) Build info:   DBG=0,OPT=
138906 1516 5 3 20 2488 9501 0 cloned.net nsrexecd RAP critical 162 Attributes '%s' and/or '%s' of the %s resource 
do not resolve to the machine's hostname '%s'. To correct the error, it may be necessary to delete the %s database.
 5 11 9 2335:name 11 17 51954:my hostname 11 11 89897:NSRLA 12 24 cloned.net 11 11 89897:NSRLA
0 1516 1 5 0 2488 9501 0 cloned.net nsrexecd NSR notice 2 %s 1 0 28 @(#) Product:      NetWorker
0 1516 1 5 0 2488 9501 0 cloned.net nsrexecd NSR notice 2 %s 1 0 37 @(#) Release:      8.2.3.5.Build.1142
0 1516 1 5 0 2488 9501 0 cloned.net nsrexecd NSR notice 2 %s 1 0 23 @(#) Build number: 1142
0 1516 1 5 0 2488 9501 0 cloned.net nsrexecd NSR notice 2 %s 1 0 47 @(#) Build date:   Thu Aug  4 00:58:05 PDT 2016
0 1516 1 5 0 2488 9501 0 cloned.net nsrexecd NSR notice 2 %s 1 0 27 @(#) Build arch.:  linux86w
0 1516 1 5 0 2488 9501 0 cloned.net nsrexecd NSR notice 2 %s 1 0 29 @(#) Build info:   DBG=0,OPT=

The hostname of cloned virtual machine resolves successfully.

root@cloned.net: cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1       localhost.localdomain   localhost
::1             localhost.localdomain   localhost

root@cloned.net: nslookup cloned.net
Server:         10.1.1.50
Address:        10.1.1.50#53

Name:   cloned.net
Address: 10.1.1.20

root@cloned.net: nslookup 10.1.1.20
Server:         10.1.1.50
Address:        10.1.1.50#53

20.1.1.10.in-addr.arpa  name = cloned.net.
SOLUTION

Recreate the /nsr directory

root@cloned.net: mv /nsr/ /nsr.orig.26JAN2018
root@cloned.net: mkdir /nsr

Now NetWorker client should start up successfully

root@cloned.net: ps -fe |grep nsr
root     30565 30338  0 12:52 pts/2    00:00:00 grep nsr

root@cloned.net: service networker start

root@cloned.net: ps -fe |grep nsr
root     30578     1  2 12:52 ?        00:00:00 /usr/sbin/nsrexecd
root     30611 30338  0 12:52 pts/2    00:00:00 grep nsr

Written At
29 JAN 201814:00
OEL Release
5.11 x64
NetWorker Client
8.2.3.5