And we have plans to fix the issue on the server once 4.1.8 is released for a
week or two.
Sent from my iPhone
> On Oct 8, 2020, at 2:24 PM, Pedro Lino wrote:
>
> Hi John
>
>
>>> On 10/08/2020 8:51 PM John D'Orazio
>>> wrote:
>>
>> Is the
Hi John
> On 10/08/2020 8:51 PM John D'Orazio
> wrote:
> Is the "Check for Updates" function broken by chance? Or is it just me?
> This is on a Windows 10 PC...
It is indeed broken (it has been for some years now) but fortunately it is
already fixed in version 4.1.
for an update failed.
DESCRIPTION: Error reading data from the Internet.
Server error message: .
Is the "Check for Updates" function broken by chance? Or is it just me?
This is on a Windows 10 PC...
--
John R. D'Orazio
Hi Matthias
>
> > > Version 4.1.6 was released one month ago.
> > This problem has not been solved yet (so in theory many users were
> > not notified of this update)
> > Can this be fixed?
> >
> > > It has a smaller impact than I would have expected. We
Hi Pedro,
Am 18.12.18 um 12:23 schrieb Pedro Lino:
> Hi all
>
> Version 4.1.6 was released one month ago.
> This problem has not been solved yet (so in theory many users were not
> notified of this update)
> Can this be fixed?
It has a smaller impact than I would have expected. We do have 2
Hi all
Version 4.1.6 was released one month ago.
This problem has not been solved yet (so in theory many users were not notified
of this update)
Can this be fixed?
Best regards,
Pedro
> On December 7, 2018 at 10:12 PM Peter Kovacs wrote:
>
>
> nope. I am the only one who has currently
nope. I am the only one who has currently access.
On 07.12.18 23:01, Pedro Lino wrote:
>> On December 5, 2018 at 10:01 PM Peter Kovacs wrote:
>>
>> On 05.12.18 08:08, Andrea Pescetti wrote:
>>> If yes, we'll have to look into another environment. If no, we can
>>> reuse one of these two VMs as
> On December 5, 2018 at 10:01 PM Peter Kovacs wrote:
>
> On 05.12.18 08:08, Andrea Pescetti wrote:
> >
> > If yes, we'll have to look into another environment. If no, we can
> > reuse one of these two VMs as the new updates server.
> We could try the OpenGrok Server.
Has this been tested?
On 05.12.18 08:08, Andrea Pescetti wrote:
>
> If yes, we'll have to look into another environment. If no, we can
> reuse one of these two VMs as the new updates server.
We could try the OpenGrok Server.
-
To unsubscribe,
On 12/5/2018 2:08 AM, Andrea Pescetti wrote:
> On 25/11/2018 Andrea Pescetti wrote:
>> It is a matter of virtual machines and policy. The virtual machines we
>> have available for the moment (and one would need to open the URLs
>> with "soffice URL" to check) are:
>> - https://wiki.openoffice.org
> On December 5, 2018 at 7:08 AM Andrea Pescetti wrote:
> Are the current VMs unreachable from the affected systems? I mean, does
>
> $ soffice https://wiki.openoffice.org
> $ soffice https://forum.openoffice.org
>
> give "Server error" from the machine where updates cannot be reached?
Both
> On Dec 4, 2018, at 11:08 PM, Andrea Pescetti wrote:
>
> On 25/11/2018 Andrea Pescetti wrote:
>> It is a matter of virtual machines and policy. The virtual machines we have
>> available for the moment (and one would need to open the URLs with "soffice
>> URL" to check) are:
>> -
On 25/11/2018 Andrea Pescetti wrote:
It is a matter of virtual machines and policy. The virtual machines we
have available for the moment (and one would need to open the URLs with
"soffice URL" to check) are:
- https://wiki.openoffice.org
- https://forum.openoffice.org
-
> On November 25, 2018 at 12:13 PM Matthias Seidel <
> matthias.sei...@hamburg.de mailto:matthias.sei...@hamburg.de > wrote:
>
> No need to download it again as it is already in your profile. Just add
> it by using "Add..."
>
That doesn't work unless you have the oxt file
There
Am 25.11.18 um 13:09 schrieb Pedro Lino:
> Hi Matthias
>
>
>> > > This means that the program is getting version
>> information from the server so some communication is passing through...
>>> > You did a reinstall without deleting the profile? Probably you
>>> updated
>>
Hi Matthias
>
> > > This means that the program is getting version
> information from the server so some communication is passing through...
> >
> > > You did a reinstall without deleting the profile? Probably you
> > updated
> some dictionary before and AOO just
Am 25.11.18 um 11:58 schrieb Pedro Lino:
> Hi Dave, Andrea, all
>
>> Let’s do our required migrations this week and then we can play with this TLS
>> issue. This may be more complex. My concern is whether or not older AOO is
>> even using TLS. Since legacy forums and wiki must be cut over by Nov
Hi Dave, Andrea, all
> Let’s do our required migrations this week and then we can play with this TLS
> issue. This may be more complex. My concern is whether or not older AOO is
> even using TLS. Since legacy forums and wiki must be cut over by Nov 30th we
> must prioritize.
Agreed.
Keep in
Hi -
Sent from my iPhone
> On Nov 24, 2018, at 4:08 PM, Andrea Pescetti wrote:
>
>> On 24/11/2018 Pedro Lino wrote:
>> Any news on this issue? Can this be solved by Infra or by someone
>> on the PMC? I believe this issue should have some priority especially
>> because it affects the Windows
On 24/11/2018 Pedro Lino wrote:
Any news on this issue? Can this be solved by Infra or by someone
on the PMC? I believe this issue should have some priority especially because
it affects the Windows OS users (the vast majority of the users)...
It is a matter of virtual machines and policy.
Any news on this issue? Can this be solved by Infra or by someone
on the PMC? I believe this issue should have some priority especially because
it affects the Windows OS users (the vast majority of the users)...
Regards,
Pedro
> On November 20, 2018 at 10:30 PM Pedro Lino wrote:
>
>
> Hi
Hi Andrea, all
> On November 19, 2018 at 5:17 PM Andrea Pescetti wrote:
> > Can this change be reversed or an exception opened for AOO?
>
> Sure, we have multiple options available. Including moving this server
> to a smaller (or even dedicated) virtual machine. Note that, even if we
> miss
On 19.11.2018 18:17, Andrea Pescetti wrote:
> Pedro Lino wrote:>> On November 19, 2018 at 12:52 AM Branko Čibej wrote:
>>> It looks like you found the real problem:
>>> $ curl -sviI --tlsv1.0 https://ooo-updates.apache.org/
>
> This makes sense, but I still don't understand it as the full
>
> On November 19, 2018 at 5:17 PM Andrea Pescetti wrote:
> Does the current explanation actually explain why the first command
> succeeds on Fedora? (of course, this also reflects in GUI, where the
> check for updates only succeeds on Fedora).
Not at all. If the problem was simply on the
Pedro Lino wrote:>> On November 19, 2018 at 12:52 AM Branko Čibej wrote:
It looks like you found the real problem:
$ curl -sviI --tlsv1.0 https://ooo-updates.apache.org/
This makes sense, but I still don't understand it as the full explanation.
I mean, if this is due to bundled libraries then
On 19.11.2018 10:11, Pedro Lino wrote:
> Hi Brane, all
>
>> On November 19, 2018 at 12:52 AM Branko Čibej wrote:
>>> Does the Apache web server still support TLS version 1.0? The old
>>> version of OpenSSL that we bundle with the Windows and Linux versions
>>> doesn't support anything newer than
Hi Brane, all
> On November 19, 2018 at 12:52 AM Branko Čibej wrote:
> > Does the Apache web server still support TLS version 1.0? The old
> > version of OpenSSL that we bundle with the Windows and Linux versions
> > doesn't support anything newer than that.
>
>
> It looks like you found the
On 18.11.2018 23:30, Don Lewis wrote:
> On 17 Nov, Pedro Lino wrote:
>>> On November 17, 2018 at 5:32 PM Andrea Pescetti wrote:
>>> A nice additional benefit is that this gives us a simple way to
>>> reproduce the bug, equivalent to the update notification.
>>>
>>> $ soffice
On 17 Nov, Pedro Lino wrote:
>> On November 17, 2018 at 5:32 PM Andrea Pescetti wrote:
>
>> A nice additional benefit is that this gives us a simple way to
>> reproduce the bug, equivalent to the update notification.
>>
>> $ soffice https://ooo-updates.apache.org/index.html
>> (this fails on
On 18.11.2018 18:41, Branko Čibej wrote:
> On 18.11.2018 17:19, Andrea Pescetti wrote:
>> Pedro Lino wrote:
>>> However the AOO site does not specify any charset. Could that be the
>>> problem?
>> I don't think the charset is a major issue, but indeed (if I do the
>> same test with openssl) there
On 18.11.2018 17:19, Andrea Pescetti wrote:
> Pedro Lino wrote:
>> However the AOO site does not specify any charset. Could that be the
>> problem?
>
> I don't think the charset is a major issue, but indeed (if I do the
> same test with openssl) there is something interesting that can
> probably
Pedro Lino wrote:
However the AOO site does not specify any charset. Could that be the problem?
I don't think the charset is a major issue, but indeed (if I do the same
test with openssl) there is something interesting that can probably be
submitted to Infra for investigation.
On any
> On November 18, 2018 at 2:48 PM Andrea Pescetti wrote:
> > For debugging, I suggest using cURL instead of OO, for example:
> > curl -sviI https://www.openoffice.org/
>
> Thanks, if the issue is with SSL this indeed helps in finding more
> details. Still, curl will always work also on
Branko Čibej wrote:
Note that all the sites that fail in your list have wildcard
certificates — CN=*.apache.org for the Apache sites and
CN=*.openoffice.org for the OO sites. This may be related to wildcard
cert support
Interesting find, and I was hopeful this could be the solution. But if
> On November 18, 2018 at 12:00 AM Branko Čibej wrote:
> For debugging, I suggest using cURL instead of OO, for example:
>
> curl -sviI https://www.openoffice.org/
The output is below
* Trying 95.216.24.32...
* Connected to www.openoffice.org (95.216.24.32) port 443 (#0)
* found 148
On 17.11.2018 18:32, Andrea Pescetti wrote:
> Dave Fisher wrote:
>> I’ve been on with Infra on HipChat and both servers are the same with
>> the same content internally,
>
> Yes, I don't see this as a major issue either. It is probably too
> early for Infra to jump in, since we haven't identified
>
> $ soffice https://ooo-updates.apache.org/index.html
>
> (this fails on Ubuntu, succeeds on Fedora)
>
> Note that
>
> $ soffice https://www.google.com/
>
> will work in all cases (so this is not an HTTPS bug per se) and
>
> $ soffice http://ooo-updates.apache.org/index.html
>
> will
> On November 17, 2018 at 5:32 PM Andrea Pescetti wrote:
> A nice additional benefit is that this gives us a simple way to
> reproduce the bug, equivalent to the update notification.
>
> $ soffice https://ooo-updates.apache.org/index.html
> (this fails on Ubuntu, succeeds on Fedora)
>
> Note
Just out of interest:
AOO420m1(Build:9800) - Rev. 1844412
2018-10-20_11:36:04 - Rev. 1844412
running on Xubuntu 18.04.1 64 bit (fully updated), all four URLs below work
Rory
On Sat, 17 Nov 2018 18:42:57 +0100
Matthias Seidel wrote:
> Hi Andrea,
>
> Am 17.11.18 um 18:32 schrieb Andrea
Hi Andrea,
Am 17.11.18 um 18:32 schrieb Andrea Pescetti:
> Dave Fisher wrote:
>> I’ve been on with Infra on HipChat and both servers are the same with
>> the same content internally,
>
> Yes, I don't see this as a major issue either. It is probably too
> early for Infra to jump in, since we
Dave Fisher wrote:
I’ve been on with Infra on HipChat and both servers are the same with the same
content internally,
Yes, I don't see this as a major issue either. It is probably too early
for Infra to jump in, since we haven't identified major network-related
issues so far (yes, one of
It is weird.
They checked the logs and since the last log role:
since the last log roll, the 40 box had 3667 hits to aoo415/check.Update and
the 95 box got 6570
Regards,
Dave
> On Nov 17, 2018, at 8:15 AM, Pedro Lino wrote:
>
> Hi Dave
>
>> I’ve been on with Infra on HipChat and both
Hi Dave
> I’ve been on with Infra on HipChat and both servers are the same with the
> same content internally,
But some configuration must be different because one responds to pings and the
other doesn't
> I’m being asked for IP addresses to share so that can see if there is an IP
> ban
Hi -
I’ve been on with Infra on HipChat and both servers are the same with the same
content internally,
I’m being asked for IP addresses to share so that can see if there is an IP ban
happening. There are circumstances where that would happen in only one location.
Regards,
Dave
> On Nov 17,
Hi Pedro,
Am 17.11.18 um 11:26 schrieb Pedro Lino:
>> On November 17, 2018 at 9:56 AM Andrea Pescetti wrote:
>> Another crazy test while at it: you probably know that, if you switch to
>> the OpenOffice dialog windows in Preferences - OpenOffice - General, you
>> can open URLs directly from
> On November 17, 2018 at 9:56 AM Andrea Pescetti wrote:
> Another crazy test while at it: you probably know that, if you switch to
> the OpenOffice dialog windows in Preferences - OpenOffice - General, you
> can open URLs directly from within the application.
I use that feature daily to edit
Am 17.11.18 um 10:56 schrieb Andrea Pescetti:
Pedro Lino wrote:
I don't know if this is relevant but ping to 40.79.78.1 does not work.
I can only send/receive packets to/from 95.216.24.32
the same for me. Ping works only for 95.216.24.32.
This would have been a good clue, but unfortunately
Pedro Lino wrote:
I don't know if this is relevant but ping to 40.79.78.1 does not work. I can
only send/receive packets to/from 95.216.24.32
This would have been a good clue, but unfortunately it is exactly the
same for me (and in my case updates work).
Another crazy test while at it: you
Am 17.11.18 um 01:14 schrieb Dave Fisher:
These IPs are the same as www.apache.org
I can only think that there is something flakey on one of these two.
I would suggest discussing with Infra on Hipchat.
> > $ host ooo-updates.apache.org
>
> ooo-updates.apache.org has address 40.79.78.1
>
Hi -
These IPs are the same as www.apache.org
I can only think that there is something flakey on one of these two.
I would suggest discussing with Infra on Hipchat.
Regards,
Dave
> On Nov 16, 2018, at 3:36 PM, Pedro Lino wrote:
>
> Hi Andrea, all
>
> I don't know if this is relevant but
Hi Andrea, all
I don't know if this is relevant but ping to 40.79.78.1 does not work. I can
only send/receive packets to/from 95.216.24.32
Regards,
Pedro
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For
Hi Andrea,
Am 16.11.18 um 23:40 schrieb Andrea Pescetti:
> Pedro Lino wrote:
>> Can you check the logs on the server if it received any pings from
>> 4.1.4?
>
> I don't have access to server logs or any kind of statistics; but I
> recall someone (Matthias?) monitoring how much traffic we got from
Pedro Lino wrote:
Can you check the logs on the server if it received any pings from 4.1.4?
I don't have access to server logs or any kind of statistics; but I
recall someone (Matthias?) monitoring how much traffic we got from older
versions, so maybe someone has access to them.
Regards,
Hi Andrea, Branko, all
> On November 16, 2018 at 8:25 PM Andrea Pescetti wrote:
> Just restart OpenOffice after each edit and check if now the update
> server can be found. Then you should go back to the original version of
> the file to avoid that further testing is influenced by the change.
Branko Čibej wrote:
I tried this today, just for fun. My curl etc. used the same IPv4 address
as the other published results. Maybe the OO updater picks the other server
and only that one has problems?
In my tests yesterday I tried with both IPs (one at a time) in my hosts
file and both
On Fri, 16 Nov 2018, 17:02 Andrea Pescetti Pedro Lino wrote:
> >> On November 16, 2018 at 11:54 AM Andrea Pescetti wrote:
> >> $ curl https://ooo-updates.apache.org/aoo416/check.Update
> >
> >
> >
> > http://installation.openoffice.org/description;>
> >
>
> The network diagnostics are
> On November 16, 2018 at 4:02 PM Andrea Pescetti wrote:
> In particular, the last output above shows that you can successfully
> download the update feed to your computer. You can replace "416" in the
> URL with the OpenOffice version you are actually running if you wish to
> be 100% sure.
Pedro Lino wrote:
On November 16, 2018 at 11:54 AM Andrea Pescetti wrote:
$ curl https://ooo-updates.apache.org/aoo416/check.Update
http://installation.openoffice.org/description;>
The network diagnostics are absolutely perfect (the fact that ncat had
to be terminated meant that it had
> On November 16, 2018 at 11:54 AM Andrea Pescetti wrote:
> Can you provide output of the following commands?
>
> $ host ooo-updates.apache.org
ooo-updates.apache.org has address 40.79.78.1
ooo-updates.apache.org has address 95.216.24.32
ooo-updates.apache.org has IPv6 address
Pedro Lino wrote:
I receive the error message daily on any computer I use,regardless of location,
AOO version or OS (Windows 7 or Ubuntu)
This happens with a fresh profile or any profile.
OK, let's try with Ubuntu (but you can run the equivalent commands on
Windows too).
Can you provide
Hi Andrea, all
> On November 16, 2018 at 12:10 AM Andrea Pescetti wrote:
> If someone can provide a predictable way to reproduce the issue
> consistently, solving it will likely be trivial.
I receive the error message daily on any computer I use,regardless of location,
AOO version or OS
On 15/11/2018 Pedro Lino wrote:
Any news on fixing the "Checking for an update failed." problem?
I was never able to reproduce it. Any time I believed I had reproduced
it, I found out it was due to local DNS caching on my system (something
that is not common for an ordinary user to do).
Hi all
Any news on fixing the "Checking for an update failed." problem?
Regards,
Pedro
63 matches
Mail list logo
