Strange NuGet server HTTP 500 error
Our Octopus user base has grown to a very large audience, internally speaking of course. Over the past few weeks we’ve also had to deal with our NuGet server running out of storage (so much for SCOM alerts). We keep our NuGet feeds off of the Octopus server as Octopus has one giant feed for all, but we like to partition out our feeds as we’re over 100 teams using Octopus and having them all share the same feed is a bit difficult to navigate. Over time, we’ve had a couple strange NuGet timeout’s appear in our Sumo Logic alerting. Just a small sample of teams were experiencing this bizarre timeout. This small number of teams recently had been getting a strange error in accessing their NuGet feed. From NuGet Package Explorer, the error message looked this like:
“An error occurred while processing this request..” – this is a suspect phrase, isn’t it? “The remote server returned status code: 500.” So much for details. After spending a little time digging around, looking for any useful error message, I managed to stumble onto this gem within the failing feed.
Considering all the bad error messages NuGet gives through trying to create a package, this is a welcome surprise. Looking at the packages on disk and thar’ she blows. Two zero kilobyte whales. Once they’re removed everything works normally.
I’m not sure how it was possible to upload the nuget packages, but I assume an error in transit may be the culprit. Of course, this past weeks issues with the NuGet server, the timeout issue may be one such cause for an empty NuGet package to be uploaded.