Hi Steve,
Running openacs-4.6.3, aolserver 3.4.2 with the oacs modifications, and
nsopenssl2.1a on freebsd 4 stable, we see the same errors, as well as:
Error: nsopenssl: error -1/1 during SSL handshake
without any problems reported from end-users.
We reboot aolserver once a week which seems to
Hi Torben
On Tue, 2004-10-26 at 11:51, Torben Brosten wrote:
Hi Steve,
Running openacs-4.6.3, aolserver 3.4.2 with the oacs modifications, and
nsopenssl2.1a on freebsd 4 stable, we see the same errors, as well as:
Error: nsopenssl: error -1/1 during SSL handshake
without any problems
At Tuesday 09:59 AM 10/26/2004, John Caruso wrote:
At Monday 01:08 PM 10/25/2004,
Steve wrote:
[-conn17-] Error: nsopenssl: EOF during SSL handshake
[-conn0-] Error: nsopenssl: nsdserver: connection closed by peer
[-conn15-] Error: nsopenssl: error during SSL handshake: Connection
reset by peer
On Tue, 2004-10-26 at 21:25, Torben Brosten wrote:
What hardware are you running this on?
It's in 1 of about 20 VMs on a Dual-III 1.2Ghz, 4Gig RAM server.
Thanks
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to [EMAIL PROTECTED]
I will apply it and remake the module to see if it helps. Thanks. Off hand can you remember what symptoms you saw with your 2.1a problems? Did the server restart? Did you get browser errors? Did it log errors? I'm just trying to see if your problem correlates with mine.
Thanks
Steve
On
At Tuesday 02:58 PM 10/26/2004, Steve wrote:
I will apply it and remake the module to see if it helps. Thanks. Off
hand can you remember what symptoms you saw with your 2.1a problems? Did
the server restart? Did you get browser errors? Did it log errors? I'm
just trying to see if your problem
Hi
We've been running an ecommerce site at http://www.fancydress.com for just over a month now. In that time its handled a little short of 10million hits. The site is running Aolserver 3.3oacs1 with nsopenssl2.1a on openssl-0.9.7b.
Up until today things have been fine but in the last few
On 2004.10.25, Steve [EMAIL PROTECTED] wrote:
They seem to cause a variety of errors in different browsers. I've been
on the receiving end of one of these and in Mozilla it gave a popup
message:
Are you able to reproduce this error on demand? Or is it completely
random?
Unfortunately the
FWIW, I saw those messages too, when I was using nsopenssl2.1, and I
see similar ones using AOLserver 4 and the latest nsopenssl. The only
difference is that I've never had a user complaint related to them, so
I was assuming that they were victimless crimes. Perhaps that is not
the case, though
On Mon, 2004-10-25 at 22:05, Dossy Shiobara wrote:
On 2004.10.25, Steve [EMAIL PROTECTED] wrote:
They seem to cause a variety of errors in different browsers. I've been
on the receiving end of one of these and in Mozilla it gave a popup
message:
Are you able to reproduce this error on
FWIW. I see this same behavior with a similar configuration. The only
differences are that I'm using oracle and am running on Sun Solaris 9.
It gets worse under heavy load. I never get complaints and have never
experienced a 'browser side' problem so I assumed it didn't affect
users. I get at
On Mon, 2004-10-25 at 23:22, Dossy Shiobara wrote:
On 2004.10.25, Steve [EMAIL PROTECTED] wrote:
How large is the nsd process memory footprint? What modules are you
loading? Did you upgrade anything at ALL lately? What OS is this on?
Is it a single front-end host or a farm of them?
On 2004.10.25, Steve [EMAIL PROTECTED] wrote:
jediI felt a disturbance in the force when I originally used AOLs 4
and nsopenssl 3 /jedi so for the launch I switched to 3.3oacs1 and
nsopenssl 2.1a. Its been rock solid up until now and your questions
suggest that you have something in mind.
I
On 2004.08.23, Scott Goodwin [EMAIL PROTECTED] wrote:
I haven't found precisely where this is occurring because I haven't
been able to duplicate the problem yet.
I'm hoping to get my hands on a OSX 10.3.5 box this week to try and
reproduce the problem ... I definitely have not been able to
Hello Dossy,
I finally got AOLServer, nsopenssl both from cvs HEAD, applied your
patch and tried to reproduce the error mentioned before and this time I
get this:
[22/Aug/2004:19:15:15][11703.25202688][-conn:3-] Warning: nsopenssl
(MYSERVER): SSL interrupted, perhaps by client
instead of nsopenssl
Uh ... no, small correction ... the errors that I saw previously on the
error log don't show up but the nsd process takes 100% of the cpu
(according to top) ...
:-( Is there a way that I could check what's happening with nsd? I will
try starting it with ktrace and will report if I can find out
On 2004.08.22, Bruno Mattarollo [EMAIL PROTECTED] wrote:
OK, I have started already twice the server with ktrace (a utility
similar to strace but for Mac OS X)
OK, so you're running on Mac OS X. What version?
and, before I even mention
anything about what I see on the dump file, the
Hello Dossy,
On Aug 22, 2004, at 21:37, Dossy Shiobara wrote:
OK, so you're running on Mac OS X. What version?
Latest, 10.3.5.
If a thread is spinning out of control, it may not process the shutdown
notification right away ... in which case you *could* kill -9 the nsd
which isn't very friendly,
On 2004.08.23, Bruno Mattarollo [EMAIL PROTECTED] wrote:
OK, so you're running on Mac OS X. What version?
Latest, 10.3.5.
What browser are you using to test that you're able to reproduce this
problem with?
It's 70 MB Just for the start and then making it go crazy immediately
after it's up.
Hello again,
On Aug 23, 2004, at 02:10, Dossy Shiobara wrote:
What browser are you using to test that you're able to reproduce this
problem with?
I've tried with:
(from Mac OS X)
Safari 1.2.3 (v125.9)
Firefox 0.9.3
Mozilla 1.7: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.7)
Hello again (yeah, sorry) ...
Trying to debug with DDD and it seems to me that there seem to be a
problem at the following funtions and (see below code):
NsOpenSSLConnOp (in line 664, total and bytes are both 0 -zero-).
632 NsOpenSSLConnOp(SSL *ssl, void *buffer, int bytes, int type)
633 {
On 2004.08.23, Bruno Mattarollo [EMAIL PROTECTED] wrote:
I've tried with:
(from Mac OS X)
Safari 1.2.3 (v125.9)
Firefox 0.9.3
Mozilla 1.7: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.7) Gecko/2004051
(From a Windows XP box)
IE 6.0.2800.1106.xpsp2
Firefox 0.9.2
The
On 2004.08.22, Dossy Shiobara [EMAIL PROTECTED] wrote:
Ah, interesting -- I repeated the test with 4.0.8a and this is the error
in the log:
[22/Aug/2004:23:37:44][27971.1088318384][-conn:server1::2] Debug: SSLOp(15-0):
SSL_ERROR_SSL: bytes = 16000; total = 0; rc = -1
On Aug 23, 2004, at 13:46, Dossy Shiobara wrote:
Even with Firefox from WinXP, you were able to reproduce the problem?
Yes, indeed.
Perhaps this is a MacOS X-specific issue? What version of OpenSSL are
you running? And, what version of nsopenssl 3 -- what's the file
revision on sslcontext.c
Hello again,
I just changed the values of SSLv2 on my configuration yesterday but
haven't yet used the newest AOLServer (with your patch) and I got the
error again (as detailed in my previous messages). What I did, that
triggered the error was click on a link and immediately click on
another link
If you don't need AOLserver to act as a client then simply don't
register a client context. As far as I recall it isn't required.
As for SSL2, I wouldn't trust it for e-commerce myself. I do agree that
if only for clarity that SSL2 should be enabled/disabled in both places.
It is very possible
26 matches
Mail list logo
