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

[Jeff Lane ]

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.

[Andres Rodriguez (andreserl)]

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

[Adam Collard (adam-collard)]

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

[Jeff Lane  (bladernr)]

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

[Björn Tillenius (bjornt)]

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?

[Launchpad Janitor (janitor)]

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