[ale] dhcpd misbehaving?

[Jim Kinney]

OK. That makes sense now.

I'm suspicious of a memory leak. Look at request count between start and
fail time in the logs. Also turn up the logging on dhcpd in your syslog.
Turn up system profiling with remote /proc watching with sysstat tools.

On Thu, 2015-04-02 at 20:16 +0000, Robert L. Harris wrote:
> 
> Ok, I didn't go into the vlans enough.
> 
> 
> Corp designated I use 172.27.0.0/16 for my network.  Instead of having
> 10 projects on one unmaintainable /16 I have broken it into /24's.
> VLAN 800 is 172.27.0.0/24,  vlan 801 is 172.27.1.0/24, vlan 802 is
> 172.27.2.0/24, on through 172.27.10.0/24 currently.  My core router
> has the different gateways on it for each vlan and configured a dhcpd
> helper gateway address of 172.27.0.1.  As a result my named.conf has
> 10 included configurations similar to the one I pasted for each vlan.
> I'm not seeing any bogons or martians.  When dhcpd goes stupid it does
> it for a couple IP's ( seems random which subnet it begins on ) and
> then spirals out to every subnet and all requests being ignored with
> the error messages I pasted.
> 
> 
> Robert
> 
> 
> 
> On Thu, Apr 2, 2015 at 1:57 PM Jim Kinney <jim.kinney at gmail.com>
> wrote:
>         On Thu, 2015-04-02 at 12:43 -0700, Alex Carver wrote:
>         > On 2015-04-02 12:27, Jim Kinney wrote:
>         >
>         > >>
>         > >>   The problem I'm running into is dhcpd will work great
>         for 3-5 days
>         > >> and then all of a sudden start throwing errors:
>         > >> Mar 30 15:50:01 basvc01 dhcpd: DHCPDISCOVER from
>         c8:9c:dc:da:b4:bf via
>         > >> 172.27.4.1: not responding (recovering)
>         > >> Mar 30 15:50:01 basvc01 dhcpd: DHCPDISCOVER from
>         00:50:56:a0:57:aa via
>         > >> 172.27.6.1: not responding (recovering)
>         > >
>         > > This is your gateway machine. Why is it on dhcp?
>         >
>         > Why is his gateway outside of the local subnet?  His
>         machines are
>         > 172.27.0.0/24 but his gateway is sitting outside of that.
>         
>         Looking at the dhcp address range, the gateway is in the
>         network. But
>         that 172.27.4.1 is not.
>         
>         I'm wondering if the gateway is also on the 172.27.4.0/24
>         network on
>         another nic but badly misconfigured or it's using multiple IPs
>         per nic.
>         That will totally crap out dhcp discover.
>         > _______________________________________________
>         > Ale mailing list
>         > Ale at ale.org
>         > http://mail.ale.org/mailman/listinfo/ale
>         > See JOBS, ANNOUNCE and SCHOOLS lists at
>         > http://mail.ale.org/mailman/listinfo
>         
>         --
>         James P. Kinney III
>         
>         Every time you stop a school, you will have to build a jail.
>         What you
>         gain at one end you lose at the other. It's like feeding a dog
>         on his
>         own tail. It won't fatten the dog.
>         - Speech 11/23/1900 Mark Twain
>         
>         http://heretothereideas.blogspot.com/
>         
>         _______________________________________________
>         Ale mailing list
>         Ale at ale.org
>         http://mail.ale.org/mailman/listinfo/ale
>         See JOBS, ANNOUNCE and SCHOOLS lists at
>         http://mail.ale.org/mailman/listinfo
> _______________________________________________
> Ale mailing list
> Ale at ale.org
> http://mail.ale.org/mailman/listinfo/ale
> See JOBS, ANNOUNCE and SCHOOLS lists at
> http://mail.ale.org/mailman/listinfo