[Modules] [mod_gnutls] Keep-Alive possible?

Hardy Griech ntbox at mardys.de
Thu Sep 23 05:22:54 EDT 2010


On 22.09.2010 22:48, Nikos Mavrogiannopoulos wrote:
> On 09/22/2010 10:13 PM, Hardy Griech wrote:
:
>> Both "DB" and "DEFAULT" generate a file with '/tmp-ram/gnutls: Berkeley
>> DB (Hash, version 9, native byte-order)'
>
> Does the DB have problems with many connections (e.g. when using siege
> on the webserver)?. I had issues with that and that's why I made sdbm
> the default.
:

Autsch, it seems that - even without GnuTLSCache configured - siege has 
or generates errors:

[Thu Sep 23 11:07:41 2010] [notice] SIGHUP received.  Attempting to restart
[Thu Sep 23 11:07:41 2010] [notice] Apache/2.2.16 (Debian) DAV/2 
mod_gnutls/0.5.8 configured -- resuming normal operations
[Thu Sep 23 11:07:41 2010] [info] Server built: Aug 29 2010 14:59:54
[Thu Sep 23 11:07:41 2010] [debug] worker.c(1757): AcceptMutex: sysvsem 
(default: sysvsem)
[Thu Sep 23 11:07:41 2010] [crit] [GnuTLS] - No Cache Configured. Hint: 
GnuTLSCache
[Thu Sep 23 11:07:41 2010] [crit] [GnuTLS] - No Cache Configured. Hint: 
GnuTLSCache
[Thu Sep 23 11:07:56 2010] [error] [client 127.0.0.1] GnuTLS: Handshake 
Failed (-9) 'A TLS packet with unexpected length was received.'

And thats with '-c1'!  With '-c2' it is looking worse:

[Thu Sep 23 11:11:02 2010] [info] [client 127.0.0.1] (32)Broken pipe: 
core_output_filter: writing data to the network
[Thu Sep 23 11:11:02 2010] [error] [client 127.0.0.1] GnuTLS: Handshake 
Failed (-53) 'Error in the push function.'
[Thu Sep 23 11:11:02 2010] [info] [client 127.0.0.1] (32)Broken pipe: 
core_output_filter: writing data to the network
[Thu Sep 23 11:11:02 2010] [error] [client 127.0.0.1] GnuTLS: Handshake 
Failed (-53) 'Error in the push function.'

I'm not very confident with siege, because my test client (single 
threaded though) does not raise such messages.

Do you know about any other https stresser?

> I have libapr 1.3.8 and this could be the issue. Maybe something was
> introduced in libapr that causes that issue in apr_dbm. It seems I
> should allow flexibility on using the various DBs.

The apr_dbm is in apr-util.  My libaprutil1 is at 1.3.9, so not so far 
away from yours.

Hardy


More information about the Modules mailing list