Still having this error about twice a day. I put a cron job in place to restart the server hourly since selenium testing for the failure proved less stable than the server itself - too many false positives. Alas, the restart is less than ideal as we're dropping several hundred connections during peak times.
Even with an hourly restart, this error is still occuring sporadically. Once further piece of information I didn't realize may be significant before is that I have not configured DH parameters. I'm not sure if they're at all necessary as SSL was still working and I've never had to do this with any other webserver. Are the DH parameters are used for generating the session keys? Perhaps creating DH parameter files will do something for me? I will test and write back. Ryan
_______________________________________________ Cherokee mailing list [email protected] http://lists.octality.com/listinfo/cherokee
