Community Forum

Resolved
0 votes
Running ClearOS 6.6 Pro, Lite

Had a recent issue where my ClearOS box was not handing out IPs even though the DHCP server was supposedly running. I had to reboot the ClearOS box to get everything working. Would have been much nicer if I could have simply restarted the DHCP service as I could do in ClearOS 5, and as I can do with several other services in ClearOS 6.
Friday, August 21 2015, 03:14 AM
Share this post:
Responses (7)
  • Accepted Answer

    Tuesday, September 05 2017, 11:20 AM - #Permalink
    Resolved
    0 votes
    There is no need to restart the server to restart DHCP. From the command line, just do a "service dnsmasq restart" or, in the system way, "systemctl restart dnsmasq.service". This is from memory and a little niggle says systemctl for dnsmasq does not support a restart so you may have to do a stop followed by a start.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, September 05 2017, 08:21 AM - #Permalink
    Resolved
    0 votes
    OK, thanks for that, it makes a lot of sense.

    I am trying to get Avaya handsets to get a DHCP address in the correct VLAN/subnet and had added a line to the dnsmasq.conf file and just wanted to restart the service without restarting the server.

    Still not working as planned on a handset level, but that's a topic for a new thread.


    Dave Loper wrote:

    I don't know that the term 'oversight' is appropriate here. DNSmasq not only provides DHCP services but it is also the foundation for a number of services which required a functioning DNS server. The services include:

    Samba
    Gateway.Management
    DNSThingy
    ...and every single update including security updates.

    Simply stopping in essentially breaks a number of things. If you are skilled enough to compensate for these by properly assembling a replacement or by over the architecture of the DNS of the server with some replacement then it will also be trivial for you do the other types of things that does whatever it is that you need to do. Some of these other tasks include:

    Disabling the consumption of port 53 by DNSMasq by setting the port parameter to '0'.
    Rolling in Bind and DHCPd from ISC because you want to use them instead.

    The purpose for not having the start/stop button is to save people from breaking essential functions of the system. Feel free to do it manually but having that button NOT there is a good thing and will save a lot of heartache for those people who don't know/realize that the DHCP services is also the same thing that is making it so that there server can run DNS resolution on their updates.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, September 05 2017, 07:48 AM - #Permalink
    Resolved
    0 votes
    I don't know that the term 'oversight' is appropriate here. DNSmasq not only provides DHCP services but it is also the foundation for a number of services which required a functioning DNS server. The services include:

    Samba
    Gateway.Management
    DNSThingy
    ...and every single update including security updates.

    Simply stopping in essentially breaks a number of things. If you are skilled enough to compensate for these by properly assembling a replacement or by over the architecture of the DNS of the server with some replacement then it will also be trivial for you do the other types of things that does whatever it is that you need to do. Some of these other tasks include:

    Disabling the consumption of port 53 by DNSMasq by setting the port parameter to '0'.
    Rolling in Bind and DHCPd from ISC because you want to use them instead.

    The purpose for not having the start/stop button is to save people from breaking essential functions of the system. Feel free to do it manually but having that button NOT there is a good thing and will save a lot of heartache for those people who don't know/realize that the DHCP services is also the same thing that is making it so that there server can run DNS resolution on their updates.
    The reply is currently minimized Show
  • Accepted Answer

    Tuesday, September 05 2017, 07:31 AM - #Permalink
    Resolved
    0 votes
    I know this is an OLD thread but it seems like the "oversight" still hasn't been fixed.

    Are there any plans to do so?

    Daniel Castellanos wrote:

    Ben Chambers wrote:

    That looks to be an oversight...DHCP is provided by the Dnsmasq package, but there's no stop/start button for DNS either.

    Workaround...install the app "Services" from the Marketplace. There you can stop/start any registered service...DNS Server (aka dnsmasq) included, which, as I just mentioned, provided DHCP too.

    B


    So where can we get this reported as a "oversight" to be fixed?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 26 2015, 02:10 PM - #Permalink
    Resolved
    0 votes
    Ben Chambers wrote:

    That looks to be an oversight...DHCP is provided by the Dnsmasq package, but there's no stop/start button for DNS either.

    Workaround...install the app "Services" from the Marketplace. There you can stop/start any registered service...DNS Server (aka dnsmasq) included, which, as I just mentioned, provided DHCP too.

    B


    So where can we get this reported as a "oversight" to be fixed?
    The reply is currently minimized Show
  • Accepted Answer

    Wednesday, August 26 2015, 02:08 PM - #Permalink
    Resolved
    0 votes
    I double-posted. Am I blind or is there no way to delete a post on these new forums?
    The reply is currently minimized Show
  • Accepted Answer

    Monday, August 24 2015, 02:27 PM - #Permalink
    Resolved
    0 votes
    That looks to be an oversight...DHCP is provided by the Dnsmasq package, but there's no stop/start button for DNS either.

    Workaround...install the app "Services" from the Marketplace. There you can stop/start any registered service...DNS Server (aka dnsmasq) included, which, as I just mentioned, provided DHCP too.

    B
    The reply is currently minimized Show
Your Reply