Upgrade from 1.10.6 to 1.12.4 errored out

pdavidson's Avatar

pdavidson

26 May, 2018 11:01 PM

Hi Anton:

I might have fixed the issue.
For some reason, the web.config file was trying to point the hg.exe path to x86
We're on a 64 bit server so....

I had changed, during the install of the upgrade, this path to point at the Program Files\TortoiseHg folder but it appears this didn't take in the web.config file. Seems like every time I apply an upgrade this might be happening, that I have to change that path?

I am a bit concerned about the status of our system.
It is now coming up to the Dashboard, yay, but....
BTW - I changed the web.config, things looked good.
But I did reboot the server.

I also was digging through the logs and notice a lot of socket errors like this:
16:06:55.5777 - Error - - HgLab.Core.Framework.Appcast.AppcastManager - could not check for updatesSystem.Net.WebException: The underlying connection was closed: An unexpected error occurred on a send. ---> System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host
   at System.Net.Sockets.Socket.Receive(Byte[] buffer, Int32 offset, Int32 size, SocketFlags socketFlags)
   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.SslState.StartReceiveBlob(Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.CheckCompletionBeforeNextReceive(ProtocolToken message, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.StartSendBlob(Byte[] incoming, Int32 count, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ForceAuthentication(Boolean receiveFirst, Byte[] buffer, AsyncProtocolRequest asyncRequest)
   at System.Net.Security.SslState.ProcessAuthentication(LazyAsyncResult lazyResult)
   at System.Net.TlsStream.CallProcessAuthentication(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
   at System.Net.TlsStream.ProcessAuthentication(LazyAsyncResult result)
   at System.Net.TlsStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.PooledStream.Write(Byte[] buffer, Int32 offset, Int32 size)
   at System.Net.ConnectStream.WriteHeaders(Boolean async)
   --- End of inner exception stack trace ---
   at System.Net.WebClient.DownloadFile(Uri address, String fileName)
   at System.Net.WebClient.DownloadFile(String address, String fileName)
   at HgLab.Core.Framework.Appcast.AppcastManager.DiscoverUpdates(String appcastFeedUrl, Version currentVersion) in d:\projects\hglab\src\HgLab.Core\Framework\Appcast\AppcastManager.cs:line 67 at System.Net.WebClient.DownloadFile(Uri address, String fileName)
   at System.Net.WebClient.DownloadFile(String address, String fileName)
   at HgLab.Core.Framework.Appcast.AppcastManager.DiscoverUpdates(String appcastFeedUrl, Version currentVersion) in d:\projects\hglab\src\HgLab.Core\Framework\Appcast\AppcastManager.cs:line 67
System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host. ---> System.Net.Sockets.SocketException: An existing connection was forcibly closed by the remote host

And in the hgrpcsharp.log:
15:59:46.8687 - Info - pdavidson - HgRpcSharp.HgRpcServer - starting HgRpcServer with hgExeFullPath: 'C:\Program Files (x86)\TortoiseHg\hg.exe'

Which is the wrong path...

Maybe we can schedule a shared view next week just to have you diagnose and bless the system?
Or is there a way I can run a health check on it?

Thanks!

  1. 1 Posted by pdavidson on 27 May, 2018 01:33 AM

    pdavidson's Avatar

    As far as I can tell, this issue was related to the web.config pointing at a 32 bit hg.exe that did not exist. This is a 64 bit server.
    Once I fixed the line the web.config, the upgrade was successful and things look OK again.
    The error was:
        <add key="hglab.general.hg-executable-path" value="C:\Program Files (x86)\TortoiseHg\hg.exe"/>

    The fixed line is:
        <add key="hglab.general.hg-executable-path" value="C:\Program Files\TortoiseHg\hg.exe"/>

    I had noticed during the upgrade that I had to change the path of the hg.exe.
    I think this might be common when I upgrade HgLab but it's been awhile so I can't remember.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac

Recent Discussions

31 May, 2019 02:29 PM
26 Nov, 2018 01:47 PM
16 Nov, 2018 07:51 PM
06 Nov, 2018 04:30 PM
24 Oct, 2018 07:57 AM

 

20 Jul, 2018 11:07 PM
05 Jul, 2018 10:53 AM
27 May, 2018 01:33 AM
14 May, 2018 03:38 PM
04 May, 2018 07:45 AM
28 Feb, 2018 07:08 AM