• If you are still using CentOS 7.9, it's time to convert to Alma 8 with the free centos2alma tool by Plesk or Plesk Migrator. Please let us know your experiences or concerns in this thread:
    CentOS2Alma discussion

List of applications could not be loaded at the moment.

AlisonP

New Pleskian
When looking at applications on a domain, [Featured applications] shows the message "Search results could not be loaded at the moment." with a link to retry without fail.

On [All available applications] we can see the overall structure (Web, Personal, sub categories) but if we try to look at a section, particularly a larger one, such as web it will just show "List of applications could not be loaded at the moment.", again with the option to keep retrying.
Searching seems to work for some queries and not others - it seems like if a list of a certain size would be returned it just won't show it.

The attached image shows in red ones that we have had problems with if that helps diagnose a pattern.
Is it possible that we just have a slow connection and that it times out?
 

Attachments

  • apsfail.png
    apsfail.png
    71.8 KB · Views: 20
Hm we don't seem to get that - was it on the panel or in logs?

right - but instead of you, we even can not access the application vault manager. maybe this odbc-error-message can help parallels, to fix this issue.

regards, gtsupport
 
After looking in /var/log/sw-cp-server/error_log I see lots of entries along the lines of

2011-07-14T15:30:26+01:00 ERR (3): APS Catalog error: Unable to define main IP address

After attempting once more to go to the applications vault the line appeared again in the error log so I'm pretty sure this is the issue.
Unfortunately I am unsure if this refers to the APS catalogue IP or the server's.
It seems odd that this only affects some parts of the catalog and only some searches though.


FIXED
-----------------------------------------------------------
After a very nice member of the plesk support team has looked at our server, they found this error message and made the following changes.
It seems that due to an issue we had previously had the server considered its only IP address not to be the main one.

mysql> select * from psa.IP_Addresses;
+----+-------------+-----------------+-------+--------------------+-------------------+-------+-------+--------+
| id | ip_address | mask | iface | ssl_certificate_id | default_domain_id | ftps | main | status |
+----+-------------+-----------------+-------+--------------------+-------------------+-------+-------+--------+
| 2 | xx.xx.xx.xx | 255.255.255.240 | eth0 | 4 | 12 | false | false | 0 |
+----+-------------+-----------------+-------+--------------------+-------------------+-------+-------+--------+

mysql> update IP_Addresses set main = 'true' where id=2;

mysql> select * from psa.IP_Addresses;
+----+-------------+-----------------+-------+--------------------+-------------------+-------+------+--------+
| id | ip_address | mask | iface | ssl_certificate_id | default_domain_id | ftps | main | status |
+----+-------------+-----------------+-------+--------------------+-------------------+-------+------+--------+
| 2 | xx.xx.xx.xx | 255.255.255.240 | eth0 | 4 | 12 | false | true | 0 |
+----+-------------+-----------------+-------+--------------------+-------------------+-------+------+--------+


-----------------------------------------------------------
 
Last edited:
Back
Top