Hi,
I have started receiving error this morning on a new deployment (for an existing project).
Suddently, octopus was unable to download a newly uploaded package on our nuget private gallery.
The first error was our fault : the nuget server was running low on memory, and nuget did not allow the WCF service to start. Octopus was complaining about a strage error.
But beside the fact that the nuget server was now up a running smoothly, octopus was still hanging in the download process of the nuget package.
Event the nuget feed test form failed with the following exception :
@@@
2014-01-20 12:31:12.5969 ERROR Unhandled error on request: http://octopus.mycompany.lan/octopus/api/feeds/feeds-2/packages?packageId=mypackage&partialMatch=true&take=10 : Expected an absolute, well formed http URL without a query or fragment.
Parameter name: serviceRoot
System.ArgumentException: Expected an absolute, well formed http URL without a query or fragment.
Parameter name: serviceRoot
at System.Data.Services.Client.DataServiceContext…ctor(Uri serviceRoot)
at NuGet.DataServiceContextWrapper…ctor(Uri serviceRoot)
at NuGet.DataServicePackageRepository.GetPackages()
at Octopus.Server.Web.Api.Actions.PackageSearchAction.SearchForPackagesNamedLike(IPackageRepository repository, String packageId, Int32 take) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Web\Api\Actions\PackageSearchAction.cs:line 120
at Octopus.Server.Web.Api.Actions.PackageSearchAction.Search(String feedId, String packageId, Boolean partialMatch, Boolean includeMultipleVersions, Boolean includeNotes, Boolean includePreRelease, Int32 take) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Web\Api\Actions\PackageSearchAction.cs:line 59
at Octopus.Server.Web.Api.Actions.PackageSearchAction.Execute() in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Web\Api\Actions\PackageSearchAction.cs:line 42
at Octopus.Platform.Web.Api.Responder1.Respond(TDescriptor options, NancyContext context) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Platform.Web\Api\Responder.cs:line 163 at System.Dynamic.UpdateDelegates.UpdateAndExecute3[T0,T1,T2,TRet](CallSite site, T0 arg0, T1 arg1, T2 arg2) at CallSite.Target(Closure , CallSite , Object , Object , NancyContext ) at Octopus.Server.Web.Api.OctopusRestApiModule.<>c__DisplayClass5.<.ctor>b__2(Object o) in c:\TeamCity\buildAgent\work\1116bd9da9e239fd\source\Octopus.Server\Web\Api\OctopusRestApiModule.cs:line 47 at CallSite.Target(Closure , CallSite , Func
2 , Object )
at Nancy.Routing.Route.<>c__DisplayClass4.b__3(Object parameters, CancellationToken context)
@@@
I’ve been able to workaround this problem by restarting the octopus portal service, but I still don’t know why octopus was blocked.
I am not sure if you will be able to find the root cause of this problem, but I prefer to let you know about it.