• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Resolved Unable to back up extension. Unable to find row in Modules table.

paolotrombini25

New Pleskian
Server operating system version
CentOS Linux 7.9.2009 (Core)
Plesk version and microupdate number
18.0.70 Update #3
Hello,

I'm encountering an issue when Plesk attempts to create a backup. The following error is displayed:

Code:
<message severity="warning">
    <description>Unable to back up extension. Error: Failed to exec backup_restore_helper: Exit code: 1: Unable to find row with id 199 in Modules table.</description>
</message>

It appears that a module is missing or not properly registered in the database.

Could you please assist in identifying and resolving this issue?

Thank you,
Paolo
 
Hello, Paolo. Is that the full error message? Isn't the extension causing the issue mentioned in the message as well? If it's unclear, please check var/log/plesk/PMM/backup-timestamp/backup.log. Once you identify the extension, please try reinstalling it. Afterward, run the following command to repair the database:

Bash:
plesk repair db

I hope that helps.
 
Hello, Paolo. Is that the full error message? Isn't the extension causing the issue mentioned in the message as well? If it's unclear, please check var/log/plesk/PMM/backup-timestamp/backup.log. Once you identify the extension, please try reinstalling it. Afterward, run the following command to repair the database:

Bash:
plesk repair db

I hope that helps.
Thanks for the reply.
From the log I see this:

Code:
[2025-07-19 15:45:07.967|15829] INFO: Repository '/usr/local/psa/var/modules/imunify360/': Initializing...
[2025-07-19 15:45:07.968|15829] INFO: Repository '/usr/local/psa/var/modules/imunify360/': Initialized
[2025-07-19 15:45:07.968|15829] INFO: Repository '/var/lib/psa/dumps': Pack  from /usr/local/psa/var/modules/imunify360/ to backup_ext_imunify360_2507190216.tzst. Additional files count: 0. Split size: -1
[2025-07-19 15:45:07.987|15829] INFO: ENV[LANG]=en_US.UTF-8
[2025-07-19 15:45:07.987|15829] INFO: Executing utility: /usr/lib64/plesk-9.0/sw-tar --create --file - --ignore-failed-read --warning no-file-changed --use-compress-program pzstd\ -5 --verbatim-files-from --anchored --files-from /usr/local/psa/PMM/tmp/pmm-ru-cd-includes-AV30FR
[2025-07-19 15:45:08.160|15829] INFO: The utility succesfully executed.
[2025-07-19 15:45:08.160|15829] INFO: backup-archiver finished. Exit code: 0
[2025-07-19 15:45:08.621|15845] ERR [panel] Unable to find row with id 199 in Modules table.
[2025-07-19 15:45:12.256|15886] INFO: pmm-ras started : /usr/local/psa/admin/bin/pmm-ras --get-dump-info --session-path=/usr/local/psa/PMM/sessions/2025-07-19-021326.472 --dump-file-specification=backup_info_2507190216.xml --with-feedback
[2025-07-19 15:45:12.256|15886] INFO: Repository '/var/lib/psa/dumps': Initializing...

It is not clear what extension it is
 
Back
Top