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

ServicePulse fails to start after upgrading to 1.24 #823

Closed
davidsavagejr opened this issue Feb 11, 2020 · 9 comments
Closed

ServicePulse fails to start after upgrading to 1.24 #823

davidsavagejr opened this issue Feb 11, 2020 · 9 comments
Labels
Milestone

Comments

@davidsavagejr
Copy link

@davidsavagejr davidsavagejr commented Feb 11, 2020

Upgraded to 1.24 and ServicePulse fails to start. Initial problem appeared to be a permission issue. Running manually via cmd prompt or as "Local System" was able to get it into a "running" state but then I was only able to get an HTTP 503 when hitting the app via the browser.

It's hosted on port 80 and was working find up to 1.23


Technical information if reporting a bug:

  • ServicePulse version: 1.24
  • ServiceControl version: 4.5.3
  • Browser version: Brave 1.2.43
@saschanm

This comment has been minimized.

Copy link

@saschanm saschanm commented Feb 11, 2020

Same here....service fails to start after upgrade from 1.23 to 1.24.

Windows logs show:
Application: ServicePulse.Host.exe Framework Version: v4.0.30319 Description: The process was terminated due to an unhandled exception. Exception Info: System.NullReferenceException at ServicePulse.Host.Hosting.Host.OnStop() at ServicePulse.Host.Hosting.Host.Dispose(Boolean) at System.ComponentModel.Component.Dispose() at System.ServiceProcess.ServiceBase.Run(System.ServiceProcess.ServiceBase[]) at ServicePulse.Host.Commands.RunCommand.Execute(ServicePulse.Host.Hosting.HostArguments) at ServicePulse.Host.Commands.CommandRunner.Execute(ServicePulse.Host.Hosting.HostArguments) at ServicePulse.Host.Program.Main(System.String[])

@Dunge

This comment has been minimized.

Copy link

@Dunge Dunge commented Feb 11, 2020

Same, upgraded for no reason other than the "new version available" link in the page, and now the service shut down after starting it.

@saschanm

This comment has been minimized.

Copy link

@saschanm saschanm commented Feb 12, 2020

I got blue screen when I attempted to uninstall also. After restart I uninstalled manually and then reinstalled a clean install of 1.24. Same issue with null reference exception.

Uninstalled and reinstalled previous version 1.23 without issue.

@WojcikMike

This comment has been minimized.

Copy link
Member

@WojcikMike WojcikMike commented Feb 12, 2020

Hi @saschanm , @Dunge and @davidsavagejr

Thank you for your posts. We are working on the fix of that issue.

@janovesk

This comment has been minimized.

Copy link
Member

@janovesk janovesk commented Feb 12, 2020

Hey, @saschanm , @Dunge and @davidsavagejr!

Could you run netsh http show urlacl in a command window for me and see if you find any reservations for port 8081 (or whatever other port you have configured ServicePulse to run on)? If so, can you paste the value here? It should look something like :

Reserved URL : http://+:8081/
User: \Everyone
Listen: Yes
Delegate: No
SDDL: D:(A;;GX;;;WD)

@janovesk janovesk added the Type: Bug label Feb 12, 2020
@janovesk janovesk added this to the 1.24.1 milestone Feb 12, 2020
@janovesk

This comment has been minimized.

Copy link
Member

@janovesk janovesk commented Feb 12, 2020

We just released 1.24.1 to fix this issue. Check it out and let us know if there are any other issues.

@janovesk

This comment has been minimized.

Copy link
Member

@janovesk janovesk commented Feb 12, 2020

For those interested, the problem was that NancyFX and OWIN treat listening to a localhost URL differently. NancyFX will, by default, listen to all hostnames if you tell it to listen to localhost while OWIN will not. This created a crash with the registered urlacl registration for OWIN. With this fix, the old behavior is back.

@janovesk janovesk closed this Feb 12, 2020
@davidsavagejr

This comment has been minimized.

Copy link
Author

@davidsavagejr davidsavagejr commented Feb 12, 2020

Up and running on 1.24.1, installed without any issues.
Awesome turnaround, thanks guys!

@saschanm

This comment has been minimized.

Copy link

@saschanm saschanm commented Feb 13, 2020

Confirmed working for me too on 1.24.1.

Thanks for the quick fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
5 participants
You can’t perform that action at this time.