On Wed, May 05, 2004 at 08:22:44AM +0200, Bernd Eidenschink wrote:
> I became aware of the mistake, but 'corrected' always the other of
> the two config files I did not use for the server startup...
Oh, I'm sure we've ALL made that sort of "I fixed the wrong file"
mistake sometime, more than once
> > > It might help to post your entire config .tcl and more of the server
> > > log at startup.
> >
> > no, the line for the driver was there, it was another mistake on my side.
> > I was blind, so blind. Sorry. It works now...
>
> Don't keep us in suspense! What was it? :-) It's always good to
To answer my own question:
Q: But why not to 192.168.1.2?
A: Because previously I didn't explicitly specify the IP address in the
nsopnessl driver section. Now that I do, it does work. Even though it
previously inherited the same address from nssock? The log showed that it
tried to bind to 192.
Vlad,
Lo and behold nsopenssl can listen to localhost:443. But why not to
192.168.1.2? To which nsopenssl 2.1 w/ aolserver 3.5 _could_ listen!
/Bart
--
AOLserver - http://www.aolserver.com/
To Remove yourself from this list, simply send an email to <[EMAIL PROTECTED]> with the
body of "SIGNOFF
Can you as an experiment change 443 binding to 127.0.0.1:443 everywhere,
in the command line -b 127.0.0.1:443
and in nsd.tcl
ns_param address 127.0.0.1
ns_param port 443
Bart Teeuwisse wrote:
Vlad,
netstat -anp produces:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Loca
Vlad,
netstat -anp produces:
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
PID/Program name
tcp0 0 127.0.0.1: 0.0.0.0:* LISTEN
1377/nsd
tcp0 0 0.0.0.0:139
What does netstat -anp tell?
or just netstat -an if it does not support -p options
Bart Teeuwisse wrote:
Adding NsWaitDriversStartup() didn't help. The strang thing is that port 80
works fine, just 443 doesn't get permission:
[04/May/2004:12:43:33][1377.1024][-main-] Error: nsopenssl: failed to lis
Hello,
I'm working on a site that uses SSL, and want to redirect users who
access the site via http to https.
The way I've done this in the past is to check ns_conn driver, then
redirect to a hardcoded URL.
However, I would like to be able to do this independent of the system
aolserver is runnin
Adding NsWaitDriversStartup() didn't help. The strang thing is that port 80
works fine, just 443 doesn't get permission:
[04/May/2004:12:43:33][1377.1024][-main-] Error: nsopenssl: failed to listen
on 192.168.1.2:443: Permission denied
[04/May/2004:12:43:33][1377.1024][-main-] Notice: nssock: list
Dossy,
> On 2004.05.03, Fen Tamanaha <[EMAIL PROTECTED]> wrote:
> > Sadly, there's nothing interesting in the logs. Here's the
> end of the
> > error and access logs from the latest hung server:
> >
> > [03/May/2004:17:53:33][31889.9225][-sched:idle1-] Notice: starting
> > [03/May/2004:17:54:28][
On 2004.05.04, Bernd Eidenschink <[EMAIL PROTECTED]> wrote:
> > Where's the line that looks like:
> >
> > ns_param postgres ${bindir}/postgres.so
> >
> > ???
> >
> > It might help to post your entire config .tcl and more of the server
> > log at startup.
>
> no, the line for the driver was ther
> Where's the line that looks like:
>
> ns_param postgres ${bindir}/postgres.so
>
> ???
>
> It might help to post your entire config .tcl and more of the server
> log at startup.
no, the line for the driver was there, it was another mistake on my side.
I was blind, so blind. Sorry. It works no
This could be the prebound/timing issue that Dossy fixed earlier this
year with his NsWaitDriversStartup() fix in the cvs tip. I've attached a
patch that backports this fix if you want to try it. I didn't really
test this so YMMV.
This is diff'ed against AS 4.0.3.
rob
Bart Teeuwisse wrote:
On Mon,
On 2004.05.04, Bernd Eidenschink <[EMAIL PROTECTED]> wrote:
> ns_section "ns/server/${servername}/modules"
> ns_param nssock ${bindir}/nssock.so
> ns_param nslog ${bindir}/nslog.so
> ns_param nsdb ${bindir}/nsdb.so
>
> When starting AOLServer 4.0 I get:
>
> Notice: modload: loading '/ns
Hi,
it must be something simple, but I don't see it:
I placed the nsdb module under the modules-section of the config
file, like:
ns_section "ns/server/${servername}/modules"
ns_param nssock ${bindir}/nssock.so
ns_param nslog ${bindir}/nslog.so
ns_param nsdb ${bindir}/nsdb.so
When s
15 matches
Mail list logo
