Jump to content

"Update Now" issue


Raff

Recommended Posts

I have the "Update Now" button on my 3.0.5641.4 server summary page, but it doesn't trigger the update when pressed in either Chrome or IE. I tried a restart and also tried a complete shutdown, checked to see everything quit, and start.

 

It looks like the button fires off the Check for Application Updates scheduled task:

2015-07-11 11:12:04.5512 Info - App: Executing Check for application updates
2015-07-11 11:12:04.5512 Info - App: New application version is available: 3.0.5666.8
2015-07-11 11:12:04.5512 Info - App: A new version of Media Browser Server is available.
2015-07-11 11:12:04.5512 Info - App: Check for application updates Completed after 0 minute(s) and 0 seconds
2015-07-11 11:12:04.5668 Info - ServerManager: Sending web socket message ScheduledTaskEnded
2015-07-11 11:12:04.6760 Debug - HttpServer: HTTP Response 204 to 127.0.0.1. Response time: 124.8003 ms.
	Url: http://localhost:8096/ScheduledTasks/Running/7717368eb904db8e2522240726ba251a

The ID 7717368eb904db8e2522240726ba251a is the check for update, and the last run time seems to indicate that it did fire. I don't see the update archive so it doesn't appear that anything actually happened.

 

I am seeing a bunch of DNLA messages where the user agent is Wget which is new:

2015-07-11 11:35:04.9760 Debug - Dlna: No matching device profile found. The default will be used. User-agent: Wget. 
2015-07-11 11:35:04.9760 Debug - HttpServer: HTTP Response 200 to [my gateway]. Response time: 15.6 ms.
	Url: http://[my server]:8096/dlna/fe7b3852bccf9dba28cbec2627d4147e/description.xml

Anyone else having issues?

Link to comment
Share on other sites

I am seeing the same thing. The update now button processes then says the server needs to restart. You press restart now and the server does actually restart and it then says the same update is available to install again.

Link to comment
Share on other sites

I went ahead and did a manual update to get on the new version. I'm still not sure what happened, as every update before this worked for the most part.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...