Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Cannot upgrade Audit Instance in ServiceControl Management using the Upgrade link #1737

Closed
mohlerm opened this issue Aug 16, 2019 · 7 comments

Comments

@mohlerm
Copy link

commented Aug 16, 2019

See https://discuss.particular.net/t/servicecontrol-4-3-1-patch-release-available/1369

Hi

I just upgraded to ServiceControl 4.1.0.
Upgrading the ServiceControl Instance went through but I do not seem to be able to upgrade the Audit instance. It shows the 'Upgrade' button but clicking on it shows no reaction:
2019-08-16_164515

I've also tried shutting down the Audit instance prior to updating but didn't help.

However, using the powershell command:
Invoke-ServiceControlAuditInstanceUpgrade -Name Particular.ServiceControl.Audit
upgrade seems to have worked (version number is updated in the UI).

However I'm seeing the following errors in my ServiceControl instance log:

2019-08-16 16:48:42.1917|46|Warn|ServiceControl.CompositeViews.Messages.ScatterGatherApi`2[[System.String, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089],[System.Collections.Generic.IList`1[[ServiceControl.CompositeViews.Messages.MessagesView, ServiceControl, Version=4.0.0.0, Culture=neutral, PublicKeyToken=null]], mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]]|Failed to query remote instance at http://removed/api/.
Newtonsoft.Json.JsonReaderException: Unexpected character encountered while parsing value: <. Path '', line 0, position 0.
   at Newtonsoft.Json.JsonTextReader.ParseValue()
   at Newtonsoft.Json.JsonReader.ReadForType(JsonContract contract, Boolean hasConverter)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonSerializer.Deserialize[T](JsonReader reader)
   at ServiceControl.CompositeViews.Messages.ScatterGatherApi`2.<ParseResult>d__20.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at ServiceControl.CompositeViews.Messages.ScatterGatherApi`2.<FetchAndParse>d__19.MoveNext()

I was able to get rid of this message by removing/adding my ServiceControl & ServiceControl.Audit instance.

Cheers

@mohlerm mohlerm changed the title Cannot upgrade Audit Instance to V4.1.0 Cannot upgrade Audit Instance in ServiceControl Management to V4.1.0 Aug 16, 2019

@WilliamBZA WilliamBZA added the Bug label Aug 19, 2019

@WilliamBZA WilliamBZA added this to the 4.1.1 milestone Aug 19, 2019

@WilliamBZA

This comment has been minimized.

Copy link
Member

commented Aug 19, 2019

Definitely a bug. Thanks for reporting it, I'll keep you posted

@SzymonPobiega

This comment has been minimized.

Copy link
Member

commented Aug 21, 2019

Workarounds:

  • Use Invoke-ServiceControlAuditInstanceUpgrade -Name Particular.ServiceControl.Audit as @mohlerm suggested
  • Remove existing instance (while preserving logs and data folders) and create a new instance with the same log and data paths
@SeanFeldman

This comment has been minimized.

Copy link
Contributor

commented Aug 26, 2019

@WilliamBZA please note there's going to be a 4.2.0 release and the milestone on this issue will have to be updated.

@SeanFeldman SeanFeldman changed the title Cannot upgrade Audit Instance in ServiceControl Management to V4.1.0 Cannot upgrade Audit Instance in ServiceControl Management using the Upgrade link Aug 26, 2019

@SeanFeldman

This comment has been minimized.

Copy link
Contributor

commented Aug 26, 2019

Updated the title of the issue to indicate that the upgrade link is broken, not SC v4.1.0.

@danielmarbach

This comment has been minimized.

Copy link
Member

commented Sep 6, 2019

Fixed. Closing. Will post the announcement link containing more details soon

@danielmarbach

This comment has been minimized.

Copy link
Member

commented Sep 6, 2019

@indualagarsamy

This comment has been minimized.

Copy link
Member

commented Sep 6, 2019

Here's the associated PR with the fix: #1757

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
7 participants
You can’t perform that action at this time.