I am migrating our Octopus 2.6 server over to a 3.0 instance (new install). This is on a Windows 2012 R2 Standard machine. SQL Server is on another machine accessible via the network. I have installed 3.0.6 on a fresh VM. I migrated our 2.6 data over using the import tool and it apparently succeeded. However, I’m having problems with the bindings. The service refuses to start with the following error in the logs:
2015-07-27 11:43:15.4604 5 FATAL Unhandled AppDomain exception occurred: The HTTP server could not start because namespace reservations have not been made. Ensure that the current user has access to listen on these prefixes by running the following command(s):
netsh http add urlacl url=http://+:80/ user=MYDOMAIN\svc_Octopus
netsh http add urlacl url=http://+:80/ user=MYDOMAIN\svc_Octopus
If I use the Octopus Manager to get rid of the localhost binding and if I use this command, the service appears to start:
netsh http add urlacl url=http://octopus.mydomain.net:80/ user=MYDOMAIN\svc_Octopus
But I can’t navigate to it and this appears in the logs:
2015-07-27 11:53:30.8035 5 INFO Browse your Octopus server at: http://localhost:80/
I’m also having issues reaching various tentacles that have been upgraded using Hydra with the following error:
Halibut.Transport.Protocol.ConnectionInitializationFailedException: Unable to process remote identity; unknown identity type: ‘HTTP/1.0’ —> Halibut.Transport.Protocol.ProtocolException: Unable to process remote identity; unknown identity type: ‘HTTP/1.0’
Their fix was to uninstall and reinstall the tentacle using the MSI on the download page instead of the link in the documentation… a PITA but now have working tentacles. Looks like the link in the doc is to 3.0.6.2130 whereas the link on the download page is 3.0.6.2140…
Sorry to hear you had some hassles but glad you got it working.
Thanks for the debug data though, we’ll take a look and see if we can figure out what went wrong and make things smoother for the next people to trad your path.
Just a thought, Hydra has some log files ( http://docs.octopusdeploy.com/display/OD/Troubleshooting ) which might explain what went wrong with the upgrade, are you able to have a quick look there and see if there are any clues ?
I haven’t found any of the log files mentioned on the troubleshooting page.
While health checks and deployments are taking place successfully, I am still getting this err on tentacles (removed the IP):
2015-07-28 08:00:26.1802 62 INFO listen://0.0.0.0:10933/ 62 Unhandled error when handling request from client: xxx.xxx.xxx.xxx:54028
System.IO.IOException: Unable to read data from the transport connection: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. —> System.Net.Sockets.SocketException: A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
— End of inner exception stack trace —
at System.Net.Sockets.NetworkStream.Read(Byte[] buffer, Int32 offset, Int32 size)
at System.Net.FixedSizeReader.ReadPacket(Byte[] buffer, Int32 offset, Int32 count)
at System.Net.Security._SslStream.StartFrameHeader(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.StartReading(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security._SslStream.ProcessRead(Byte[] buffer, Int32 offset, Int32 count, AsyncProtocolRequest asyncRequest)
at System.Net.Security.SslStream.Read(Byte[] buffer, Int32 offset, Int32 count)
at System.IO.StreamReader.ReadBuffer()
at System.IO.StreamReader.ReadLine()
at Halibut.Transport.Protocol.MessageExchangeStream.ReadLine() in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\Protocol\MessageExchangeStream.cs:line 91
at Halibut.Transport.Protocol.MessageExchangeStream.ExpectNextOrEnd() in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\Protocol\MessageExchangeStream.cs:line 65
at Halibut.Transport.Protocol.MessageExchangeProtocol.ProcessClientRequests(Func2 incomingRequestProcessor) in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\Protocol\MessageExchangeProtocol.cs:line 110 at Halibut.Transport.Protocol.MessageExchangeProtocol.ExchangeAsServer(Func2 incomingRequestProcessor, Func`2 pendingRequests) in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\Protocol\MessageExchangeProtocol.cs:line 90
at Halibut.Transport.SecureListener.ExecuteRequest(TcpClient client) in y:\work\7ab39c94136bc5c6\source\Halibut\Transport\SecureListener.cs:line 122
That seems odd. Just so I know we’re on the same page, they are log files sitting on the Tentacle ?
Also, everything is working with your 3.0 instance ?
Do you have your 2.6 server still online trying to connect to those machines ?
21:33:00 Info | Starting health check for a limited set of deployment targets
21:33:00 Info | 1 machines will have their health checks taken.
21:33:05 Fatal | The health check failed. One or more deployment targets were not available.
|
| == Failed: Check deployment target: Test Tentacle ==
21:33:05 Fatal | An error occurred when sending a request to ‘https://(my_ip_addr):10933/’, before the request could begin: Unable to process remote identity; unknown identity type: 'HTTP/1.0’
21:33:05 Verbose | An error occurred when sending a request to ‘https://(my_ip_addr):10933/’, before the request could begin: Unable to process remote identity; unknown identity type: ‘HTTP/1.0’
| Halibut.HalibutClientException: An error occurred when sending a request to ‘https://(my_ip_addr):10933/’, before the request could begin: Unable to process remote identity; unknown identity type: ‘HTTP/1.0’ —> Halibut.Transport.Protocol.ConnectionInitializationFailedException: Unable to process remote identity; unknown identity type: ‘HTTP/1.0’ —> Halibut.Transport.Protocol.ProtocolException: Unable to process remote identity; unknown identity type: ‘HTTP/1.0’
Sorry for the troubles. You cannot update 2.6 Tentacles with 3.0 Octopus, they cannot communciate. You need to use Hydra in 2.6 to upgrade Tentacles to 3.0.
I have also seen Unable to process remote identity; unknown identity type: 'HTTP/1.0 error when the Octopus communication is intercepted by a firewall or similar.
What happens when you attempt to go to https://(my_ip_addr):10933/ from your Octopus Server through a browser? Do you see a connected Tentacle message?
Your advice was very helpful and it became clear what was going wrong with my Octopus and Tentacle update process. I didn’t know that Octopus 3.x can’t communicate with Tentacle 2.6 at all.
Glad to hear you figured it out. We try to be very clear when Hydra needs to run on our upgrade pages: http://docs.octopusdeploy.com/display/OD/Upgrading+from+Octopus+2.6
Do you think we could be clearer? Did you follow any specific help page when starting your upgrade?