Plesk installer failed: Repository.cpp:136: void Repository::addFromCache(FILE*, Package::type_t, Repository::dups_mode_t, const Source*)

Created:

2016-11-16 13:00:11 UTC

Modified:

2017-08-16 17:30:51 UTC

0

Was this article helpful?


Have more questions?

Submit a request

Plesk installer failed: Repository.cpp:136: void Repository::addFromCache(FILE*, Package::type_t, Repository::dups_mode_t, const Source*)

Applicable to:

  • Plesk 11.x for Linux
  • Plesk 12.0 for Linux

Symptoms

Unable to run Plesk Installer and install components due to the following error:

# /usr/local/psa/admin/sbin/autoinstaller --select-release-current --install-component postfix
parallels_installer_CentOS_5_i386: Repository.cpp:136: void Repository::addFromCache(FILE*, Package::type_t, Repository::dups_mode_t, const Source*): Assertion `point != pkgList.end()' failed.

Cause

This is Plesk internal issue with id #PPPM-4492 , the fix will be included in the next Plesk updates.

Workaround

  1. Check pubkeys on the server:

    # rpm -qa | grep gpg-pubkey | sort | uniq -c
    1 gpg-pubkey-00f97f56-467e318a
    2 gpg-pubkey-217521f6-45e8a532
    5 gpg-pubkey-5ebd2744-418ffac9
    2 gpg-pubkey-e8562897-459f07a4
  2. Import the pubkeys which are not equals to 1 into files, in this example: gpg-pubkey-217521f6-45e8a532, gpg-pubkey-5ebd2744-418ffac9, gpg-pubkey-e8562897-459f07a4 :

    # rpm -qi gpg-pubkey-217521f6-45e8a532 > pubkeys.import1
    # rpm -qi gpg-pubkey-5ebd2744-418ffac9 > pubkeys.import2
    # rpm -qi gpg-pubkey-e8562897-459f07a4 > pubkeys.import3
  3. Manually remove duplicate records in files using test editor. Make sure that only one public key block exists, for example:

    Name        : gpg-pubkey                   Relocations: (not relocatable)
    Version : 217521f6 Vendor: (none)
    ...
    ...
    -----BEGIN PGP PUBLIC KEY BLOCK-----
    Version: rpm-4.4.2 (beecrypt-4.1.2)

    mQGiBEXopTIRBACZDBMOoFOakAjaxw1LXjeSvh/kmE35fU1rXfM7T0AV31NATCLFl5CQiNDA
    4oWreDThg2Bf6+LIVTsGQb1V+XXuLak4Em5yTYwMTVB//4/nMxQEbpl/QB2XwlJ7EQ0vW+ki
    PDz/7pHJz1p1jADzd9sQQicMtzysS4qT2i5A23j0VwCg1PB/lpYqo0ZhWTrevxKMa1n34FcD
    ...

    W+89avct35gIyrBbof5M+CBXyAOUaSWmpM2eub240qbqiSr/Y6Om0t6vSzR8gRk7g+1H6IE0
    Tt1IJCvCAMimiE8EGBECAA8FAkXopTYCGwwFCRLMAwAACgkQEZzANiF1IfZQYgCgiZHCv4xb
    +sTHCn/otc1Ovvi/OgMAnRXYbbsLFWOfmzAnNIGvFRWy+YHi
    =MMNL
    -----END PGP PUBLIC KEY BLOCK-----
  4. Remove current pubkeys:

    # rpm -e --allmatches gpg-pubkey-217521f6-45e8a532
    # rpm -e --allmatches gpg-pubkey-5ebd2744-418ffac9
    # rpm -e --allmatches gpg-pubkey-e8562897-459f07a4
  5. And then import correct ones:

    # rpm --import pubkeys.import1
    # rpm --import pubkeys.import2
    # rpm --import pubkeys.import3
  6. Check the output:

    # rpm -qa | grep gpg-pubkey | sort | uniq -c
    1 gpg-pubkey-00f97f56-467e318a
    1 gpg-pubkey-217521f6-45e8a532
    1 gpg-pubkey-5ebd2744-418ffac9
    1 gpg-pubkey-e8562897-459f07a4
Have more questions? Submit a request
Please sign in to leave a comment.