We’re getting inconsistent IIS ARR 502 errors with NuGet pushes from VSTS. I haven’t seen this before until earlier this week. When I run the push from my laptop, I don’t have any issues.
From VSTS, it’s farily consistent in not working, but on occasion it will work once - but only for this instance (running Octopus v2018.6.1). Most of our clusters still run a much older version so we’re experimenting in production with a select few Octopus instances and this is one issue that’s come up that I don’t even know how to effectively troubleshoot.
Here’s the error from VSTS:
We have AWS ELB in front of 2 IIS ARR servers. Both servers have 50% distribution and URL rewrite down to the Octopus 2-way HA cluster. I’ve witnessed thru IIS monitoring both HA nodes throw an error so it’s not just one of the servers. Both servers have the exact same URL bindings within Octopus as well as SSL certs (as do IIS ARR and ELB). I’m not a whiz with IIS logs but the inconsistency is downright confusing.
One odd thing I’ve seen in the Octopus logs is this:
Unhandled error on request: https://octopus.accenture.com/DevArchMaturity_9347/api/octopusservernodes/VW106830 817a6b64976b4774ab1294c8d216699f by email@example.com : ‘VW106830’ is not a valid document Id. It should have the format ‘-’. Example: ‘Projects-101’. System.Exception: ‘VW106830’ is not a valid document Id. It should have the format ‘-’. Example: ‘Projects-101’. at Octopus.Core.Resources.DocumentIdParser.AssertValidDocumentId(String documentId) at Octopus.Server.Web.Infrastructure.Api.ModifyResponseDescriptor
2.Responder.Execute() at Octopus.Server.Web.Infrastructure.Api.Responder1.ExecuteRegistered() at Octopus.Server.Web.Infrastructure.Api.Responder
1.Respond(TDescriptor options, NancyContext context) 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.Infrastructure.OctopusNancyModule.<>c__DisplayClass14_0.<get_Routes>b__1(Object x) at CallSite.Target(Closure , CallSite , Func2 , Object ) at Nancy.Routing.Route.<>c__DisplayClass4.b__3(Object parameters, CancellationToken context)
I’m not sure if this related to our issue or not, but it’s very pecuilar and I’ve never seen an issue like this before. I don’t know if this is a related issue or not.
Any thoughts/ideas/logs to hunt down? This is very similar to this reported post here: Bad Gateway Error but no solution was ever reported.