Apache OpenOffice (AOO) Bugzilla – Issue 98546
Automatic Update Check not reliable
Last modified: 2010-07-21 11:15:58 UTC
First of all, I have donated and this is a real pain in the a$$... I received the email regarding 3.0.1 availability and promptly opened Openoffice and here is he error I KEEP getting: Checking for an update failed. Do I have to delete 3.0.0? If not, how do I update it??
I checked with "Ooo 3.0.0 (DE) Multilingual version German UI WIN XP: [OOO300m9 (Build9358)]" and I can confirm that automatic update checker might be not be liable for 3.0.1. Steps to reproduce: 1. Meun 'Tools -> Options -> Online Update -> Search now' (All: translated from German UI) Expected: "There is a new Version 3.0.1" Atual: "OOo 3.0 ist auf dem neuesten Stand" (3.0 is the current version) The message is not really wrong because 3.0.0 and 3.0.1. both are 3.0 versions. But this information is not really useful, information concerning 3.0.1 available should have been shown. I checked homepage and mirrors; version 3.0.1 is available. @dlprobert: Thank you for your report, but: The Issue tracker is not a user help facility. Please read the FAQ and other information linked in the left frame of this screen. You can get help from the public users mailing list users@openoffice.org or on the forum at <http://user.services.openoffice.org/en/forum/>
Same with with "Ooo-dev 3.0.0 Multilingual version English UI WIN XP: [DEV300m39 (Build 9378)]" Sorry, until now only checked with WIN
*** Issue 98577 has been marked as a duplicate of this issue. ***
added ja
Update service of 3.0.1 has not been activated yet. I'll prepare this within the next days or weeks depending on the load of the download infrastructure. Just keep in mind that several million (>30000000) installations will get notified
In future we should have a hint like "automatic update information from your OOo installation might be delayed some days" in announce e-mail and on the OOo WEB pages to beware of lots of Issue reports ;-)
Product Update Notification has been enabled for en-US, de and fr. I'll follow-up with those localizations where the build is capable of using this service (Pavel's and Maho's builds are not). I expect pl and ru localization to follow whereas da is a build from Pavel.
Has the Update service of 3.0.1 has not been activated yet ? Because when I choose 'Check for Updates' in 3.0.1, I still get the message : "Checking for an update failed. Could not establish Internet connection to update30.services.openoffice.org.".
Why is this issue marked 'resolved' ? When I try to update OpenOffice.org 3.0.0 I *still* get the error message: "Checking for an update failed. Could not establish Internet connection to update30.services.openoffice.org.". I assume that this means that the issue should be re-opened, at least ?
ja: lbalbalba told us that it is not fixed. also this was reported at QA list of JA project. * http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=841 * http://ja.openoffice.org/servlets/ReadMsg?list=qa&msgNo=859 3.0, 3.0.1 says 3.0 is the newest one. on XP 2.4.1 says 3.0 is available but only "download.php" is downloaded. I reopen this issue, thanks!
I will activate the service within the next days when download numbers go down a bit. Within the first week of OOo 3.1.0 we already had 2350000 downloads. I don't want to DDOS the load balancer.
ja: matukai-san verified that automatic update check is now working. thanks
closing issue
There should be done some fixes after Issue 113114 but now "looking for an update failed" or similar. i only see the German Error message "Die Suche nach einem Update ist fehlgeschlagen" this messsage comes in less than 1 sec. A ping from the same maschine to the server gives nearly 70 ms
This should be a release_blocker. It is intilerable to have an unsuable function of update services. After a release we publish that this release contains security fixes and the update services didn't work.
Everything should work as expected. Try again later. Maybe the service is a bit overloaded in the moment. Reassigning to Frank as I'm not responsible for the service infrastructure
Known issue, set to duplicate. *** This issue has been marked as a duplicate of 95975 ***
duplicate -> closed