How to debug problems with Octopus

Legacy Uncategorised
1

Hi,

I got this error and I’m wondering if there are any logs I can use to investigate it. There seems to be nothing in the Event Log.

Thanks

Pawel

“Getting package versions for each step…
Octopus server responded with: The remote server returned an error: (400) Bad Request.
System.Net.WebException: The remote server returned an error: (400) Bad Request.
at System.Net.HttpWebRequest.GetResponse()
at OctopusTools.Client.OctopusSession.Get[TResource](String path)
at OctopusTools.Client.OctopusSession.List[TResource](String path)
at ProjectExtensions.GetLatestPackageForStep(IOctopusSession session, Step step)
at OctopusTools.Commands.CreateReleaseCommand.Execute()
at OctopusTools.Infrastructure.CommandProcessor.Process(String[] args)”

2

Hi Pawel,

Since you are using octo.exe you could try running Fiddler - the 400 bad request might also include a JSON payload explaining it (for some reason that doesn’t show up in release builds), or try upgrading to the latest Octopus+Octo where this bug should be fixed.

Paul

3

Hi,

Usually this is what I would do but this problem is intermittent and I can’t even reproduce it. It would be good to have some kind of file based log for errors in the Portal and the Server.

I will upgrade to the latest version from 1.0.30.1340 and see if it fixes it.

Thanks

Pawel