Apache OpenOffice (AOO) Bugzilla – Issue 119361
Cannot Update OpenOffice Software in AOO 3.4
Last modified: 2012-06-18 08:18:59 UTC
Created attachment 77549 [details] This is a screenshot of the software after the updater has failed to connect to the internet. To be honest, I am not certain this is the exact section to put this bug but it seemed to most fitting. I am running OpenOffice 3.4 on a Windows 7 Ultimate PC and after installing I decided to see if there was a quick follow up update like some companies will do. When I checked this the update manager said "Checking for an update failed." In the description it says "General Internet error has occurred." I have checked my firewall settings and my internet settings, and I see nothing that should be interfering with that process. If you require more information just let me know.
Confirming. The reason for this defect is that the servers hosting the update service are no longer available. But we are working on the establishment of new ones.
Several of the host names which may be embedded in releases currently point to what appears to be 3rd party hosts, viz: sd-web2.staroffice.de (192.18.197.109) and sd-web4.staroffice.de (192.18.197.105) These IPs are not responding. The host names that are affected include the following: update.services.openoffice.org is an alias for sd-web4.staroffice.de. update30.services.openoffice.org is an alias for sd-web2.staroffice.de. update31.services.openoffice.org is an alias for sd-web2.staroffice.de. update32.services.openoffice.org is an alias for sd-web2.staroffice.de. update33.services.openoffice.org is an alias for sd-web2.staroffice.de. update34.services.openoffice.org is an alias for sd-web2.staroffice.de. update35.services.openoffice.org is an alias for sd-web2.staroffice.de. update36.services.openoffice.org is an alias for sd-web2.staroffice.de. I don't know if there are any other such aliases, or if all of them have actually been used in OoO releases. These aliases need to be redirected to a host under the control of the ASF. Also, DNS entries would need to be set up for any other update* hostnames that have been used in OoO releases.
ad sebb: Thx for the information - for myself I had already marked your corresponding post ooo-dev. As far as I know ASF has the control to redirect all the updateXX.services... URLs to its own hosts/servers.
Start to work on a solution which will at least provide the user with the information that her/his installed AOO 3.4 is up to date. Created HTTP resource http://www.openoffice.org/projects/update38/ProductUpdateService/check.Update. It's an XML document containing the needed data for the update functionality of installed AOO 3.4 instances to work. Now, it is needed that the Update URL of installed AOO 3.4 instances is redirected to the above new HTTP resource --> JIRA issue for Apache Infrastructure needed.
JIRA issue for the redirect has been submitted - https://issues.apache.org/jira/browse/INFRA-4830
JIRA issue has been solved. --> this issue is also solved.
I don't think this issue is quite complete, as some of the update hostnames still point outside the ASF. At least one of the names I listed in comnent 2 is in use for existing releases - just use a search engine to look for update36.services.openoffice.org and there are several hits for complaints about it not working. I think all the update* hostnames should be redirected to ASF hosts. AIUI infra can do this, but someone on the PPMC will need to ask for it to be done.
@sebb: I have used this issue to bring back the update service for AOO 3.4. I have mentioned it in the corresponding thread on ooo-dev, but not here. I am sorry for that. There is another issue - bug 119323 - which I will use to bring back the update service for former OOo versions - may be not all. Thus, this issue is for the update service of AOO 3.4: - updating summary accordingly - resolving issue as fixed
verified in r1350879. It says "OpenOffice.org 3.4 is up to date" in the check for updates dialog