• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • (Plesk for Windows):
    MySQL Connector/ODBC 3.51, 5.1, and 5.3 are no longer shipped with Plesk because they have reached end of life. MariaDB Connector/ODBC 64-bit 3.2.4 is now used instead.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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: 24
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