infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Chris Lambertus (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-16253) [mail-private] httpd does not automatically pick up new configs
Date Wed, 28 Mar 2018 23:52:00 GMT

    [ https://issues.apache.org/jira/browse/INFRA-16253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16418257#comment-16418257
] 

Chris Lambertus commented on INFRA-16253:
-----------------------------------------

What specifically makes you think this is the case? Changes to the httpd config will cause
a reload, this is the case on all our systems which use puppetized httpd configs. If it's
not doing this, then chances are that something else in the puppet apply is failing.

> [mail-private] httpd does not automatically pick up new configs
> ---------------------------------------------------------------
>
>                 Key: INFRA-16253
>                 URL: https://issues.apache.org/jira/browse/INFRA-16253
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Mail Archives
>            Reporter: Sebb
>            Priority: Major
>
> Changes to puppet files can result in changes to the httpd config.
> Likewise changes to the directory structure and LDAP may change the config.
> However it seems that the server does not pick up the changes automatically.
> Possible solutions:
> - cron job to do a graceful restart every few hours
> - scripts that create httpd config files could detect if the output has changed and request
a restart if so
> - does puppet have a way to trigger a script based on file timestamps?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Mime
View raw message