• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Warning message on update

Gabor H

Basic Pleskian
TITLE:
Warning message on update
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE:
OS ‪CentOS Linux 7.4.1708 (Core)‬
Product Plesk Onyx
Version 17.8.10
PROBLEM DESCRIPTION:
Warning: Information on some packages might not be actual: inconsistencies were detected in the system's package manager database. Please resolve this issue manually.​
STEPS TO REPRODUCE:
Tools/settings ---> System update​
ACTUAL RESULT:
Top of the screen, the above error message visible.
Unable to resolve manually, `yum` doesn't show error message.​
EXPECTED RESULT:
fix the issue​
ANY ADDITIONAL INFORMATION:
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM:
Help with sorting out
 
Try to fix it with

# plesk installer --select-release-current --reinstall-patch --upgrade-installed-components
 
Hi,
Tried the command, but the error message of above is still visible within Plesk : Tools/settings ---> System updates
 
It responds the following. What to do with that?


Loaded plugins: fastestmirror, langpacks
Error: check ['dependencies', 'duplicates', 'obsoletes']
psa-mnemo-4.2.14-cos7.build1708180202.11.noarch has missing requires of psa-horde >= ('0', '5.1.6', None)
psa-mnemo-4.2.14-cos7.build1708180202.11.noarch has missing requires of psa-imp >= ('0', '6.1.7', None)
2018-02-16 02:08:38 ERROR: Exited with returncode 1.
exit status 1


EDIT: horde is not installed



How about this?

# plesk sbin pum --check
 
# rpm -e psa-mnemo-4.2.14-cos7.build1708180202.11.noarch

Tried it, but doesn't look really good:


Console_Getopt: unrecognized option --nobuild

WARNING!
Some problems are found during uninstall package /usr/share/psa-horde/mnemo/.xml/mnemo.xml in PEAR(see log file: /var/log/plesk/install/plesk_17.8.10_installation.log)

Continue...

Console_Getopt: unrecognized option --nobuild

WARNING!
Some problems are found during uninstall package /usr/share/psa-horde/mnemo/.xml/mnemo.xml in PEAR(see log file: /var/log/plesk/install/plesk_17.8.10_installation.log)

Continue...


ERROR while trying to uninstall H5-application mnemo
Check the error reason(see log file: /var/log/plesk/install/plesk_17.8.10_installation.log), fix and try again

Console_Getopt: unrecognized option --nobuild

WARNING!
Some problems are found during uninstall package /usr/share/psa-horde/mnemo/.xml/mnemo.xml in PEAR(see log file: /var/log/plesk/install/plesk_17.8.10_installation.log)

Continue...


ERROR while trying to uninstall H5-application mnemo
Check the error reason(see log file: /var/log/plesk/install/plesk_17.8.10_installation.log), fix and try again


uninstall H5-application mnemo

***** installing problem report *****
ERROR while trying to uninstall H5-application mnemo
Check the error reason(see log file: /var/log/plesk/install/plesk_17.8.10_installation.log), fix and try again
uninstall H5-application mnemo
error: %preun(psa-mnemo-4.2.14-cos7.build1708180202.11.noarch) scriptlet failed, exit status 1
error: psa-mnemo-4.2.14-cos7.build1708180202.11.noarch: erase failed
 
Well screw the files I guess, you can try just pulling it out of the DB;

rpm -e --justdb pkgname
 
It seems that this one did the trick.
Or together with the previous command.

Now it's up to PLESK support team to find out why it came out on a fresh Plesk install and what's the root cause.

Thanks Mark!!


Ugh, maybe try;

# plesk sbin pum --update
 
Back
Top