Unsolved
This post is more than 5 years old
77 Posts
0
6637
unable to connect to client push daemon
Hi Everyone,
I'm currently deploying a new Networker version in 9.1.1.1 Built 145, i have several issues right now that need attention and would like your advice if anyone saw this problem in their environnement.
I ran a test bench with version 9.1.0.2 and everything worked great at the level of the nsrpush daemon, unfortunatly, since i installed the newer version of Networker. I can't work with the nsrpush anymore, i'm allways getting the error message "unable to connect to client push daemon"
I got a reference about that problem, but it was for the case where the console is on another server, which is not my case.
Let me know if you have an idea, it would help a lot.
Thank you and have a nice day ahead,
Christian Carrier
bingo.1
2.4K Posts
0
July 19th, 2017 14:00
nsrcpd is a daemon on the NetWorker server which should be started when you need it.
Such will be the case once you start the software configuration wizard. So have a look whether it is running at all when you start the process. If not, have a look at the daemon.raw file to find out the troublemaker.
bingo.1
2.4K Posts
0
July 19th, 2017 17:00
In a separate cmd/telnet window, start the process manually with mire debug information (nsrcpd -D5).
This should show you more details.
It seems that there is an issue with the system itself if eben SYSTEM cannot start the nsrmmd process which I guess will be retried every 30s. So at least one device will not be accessible as well.
Worst case, try to reboot your host.
CarC8
77 Posts
0
July 19th, 2017 17:00
Hi bingo,
I looked to find the process nsrcpd, however, it is not running, i looked after trying to access NSRPUSH menu.
I then looked at the daemon.raw file, and notice, that NetWorker tries to start it, but can't for some reason. Here are the message i'm seeing in the log:
nsrcpd NSR info Starting nsrcpd 9.1.1.1.Build.145.Build.145
nsrd NSR critical unable to start nsrcpd
146682 2017-07-18 14:48:43 1 5 0 8148 10524 0
N.B: I'm seeing a lot of those errors in the log:
nsrmmd SYSTEM critical Failed to bind socket for RPC service: Operation not permitted
Thank you,
Chris
CarC8
77 Posts
0
July 20th, 2017 05:00
Hi Bingo,
I ran the command for starting the nsrcpd daemon and here's the result:
C:\Program Files\EMC NetWorker\nsr\logs>nsrcpd -D5
151893 1500552650 0 10 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR info 27 Starting nsrcpd %s.Build.%s 2 10 17 9.1.1.1.Build.145 10 3 145
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.703711 0 67 lgwstat: Failed to open file/directory: \
\?\C:\nsr\debug\nodelayeor
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.703711 0 56 Did not find NetWorker portmapper port, s
etting to 7938.
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.703711 0 45 Found system portmapper port, setting to
111.
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.719311 0 56 FIPS library path=C:\Program Files\EMC Ne
tWorker\nsr\bin
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.750512 0 53 Setting default RPC socket send buffer si
ze to 262144
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.750512 0 56 Setting default RPC socket receive buffer
size to 262144
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.766112 0 35 Auth methods not set, using default
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.766112 0 35 Auth methods not set, using default
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.766112 0 35 Auth methods not set, using default
0 1500552650 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:50.781712 0 35 Auth methods not set, using default
0 1500552651 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:51.078114 0 91 Setting DNS cache TTLs to 1800 secs for p
ositive lookups and 1800 secs for negative lookups
0 1500552651 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:51.078114 0 94 No access to file C:\Program Files\EMC Ne
tWorker\nsr\bin\lcmap.bat: No such file or directory
0 1500552651 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:51.093714 0 99 lgwstat: Failed to open file/directory: \
\?\C:\Program Files\EMC NetWorker\nsr\use_nsr_instance_dir
0 1500552651 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:51.093714 0 110 lgwstat: Failed to open file/directory:
\\?\C:\Program Files\EMC NetWorker\nsr\tmp\sec\tokens\.nsrlogin.XYZ
0 1500552651 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:51.124914 0 126 RPC Authentication: error in LookupAccou
ntSid: No mapping between account names and security IDs was done. (Win32 error 0x534)
0 1500552651 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:51.421316 0 33 lgto_auth for `nsrexec' succeeded
0 1500552652 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:52.045320 0 33 lgto_auth for `nsrexec' succeeded
0 1500552652 1 5 0 7940 10648 0 "BACKUP_SERVER" nsrcpd NSR notice 5 %s %s 2 0 24 07/20/17 08:10:52.482123 0 33 lgto_auth for `nsrexec' succeeded
Let me know if this can help in figuring out whats going on. I see some errors of file not found in the beginning of the log.
Thank you,
Chris
bingo.1
2.4K Posts
0
July 20th, 2017 06:00
The messages about missing directories might be ok - sometimes it is just checking and reports that they do not exist.
Once again, I do not see the primary issue with nsrcpd but with RPC.
This would also explain why nsrmmd processes will not come up as well.
On the other hand - if RPC is not working properly I would expect the NW server to fail in general.
TCP & RDP are absolute mandatory for NW to work.
bingo.1
2.4K Posts
0
July 27th, 2017 07:00
So it fails on the NW server itself (localhost = 127.0.0.1, port 7971). Make sure that you have not only your service ports but also your connection ports setup properly.
CarC8
77 Posts
0
July 27th, 2017 07:00
Hi Bingo,
On NetWorker server, this is the ourput of the nsrports command:
Service ports: 7937-7990
Connection ports: 0-0 (default, i never changed that)
Sould the connection port be something else ?
Thank you,
Chris
CarC8
77 Posts
0
July 27th, 2017 07:00
Hi Bingo,
We found out what was causing all those errors. The service ports range was way too restricted. I have opened more of them, and these error stopped.
Now, the service nsrcpd.exe is starting, but i'm getting a different error:
RPC send operation failed; peer = 127.0.0.1:7971, errno = An existing connection was forcibly closed by the remote host.
I'm getting this error, when i try to add something in the repository.
N.B: I'm allready working with support on this, but if anyone ever saw this, it would help to troubleshoot.
Thank you,
Chris
bingo.1
2.4K Posts
0
July 27th, 2017 10:00
'0-0' is fine. NetWorker-
wise.
Just be sure that nothing else will block these ports.
And that you have a 'localhost' entry in ..\etc\hosts
Reggie Hobbs
7 Posts
0
September 28th, 2018 13:00
Try This:
Unable to connect to client push daemon This error message appears when you click on the Software Inventory or Software Repository tabs on the Hosts window, and the NetWorker Server and NMC Server are on different hosts. To resolve this issue, provide the admin user on the NMC Server access to the NetWorker Server by typing the following command from a command prompt on the NetWorker Server:
nsraddadmin -u "user=username, host=NMC_server_hostname"