Per User wrote: > Thanks for the quick reply. Removing Namevirtualhost gives Apache warn > errors, it still starts, but does not serve HTTPS still. > >
Hmm, it shouldn't give any warnings, unless you have multiple virtualhosts on the same ip/port (you can't use name-based virtualhosts with ssl anyway). > It still continues to throw this error in the Apache2 error log, > > [Tue Jun 02 12:41:16 2009] [info] [client 90.152.0.26] SSL handshake failed: > HTTP spoken on HTTPS port; trying to send HTML error page > [Tue Jun 02 12:41:16 2009] [info] SSL Library Error: 336027804 > error:1407609C:SSL routines:SSL23_GET_CLIENT_HELLO:http request speaking > HTTP to HTTPS port!? > On my CentOS 5 box, if I set NameVirtualhost on a ip/port that's used for SSL, I basically get the same thing. Checking it with wireshark shows that the browser and server start communicating over ssl, but then the server randomly responds with a plain html error (this probably creates the "ssl_error_rx_record_too_long" error you see on the browser because it tries to parse this as ssl). Not sure why it does that, but removing the Namevirtualhost on that port seemed to resolve this issue. > The conf like for User3 is the same for Users 1 > 10, but for whatever > reason, it refuses to work on User3. Apache will start and will > continue to serve to other users, but any requests to virtualhosts > under User3 and that particular child instantly segfaults Would it be possible that you compile peruser with debugging enabled (by uncommenting the MPM_PERUSER_DEBUG in peruser.c) and attach the debug log about these seg faulting children? Note that the debug creates pretty much IO load on the server, so I wouldn't suggest running it for a long time. Taavi _______________________________________________ Peruser mailing list [email protected] http://www.telana.com/mailman/listinfo/peruser
