Error on Machine Creation: "Value cannot be null. Parameter name: remoteSpace."

Legacy Uncategorised
1

I am getting an error upon adding a machine to an environment. “Value cannot be null. Parameter name: remoteSpace.”

We have numerous environments and machines already setup so it was working up until this last week or so.

We are on version OctoDeploy 2.5.7.384

Here is the actual response from the server:
{
“ErrorMessage”: “Value cannot be null.\r\nParameter name: remoteSpace”,
“FullException”: “System.ArgumentNullException: Value cannot be null.\r\nParameter name: remoteSpace\r\n at Pipefish.Transport.SecureTcp.MessageExchange.Server.SecureTcpServerDistributor.RemoveEndpoint(String remoteSpace) in y:\work\3cbe05672d69a231\source\Pipefish.Transport.SecureTcp\MessageExchange\Server\SecureTcpServerDistributor.cs:line 68\r\n at Octopus.Server.Communications.TcpServer.TcpServerDistributionChannel.RemoveMachine(Machine machine) in y:\work\refs\heads\master\source\Octopus.Server\Communications\TcpServer\TcpServerDistributionChannel.cs:line 67\r\n at Octopus.Server.Communications.DistributionStarter.Remove(Machine machine) in y:\work\refs\heads\master\source\Octopus.Server\Communications\DistributionStarter.cs:line 44\r\n at Octopus.Server.Communications.DistributionStarter.Reconfigure() in y:\work\refs\heads\master\source\Octopus.Server\Communications\DistributionStarter.cs:line 80\r\n at Octopus.Platform.Web.Api.Responder1.ExecuteRules[TRule](Action2 ruleCallback) in y:\work\refs\heads\master\source\Octopus.Platform.Web\Api\Responder.cs:line 185\r\n at Octopus.Platform.Web.Api.Responder1.Respond(TDescriptor options, NancyContext context) in y:\\work\\refs\\heads\\master\\source\\Octopus.Platform.Web\\Api\\Responder.cs:line 166\r\n at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2)\r\n at CallSite.Target(Closure , CallSite , Object , Object , NancyContext )\r\n at Octopus.Server.Web.Api.OctopusRestApiModule.<>c__DisplayClass5.<.ctor>b__2(Object o) in y:\\work\\refs\\heads\\master\\source\\Octopus.Server\\Web\\Api\\OctopusRestApiModule.cs:line 47\r\n at CallSite.Target(Closure , CallSite , Func2 , Object )\r\n at Nancy.Routing.Route.<>c__DisplayClass4.b__3(Object parameters, CancellationToken context)”
}

2014-10-10_14-43-47.png
2014-10-10_14-43-47.png920×234 19.7 KB

2

Hi William,

Thanks for getting in touch! This is a known bug that has been fixed. If you are able to, please upgrade to 2.5.10.
The issue is the SQUID is null, and it cannot find the machine. Was the reset connection button hit twice by any chance?
Is it a listening or polling tentacle?

Vanessa

3

That fixed the issue. Thanks.

4

Does there happen to be a manual work around for this issue, such as modifying data in the database? We just ran into this issue on version 2.5.7.384. We want to avoid upgrading at this point to mitigate risk. Our tentacles are setup as listening.

Thanks,
Mike

5

Hi Mike,

It’s a bug that was fixed with the patch. Upgrading to that specific version is the only fix.

Vanessa