Hi,
Just FYO - I've been having troubles to download any patch from SunSolve
in the last 5-6 hours. I assume it's a general problem with the server
once again.
Martin.
Same here, having issues only via PCA. Can download via web browser. But
trying to download 160+ patches via http is not fun.
-GGR
--
Rajiv G Gunja
Blog: http://ossrocks.blogspot.com
On Mon, Aug 30, 2010 at 06:49, Martin Paul wrote:
> Hi,
>
> Just FYO - I've been having troubles to download an
Same here, it seems that only https is not working (wget and browser, same
result).
thomas
Am 30.08.2010 um 12:49 schrieb Martin Paul:
> Hi,
>
> Just FYO - I've been having troubles to download any patch from SunSolve in
> the last 5-6 hours. I assume it's a general problem with the server onc
And here we go again. Can't even get patchdiag.xref this time:
Resolving sunsolve.sun.com... 192.18.108.40
Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
^C
Martin.
I'll follow up Martin.
Thanks for letting me know.
Best,
-Don
Martin Paul wrote:
And here we go again. Can't even get patchdiag.xref this time:
Resolving sunsolve.sun.com... 192.18.108.40
Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
^C
Martin.
I'm seeing an issue with one of the backend load-balanced download servers.
Very few people should be impacted.
I'll get it resolved asap.
Best,
-Don
Don O'Malley wrote:
I'll follow up Martin.
Thanks for letting me know.
Best,
-Don
Martin Paul wrote:
And here we go again. Can't even get
Martin Paul wrote:
And here we go again. Can't even get patchdiag.xref this time:
Resolving sunsolve.sun.com... 192.18.108.40
Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
^C
Martin.
This worked (changed protocol back from https to http @ SunSolve)
(certificate PEM f
> And here we go again. Can't even get patchdiag.xref this time:
>
>Resolving sunsolve.sun.com... 192.18.108.40
>Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
>^C
>
> Martin.
I was able to get patchdiag.xref but not one single patch.
I say we organize a class action
Hi Bernd,
Changing the protocol from http to https will usually cause you top be
redirected to a different back-end SunSolve server, so this is why you
may see https fail, but subsequent http requests pass.
The offending server in this case has now been fixes and so the issue
should be resol
Dennis Clarke wrote:
Personally I paid money for my support and if I can not get a damn patch
that is a breech of contract.
I understand your anger, but I'm afraid that the most probable reaction
to that would be an immediate stop of Oracle's support for the automatic
hands-off patch download
Hi Dennis,
Are you still seeing patch download fails?
If so, could you send on an example of a failing patch download request
please?
Thanks!
-Don
Dennis Clarke wrote:
And here we go again. Can't even get patchdiag.xref this time:
Resolving sunsolve.sun.com... 192.18.108.40
The problem here, that the suits in the offices at Oracle do not get, is
that this was a long weekend. Long weekends are when production servers
often get admin work done because you have some downtime. The weekend was
screwed up and time lost because, as usual, Oracle has failed to deliver
on a v
> Dennis Clarke wrote:
>> Personally I paid money for my support and if I can not get a damn patch
>> that is a breech of contract.
>
> I understand your anger, but I'm afraid that the most probable reaction
> to that would be an immediate stop of Oracle's support for the automatic
> hands-off pat
Martin Paul wrote:
>Resolving sunsolve.sun.com... 192.18.108.40
>Connecting to sunsolve.sun.com|192.18.108.40|:443... connected.
Download issues seem to be quite often caused by one or more servers
behind the sunsolve.sun.com load balancer being unresponsive. AFAIK when
you first connect s
14 matches
Mail list logo
