Re: [AOLSERVER] Fatal error laoding aolserver4-nssha1

2013-05-22 Thread Iuri Sampaio

Hi,

So far I resolved the issues. I made a few work around that I believe 
it's worthwhile sharing here:


As previous emails I got errors with aolserver4-core, 
aolserver4-nspostgres, aolserver4-nssha1 and libthread2.7.0


To fix errors of aolserver4* I did the following:

1. I installed them using ubuntu 12.04 precise pangolin offical repos.
apt-get install aolserver4-core aolserver4-nssha1 aolserver-nspostgres

2. Once them installed, I downloaded .deb pkgs from an older version and 
placed them within /usr/local/src/ for instance.
Not that old versions. I didn't want to miss too much of new code from 
possible new releases that would have come with ubuntu precise.
I haven't checked if their packages were update from lucid to precise. 
I'm hoping they weren't.


http://packages.ubuntu.com/lucid/web/aolserver4-core 
<http://packages.ubuntu.com/lucid/amd64/aolserver4-core/download>

http://packages.ubuntu.com/lucid/web/aolserver4-nspostgres
http://packages.ubuntu.com/lucid/web/aolserver4-nssha1 
<http://packages.ubuntu.com/lucid/web/aolserver4-nspostgres>



3. Then I extracted their files by running dpkg -x  and 
copied *.so libs over their respective at /usr/lib/aolserver4/bin and 
/usr/lib/aolserver4/lib.  (*** I replaced their libs with *.so old 
versions.)


4. Then I copied the whole directory /usr/share/aolserver4 I have in 
another machine and created the symbolic link within 
/usr/lib/aolserver4/include to /usr/share/aolserver4/include



5. After all that, I was able to compile and install tcl libthread2.6.5.

6. And Aolserver4.5 loaded up with no errors at error.log.
http://experiences.planetnatopia.com

7. Then I gave a deep last breath and told to myself: "What a mess!"


Best wishes,
Iuri Sampaio




On 05/22/2013 10:09 PM, Iuri Sampaio wrote:

Gustaf,

The situation is even worst.

I went further in the analyzing aolserver4-* packages. So far, I found 
problems on aolserver4-nspostgres and aolserver4-core.



aolserver4-core installation via apt-get doesn't create required 
folder and files


/usr/share/aolserver4/
/usr/share/aolserver4/ns.mak
/usr/share/aolserver4/nsmakeall.tcl
/usr/share/aolserver4/nsremove.tcl
/usr/share/aolserver4/debian.substvars
/usr/share/aolserver4/Makefile.module
/usr/share/aolserver4/include/
/usr/share/aolserver4/include/nsdb.h
/usr/share/aolserver4/include/nsattributes.h
/usr/share/aolserver4/include/nspd.h
/usr/share/aolserver4/include/nsthread.h
/usr/share/aolserver4/include/nsextmsg.h
/usr/share/aolserver4/include/ns.h
/usr/share/aolserver4/Makefile.global
/usr/share/aolserver4/nsinstall.tcl



Furthermore, aolserver4-nspostgres has error when booting up 
aolserver. Similar to what happened to aolserver4-nssha1. There are 
errors within nspostgres.so. I believe it wasn't properly compiled to 
a .deb pkg as well


8:15:44][31887.18446744073291147008][-main-] Notice: modload: loading 
'/usr/lib/aolserver4/bin/nspostgres.so'
[22/May/2013:18:15:44][31887.18446744073291147008][-main-] Warning: 
modload: could not find Ns_DbDriverInit in 
/usr/lib/aolserver4/bin/nspostgres.so
[22/May/2013:18:15:44][31887.18446744073291147008][-main-] Error: 
dbdrv: failed to load driver 'postgres'
[22/May/2013:18:15:44][31887.18446744073291147008][-main-] Error: 
dbinit: no such default pool 'pool1'

[



The best is whether to stick with the  painful installation from 
source or be under old debian versions


Best wishes,




On 05/19/2013 10:37 PM, Iuri Sampaio wrote:

Hi there,

In attempt to install OpenACS from scratch on ubuntu precise 12.04 I 
got the following error on aolserver4-nssha1. "could not find 
Ns_ModuleInit"


When I start up aolserver service I get a warning then a fatal error 
as decribed bellow:


[19/May/2013:19:27:15][18052.714974976][-main-] Notice: modload: 
loading '/usr/lib/aolserver4/bin/nssha1.so'
[19/May/2013:19:27:15][18052.714974976][-main-] Warning: modload: 
could not find Ns_ModuleInit in /usr/lib/aolserver4/bin/nssha1.so
[19/May/2013:19:27:15][18052.714974976][-main-] Fatal: modload: 
failed to load module '/usr/lib/aolserver4/bin/nssha1.so'



I verified that both files are correctly in place
/usr/lib/aolserver4/bin/nssha1.so
/usr/lib/aolserver4/lib/libnssha1.so

Furthermore, I installed aolserver packages via apt-get

I believe the package available on ubuntu repository was compiled 
without Ns_ModuleInit block.


Although, I'm reluctant to believe so I removed nssha1 and installed 
again fro tarball and the problem was solved.


Does anyone have any idea what it could be?
or if my assumption is valid?

Best wishes,
Iuri




--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor 

Re: [AOLSERVER] Fatal error laoding aolserver4-nssha1

2013-05-22 Thread Iuri Sampaio
Gustaf,

The situation is even worst.

I went further in the analyzing aolserver4-* packages. So far, I found 
problems on aolserver4-nspostgres and aolserver4-core.


aolserver4-core installation via apt-get doesn't create required folder 
and files

/usr/share/aolserver4/
/usr/share/aolserver4/ns.mak
/usr/share/aolserver4/nsmakeall.tcl
/usr/share/aolserver4/nsremove.tcl
/usr/share/aolserver4/debian.substvars
/usr/share/aolserver4/Makefile.module
/usr/share/aolserver4/include/
/usr/share/aolserver4/include/nsdb.h
/usr/share/aolserver4/include/nsattributes.h
/usr/share/aolserver4/include/nspd.h
/usr/share/aolserver4/include/nsthread.h
/usr/share/aolserver4/include/nsextmsg.h
/usr/share/aolserver4/include/ns.h
/usr/share/aolserver4/Makefile.global
/usr/share/aolserver4/nsinstall.tcl



Furthermore, aolserver4-nspostgres has error when booting up aolserver. 
Similar to what happened to aolserver4-nssha1. There are errors within 
nspostgres.so. I believe it wasn't properly compiled to a .deb pkg as well

8:15:44][31887.18446744073291147008][-main-] Notice: modload: loading 
'/usr/lib/aolserver4/bin/nspostgres.so'
[22/May/2013:18:15:44][31887.18446744073291147008][-main-] Warning: 
modload: could not find Ns_DbDriverInit in 
/usr/lib/aolserver4/bin/nspostgres.so
[22/May/2013:18:15:44][31887.18446744073291147008][-main-] Error: dbdrv: 
failed to load driver 'postgres'
[22/May/2013:18:15:44][31887.18446744073291147008][-main-] Error: 
dbinit: no such default pool 'pool1'
[



The best is whether to stick with the  painful installation from source 
or be under old debian versions

Best wishes,




On 05/19/2013 10:37 PM, Iuri Sampaio wrote:
> Hi there,
>
> In attempt to install OpenACS from scratch on ubuntu precise 12.04 I 
> got the following error on aolserver4-nssha1. "could not find 
> Ns_ModuleInit"
>
> When I start up aolserver service I get a warning then a fatal error 
> as decribed bellow:
>
> [19/May/2013:19:27:15][18052.714974976][-main-] Notice: modload: 
> loading '/usr/lib/aolserver4/bin/nssha1.so'
> [19/May/2013:19:27:15][18052.714974976][-main-] Warning: modload: 
> could not find Ns_ModuleInit in /usr/lib/aolserver4/bin/nssha1.so
> [19/May/2013:19:27:15][18052.714974976][-main-] Fatal: modload: failed 
> to load module '/usr/lib/aolserver4/bin/nssha1.so'
>
>
> I verified that both files are correctly in place
> /usr/lib/aolserver4/bin/nssha1.so
> /usr/lib/aolserver4/lib/libnssha1.so
>
> Furthermore, I installed aolserver packages via apt-get
>
> I believe the package available on ubuntu repository was compiled 
> without Ns_ModuleInit block.
>
> Although, I'm reluctant to believe so I removed nssha1 and installed 
> again fro tarball and the problem was solved.
>
> Does anyone have any idea what it could be?
> or if my assumption is valid?
>
> Best wishes,
> Iuri


--
Try New Relic Now & We'll Send You this Cool Shirt
New Relic is the only SaaS-based application performance monitoring service 
that delivers powerful full stack analytics. Optimize and monitor your
browser, app, & servers with just a few lines of code. Try New Relic
and get this awesome Nerd Life shirt! http://p.sf.net/sfu/newrelic_d2d_may
___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk


[AOLSERVER] Fatal error laoding aolserver4-nssha1

2013-05-19 Thread Iuri Sampaio
Hi there,

In attempt to install OpenACS from scratch on ubuntu precise 12.04 I got
the following error on aolserver4-nssha1. "could not find Ns_ModuleInit"

When I start up aolserver service I get a warning then a fatal error as
decribed bellow:

[19/May/2013:19:27:15][18052.714974976][-main-] Notice: modload: loading
'/usr/lib/aolserver4/bin/nssha1.so'
[19/May/2013:19:27:15][18052.714974976][-main-] Warning: modload: could not
find Ns_ModuleInit in /usr/lib/aolserver4/bin/nssha1.so
[19/May/2013:19:27:15][18052.714974976][-main-] Fatal: modload: failed to
load module '/usr/lib/aolserver4/bin/nssha1.so'


I verified that both files are correctly in place
/usr/lib/aolserver4/bin/nssha1.so
/usr/lib/aolserver4/lib/libnssha1.so

Furthermore, I installed aolserver packages via apt-get

I believe the package available on ubuntu repository was compiled without
Ns_ModuleInit block.

Although, I'm reluctant to believe so I removed nssha1 and installed again
fro tarball and the problem was solved.

Does anyone have any idea what it could be?
or if my assumption is valid?

Best wishes,
Iuri
--
AlienVault Unified Security Management (USM) platform delivers complete
security visibility with the essential security capabilities. Easily and
efficiently configure, manage, and operate all of your security controls
from a single console and one unified framework. Download a free trial.
http://p.sf.net/sfu/alienvault_d2d___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk


Re: [AOLSERVER] qsset argument within ns_httpspost

2013-03-17 Thread Iuri Sampaio
So far,

The dummy mistake was in the curly braquets.

set result [ns_httpspost "https://acesso.uol.com.br/login.html"; {} {$qsset}
{} {} 30 {}]

After I took them out it worked fine.

set result [ns_httpspost "https://acesso.uol.com.br/login.html"; {} $qsset
{} {} 30 {}]


I can connect through and the post result the session code value
"
http://mail.uol.com.br/login/doorway?_webmail_session_id=clllcUdVWnh4QURMNWpjaGlublUyeWtKNndCUDkraC9VMlZWcjk3MFdVQ0RoNERsL1JBK3lkVWJYMEtTZ0l1T09YSWxLZzlwWFA3T25ZbG1ITHJuRVFIWVRxcG9LNE9USCs2TlZsNmxPZFZaaFZqOG5BSzJWSXk2YmlCbm41ZnItLUVWVFdPKzRjRXpHaStWZmo3aTJ0MHc9PQ
"


Now, I have a problem with requesting data I need. With the result of
httpspost I create  new ns_set and tried to get the http result:

set qsset [ns_set create qsset $url $arg]
set result [ns_httpget "http://mail.uol.com.br/addressbook"; 30 0 $qsset]

But somehow if kicks me out telling the session was expired.

Is there a way to keep connected not loosing the auths values and sessions
variables and then get the data I need?


Cheers,
Iuri


On Sun, Mar 17, 2013 at 8:58 AM, Iuri Sampaio wrote:

> Hi there,
>
> I created the code bellow that calls httpspost to authenticates against a
> https url with a few arguments (user, password, skin, dest). In order to
> pass arguments through via post they must be within a set structure.
>
> *** I believe I didn't even need  the first line becasue ns_getform
> already returns the identical set structure needed as argument for qsset on
> httpspost. However I added it just to stay o the right side.  The TCL
> script is bellow.
>
> ## script.tcl
>
> ns_set create qsset [ns_getform]
>
> set result [ns_httpspost "https://acesso.uol.com.br/login.html"; {}
> {$qsset} {multipart/form-data} {} {30} {}]
>
> ##
>
>
> However [ns_httpspost] returns an error  regarding the  command [ns_set
> size $qsset] at line 250
>
> [17/Mar/2013:11:42:46][30452.3039562608][-default:10-] Error: POST
> http://206.192.23.166:8050/natopia-core/invite/invite-uol?
> referred by "
> http://natopia.iurix.com/natopia-core/invite/invite-emails.html";
> no such set: $qsset
> while executing
> "ns_set size $qsset"
> (procedure "ns_httpspost" line 46)
> invoked from within
> "ns_httpspost "https://acesso.uol.com.br/login.html"; {} {$qsset}
> {multipart/form-data} {} {30} {}"
> invoked from within
> "set result [ns_httpspost "https://acesso.uol.com.br/login.html"; {}
> {$qsset} {multipart/form-data} {} {30} {}]"
> ("uplevel" body line 38)
> invoked from within
> "uplevel {
> ad_page_contract {}
>
>
>
> I went to ns_httpspost source code and I placed a ns_log within it.
>
> ns_log Notice "$url \n $rqset \n $qsset \n $type "
>
> Curiously It doesn't show the content of qsset but its label "$qsset"
>
> [17/Mar/2013:11:42:46][30452.3039562608][-default:10-] Notice:
> https://acesso.uol.com.br/login.html
>
>  $qsset
>  multipart/form-data
> [17/Mar/2013:11:42:46][30452.3039562608][-default:10-] Warn...
>
>
> Does it have any relation with the error?
> How do I make qsset variable to be recognizable within the procedure
> ns_httpspost
>
>
> Cheers,
> Iuri
>
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk


[AOLSERVER] qsset argument within ns_httpspost

2013-03-17 Thread Iuri Sampaio
Hi there,

I created the code bellow that calls httpspost to authenticates against a
https url with a few arguments (user, password, skin, dest). In order to
pass arguments through via post they must be within a set structure.

*** I believe I didn't even need  the first line becasue ns_getform already
returns the identical set structure needed as argument for qsset on
httpspost. However I added it just to stay o the right side.  The TCL
script is bellow.

## script.tcl

ns_set create qsset [ns_getform]

set result [ns_httpspost "https://acesso.uol.com.br/login.html"; {} {$qsset}
{multipart/form-data} {} {30} {}]

##


However [ns_httpspost] returns an error  regarding the  command [ns_set
size $qsset] at line 250

[17/Mar/2013:11:42:46][30452.3039562608][-default:10-] Error: POST
http://206.192.23.166:8050/natopia-core/invite/invite-uol?
referred by "http://natopia.iurix.com/natopia-core/invite/invite-emails.html
"
no such set: $qsset
while executing
"ns_set size $qsset"
(procedure "ns_httpspost" line 46)
invoked from within
"ns_httpspost "https://acesso.uol.com.br/login.html"; {} {$qsset}
{multipart/form-data} {} {30} {}"
invoked from within
"set result [ns_httpspost "https://acesso.uol.com.br/login.html"; {}
{$qsset} {multipart/form-data} {} {30} {}]"
("uplevel" body line 38)
invoked from within
"uplevel {
ad_page_contract {}



I went to ns_httpspost source code and I placed a ns_log within it.

ns_log Notice "$url \n $rqset \n $qsset \n $type "

Curiously It doesn't show the content of qsset but its label "$qsset"

[17/Mar/2013:11:42:46][30452.3039562608][-default:10-] Notice:
https://acesso.uol.com.br/login.html

 $qsset
 multipart/form-data
[17/Mar/2013:11:42:46][30452.3039562608][-default:10-] Warn...


Does it have any relation with the error?
How do I make qsset variable to be recognizable within the procedure
ns_httpspost


Cheers,
Iuri
--
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_mar___
aolserver-talk mailing list
aolserver-talk@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/aolserver-talk


Re: [AOLSERVER] SSL connection error

2012-06-20 Thread Iuri Sampaio
Of course

ns_section "ns/server/${server}/module/nsopenssl"

# this is used by acs-tcl/tcl/security-procs.tcl to get the https port.
ns_param ServerPort$httpsport
# setting maxinput higher than practical may leave the server
vulnerable to resource DoS attacks
# see http://www.panoptic.com/wiki/aolserver/166
# must set maxinput for nsopenssl as well as nssock
ns_param   maxinput   [expr {$max_file_upload_mb * 1024 *
1024}] ;# Maximum File Size for uploads in bytes

# We explicitly tell the server which SSL contexts to use as defaults
when an
# SSL context is not specified for a particular client or server SSL
# connection. Driver connections do not use defaults; they must be
explicitly
# specificied in the driver section. The Tcl API will use the defaults
as there
# is currently no provision to specify which SSL context to use for a
# particular connection via an ns_openssl Tcl command.
ns_section "ns/server/${server}/module/nsopenssl/sslcontexts"
ns_param users"SSL context used for regular user access"
# ns_param admins   "SSL context used for administrator access"
ns_param client   "SSL context used for outgoing script socket
connections"

ns_section "ns/server/${server}/module/nsopenssl/defaults"
ns_param server   users
ns_param client   client

ns_section "ns/server/${server}/module/nsopenssl/sslcontext/users"
ns_param Role  server
ns_param ModuleDir ${serverroot}/etc/certs
#ns_param CertFile  users-certfile.pem
ns_param CertFile  cnauto-cert.pem
#ns_param KeyFile   users-keyfile.pem
ns_param KeyFile   cnauto-key.pem
 # CADir/CAFile can be commented out, if CA chain cert is appended to
CA issued server cert.
ns_param CADir ${serverroot}/etc/certs
#ns_param CADir
/usr/local/src/nsopenssl-3.0beta26/ca/ca1/
#   ns_param CAFileusers-ca.crt
ns_param CAFileca1.pem
 # for Protocols"ALL" = "SSLv2, SSLv3, TLSv1"
ns_param Protocols "SSLv3, TLSv1"
ns_param CipherSuite
"ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP"
ns_param PeerVerifyfalse
ns_param PeerVerifyDepth   3
ns_param Trace false

# following helps to stablize some openssl connections from buggy
clients.
ns_param SessionCache true
ns_param SessionCacheID 1
ns_param SessionCacheSize 512
ns_param SessionCacheTimeout 300

ns_section "ns/server/${server}/module/nsopenssl/sslcontext/client"
ns_param Role  client
ns_param ModuleDir ${serverroot}/etc/certs
ns_param CertFile  cnauto-cert.pem
ns_param KeyFile   cnauto-key.pem
# CADir/CAFile can be commented out, if CA chain cert is appended to CA
issued server cert.
ns_param CADir ${serverroot}/etc/certs
ns_param CAFileca1.pem
# for Protocols"ALL" = "SSLv2, SSLv3, TLSv1"
ns_param Protocols "SSLv2, SSLv3, TLSv1"
ns_param CipherSuite
"ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP"
ns_param PeerVerifyfalse
ns_param PeerVerifyDepth   3
ns_param Trace false



On Wed, Jun 20, 2012 at 2:01 AM, Sep Ng  wrote:

> My guess is it has something to do with your keys and certificates,
> maybe.  Maybe you should post relevant sections of your config.tcl.
>
>
> On Monday, June 18, 2012 8:11:18 PM UTC+8, Iuri Sampaio wrote:
>>
>> Hi there,
>>
>> After setting up nsopenssl on aolserver I got the following error.
>>
>>
>>
>>  SSL connection error
>> Unable to make a secure connection to the server. This may be a problem
>> with the server, or it may be requiring a client authentication certificate
>> that you don't have.
>>  Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.
>>
>>
>>
>> Though, 1) config.tcl is properly set
>> 2) paths and permissions are properly set
>> 3) and logs show the libs and certs were loaded sucessfully
>>
>>
>> [17/Jun/2012:20:20:45][30618.
>> 3074823872][-main-] Notice: modload: loading '/usr/lib/aolserver4/bin/**
>> nssha1.so'
>> [17/Jun/2012:20:20:45][30618.**3074823872][-main-] Notice: modload:
>> loading '/usr/lib/aolserver4/bin/**nsopenssl-3.0/nsopenssl.so'
>> [17/Jun/2012:20:20:45][30618.**3074823872][-main-] Notice: nsopenssl:
>> generating 512-bit temporary RSA key ...
>> [17/Jun/2012:20:20:45][30618.**3074823872

[AOLSERVER] SSL connection error

2012-06-19 Thread Iuri Sampaio
Hi there,

After setting up nsopenssl on aolserver I got the following error.



SSL connection error
Unable to make a secure connection to the server. This may be a problem
with the server, or it may be requiring a client authentication certificate
that you don't have.
Error 107 (net::ERR_SSL_PROTOCOL_ERROR): SSL protocol error.



Though, 1) config.tcl is properly set
2) paths and permissions are properly set
3) and logs show the libs and certs were loaded sucessfully


[17/Jun/2012:20:20:45][30618.
3074823872][-main-] Notice: modload: loading
'/usr/lib/aolserver4/bin/nssha1.so'
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: modload: loading
'/usr/lib/aolserver4/bin/nsopenssl-3.0/nsopenssl.so'
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl:
generating 512-bit temporary RSA key ...
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl:
generating 1024-bit temporary RSA key ...
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): loading SSL context 'users'
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'users' ciphers loaded successfully
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'users' using SSLv3 protocol
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'users' using TLSv1 protocol
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'users' certificate and key loaded successfully
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'users' CA file loaded successfully
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: users (nsopenssl):
session cache is turned on for sslcontext 'cnauto'
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): loading SSL context 'client'
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'client' ciphers loaded successfully
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'client' using SSLv2 protocol
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'client' using SSLv3 protocol
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'client' using TLSv1 protocol
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'client' certificate and key loaded successfully
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): 'client' CA file loaded successfully
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: client
(nsopenssl): session cache is turned on for sslcontext 'cnauto'
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): default SSL context for server is users
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: default server SSL
context: users
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): default SSL context for client is client
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: default client SSL
context: client
[17/Jun/2012:20:20:45][30618.3074823872][-main-] Notice: nsopenssl
(cnauto): loading 'users' SSL driver
...
[17/Jun/2012:20:20:56][30618.3052837744][-nsopenssl:driver-] Notice:
starting
[17/Jun/2012:20:20:56][30618.3052837744][-nsopenssl:driver-] Notice:
nsopenssl: listening on 127.0.0.1:8443
###


I believe the error is related to the 'client'  certificate.  Before I got
the error:



[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): loading SSL context 'client'
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): 'client' ciphers loaded successfully
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): 'client' using SSLv2 protocol
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): 'client' using SSLv3 protocol
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): 'client' using TLSv1 protocol
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Error: nsopenssl (cnauto):
'client' certificate file is not readable or does not exist
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Error: nsopenssl (cnauto):
SSL context 'client' left uninitialized
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): default SSL context for server is users
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: default server SSL
context: users
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): default SSL context for client is client
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: default client SSL
context: client
[17/Jun/2012:20:00:42][30405.3074971328][-main-] Notice: nsopenssl
(cnauto): loading 'users' SSL driver
#

Then I changed the 'client' cert's paths within config.tcl to the same of
users



Would that be the issue?

Best wishes,
Iuri
--
Li