# Gaia database lock on a Maestro Security Group configured with Management Aggregation (MAGG) is lost when using API or Gaia gClish to add a new Management interface to the Security Group

**Product**: Maestro HyperScale Firewall  
**Version**: R82, R82.10  
**OS**: Gaia  
**Last Modified**: 2025-11-05

## Symptoms

- If a Maestro Security Group (in the VSNext mode or Traditional VSX mode) is configured with Management Aggregation (MAGG), then adding a new Management interface to this Security Group in Gaia gClish or with API may fail because the Gaia database lock is continuously lost. During this issue, the `/var/log/messages` file repeatedly shows:
  
  ```
  cmd by admin: Start executing : add bonding ...
  
  cmd by admin: Start executing : delete bonding ...
  ```
- You cannot run gClish commands because of the missing lock. The issue persists after you run the "`lock database override`" command.

## Solution

This problem was fixed. The fix is included in:

- [Jumbo Hotfix Accumulator for R82](https://sc1.checkpoint.com/documents/Jumbo_HFA/R82/Default.htm) starting from Take 44

If you choose not to upgrade, do not use Gaia API or gClish to create a Maestro Security Group configured with Management Aggregation (MAGG). To create a Maestro Security Group configured with Management Aggregation (MAGG), use the Gaia Portal.

**Workaround**:

If the issue occurs on an existing Maestro Security Group, then run this command in the Expert mode on each Maestro Security Group:

```sh
grep -q MAGG_AUTO_JOIN_FLAG /etc/init.d/smartd || { echo Patching && sed -i '/^[^#]*\update_mgmt_interface_following_sgdb_change/s/^/#/' /etc/init.d/smartd && echo Success && service smartd stop && service smartd start; };
```

#### NOTE

This solution has been verified for the specific scenario, described by the combination of Product, Version and Symptoms. It may not work in other scenarios.

## Article Properties

**Access Level**: General  
**Status**: Approved by TAC  
**Date Created**: 2025-01-15  
**Last Modified**: 2025-11-05