What you did so far is correct. It seems as if there is a problem with the authentication db (/nsr/res/nsrladb).

  - Stop the daemons (/etc/init.d/networker stop   or   nsr_shutdown)

  - Rename the directory

  - Restart the daemons

Unfortunately it didn't help. Nsrd still won't start.

Hmmm ... look which daemons have really been started. (ps -ef | grep nsr)

Your first message made me think that there is an issue with the client.

However, if there is an nsrexecd process then the server is failing to start (nsrd). This is due to either a corrupt res file or/and the media index.

As it is a new install ...

  - Make sure all nsr daemons have been stopped. If necessary, kill them

  - Delete

        /nsr/res/

        /nsr/mm/

        /nsr/index/

        /nsr/logs/

        /nsr/tmp/

  - Now start NW again.

Verify which NW daemons are running.

Only nsrexecd was started.

I removed the directories you listed from /nsr and started Networker again, however only nsrexecd is running. When I then tried to start nsrd manually, the same error as above (daemon credentials) happened.

The same result:

[root@localhost to]# /usr/sbin/nsrexecd

[root@localhost to]# ps -ef | grep nsrexecd

root    25361    1  1 09:26 ?        00:00:00 /usr/sbin/nsrexecd

root    25371 24550  0 09:27 pts/1    00:00:00 grep --color=auto nsrexecd

[root@localhost linux_x86_64]# /usr/sbin/nsrd -D1

0 1455632858 1 5 0 792016704 25426 0 localhost nsrd NSR notice 5 %s %s 2 0 24 02/16/16 09:27:38.191963 0 27 Shutdown_delay_interval: 10

83271 1455632858 1 5 0 792016704 25426 0 localhost nsrd NSR notice 76 Startup in process (step %d of %d); opening NetWorker server RAP database... 2 1 1 1 1 1 5

83272 1455632858 1 5 0 792016704 25426 0 localhost nsrd NSR notice 64 Startup in process (step %d of %d); initializing RAP handlers... 2 1 1 2 1 1 5

71193 1455632858 0 0 0 792016704 25426 0 localhost nsrd NSR info 9 %s %s: %s 3 11 11 2646:Server 11 12 19362:Notice 49 14 7324 7 started

88940 1455632858 5 5 0 792016704 25426 0 localhost nsrd NSR critical 61 %s: Cannot get server credentials from authentication daemon. 1 0 10 GSS Legato

12546 1455632858 1 5 0 792016704 25426 0 localhost nsrd NSR notice 13 shutting down 0

0 1455632858 1 5 0 792016704 25426 0 localhost nsrd NSR notice 5 %s %s 2 0 24 02/16/16 09:27:38.388915 0 225 An unexpected error occured in file: rpc/lib/gssglue.c, line: 159, message = "Daemon credential was not properly acquired at startup.  gsslgtov1 authentication is disabled.  Please call get_gss_server_cred at daemon startup."

Can you run nsrexecd in one ssh session. once that is running open another ssh session and run nsrd manually? Share the output here. I know you have done this earlier but i assume at that moment the nsrd was already trying to come up but failed.

At this point I do not know anything else but to

  - Deinstall NW

  - Remove /nsr completely

  - Reinstall NW

The same behavior as before.

Maybe I should try on Centos 6?

I don't think so. I have successfully installed NW 8.2.2 on Centos 7.

Please see the Compatibility Guide to verify your configuration.

Do not forget

  - beware of dependencies - let Centos install missing packages

  - Disable the firewall (for test purposes only)

I'm using Virtualbox - maybe that's the problem?

Compatibility Guide requires kernel 2.6 - I assume that means also all higher versions (for example 3.10)?

I installed ksh, glibc.i686, nss-softokn-freebl.i686 and compat-libstdc++-33 manually. I assumed yum would install any missing dependencies?

I stopped firewalld, but it didn't help.

I noticed that I skipped SELinux configuration step because I assumed it won't be enabled if I don't do it manually. However it seems CentOS enables it by default. I executed commands from installation guide ('semanage fcontext -a -t textrel_shlib_t "/usr/lib/nsr/lib.*\.so' and 'restorecon -R /usr/lib/nsr', but only after installing Networker).