External-worker config throwing exception

Legacy Execution
1

We have an HA pair, I configured them to use an external worker as per the documentation. now any deployment steps are failing, even those run on tentacles that are not the external worker. the exception is:
The step failed: Activity SQL Server Standard Database Deployment on LBRODY2 failed with error 'An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ScriptActionHandler (DelegateActivator), Services = [Octopus.Server.Orchestration.ServerTasks.Deploy.Steps.Script.ScriptActionHandler], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = None, Ownership = ExternallyOwned —> An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ScriptActionHandler (ReflectionActivator), Services = [Octopus.Server.Orchestration.ServerTasks.Deploy.Steps.Script.ScriptActionHandler], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = None, Ownership = OwnedByLifetimeScope —> An exception was thrown while invoking the constructor ‘Void .ctor(Octopus.Server.Orchestration.Targets.ITargetFactory, Octopus.Core.Orchestration.Targets.Server.IServerScriptCommandFactory, Octopus.Server.Orchestration.Targets.Scripting.ILocalScriptRunner, Octopus.Core.Orchestration.ServerTasks.Deploy.Calamari.ILocalCalamari, Octopus.Core.Tasks.ITaskContext, Octopus.Core.Orchestration.Workers.IWorkerPool, Octopus.Core.Orchestration.Targets.Common.IExecuteCommand, Octopus.Server.Orchestration.Targets.Common.IBundledPackageStore, Octopus.Core.Threading.IMachineWideMutex, Octopus.Core.Orchestration.Targets.Tentacles.ITentacleCommandFactory)’ on type ‘ScriptActionHandler’. —> Invalid URI: The Authority/Host could not be parsed. (See inner exception for details.) (See inner exception for details.) (See inner exception for details.)

An error occurred during the activation of a particular registration. See the inner exception for details. Registration: Activator = ScriptActionHandler (ReflectionActivator), Services = [Octopus.Server.Orchestration.ServerTasks.Deploy.Steps.Script.ScriptActionHandler], Lifetime = Autofac.Core.Lifetime.CurrentScopeLifetime, Sharing = None, Ownership = OwnedByLifetimeScope —> An exception was thrown while invoking the constructor ‘Void .ctor(Octopus.Server.Orchestration.Targets.ITargetFactory, Octopus.Core.Orchestration.Targets.Server.IServerScriptCommandFactory, Octopus.Server.Orchestration.Targets.Scripting.ILocalScriptRunner, Octopus.Core.Orchestration.ServerTasks.Deploy.Calamari.ILocalCalamari, Octopus.Core.Tasks.ITaskContext, Octopus.Core.Orchestration.Workers.IWorkerPool, Octopus.Core.Orchestration.Targets.Common.IExecuteCommand, Octopus.Server.Orchestration.Targets.Common.IBundledPackageStore, Octopus.Core.Threading.IMachineWideMutex, Octopus.Core.Orchestration.Targets.Tentacles.ITentacleCommandFactory)’ on type ‘ScriptActionHandler’. —> Invalid URI: The Authority/Host could not be parsed. (See inner exception for details.) (See inner exception for details.)

An exception was thrown while invoking the constructor ‘Void .ctor(Octopus.Server.Orchestration.Targets.ITargetFactory, Octopus.Core.Orchestration.Targets.Server.IServerScriptCommandFactory, Octopus.Server.Orchestration.Targets.Scripting.ILocalScriptRunner, Octopus.Core.Orchestration.ServerTasks.Deploy.Calamari.ILocalCalamari, Octopus.Core.Tasks.ITaskContext, Octopus.Core.Orchestration.Workers.IWorkerPool, Octopus.Core.Orchestration.Targets.Common.IExecuteCommand, Octopus.Server.Orchestration.Targets.Common.IBundledPackageStore, Octopus.Core.Threading.IMachineWideMutex, Octopus.Core.Orchestration.Targets.Tentacles.ITentacleCommandFactory)’ on type ‘ScriptActionHandler’. —> Invalid URI: The Authority/Host could not be parsed. (See inner exception for details.)

Invalid URI: The Authority/Host could not be parsed.’.

2

Hi Leslie,

It seems there’s an issue with the URL that you’ve configured for your external worker, could you check that the value in the config key in your Octopus server config file is correct, i.e. https://10.1.1.1:10933 or similar.

I replicated the error by mistyping the URL as https:/10.1.1.1:10933, so this could be the issue here too.

I hope that helps.

Thank you and best regards,
Henrik

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.