• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Issue Apps Catalog fails: There are x dangling installations of WordPress

ehrenwert

Basic Pleskian
Hello,

I had to recover PLESK from Backup. After that the Application Vault is not working; Customers get "Failed to parse metadata" if they try to install an application like WordPress from Apps Catalog.

If I open the Application Vault I get


[2016-09-05 11:17:08] ERR [panel] There are 1 dangling installations of WordPress: (c67b9f23-6696-47d6-95fd-62160bac04e2)

[2016-09-05 11:17:08] ERR [panel] There are 1 dangling installations of WordPress: (0bd33a4c-8f8d-40f9-b5ea-9faf67f99b67)

[2016-09-05 11:17:08] ERR [panel] There are 1 dangling installations of WordPress: (df3e8641-7513-481f-b27c-0daca1aa9cd1)

[2016-09-05 11:17:08] ERR [panel] There are 1 dangling installations of WordPress: (566cacea-0df2-4da7-853b-f89e5644d141)

[2016-09-05 11:17:08] ERR [panel] There are 2 dangling installations of WordPress: (59a391c3-4dfe-44a4-af23-3a5bbea1badb, 69cdcadc-690c-4ec6-995e-c7eddf78be55)

[2016-09-05 11:17:12] ERR [panel] There are 1 dangling installations of WordPress: (c67b9f23-6696-47d6-95fd-62160bac04e2)

[2016-09-05 11:17:12] ERR [panel] There are 1 dangling installations of WordPress: (0bd33a4c-8f8d-40f9-b5ea-9faf67f99b67)

[2016-09-05 11:17:12] ERR [panel] There are 1 dangling installations of WordPress: (df3e8641-7513-481f-b27c-0daca1aa9cd1)

[2016-09-05 11:17:12] ERR [panel] There are 1 dangling installations of WordPress: (566cacea-0df2-4da7-853b-f89e5644d141)

[2016-09-05 11:17:13] ERR [panel] There are 2 dangling installations of WordPress: (59a391c3-4dfe-44a4-af23-3a5bbea1badb, 69cdcadc-690c-4ec6-995e-c7eddf78be55)

Interesting enough is that these ids are not located in the database:


MariaDB [apsc]> select `id`, `name`, `version`, `release`, `metafile_uri` from apsc.aps_package;

+----+-----------+---------+---------+----------------------------------------------------------------------------------+

| id | name | version | release | metafile_uri |

+----+-----------+---------+---------+----------------------------------------------------------------------------------+

| 1 | WordPress | 3.5 | 10 | /usr/local/psa/var/apspackages/2cf25276-7ba1-436a-aa43-a3157ecf97f1/APP-META.xml |

| 2 | WordPress | 4.3.1 | 119 | /usr/local/psa/var/apspackages/5b2ecd54-9338-46b1-81ac-e5a4373aa7df/APP-META.xml |

| 3 | WordPress | 4.3 | 118 | /usr/local/psa/var/apspackages/f2f25bc1-9076-4107-9834-9bdfd0795611/APP-META.xml |

| 4 | WordPress | 4.5 | 214 | /usr/local/psa/var/apspackages/328ccf8a-d141-4903-b636-ee8afd22f19a/APP-META.xml |

| 5 | WordPress | 4.5.3 | 221 | /usr/local/psa/var/apspackages/cfb2d56f-b678-4430-9518-aead3ebfd20b/APP-META.xml |

| 6 | WordPress | 4.1.1 | 90 | /usr/local/psa/var/apspackages/700ffcce-9b95-495a-a516-de7c98120ecb/APP-META.xml |

| 7 | WordPress | 3.7.1 | 22 | /usr/local/psa/var/apspackages/d88cefba-7eb4-43ed-b64e-77c3e9a54cfd/APP-META.xml |

| 8 | WordPress | 4.5.2 | 217 | /usr/local/psa/var/apspackages/c046bccd-36b9-45ad-a5a6-724ac4c16a97/APP-META.xml |

| 9 | magento | 1.9.2.2 | 39 | /usr/local/psa/var/apspackages/84bdfe89-61f9-4f86-897b-185fcf0b17f4/APP-META.xml |

| 10 | WordPress | 3.5.1 | 4 | /usr/local/psa/var/apspackages/5fbe428a-14e9-4204-ab54-abdbdb8115c8/APP-META.xml |

| 11 | WordPress | 3.7 | 16 | /usr/local/psa/var/apspackages/bae79a87-0f08-4628-b25e-4804097534aa/APP-META.xml |

| 12 | WordPress | 4.0 | 41 | /usr/local/psa/var/apspackages/761092b3-5647-4e96-b9f5-1753de1e9b74/APP-META.xml |

| 13 | WordPress | 4.0 | 64 | /usr/local/psa/var/apspackages/01860438-e0ae-4046-af4e-ba8bd2822c80/APP-META.xml |

| 14 | WordPress | 4.2.4 | 115 | /usr/local/psa/var/apspackages/34989e8c-4bed-4af0-a77e-30e81cab15e5/APP-META.xml |

| 15 | WordPress | 3.6.1 | 15 | /usr/local/psa/var/apspackages/2dbc15c4-e8fd-47dc-83a9-b0769ce9c4eb/APP-META.xml |

| 16 | WordPress | 3.5.1 | 6 | /usr/local/psa/var/apspackages/06f5be5b-495d-4eb0-b58e-65cd1eb0615b/APP-META.xml |

| 17 | WordPress | 4.4 | 132 | /usr/local/psa/var/apspackages/b862e755-e5ad-4a26-94a8-636e23a3c913/APP-META.xml |

| 18 | WordPress | 4.1 | 74 | /usr/local/psa/var/apspackages/1a86b61c-d8c4-454e-b0a7-e424d8be9299/APP-META.xml |

| 19 | WordPress | 3.9.1 | 37 | /usr/local/psa/var/apspackages/492bb74b-532f-47f7-95af-f4de7c6aeda8/APP-META.xml |

| 20 | WordPress | 3.9.2 | 38 | /usr/local/psa/var/apspackages/e34a7326-4bcc-444b-aa24-d969470f067f/APP-META.xml |

| 21 | WordPress | 3.9.1 | 34 | /usr/local/psa/var/apspackages/2ec0fd32-9478-4e01-aa40-1ec31193f286/APP-META.xml |

| 22 | joomla | 3.1.1 | 4 | /usr/local/psa/var/apspackages/8ee4c458-2d8e-4e4b-bdec-3dbc78b65e38/APP-META.xml |

| 23 | WordPress | 4.4.2 | 207 | /usr/local/psa/var/apspackages/60bd5c99-72a8-4463-b912-f172f5e76bb4/APP-META.xml |

| 24 | WordPress | 4.1.1 | 82 | /usr/local/psa/var/apspackages/b8c09c69-1dbf-4a6b-b35a-84b4cd6bbf63/APP-META.xml |

| 25 | WordPress | 4.0.1 | 70 | /usr/local/psa/var/apspackages/f5cf9aab-3566-4e8b-9713-02b4c3fa0821/APP-META.xml |

| 26 | joomla | 3.6.0 | 22 | /usr/local/psa/var/apspackages/bf539a28-3af3-422b-820a-5df591f3f291/APP-META.xml |

| 27 | WordPress | 4.0 | 69 | /usr/local/psa/var/apspackages/ff19a976-a51e-477d-8d5f-1c7a0ce63124/APP-META.xml |

| 28 | Piwik | 2.11.1 | 64 | /usr/local/psa/var/apspackages/d8cae54d-e577-4d3a-a4e5-ae26bcad1e01/APP-META.xml |

| 29 | joomla | 3.3.1 | 2 | /usr/local/psa/var/apspackages/58eab29f-6b89-4fb3-8123-df9c2753e88a/APP-META.xml |

| 30 | WordPress | 4.2.2 | 106 | /usr/local/psa/var/apspackages/2fb4bb60-ce0c-47e3-a18b-612d2d567e6a/APP-META.xml |

| 31 | WordPress | 3.6 | 14 | /usr/local/psa/var/apspackages/e0e1b418-dceb-47ab-9a33-2d2a91279ef9/APP-META.xml |

| 32 | WordPress | 4.2.3 | 112 | /usr/local/psa/var/apspackages/3b178ffe-ebf5-4107-9837-f6223859e4e0/APP-META.xml |

| 33 | WordPress | 4.1.1 | 81 | /usr/local/psa/var/apspackages/26acf883-eed4-4441-a6e6-0e966434baa8/APP-META.xml |

| 34 | WordPress | 3.9 | 33 | /usr/local/psa/var/apspackages/7c27c22a-af82-4407-9e7a-25248f3f7a8a/APP-META.xml |

| 35 | phpBB | 3.0.11 | 2 | /usr/local/psa/var/apspackages/2e55e1af-93c7-43d4-90e5-1f5ca7f63e62/APP-META.xml |

| 36 | PHProjekt | 6.0.6 | 2 | /usr/local/psa/var/apspackages/4bde1fc4-f380-4c97-bbc0-aff08dbd0ee1/APP-META.xml |

| 37 | WordPress | 3.8.1 | 28 | /usr/local/psa/var/apspackages/1ceaf137-42f0-496b-bf71-74a7adff034b/APP-META.xml |

| 38 | WordPress | 4.5.1 | 216 | /usr/local/psa/var/apspackages/620c4427-282b-40a3-ae45-365c0f7a8822/APP-META.xml |

| 39 | WordPress | 3.8 | 26 | /usr/local/psa/var/apspackages/443e0036-5245-4e20-8f48-7bcf1af0da36/APP-META.xml |

| 40 | magento | 1.9.2.4 | 75 | /usr/local/psa/var/apspackages/b26491e1-3f37-446f-8a34-90c273dfa82b/APP-META.xml |

+----+-----------+---------+---------+----------------------------------------------------------------------------------+

40 rows in set (0.00 sec)


Any solution for that?
 
Hi Igor,

well, I would like to solve this with this article; but is it possible that this KB is written for windows?
%plesk_dir%\MySQL\bin\mysql -P8306 -uadmin -p<plesk_admin_password> pst

let's me assume that this is the case...?

So if I would use

[2016-09-05 11:17:08] ERR [panel] There are 1 dangling installations of WordPress: (c67b9f23-6696-47d6-95fd-62160bac04e2)

I would do:

MariaDB [apsc]> select reg.id as REGISTRY_OBJECT_ID,reg.uid as APPLICATION_UID,reg.type as TYPE,ap.id as APPLICATION_ID from apsc.aps_registry_object reg left join apsc.aps_application ap on reg.id=ap.registry_object_id where reg.uid='c67b9f23-6696-47d6-95fd-62160bac04e2';

+--------------------+--------------------------------------+-----------------+----------------+

| REGISTRY_OBJECT_ID | APPLICATION_UID | TYPE | APPLICATION_ID |

+--------------------+--------------------------------------+-----------------+----------------+

| 959 | c67b9f23-6696-47d6-95fd-62160bac04e2 | aps.application | 154 |

+--------------------+--------------------------------------+-----------------+----------------+


and

mysql> delete from apsc.aps_application_resource where app_id=154;
mysql> delete from apsc.aps_application where id=154;
mysql> delete from apsc.aps_registry_object where id=959;

mysql> delete from psa.apsContextsApplications WHERE (apsContextId IN ('154'));

right?
 
Plesk database (psa) structure is the same for Windows and Linux.
So, use solution from article for your Plesk for Linux.
 
Hello Igor,

thanks a lot.

Well, I try to:


MariaDB [apsc]> select reg.id as REGISTRY_OBJECT_ID,reg.uid as APPLICATION_UID,reg.type as TYPE,ap.id as APPLICATION_ID from apsc.aps_registry_object reg left join apsc.aps_application ap on reg.id=ap.registry_object_id where reg.uid='c67b9f23-6696-47d6-95fd-62160bac04e2';

+--------------------+--------------------------------------+-----------------+----------------+

| REGISTRY_OBJECT_ID | APPLICATION_UID | TYPE | APPLICATION_ID |

+--------------------+--------------------------------------+-----------------+----------------+

| 959 | c67b9f23-6696-47d6-95fd-62160bac04e2 | aps.application | 154 |

+--------------------+--------------------------------------+-----------------+----------------+

1 row in set (0.00 sec)

MariaDB [apsc]> delete from apsc.aps_application_resource where app_id=154;

ERROR 1146 (42S02): Table 'apsc.aps_application_resource' doesn't exist
 
MariaDB [apsc]> delete from apsc.aps_application_resource where app_id=154;

ERROR 1146 (42S02): Table 'apsc.aps_application_resource' doesn't exist

Do this for the other tables:

4 - Remove the rest of the data.

mysql> delete from apsc.aps_application_resource where app_id=12;
mysql> delete from apsc.aps_application where id=12;
mysql> delete from apsc.aps_registry_object where id=666;

mysql> delete from psa.apsContextsApplications WHERE (apsContextId IN ('12'));
 
Hi Igor,

this does not work aswell:


MariaDB [apsc]> delete from apsc.aps_application where id=154;

ERROR 1451 (23000): Cannot delete or update a parent row: a foreign key constraint fails (`apsc`.`aps_resource`, CONSTRAINT `FK_aps_resource_aps_application` FOREIGN KEY (`app_id`) REFERENCES `aps_application` (`id`) ON DELETE NO ACTION ON UPDATE NO ACTION)
 
Hi Igor,

I can not - I bought the license from a German License-Dealer; so I get the response:

It was identified that your Plesk license was purchased from one of the Plesk Partners. We strongly recommend that you request support from that provider. Plesk Partners are fully trained by Plesk and deliver best-in-the-industry support for Plesk products running on their infrastructure. You can use the product documentation (docs.plesk.com) and Knowledgebase (kb.plesk.com) to find a solution or ask a question on the Plesk Forum (talk.plesk.com). Plesk Partners should use their support codes to contact Plesk technical support team.

This partner said I had to solve the problem by following the KB article. But this does not help, as I wrote above :-(
 
It is really complex apsc database inconsistency. It is very difficult to fix it in scope of forum discussion. Access to database and your server is required. Maybe someone from Plesk community will help you with it.
 
Would it be possible to create a ticket at plesk with a support code or something like that? I do not think that the plesk reseller will be able to solve the problem.
 
Hello,

I'm getting a new error:
[06-Sep-2016 15:24:53 Europe/Berlin] PHP Fatal error: Call to a member function getWordPress() on null in /usr/local/psa/admin/plib/Smb/View/List/App/Instances.php on line 152

[06-Sep-2016 15:25:17 Europe/Berlin] PHP Fatal error: Call to a member function getWordPress() on null in /usr/local/psa/admin/plib/Smb/View/List/App/Instances.php on line 152

[06-Sep-2016 15:25:31 Europe/Berlin] PHP Fatal error: Call to a member function getWordPress() on null in /usr/local/psa/admin/plib/Smb/View/List/App/Instances.php on line 152

[06-Sep-2016 15:25:40 Europe/Berlin] PHP Fatal error: Call to a member function getWordPress() on null in /usr/local/psa/admin/plib/Smb/View/List/App/Instances.php on line 152
 
Back
Top