Welcome Guest! To enable all features please Login or Register.

Notification

Icon
Error
NCrunch Grid Node cannot connect
Options
Previous Topic Next Topic
Dirk Maegh
#1 Posted : Friday, October 21, 2022 1:16:38 PM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/30/2016(UTC)
Posts: 55
Location: Belgium

Thanks: 8 times
Was thanked: 8 time(s) in 8 post(s)
Hi,

yesterday I re-installed a laptop from scratch, so a plain Windows 10 with a few automatic updates. (no programs installed, no personal tweaks, just a wifi connection)
Then I installed NCrunch Grid Node on it.

My desktop has Windows 11, VS2022 and NCrunch, all at their latest versions, latest updates.
They are on the same private network.

When I ping the laptop by name, my desktop finds its IP address, but the ping itself fails.
When NCrunch tries to Connect to the grid node, it fails.

I found in the firewall an inbound rule that the grid node server added during installation, allowing all ports, all computers - so I think that should be fine for my first try out.

I turned on the Grid node logging. (removed my initial two numbers from the ip address)

I found just one error, but I do not really understand it:

Quote:
The requested address is not valid in its context.


Quote:

[PID:8516 14:48:11.2249 ?-4] Loading internal NCrunch modules
[PID:8516 14:48:11.2409 ?-4] Loading module: AspNetMvcTestHostModule
[PID:8516 14:48:11.2409 ?-4] Registering 1 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: AzureFunctionsModule
[PID:8516 14:48:11.2409 ?-4] Registering 1 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: CodeAnalysisModule
[PID:8516 14:48:11.2409 ?-4] Registering 2 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: CodeContractsModule
[PID:8516 14:48:11.2409 ?-4] Registering 2 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: MSFakesModule
[PID:8516 14:48:11.2409 ?-4] Registering 1 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: MvcBuildModule
[PID:8516 14:48:11.2409 ?-4] Registering 1 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: PostSharpModule
[PID:8516 14:48:11.2409 ?-4] Registering 1 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: SpecFlowModule
[PID:8516 14:48:11.2409 ?-4] Registering 1 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading module: StyleCopModule
[PID:8516 14:48:11.2409 ?-4] Registering 1 extension(s)
[PID:8516 14:48:11.2409 ?-4] Loading external NCrunch modules
[PID:8516 14:48:11.2409 ?-4] Module Search paths:
C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server
[PID:8516 14:48:11.2569 ?-4] Loading module: C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\Modules\Gallio\nCrunch.Module.Gallio.crunchmodule
[PID:8516 14:48:11.3349 ?-4] Registering 3 extension(s)
[PID:8516 14:48:11.3349 ?-4] Loading module: C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\Modules\MSpec\nCrunch.Module.MSpec.crunchmodule
[PID:8516 14:48:11.3349 ?-4] Registering 3 extension(s)
[PID:8516 14:48:11.3349 ?-4] Loading module: C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\Modules\MSTest\nCrunch.Module.MSTest.crunchmodule
[PID:8516 14:48:11.3349 ?-4] Registering 4 extension(s)
[PID:8516 14:48:11.3349 ?-4] Loading module: C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\Modules\NUnit\nCrunch.Module.NUnit.crunchmodule
[PID:8516 14:48:11.3499 ?-4] Registering 3 extension(s)
[PID:8516 14:48:11.3499 ?-4] Loading module: C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\Modules\NUnit3\nCrunch.Module.NUnit3.crunchmodule
[PID:8516 14:48:11.3499 ?-4] Registering 4 extension(s)
[PID:8516 14:48:11.3499 ?-4] Loading module: C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\Modules\XUnit2\nCrunch.Module.XUnit2.crunchmodule
[PID:8516 14:48:11.3659 ?-4] Registering 3 extension(s)
[PID:8516 14:48:11.4289 ?-4] Successfully loaded file hash cache with 2894 entries
[PID:8516 14:48:11.4289 ?-4] Ensuring Gallio plug-in cache is clear
[PID:8516 14:48:11.4289 HashCacheVerifier-11] Verifying loaded cache of 2894 hashes
[PID:8516 14:48:11.4289 ?-5] Tracking activity "Initialising node: Indexing existing stored snapshot data" for #global:0
[PID:8516 14:48:11.4439 ?-5] Activity "Initialising node: Indexing existing stored snapshot data" has been marked with progress: 0%
[PID:8516 14:48:11.4439 ?-5] Analysing and storing existing snapshot at C:\NCrunch Grid Node\Snapshots\1
[PID:8516 14:48:11.4749 ?-5] Activity "Initialising node: Indexing existing stored snapshot data" has been marked with progress: 10%
[PID:8516 14:48:11.4749 ?-5] Stopping tracking of activity "Initialising node: Indexing existing stored snapshot data" for #global:0
[PID:8516 14:48:11.4749 ?-5] Tracking activity "Initialising node: Calculating disk space in use" for #global:0
[PID:8516 14:48:11.4749 ?-5] Activity "Initialising node: Calculating disk space in use" has been marked with progress: 0%
[PID:8516 14:48:11.4749 ?-4] Adding external process with Id 'b1285b1a506845409c77321ee2f645ec'
[PID:8516 14:48:11.4749 ?-4] Starting external process '"C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\nCrunch.TaskRunner40.x64.exe"' with arguments '8516 nCrunch_faced578cf494022981b74713914d364 b1285b1a506845409c77321ee2f645ec "C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\nCrunch.Core.DLL" nCrunch.Core.TestManagement.FrameworkDescriptionResolver "C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server" "False" ""'
[PID:8516 14:48:11.5069 ?-4] Process ID '7288' initialised
[PID:8516 14:48:11.5069 ?-4] Connecting to external process 'b1285b1a506845409c77321ee2f645ec' with id 7288
[PID:8516 14:48:11.6469 ProcessOutputRedirectionStd-14] Process 7288: Initialising application domain
[PID:8516 14:48:11.6469 ProcessOutputRedirectionStd-14] Process 7288: Loading task assembly: C:\Program Files (x86)\Remco Software\NCrunch Grid Node Server\nCrunch.Core.DLL
[PID:8516 14:48:11.6469 HashCacheVerifier-11] Hash cache verification completed
[PID:8516 14:48:11.6939 ?-5] Snapshot 1 is using 4895099 bytes of disk space
[PID:8516 14:48:11.6939 ?-5] Activity "Initialising node: Calculating disk space in use" has been marked with progress: 10%
[PID:8516 14:48:11.6939 ?-5] Stopping tracking of activity "Initialising node: Calculating disk space in use" for #global:0
[PID:8516 14:48:11.6939 ?-5] Publishing Event: [:nCrunch.GridNode.NodeSnapshotStore.EnsureSnapshotDataLimitIsEnforced]
[PID:8516 14:48:11.6939 ?-5] Event [:nCrunch.GridNode.NodeSnapshotStore.EnsureSnapshotDataLimitIsEnforced] is being published on thread Core to subscriber: .
[PID:8516 14:48:11.6939 ?-5] All existing snapshots loaded
[PID:8516 14:48:11.6939 Core-6] Event [:nCrunch.GridNode.NodeSnapshotStore.EnsureSnapshotDataLimitIsEnforced] is being processed on Core thread with subscriber: .
[PID:8516 14:48:11.7099 Core-6] Checking for snapshots to delete in excess of the snapshot data limit: 16106127360
[PID:8516 14:48:11.7099 Core-6] Total snapshot space in use: 4895099
[PID:8516 14:48:11.7569 ProcessOutputRedirectionStd-14] Process 7288: Waiting for instructions
[PID:8516 14:48:11.8189 ?-4] Process 'b1285b1a506845409c77321ee2f645ec' with id 7288 is connected and tethered
[PID:8516 14:48:13.0069 ?-4] Process 7288 is terminating
[PID:8516 14:48:13.0069 ?-4] Removing external process with Id 'b1285b1a506845409c77321ee2f645ec'
[PID:8516 14:48:13.0069 ?-4] Framework description manager has loaded data for 6 test frameworks
[PID:8516 14:48:13.0069 ?-4] Loaded framework descriptions:
[PID:8516 14:48:13.0069 ?-9] Process with id 7288 has exited
[PID:8516 14:48:13.0219 ?-4] [Test Framework: Gallio]
[PID:8516 14:48:13.0219 ?-4] Framework Assemblies:
[PID:8516 14:48:13.0219 ?-4] Gallio
[PID:8516 14:48:13.0219 ?-4] Gallio35
[PID:8516 14:48:13.0219 ?-4] MbUnit.Compatibility
[PID:8516 14:48:13.0219 ?-4] MbUnit
[PID:8516 14:48:13.0219 ?-4] xunit
[PID:8516 14:48:13.0219 ?-4] xunit
[PID:8516 14:48:13.0219 ?-4] Gallio40
[PID:8516 14:48:13.0219 ?-4] MbUnit35
[PID:8516 14:48:13.0219 ?-4] MbUnit40
[PID:8516 14:48:13.0219 ?-4] -------------
[PID:8516 14:48:13.0219 ?-4] [Test Framework: MSpec]
[PID:8516 14:48:13.0219 ?-4] Framework Assemblies:
[PID:8516 14:48:13.0219 ?-4] Machine.Specifications
[PID:8516 14:48:13.0219 ?-4] -------------
[PID:8516 14:48:13.0219 ?-4] [Test Framework: MSTest]
[PID:8516 14:48:13.0219 ?-4] Framework Assemblies:
[PID:8516 14:48:13.0219 ?-4] Microsoft.VisualStudio.QualityTools.UnitTestFramework
[PID:8516 14:48:13.0219 ?-4] Microsoft.VisualStudio.TestPlatform.UnitTestFramework
[PID:8516 14:48:13.0219 ?-4] Microsoft.VisualStudio.TestPlatform.TestFramework
[PID:8516 14:48:13.0219 ?-4] -------------
[PID:8516 14:48:13.0219 ?-4] [Test Framework: NUnit]
[PID:8516 14:48:13.0219 ?-4] Framework Assemblies:
[PID:8516 14:48:13.0219 ?-4] nunit.framework
[PID:8516 14:48:13.0219 ?-4] -------------
[PID:8516 14:48:13.0219 ?-4] [Test Framework: NUnit3]
[PID:8516 14:48:13.0219 ?-4] Framework Assemblies:
[PID:8516 14:48:13.0219 ?-4] NUnit.Framework
[PID:8516 14:48:13.0219 ?-4] -------------
[PID:8516 14:48:13.0219 ?-4] [Test Framework: XUnit]
[PID:8516 14:48:13.0219 ?-4] Framework Assemblies:
[PID:8516 14:48:13.0219 ?-4] xunit.core
[PID:8516 14:48:13.0219 ?-4] xunit2
[PID:8516 14:48:13.0219 ?-4] -------------
[PID:8516 14:48:13.3189 ?-4] Unable to bind a listening socket to interface with address (xxx.xxx).167.139 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 4 times.
[PID:8516 14:48:13.3189 ?-4] Unable to bind a listening socket to interface with address (xxx.xxx).108.10 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 4 times.
[PID:8516 14:48:13.3189 ?-4] Unable to bind a listening socket to interface with address (xxx.xxx).134.89 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 4 times.
[PID:8516 14:48:13.3189 ?-4] Unable to bind a listening socket to interface with address (xxx.xxx).58.241 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 4 times.
[PID:8516 14:48:13.3189 ?-4] Node server started - listening on port 41141
[PID:8516 14:48:18.3349 ?-4] Unable to bind a listening socket to interface with address (xxx.xxx).134.89 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 3 times.
[PID:8516 14:48:18.3349 ?-12] Unable to bind a listening socket to interface with address (xxx.xxx).58.241 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 3 times.
[PID:8516 14:48:18.3349 ?-5] Unable to bind a listening socket to interface with address (xxx.xxx).108.10 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 3 times.
[PID:8516 14:48:18.3349 ?-14] Unable to bind a listening socket to interface with address (xxx.xxx).167.139 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 3 times.
[PID:8516 14:48:23.3499 ?-4] Unable to bind a listening socket to interface with address (xxx.xxx).108.10 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 2 times.
[PID:8516 14:48:23.3499 ?-12] Unable to bind a listening socket to interface with address (xxx.xxx).58.241 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 2 times.
[PID:8516 14:48:23.3499 ?-5] Unable to bind a listening socket to interface with address (xxx.xxx).134.89 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 2 times.
[PID:8516 14:48:23.3499 ?-15] Unable to bind a listening socket to interface with address (xxx.xxx).167.139 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 2 times.
[PID:8516 14:48:28.3499 ?-5] Unable to bind a listening socket to interface with address (xxx.xxx).134.89 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 1 times.
[PID:8516 14:48:28.3499 ?-4] Unable to bind a listening socket to interface with address (xxx.xxx).108.10 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 1 times.
[PID:8516 14:48:28.3499 ?-14] Unable to bind a listening socket to interface with address (xxx.xxx).167.139 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 1 times.
[PID:8516 14:48:28.3499 ?-18] Unable to bind a listening socket to interface with address (xxx.xxx).58.241 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 1 times.
[PID:8516 14:48:33.3499 ?-12] Unable to bind a listening socket to interface with address (xxx.xxx).134.89 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 0 times.
[PID:8516 14:48:33.3499 ?-15] Unable to bind a listening socket to interface with address (xxx.xxx).58.241 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 0 times.
[PID:8516 14:48:33.3499 ?-5] Unable to bind a listening socket to interface with address (xxx.xxx).108.10 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 0 times.
[PID:8516 14:48:33.3499 ?-11] Unable to bind a listening socket to interface with address (xxx.xxx).167.139 on port 41141, due to exception: The requested address is not valid in its context. Will retry another 0 times.


What can I do to get this setup going ?

Thx for your views,
Dirk
Back to top
Remco
#2 Posted : Friday, October 21, 2022 10:31:08 PM(UTC)
Rank: NCrunch Developer

Groups: Administrators
Joined: 4/16/2011(UTC)
Posts: 7,161

Thanks: 964 times
Was thanked: 1296 time(s) in 1202 post(s)
Hi Dirk,

Thanks for sharing this issue.

When the grid server opens connections, it tries to do so for all allocated addresses on the machine. This often includes addresses that are associated with disabled or inactive adapters. Consequently, you'll usually see a few of these in the logs.

Is the actual intended listening address shown here with an error message?

It's remarkable these days just how many things mess with network connections. It seems the best form of security is one where no machine can ever talk to another. Have you tried using a different port? Something could be blocking the connection based on port range.
Back to top
Dirk Maegh
#3 Posted : Saturday, October 22, 2022 9:23:33 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/30/2016(UTC)
Posts: 55
Location: Belgium

Thanks: 8 times
Was thanked: 8 time(s) in 8 post(s)
Just checking - the actual intended listening address - that would the ncrunch in VS2022 on my desktop ?

When I mentioned that they are on the same network, I actually meant they are "connected" to the same router, one of them (Grid Node laptop) wireless, one of them (VS2022 desktop) wired.
But when I check the network on the desktop, the Grid Node laptop does not show, which makes me doubt that first statement.

Also when I check the ip address - my desktop shows a normal "internal" address, starting with 192.168.
My laptop however shows a different address, starting with 10.218 (which makes me think that is an external address ?)

The masked addresses in the logs were neither of those, so if 'the actual intended listening address" was supposed to be my desktop, it indeed did not show.

When I do a ping now, it does not find the ip address of the laptop. (yesterday it did, but the ping never succeeded)

All of these together should confirm: I don't know networking yet.

All these remarks together, I think changing a port is not going to solve this yet, first I need to make the computers see each other, right ?
Back to top
Dirk Maegh
#4 Posted : Saturday, October 22, 2022 9:39:12 AM(UTC)
Rank: Advanced Member

Groups: Registered
Joined: 11/30/2016(UTC)
Posts: 55
Location: Belgium

Thanks: 8 times
Was thanked: 8 time(s) in 8 post(s)
Hi again,

adding a cable and playing with it (wired, wireless, wired again, etc...) actually solved things for me.
Ping still does not work (I have no idea why) but Grid Node is connected and working now. (on same port 41141 as before)

Thx for your suggestions. They helped me in trying and testing some more, and I got a positive result ;)
Back to top
1 user thanked Dirk Maegh for this useful post.
Remco on 10/22/2022(UTC)
Users browsing this topic
Guest
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.

YAF | YAF © 2003-2011, Yet Another Forum.NET
This page was generated in 0.104 seconds.
Trial NCrunch
Take NCrunch for a spin
Do your fingers a favour and supercharge your testing workflow
Free Download