Unsolved
This post is more than 5 years old
38 Posts
0
2439
November 18th, 2011 07:00
Bizarre socket issue during non-directed recover
Hello,
I do a directed recover
recover -s server -c client
and get the following:
Success.
I use Networker User and get
nsrexec: Cannot bind socket to port in service port range on system : The requested address is not valid in its context.
6906:nsrexec: Network connection could not be established with client ' '
Fail.
I use the command:
recover -iR -s -R -c -iR -a C:\Windows\win.ini
and get
Initiating remote recover to from server , this may take a while...
67095:recover: Failed to execute directed recover: Remote process exited with errors
Fail.
Obviously, recovery works in the first case. The recover command above works with some systems, others it doesn't... no pattern seen there yet.
Surprised to get the complaint about Networker User.
And what else do those darn error codes tell me? (67095,6906)
0 events found
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
November 18th, 2011 09:00
ok, so you run this on target.... I guess something is strange there... I might try tomorrow if I catch time as I never used other two approaches (nor I plan to).
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
November 18th, 2011 09:00
I usually always use first method... but, on which host did you execute 2 other which have failed? Target host or some admin host?
cvs500
38 Posts
0
November 18th, 2011 09:00
Everything was repeated to show how weird the failure was. Same client, same server.
Does that answer your question regarding target?
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
November 22nd, 2011 07:00
Here I'm... got delayed by bizzare issue (running boinc 24/7 for past 6 months and keeping 8 cores at 100% resulted in sudden death of power supply... where is this world going to...).
Test 1 - what works
$HOST2 C:\>recover -s $SERVER -c $HOST1
Current working directory is C:\
recover> add boot
1 file(s) marked for recovery
recover> relocate C:\restore
recover> recover
Recovering 1 file from C:\ into C:\restore
Volumes needed (all near-line):
TC200082 at TC2
Requesting 1 file(s), this may take a while...
Requesting 1 recover session(s) from server
C:\restore\Boot\
Received 1 file(s) from NSR server `$SERVER'
Recover completion time: 22-11-2011 15:51:12
recover> q
Test 2: Winblows GUI
That works too.
Test 3: CLI
$HOST2 C:\>recover -s $SERVER -R $HOST2 -c $HOST1 -iR -d C:\restore3 -a C:\Boot
Initiating remote recover to $HOST2 from server $SERVER, this may take a while...
Recovering 1 file from C:\ into C:\restore3
Requesting 1 file(s), this may take a while...
Requesting 1 recover session(s) from server
C:\restore3\Boot\
Received 1 file(s) from NSR server `$SERVER'
Recover completion time: 22-11-2011 16:03:37
Not sure why it fails in your case, but it looks as it had some sort of problems accessing defined port range.