On Fri, 2004-06-04 at 17:51, Dossy wrote:
> On 2004.06.04, Ross Simpson <[EMAIL PROTECTED]> wrote:
> >
> > Perhaps something is wrong with the way I've split out the
> > configuration into separate files, or the order that the files /
> > modules are sourced in?
>
> I'd try to rule this out by removing all the other modules *except*
> nssock (remove nscp, nsopenssl, nsdb and nsmysql) and see if you can
> still reproduce the problem.
>
> If the problem goes away, then you know where to start looking -
> reintroduce the modules one by one until you figure out which one is
> giving you grief.
>
> If you STILL have the problem after removing all modules except for
> nssock, then maybe we need to look at the file you're uploading and/or
> the ADP page or registered proc code that you're using to receive it
> with on the server.
>
> -- Dossy
Ok. I just installed a fresh copy of aolserver4. No modules loaded
aside from nssock, and it works great -- 5 meg file, 10 meg file both
upload without problems.
Here's the code I'm posting to:
if [ns_queryexists file] {
set tmpname [ns_queryget file.tmpfile]
ns_log debug "tmpname: $tmpname"
file rename -force $tmpname "/tmp/upload.tmp"]
}
As soon as I enable the nsopenssl module and try to upload via https,
the problem shows up again.
I enabled the 'Trace' parameter in nsopenssl, and here's what it spit
out:
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 256 secs: before/accept initialization
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 513 secs: before/accept initialization
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 655 secs: SSLv3 read client hello A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 390 secs: SSLv3 write server hello A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 1701 secs: SSLv3 write change cipher
spec A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 737 secs: SSLv3 write finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 193 secs: SSLv3 flush data
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 126 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 159 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 228 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 267 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 333 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 331 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 208 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 242 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 277 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 182 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 1096 secs: SSLv3 read finished A
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 241 secs: SSL negotiation finished
successfully
[07/Jun/2004:11:52:59][29689.8][-conn:server1::0] Notice: nsopenssl
(server1): trace (0xc94e8): 97 secs: SSL negotiation finished
successfully
I don't know exactly what's going on here, but there don't appear to be
any glaring errors in this code.
The browser spins and spins (I left it for over 30 minutes, and I have a
100 mbit/s connection to this server -- plenty of time for it to upload.
Notice that the ns_log output does not appear -- the file did not ever
finish uploading.
Are there other debugging parameters I can enable?
Thanks again,
Ross
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF AOLSERVER" in the email message. You can leave the Subject: field of
your email blank.
