DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=29496>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=29496 New keyfile isn't always picked up when graceful restart is used ------- Additional Comments From [EMAIL PROTECTED] 2004-06-10 20:56 ------- From: Kristianne Leclair <[EMAIL PROTECTED]> To: 'Cliff Woolley' <[EMAIL PROTECTED]> Subject: RE: [Bug 29496] - New keyfile isn't always picked up when graceful restart is used Hi Cliff, Thanks, I'm sorry, if my description was not clear. The behaviour you describe below is exactly the behaviour I had observed in 1.3 - in fact for 1.3 I found that you had to stop and start the server to pick up an updated keyfile regardless of whether it was encrypted or not. What I've found for 2.0 is as follows: - if all keyfiles on the server are unencrypted a new keyfile is always picked up on graceful restart - if the server only has a single virtual host - a new encrypted keyfile seems to be picked up correctly on graceful restart - if the server has multiple virtual hosts with at least one of the servers using an encrypted keyfile, an update to any other keyfile may or may not be picked up correctly on graceful restart It is this last case that I'd tried to describe in my submission. The thing is that this behaviour seems to be slightly unpredictable. For example if you have 3 virtual hosts all with encrypted keyfiles, updating the keyflile for the second host and restarting with graceful may be fine. It seems to fail most commonly when the updated keyfile is for the first listed virtual host. I've also found that if you try restarting gracefully multiple times it may eventually recognize the change and ask you for the password. Any insights? Thanks, -Kris --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
