Resolved System Update issue - pum with arguments, missing release

[florkz.com]

Server operating system version

CentOS Linux 7.9.2009 (Core)

Plesk version and microupdate number

Plesk Obsidian 18.0.48

• panopta-agent 2022.46.2-0.1 update error with the error-code:
• • 2022-12-09 13:17:36 INFO: pum is called with arguments: ['--update', '--json', '--', 'panopta-agent']
  • 2022-12-09 13:17:38 INFO: updating packages: panopta-agent
  • 2022-12-09 13:17:42 ERROR: [u'Errors were encountered while downloading packages.', u'panopta-agent-2022.46.2-0.1.x86_64: [Errno 256] No more mirrors to try.']
  • 2022-12-09 13:17:42 ERROR: Exited with returncode 1.

Hi i'm using
CentOS Linux 7.9.2009 (Core) with Plesk Obsidian 18.0.48

how can i resole this?

 

[florkz.com]

that are the datails of the package:
Name : panopta-agent
Version : 2022.37.1
Release : 0.1
Architecture: x86_64
Install Date: Thu Oct 13 18:05:28 2022
Group : Applications/Network
Size : 27707185
License : Copyright (c) 2014 Panopta LLC
Signature : RSA/SHA1, Mon Sep 12 18:33:00 2022, Key ID 61ee28720129f5f3
Source RPM : panopta-agent-2022.37.1-0.1.src.rpm
Build Date : Fri Sep 9 15:39:55 2022
Build Host : agent-agent-29-nq5bd-vqxcd-hmc1l
Relocations : (not relocatable)
Packager : panopta
Vendor : panopta
Summary : panopta monitoring agent
Description :
Local monitoring agent that gathers and pushes system resource levels
to Panopta's central monitoring infrastructure.

 

[Peter Debik]

Could you please help me in identifying how this question is related to Plesk? In which context to Plesk are you using the package?

 

[florkz.com]

Hi, on tools&settings-> upgdates->Add and Remove Product Components->Plesk extensions
when i remove monitoring plesk didn't try to update this packege at the first time i've disabled monitoring...

...but now when i try to remove monitoring it shows this warning:
Enabled repositories check
Unable to create yum cache for '*!epel' OS repository.
Make sure the repository is available, otherwise either disable it or fix its configuration, then try again.
Proceeding with installation or upgrade without resolving the issues that were found can corrupt your data.
I confirm that I want to continue, regardless of the issues found.

is this a serious problem with a repository? what can i do?

 

[Peter Debik]

Could you please check this thread, I think it points you into the right direction:

Resolved - Updates failed due to epel repo disabled.

Hello, Product version: Plesk Obsidian 18.0.43.1 OS version: CentOS 7.9.2009 x86_64 Build date: 2022/04/14 18:00 Revision: 1a6b26fb2fd0ac923f3ca10bdfd13b721cb5c676 Just had a bunch of servers fail to update because Plesk installation requires 'epel' OS repository to be enabled. Make sure it...

talk.plesk.com

 

[florkz.com]

at this thread they try to fix this with renaming existing repo...
but my problem that i have a existing '*!epel' OS repository, which should be fixed:
[root@66 ~]# yum repolist | grep epel
* epel: mirror.23m.com
*!epel/x86_64 Extra Packages for Enterprise Linux 7 - x86_64 13,746
[root@66 ~]# ls -la /etc/yum.repos.d/epel.*
-rw-r--r-- 1 root root 1358 Dec 10 14:09 /etc/yum.repos.d/epel.repo
but how?

 

[florkz.com]

hello,
installing and uninstalling 360 Monitoring solved this problem for me. now everything is nominell.
thnx

 

[Kaspar]

Good to hear you where able to solve the issue. Thank your for posting back.