syslog flooded with dhcpd messages that seem to be due to the use of actions in MAAS 2.0

Bug #1639054 reported by Jeff Lane 
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Expired
Undecided
Unassigned

Bug Description

Discussed a bit with Andres on IRC, and the relevant difference between 1.9 and 2.0 is the use of actions with dhcp.

So I have a production MAAS 2.0 server:

And in that MAAS Server, I have 7 syslog files with nearly 8 million lines of text betwenen thm:

root@weavile:~# cat syslo* |wc -l
7903206

Of those nearly 8 million lines of text, 4 million are strictly dhcp related:
root@weavile:~# grep dhcpd syslo* |wc -l
4023399

For every DCHP request made, the log grows by 16 lines of text like this:

Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[0] = /usr/sbin/maas-dhcp-helper
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[1] = notify
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[2] = --action
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[3] = commit
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[4] = --mac
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[5] = e4:1f:13:60:68:64
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[6] = --ip-family
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[7] = ipv4
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[8] = --ip
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[9] = 10.1.11.12
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[10] = --lease-time
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[11] = 600
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[12] = --hostname
Nov 2 06:25:14 weavile dhcpd[660]: execute_statement argv[13] = wildorange
Nov 2 06:25:14 weavile dhcpd[660]: DHCPREQUEST for 10.1.11.12 from e4:1f:13:60:68:64 via eno49
Nov 2 06:25:14 weavile dhcpd[660]: DHCPACK on 10.1.11.12 to e4:1f:13:60:68:64 via eno49

Because of that, syslog can very quickly become flooded with unnecessary data and become useless.

Need a way to silence all those "execute_statement" lines that really seem to just be debug fluff and not necessary in normal production.

rsyslog has the ability to filter out messages by regex, so I'd suggest MAAS do one of the following:

Either discard all those execute_statement lines OR redirect them to a separate file.

Revision history for this message
Andres Rodriguez (andreserl) wrote :

I've quickly investigated this and seems to be related to isc only. So ISC, by default, does this.

Changed in maas:
importance: Undecided → Medium
status: New → Triaged
milestone: none → 2.2.0
Changed in maas:
milestone: 2.2.0 → 2.2.x
Changed in maas:
milestone: 2.2.x → next
importance: Medium → Wishlist
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
Revision history for this message
Jeff Lane  (bladernr) wrote :

This has not seen any activity in the last 6 months because it was triaged and then forgotten.

Changed in maas:
status: Invalid → Confirmed
Revision history for this message
Björn Tillenius (bjornt) wrote :

So, this is dhcpd that does the logging. I couldn't find anyway of silencing those logging statments, except for configuring syslog to ignore those message (which MAAS can't do).

What's your proposing that MAAS does here?

Changed in maas:
milestone: next → none
importance: Wishlist → Undecided
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

Changed in maas:
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.