Comment 30 for bug 2012596

A few questions that will help us identify the root cause.
1) Are you using custom images?
2) Could you upload a profile for rackd and regiond from the period where you observe the memory leaking? A few minutes should be sufficient.
3) Could you share anything about how that MAAS instance is used? Is it driven by automation scripts that make API calls, is it mainly left idle, etc?
4) Do you see the same leak with prometheus metrics enabled and disabled?
5) Could you share the full output of `sudo netstat -atnp` at the start and at the end of the experiment?
6) Can you share region logs? The sosreports don't seem to have them.

You can toggle profile capture by issuing the command `pkill -SIGUSR1 -f maas-regiond`, sending the same signal again will stop the capture and saves the profile. The profile file will be stored in the /var/lib/maas/profiling and the logs will also contain the location and name of the file.