123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182 |
- // Copyright (C) 2014 Internet Systems Consortium, Inc. ("ISC")
- //
- // Permission to use, copy, modify, and/or distribute this software for any
- // purpose with or without fee is hereby granted, provided that the above
- // copyright notice and this permission notice appear in all copies.
- //
- // THE SOFTWARE IS PROVIDED "AS IS" AND ISC DISCLAIMS ALL WARRANTIES WITH
- // REGARD TO THIS SOFTWARE INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY
- // AND FITNESS. IN NO EVENT SHALL ISC BE LIABLE FOR ANY SPECIAL, DIRECT,
- // INDIRECT, OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM
- // LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE
- // OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR
- // PERFORMANCE OF THIS SOFTWARE.
- #include <config.h>
- #include <dhcp4/json_config_parser.h>
- #include <dhcp4/ctrl_dhcp4_srv.h>
- #include <dhcp4/dhcp4_log.h>
- #include <dhcpsrv/cfgmgr.h>
- #include <exceptions/exceptions.h>
- #include <string>
- using namespace isc::asiolink;
- using namespace isc::dhcp;
- using namespace std;
- namespace {
- /// @brief Configure DHCPv4 server using the configuration file specified.
- ///
- /// This function is used to both configure the DHCP server on its startup
- /// and dynamically reconfigure the server when SIGHUP signal is received.
- ///
- /// It fetches DHCPv6 server's configuration from the 'Dhcp4' section of
- /// the JSON configuration file.
- ///
- /// @param file_name Configuration file location.
- void configure(const std::string& file_name) {
- // This is a configuration backend implementation that reads the
- // configuration from a JSON file.
- // We are starting the configuration process so we should remove any
- // staging configuration that has been created during previous
- // configuration attempts.
- CfgMgr::instance().rollback();
- isc::data::ConstElementPtr json;
- isc::data::ConstElementPtr dhcp4;
- isc::data::ConstElementPtr logger;
- isc::data::ConstElementPtr result;
- // Basic sanity check: file name must not be empty.
- try {
- if (file_name.empty()) {
- // Basic sanity check: file name must not be empty.
- isc_throw(isc::BadValue, "JSON configuration file not specified."
- " Please use -c command line option.");
- }
- // Read contents of the file and parse it as JSON
- json = isc::data::Element::fromJSONFile(file_name, true);
- if (!json) {
- isc_throw(isc::BadValue, "no configuration found");
- }
- // If there's no logging element, we'll just pass NULL pointer,
- // which will be handled by configureLogger().
- Daemon::configureLogger(json->get("Logging"),
- CfgMgr::instance().getStagingCfg());
- // Get Dhcp4 component from the config
- dhcp4 = json->get("Dhcp4");
- if (!dhcp4) {
- isc_throw(isc::BadValue, "no mandatory 'Dhcp4' entry in"
- " the configuration");
- }
- // Use parsed JSON structures to configure the server
- result = ControlledDhcpv4Srv::processCommand("config-reload", dhcp4);
- if (!result) {
- // Undetermined status of the configuration. This should never
- // happen, but as the configureDhcp4Server returns a pointer, it is
- // theoretically possible that it will return NULL.
- isc_throw(isc::BadValue, "undefined result of "
- "processCommand(\"config-reload\", dhcp4)");
- }
- // Now check is the returned result is successful (rcode=0) or not
- // (see @ref isc::config::parseAnswer).
- int rcode;
- isc::data::ConstElementPtr comment =
- isc::config::parseAnswer(rcode, result);
- if (rcode != 0) {
- string reason = comment ? comment->stringValue() :
- "no details available";
- isc_throw(isc::BadValue, reason);
- }
- // If configuration was parsed successfully, apply the new logger
- // configuration to log4cplus. It is done before commit in case
- // something goes wrong.
- CfgMgr::instance().getStagingCfg()->applyLoggingCfg();
- // Use new configuration.
- CfgMgr::instance().commit();
- } catch (const std::exception& ex) {
- // If configuration failed at any stage, we drop the staging
- // configuration and continue to use the previous one.
- CfgMgr::instance().rollback();
- LOG_ERROR(dhcp4_logger, DHCP4_CONFIG_LOAD_FAIL)
- .arg(file_name).arg(ex.what());
- isc_throw(isc::BadValue, "configuration error using file '"
- << file_name << "': " << ex.what());
- }
- }
- /// @brief Signals handler for DHCPv4 server.
- ///
- /// This signal handler handles the following signals received by the DHCPv4
- /// server process:
- /// - SIGHUP - triggers server's dynamic reconfiguration.
- /// - SIGTERM - triggers server's shut down.
- /// - SIGINT - triggers server's shut down.
- ///
- /// @param signo Signal number received.
- void signalHandler(int signo) {
- // SIGHUP signals a request to reconfigure the server.
- if (signo == SIGHUP) {
- // Get configuration file name.
- std::string file = ControlledDhcpv4Srv::getInstance()->getConfigFile();
- try {
- LOG_INFO(dhcp4_logger, DHCP4_DYNAMIC_RECONFIGURATION).arg(file);
- configure(file);
- } catch (const std::exception& ex) {
- // Log the unsuccessful reconfiguration. The reason for failure
- // should be already logged. Don't rethrow an exception so as
- // the server keeps working.
- LOG_ERROR(dhcp4_logger, DHCP4_DYNAMIC_RECONFIGURATION_FAIL)
- .arg(file);
- }
- } else if ((signo == SIGTERM) || (signo == SIGINT)) {
- isc::data::ElementPtr params(new isc::data::MapElement());
- ControlledDhcpv4Srv::processCommand("shutdown", params);
- }
- }
- }
- namespace isc {
- namespace dhcp {
- void
- ControlledDhcpv4Srv::init(const std::string& file_name) {
- // Call parent class's init to initialize file name.
- Daemon::init(file_name);
- // Configure the server using JSON file.
- configure(file_name);
- // We don't need to call openActiveSockets() or startD2() as these
- // methods are called in processConfig() which is called by
- // processCommand("reload-config", ...)
- // Set signal handlers. When the SIGHUP is received by the process
- // the server reconfiguration will be triggered. When SIGTERM or
- // SIGINT will be received, the server will start shutting down.
- signal_set_.reset(new isc::util::SignalSet(SIGINT, SIGHUP, SIGTERM));
- // Set the pointer to the handler function.
- signal_handler_ = signalHandler;
- }
- void ControlledDhcpv4Srv::cleanup() {
- // Nothing to do here. No need to disconnect from anything.
- }
- };
- };
|