Landscape 23.03 memory leak

Bug #2040257 reported by Aliaksandr Vasiuk
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Landscape Server
Fix Released
Undecided
Unassigned

Bug Description

Hello,

In two independent environments, I observed Landscape 23.03 version memory consumption grows constantly.
These two environments have HA setup with 3 Landscape server units on three VMs for each setup.
I'm attaching "Used Memory" graphs from Grafana. It is seen that memory usage constantly grows, then landscape services get restarted whether manually by an operator or the process just got killed because of OOM error.
The landscape-appserver process is the most memory consuming, and by restarting it I can free up memory which is enough for a week or more.
For the environment from 1.png installed packages are:
```
landscape-client 23.02+git6242-0ubuntu0 amd64
landscape-common 23.02+git6242-0ubuntu0 amd64
landscape-hashids 22.10+7-landscape1~ubuntu20.04.2 all
landscape-server 23.03+9-0landscape0 amd64
```
For the environment from 2.png installed packages are:
```
landscape-client 23.02+git6277-0ubuntu0 amd64
landscape-common 23.02+git6277-0ubuntu0 amd64
landscape-hashids 22.10+8-landscape1 all
landscape-server 23.03+12.1-0landscape0 amd64
```
Please tell if I can provide any other helpful information.

Best Regards,
Aliaksandr Vasiuk.

Revision history for this message
Aliaksandr Vasiuk (valexby) wrote :
Revision history for this message
Aliaksandr Vasiuk (valexby) wrote :
information type: Proprietary → Public
Revision history for this message
Kevin Nasto (silverdrake11) wrote :

In version +13, released end of June 2023. A fix has been added https://code.launchpad.net/~mitchburton/landscape/+git/landscape/+merge/445148 which restarts the services automatically without any interaction, when memory usage is above a certain limit. This can be configurable in the settings conf

Changed in landscape:
status: New → Fix Released
Revision history for this message
Kevin Nasto (silverdrake11) wrote :

Looking at this more carefully, in order to activate this feature, in the settings.conf "global" section. A config called "max-service-memory" needs to be added, which is an integer in megabytes

Revision history for this message
Aliaksandr Vasiuk (valexby) wrote (last edit ):

Hi,

To workaround it with juju, there is `max-service-memory` configuration option in `/etc/landscape/server.conf` `[global]` section. There one can set a memory usage cap in MBs.
I tried to do juju-managed way today with
```
$ juju config landscape-server additional_service_config="""
> [global]
> max-service-memory=2500
> """
```
Will observe how it will work from now on.

Best Regards,
Aliaksandr Vasiuk.

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.