Issue 119323 - Check for Update always fails in former OOo versions
Summary: Check for Update always fails in former OOo versions
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 3.3
Hardware: All All
: P3 Major (vote)
Target Milestone: ---
Assignee: Oliver-Rainer Wittmann
QA Contact:
URL:
Keywords:
: 95975 119645 (view as issue list)
Depends on:
Blocks:
 
Reported: 2012-05-10 13:29 UTC by jspitzer
Modified: 2016-03-22 21:47 UTC (History)
11 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments
screenshot of experimental update notification dialog (63.84 KB, image/jpeg)
2013-02-28 12:30 UTC, Oliver-Rainer Wittmann
no flags Details

Note You need to log in before you can comment on or make changes to this issue.
Description jspitzer 2012-05-10 13:29:15 UTC
I have been using OOo for years and the Help | Check for Updates invariable results in "Fail" messages.  Since OOo can also be set to alter the user that updates are available, that alert will never happen.

I have administrator rights, no firewall is blocking internet access.  The update checking feature just plain does not work!
Comment 1 jspitzer 2012-05-10 13:35:14 UTC
Sorry had some typos that I cannot figure out how to correct. Most important is "alter" should be alert.
Comment 2 Keith Roe 2012-05-11 05:36:53 UTC
I am receiving the same error.  I am also using Windows 7 and I wonder if it might be an issue with OOo on Windows 7.  I get a status of "Checking for internet update failed." with an error of "General Internet error has occurred."
Comment 3 Oliver-Rainer Wittmann 2012-05-11 06:48:28 UTC
The reason for this issue is not Apache OpenOffice respectively OpenOffice.org.
The update service which AOO/OOo wants to contact via HTTP is not working anymore and needs to be reestablished.
When the update service is back the update functionality will be working again.
Comment 4 Oliver-Rainer Wittmann 2012-05-16 06:41:58 UTC
There is also bug 119361 which will be used for bringing back the update service for version AOO 3.4.

The update service for former versions - may be not for all, but at least for OOo 3.3 - will hopefully follow.
Comment 5 Oliver-Rainer Wittmann 2012-05-23 06:52:52 UTC
This issue will be used to bring back the update service for former OOo 3.x (x<4) versions. It will be discussed, if this is needed for all of these versions.
Comment 6 Oliver-Rainer Wittmann 2012-05-23 07:05:43 UTC
*** Issue 95975 has been marked as a duplicate of this issue. ***
Comment 7 sebb 2012-05-24 18:12:09 UTC
From Bug 119361:

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.

==

Regardless of whether the names are still needed or not, it does not seem right for the alias of an openoffice.org host to point to a 3rd party host.

If the alias is still needed, it should be redirected to the appropriate ASF host.

If the alias is not needed, it should be removed.
Comment 8 Oliver-Rainer Wittmann 2012-05-25 13:50:32 UTC
sebb@apache.org:
I agree this you.
I will try to get in contact with ASF infrastructure team. I will ask them about their opinion.

There are some "little" problems:
(1) Once the Update URLs in the former OOo version gets resolved to something, I am not sure which message the update functionality in these versions will reply to the user. I think we need to check this before we redirect these Update URLs.

(2) I am not sure about the amount of traffic which is generated by the update functionality of these versions and if our server can handle it. I think this needs also to be checked.
Comment 9 Marcus 2012-05-28 10:41:43 UTC
*** Issue 119423 has been marked as a duplicate of this issue. ***
Comment 10 sebb 2012-05-28 11:01:05 UTC
(In reply to comment #9)
> *** Bug 119423 has been marked as a duplicate of this bug. ***

Are you sure? That bug appears to be about something else entirely.
Comment 11 jvchbabu 2012-05-28 11:05:23 UTC
(In reply to comment #10)
> (In reply to comment #9)
> > *** Bug 119423 has been marked as a duplicate of this bug. ***
> 
> Are you sure? That bug appears to be about something else entirely.

Yeah.It's differing with context of issue.
Comment 12 Olaf Felka 2012-05-31 18:36:29 UTC
*** Issue 119645 has been marked as a duplicate of this issue. ***
Comment 13 Oliver-Rainer Wittmann 2012-07-06 10:40:48 UTC
Some updates on this issue:
- update service for OOo 3.3 has been established. It is working since 2012-06-14 for all languages and platforms for which we have an AOO 3.4 installation package available.
- update service for OOo 3.2.1 and OOo3.2 for all languages and platforms for which we have an AOO 3.4 installation package available is in progress.
Comment 14 Oliver-Rainer Wittmann 2012-07-06 12:00:33 UTC
(In reply to comment #7)
> 
> [snip]
> 
> Regardless of whether the names are still needed or not, it does not seem
> right for the alias of an openoffice.org host to point to a 3rd party host.
> 
> If the alias is still needed, it should be redirected to the appropriate ASF
> host.
> 
> If the alias is not needed, it should be removed.

I was in contact with ASF infra:
- The pointer to non-apache hosts are our (AOOi PPMC) business. We (AOOi PPMC) can make requests for changes and ASF infra will in general fullfill them.
- Pointer to non-apache hosts are in general no problem.

My view:
We should get rid of all update*.services.openoffice.org which are not needed.
I think we only need the ones for update service of OOo 3.3, OOo 3.2.1 and OOo 3.2.
Comment 15 Oliver-Rainer Wittmann 2012-08-13 12:32:44 UTC
status report:
update service for OOo 3.2, OOo 3.2.1 and OOo 3.3 for the platforms and languages for whose we have an AOO 3.4 release have been established.
Comment 16 Oliver-Rainer Wittmann 2013-02-28 12:30:59 UTC
Created attachment 80370 [details]
screenshot of experimental update notification dialog
Comment 17 orcmid 2015-11-05 19:36:30 UTC
(In reply to Oliver-Rainer Wittmann from comment #15)
> status report:
> update service for OOo 3.2, OOo 3.2.1 and OOo 3.3 for the platforms and
> languages for whose we have an AOO 3.4 release have been established.

This incident was resolved with respect to these distributions of OpenOffice.org that preceded releases from Apache OpenOffice, starting with AOO 3.4.

(It is not known whether these were extended when additional languages were released in subsequent updates of 3.4.)

I am resolving this as fixed with regard to as much as was done for legacy OpenOffice.org distributions.  

Any difficulties with update notices from Apache OpenOffice distributions that fail to find the latest AOO versions should be treated as new incidents and possible defects.