Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Learn More

Auto update on Win 2012 R2

  • 6 wotmołwy
  • 1 ma tutón problem
  • 615 napohladow
  • Poslednja wotmołwa wot tilo

more options

hi, auto update doesn't seem to work on Win 2012 R2 server. (used as Workstation) Firefox ESR 24.6.0 and I would expect an update to ESR 31 or at least to 24.8.

Did enable app.update.log and here the URL it checked which show no update available. https://aus3.mozilla.org/update/3/Firefox/24.6.0/20140609182057/WINNT_x86-msvc/en-US/esr/Windows_NT%206.3.0.0%20(x64)/default/default/update.xml?force=1

Any idea why? should I file a bug?

hi, auto update doesn't seem to work on Win 2012 R2 server. (used as Workstation) Firefox ESR 24.6.0 and I would expect an update to ESR 31 or at least to 24.8. Did enable app.update.log and here the URL it checked which show no update available. https://aus3.mozilla.org/update/3/Firefox/24.6.0/20140609182057/WINNT_x86-msvc/en-US/esr/Windows_NT%206.3.0.0%20(x64)/default/default/update.xml?force=1 Any idea why? should I file a bug?

Wubrane rozrisanje

Nick from ESR team clarified: The updates from 24.x.y to 31.2.0 were disabled because of crashes on startup in some situations. They'll be enabled again once 31.3.0 ships, which is scheduled for Dec 1. There are no known issues with the update server configuration.

Tutu wotmołwu w konteksće čitać 👍 0

Wšě wotmołwy (6)

more options
more options

This should be fixed https://bugzilla.mozilla.org/show_bug.cgi?id=996139

Please check the user profile to make sure that there is not a lock file that may be blocking certain user features. This lists the user.js features that would lock these: http://forums.frontmotion.com/viewtopic.php?f=10&t=1539&sid=185f6a...

If there is further troubleshooting needed, the ESR working group is a good place to ask the experts as well.

more options

thanks, I don't have a C:\Program Files (x86)\Mozilla Firefox\mozilla.cfg file at all, so no restriction there.

here the log: [15:46:47.957] [Exception... "Component returned failure code: 0x8000ffff (NS_ERROR_UNEXPECTED) [nsIPrefBranch.getCharPref]" nsresult: "0x8000ffff (NS_ERROR_UNEXPECTED)" location: "JS frame :: chrome://browser/content/aboutDialog.js :: init :: line 14" data: no] @ chrome://browser/content/aboutDialog.js:32 [15:46:48.011] AUS:SVC Creating UpdateService [15:46:48.013] AUS:SVC Checker: checkForUpdates, force: true [15:46:48.024] AUS:SVC getLocale - getting locale from file: resource://gre/update.locale, locale: en-US [15:46:48.025] AUS:SVC Checker:getUpdateURL - update URL: https://aus3.mozilla.org/update/3/Firefox/24.8.0/20140825140210/WINNT_x86-msvc/en-US/esr/Windows_NT%206.2.0.0%20(x64)/default/default/update.xml?force=1 [15:46:48.025] AUS:SVC gCanCheckForUpdates - able to check for updates [15:46:48.061] AUS:SVC Checker:checkForUpdates - sending request to: https://aus3.mozilla.org/update/3/Firefox/24.8.0/20140825140210/WINNT_x86-msvc/en-US/esr/Windows_NT%206.2.0.0%20(x64)/default/default/update.xml?force=1 [15:46:48.295] GET https://aus3.mozilla.org/update/3/Firefox/24.8.0/20140825140210/WINNT_x86-msvc/en-US/esr/Windows_NT%206.2.0.0%20(x64)/default/default/update.xml?force=1 [HTTP/1.1 200 OK 469ms] [15:46:48.663] AUS:SVC Checker:onLoad - request completed downloading document [15:46:48.664] AUS:SVC Checker:onLoad - number of updates available: 0


It seems as the list (https://mxr.mozilla.org/firefox/source/webtools/aus/xml/inc/config-dist.php) need to be fixed but not sure. (as the URL reports: number of updates available: 0)

sorry for the format but couldn't format the log to show nicely.

more options

Wot tilo změnjeny

more options
more options

Wubrane rozrisanje

Nick from ESR team clarified: The updates from 24.x.y to 31.2.0 were disabled because of crashes on startup in some situations. They'll be enabled again once 31.3.0 ships, which is scheduled for Dec 1. There are no known issues with the update server configuration.