Apache reload config file

Copy the original file to some other file and create a backup. This will help you recover any mistakes while editing the file. If any mistakes are found in httpd. To edit httpd. After editing, reload the file or stop and start httpd process. If web server does not work properly, then you have made some typo mistakes. Configuration Directives in httpd. LockFile It sets the path to the lockfile. Timeout Timeout sets the amount of time in seconds that your server will wait for response and transmissions during communications.

By default, it is set to seconds, which is appropriate for most situations. KeepAlive It sets whether the server allows more than one request per connection and can be used to prevent a client from using too much of the servers resources. By default, KeepAlive is set to off that means server does not allow continuous connections.

It is set to by default, which should be suitable for most situations. KeepAliveTimeout This directive sets the number of seconds your server will wait for next request, after a request has been served before it closes the connection. By default, it is set to 15 seconds. StartServers This directive sets how many server processes are created upon startup.

The Web server is set to start 8 server processes at startup. This method expects a ReloadingController object as argument. It performs some event listener registrations to ensure that reloading events fired by the controller cause the builder's result object to be invalidated, and that the creation of a new result object causes the controller's reloading state to be reset. In a nutshell, this is a full implementation of the reloading protocol.

For some applications it may not be necessary to react on external changes on their configuration immediately. It just has to be ensured that when an access to configuration data is performed, the most recent settings are read.

This is in principle similar to the mechanism implemented in Commons Configuration 1. It is possible to set up a configuration builder in a way that each time the getConfiguration method is called a reloading check is performed. If the reloading controller detects that the monitored source has changed, the managed configuration is replaced by an updated one.

So the builder returns the fresh configuration instance. If used this way, no special reloading trigger has to be installed; reloading can only happen when the builder is queried for its managed configuration.

But then it is guaranteed that an up-to-date configuration instance is returned. Note the main difference to the old model as used in Commons Configuration 1.

In order to configure a configuration builder to trigger reloading checks each time its managed configuration is accessed, a special event generated by the builder can be used: the configuration request event.

This event is passed to registered event listeners before the managed configuration is accessed. More information about event listeners can be found in the chapter about events. A listener for this event just has to trigger a reloading controller. This will cause the managed configuration to be invalidated and replaced before it is returned to the caller. The following example shows how this can be achieved. It makes use of a ReloadingFileBasedConfigurationBuilder because this class provides easy access to its associated reloading controller.

However, the same principle also works for other builders connected to a reloading controller as described in the previous section :. ManagedReloadingDetector is an alternative to automatic reloading. It allows to hot-reload properties on a running application, but only when requested by an administrator.

The detector class defines a refresh method which forces a reload of the configuration source the next time a reloading check on the associated ReloadingController is triggered. All Rights Reserved. Automatic Reloading of Configuration Sources If an application has special requirements regarding its availability, it is probably desired that changes on configuration files can be done without the need for a restart.

Components for Reloading The reloading mechanism defined by Commons Configuration involves multiple components which all work together to detect changes on a configuration source and trigger the actual reload operation. This is reflected in the methods defined by the ReloadingDetector interface: The isReloadingRequired method is called to trigger a check. The detector has to determine whether something has changed on the monitored source and returns a boolean flag as result.

The reloadingPerformed method is called after a reload operation was performed. This method gives the detector the opportunity to reset itself so that new changes on the associated configuration source can be detected. Reloading File-based Configurations As was already stated, reloading is not limited to file-based configurations.

Builder Configuration Related to Reloading When setting up a configuration builder with reloading support for file-based configurations some settings can be defined that influence reloading operations. These settings are part of the initialization parameters for file-based configurations and defined by the FileBasedBuilderProperties interface: The ReloadingDetectorFactory to be used when the reloading controller is created.

An application with special requirements related to the detection of changes can here provide a custom factory. As was mentioned above, the default factory creates a suitable detector for detecting changes on a file. The so-called reloading refresh delay. This is a numeric value in milliseconds limiting the access to the underlying file.

The reloading detector will check for updates on the file only if the last check was not within the time span defined by the refresh delay.

This value can be used to improve performance if there are many accesses to a configuration builder in short intervals.

Generic Reloading Support In fact, ReloadingFileBasedConfigurationBuilder is a pretty thin implementation around a generic reloading mechanism already supported by the BasicConfigurationBuilder base class. So the recipe to activate reloading for a builder instance is as follows: Create and initialize the builder instance as usual. Create a ReloadingDetector which is able to monitor the configuration source in question and to find out whether a reload action has to be performed.

Find centralized, trusted content and collaborate around the technologies you use most. Connect and share knowledge within a single location that is structured and easy to search. Today I request its homepage, I see a timezone error, as it should be configured into my php.

Try sudo service apache2 restart from the command line. TL;DR; If you're still having trouble after restarting apache or nginx, also try restarting the php-fpm service. The answers here don't always satisfy the requirement to force a reload of the php. On numerous occasions I've taken these steps to be rewarded with no update, only to find the solution I need after also restarting the php-fpm service. So if restarting apache or nginx doesn't trigger a php. The above commands taken directly from this server fault answer.

You also can use graceful restart the apache server with service apache2 reload or apachectl -k graceful. As the apache doc says:.

The USR1 or graceful signal causes the parent process to advise the children to exit after their current request or to exit immediately if they're not serving anything. The parent re-reads its configuration files and re-opens its log files.

As each child dies off the parent replaces it with a child from the new generation of the configuration, which begins serving new requests immediately. Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Collectives on Stack Overflow. Learn more.