• Halloween is coming! To celebrate the occasion, we dusted off a couple of old skins, and even created a brand new one (Pixel).
    To get into the festive spirit, install the Skins extension.
  • The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question SOS: Inconsistency in the table 'DomainServices' for the column ipCollectionId: Web service cannot operate: the IP address list with ID 64 is empty.

JediSupport2

New Pleskian
Hello,

Grateful if anyone here can help guide me through resolving the error:
Inconsistency in the table 'DomainServices' for the column ipCollectionId: Web service cannot operate: the IP address list with ID 64 is empty.
The diagnose and repair function is unable to resolve the above.

Secondly, this is creating database inconsistency for the mail server. No mails processing for over 24 hours now.

Many thanks,
 

Attachments

  • Screenshot 2020-08-09 at 13.55.15.png
    Screenshot 2020-08-09 at 13.55.15.png
    235.4 KB · Views: 26
I don't know what the repair button does here. Have you tried fixing the Plesk database yet? Via shell command:

# plesk repair db
 
Issue is caused by the database inconsistency: there are domains without ipaddressid value set. You can find them with following command:

# plesk db "SELECT d.name,ipc.ipAddressId FROM domains d JOIN DomainServices ds on d.id=ds.dom_id LEFT JOIN IpAddressesCollections ipc on (ds.ipCollectionId = ipc.ipCollectionId ) WHERE ds.type='mail'"

So you have to fix this inconsistency by setting a proper IP address id for all domains with NULL in ipAddressId.
 
OK, but it is quite normal that there is no IP address, when the hosting type is set to "no hosting".

Like f.i. when I only host the DNS and mail systems for a domain, and the related website is hosted somewhere else.
With as consequence that the A record for the web content sends to an IP address that is not managed on the Plesk server.

In this case, "plesk repair db" gives messages like:

Inconsistency in the table 'DomainServices' for the column
ipCollectionId: Web service cannot operate: the IP address list with
ID 539 is empty ................................................... [
ERROR]
Generate an IP address list based on DNS records? [Y/n] y
Generating an IP address list ................................... [
FAILED]
- No IP addresses found in DNS records.


The diagnostic is correct, but systematically proclaiming that it is an error is a bit premature.
Because setting an IP address is a no-go, as Plesk will only admit the addresses that have been attributed to the server, not an external one.

Or am I missing something?
 
Back
Top