Resolved Imunify360 can't find archive

[Liberator]

Server operating system version

Debian 12

Plesk version and microupdate number

18.0.63 #4

I am experiencing update failures and receiving failure emails daily. Each time the failure reason is different.

2 days ago:
Reason: 2024-09-19 06:25:16 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']
2024-09-19 06:25:17 ERROR: Apt cache fetch failed: W:GPG error: Index of /imunify360/debian/12/ bookworm InRelease: The following signatures couldn't be verified because the public key is not available: NO_PUBKEY 8C55A6628608CB71, E:The repository 'Index of /imunify360/debian/12/ bookworm InRelease' is not signed. 2024-09-19 06:25:17 ERROR: W:GPG error:
(This reason was repeated with 'Exited with returncode 1' appended)

1 day ago:
Reason: 2024-09-20 06:25:21 INFO: pum is called with arguments: ['--update', '--json']
2024-09-20 06:25:25 INFO: no packages to update
2024-09-20 06:25:25 ERROR: E:dpkg was interrupted, you must manually run 'dpkg --configure -a' to correct the problem.
2024-09-20 06:25:25 ERROR: Exited with returncode 1.
It suggested I manually run the update which also failed with the message 'Error: Unable to receive update information for the package(s)'. There is a warning on this page 'Warning: Information on some packages might not be actual: inconsistencies were detected in the system's package manager database. Please resolve this issue manually.'

Today:
Reason: 2024-09-21 06:25:16 INFO: pum is called with arguments: ['--list', '--repo-info', '--json']

I cannot run update from console because it errors with the message:
'The package imunify360-venv needs to be reinstalled, but I can't find an archive for it'

This may be related to the fact that this package has been renamed - Changelog shows ' 7.16 Renamed the Imunify360 extension to Imunify'

I am not very experienced with Plesk and would appreciate any help!

 

[Sebahat.hadzhi]

Hey, @Liberator. Could you please try the workaround described in the following article?

 

[Liberator]

Unfortunately that fails at the first command -

'-bash: imunify360-agent: command not found'.

Any other ideas?

 

[Sebahat.hadzhi]

Are you planning to use Imunify360? If not, please try moving the imunify360 source manually to another directory. For example:

mv /etc/apt/sources.list.d/imunify360* /root/

After that, update the system:

apt clean
apt update
apt upgrade

Alternatively, please try to fetch and install GPG key:

wget https://repo.imunify360.cloudlinux.com/imunify360/debian/12/dists/bookworm/Release.gpg
sudo apt-key add Release.gpg

Please let us know, if the issue still persists afterward.

 

[Liberator]

Strange.

mv /etc/apt/sources.list.d/imunify360* /root/
mv: cannot stat '/etc/apt/sources.list.d/imunify360*': No such file or directory

Now I can update no problem and no more failure emails - go figure!

 

[Sebahat.hadzhi]

That's indeed strange. Still, glad to hear you were able to update now.

 

[AndyWe]

Hi, exactly same problem here.

Server operating system version: Ubuntu 22.04.5 LTS (ESM)
Plesk version and microupdate number: 18.0.63 #4

solution for me:

dpkg --purge --force-all imunify360-venv

Probably the original reason was to try to install the new Imunify. This does not work, but ends in an endless loop of installation-stopped-installation-stopped and so on (in the Plesk interface). The removal of the extension in the Plesk interface is probably not complete, although it no longer appears. Then the error occurs.

 

[landrei]

Thanks @AndyWe that worked for me too