@vmayer When the growth happens, please post the output of the following commands:
ps auxw --sort=rss
ps auxw --sort=vsz
df -k /dev/shm
ipcs -m
It doesn’t have to be when the usage is at its peak; as soon as swap starts to get used for real suffices.
Beyond that you can find lots of messages like this:
Those messages have nothing to do with memory usage, even less with its growth. They’re just a note by the LDAP server that a search query could be sped up if there was an index for the attribute looked up.
This attribute (member
) is not a real attribute used by the OpenLDAP schema (and therefore slapd
). It is used in the Active Directory schema, though (and therefore the LDAP server provided by Samba). My guess is that there’s at least one application targeting the LDAP server that uses a filter which includes the member
attribute.
As the OpenLDAP scheme doesn’t normally use said attribute, it isn’t indexed by default. You can add an index for it, which will silence the warning and increase search speed very, very slightly. It might be better to figure out which application sends such a search filter, though (e.g. by increasing the LDAP log level to log all search queries and going from there). Follow the steps in the article you linked to.
Or you can just ignore the warning. It doesn’t really hurt.
@tpfann Your problem does not look like the original poster’s problem. For vmayer the issue is that the memory usage keeps growing and growing until he has to reboot the server. That doesn’t seem to happen to you. Please open a separate topic for your issue — discussing most likely unrelated things in the same topic leads to a lot of confusion. Thanks.