• 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!
  • 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.

Errors migrating domains with mailing lists

E

eryan

Guest
Hi.
Attempting to migrate domains with mailman mailing lists from a 9.5.3 server to a 10.01.

Source server: 9.5.3 RedHat el5 95101022.03
Destination:10.0.1 Debian 5.0 109101029.19

The domain and lists do seem to be created, but the mailing lists have a number of email subscribers missing.

Whether the errors are directly related to this is hard to tell.

Any help or suggestions greatly appreciated.

The errors starts follows and continues in the same vein for a while:

<?xml version="1.0"?>
<execution-result status="success"><object name="domainchanged.com" type="domain"><object name="andrew.connor@domainchanged.com" type="mailname"><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message></object><object name="ben.whittaker@domainchanged.com" type="mailname"><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message><message code="ExecCliGate::InternalServerError" severity="error"><context>void plesk::CliExec::analyzeResponse()</context><file>./cmd_exec.cpp</file><line>179</line><text>Internal server error: &lt;cli&gt;&lt;failure&gt;MySQL query failed: Unknown column 'object_name' in 'field list'&lt;/failure&gt;&lt;/cli&gt;</text></message>
 
Internal server error at restoring of mail name (MySQL query failed: Unknown column 'object_name' in 'field list') is related to psa-turba package. There can be old version of package installed on source server. For example:
# rpm -qa | grep turba
psa-turba-2.1.7-cos5.build86080722.00

# grep "DROP COLUMN" /usr/share/psa-horde/turba/scripts/upgrades/2.1_to_2.2_sql_schema.php
'ALTER TABLE ' . $db_table . ' DROP COLUMN object_name',
'ALTER TABLE ' . $db_table . ' DROP COLUMN object_homeaddress',
'ALTER TABLE ' . $db_table . ' DROP COLUMN object_workaddress',
Horde 2.2 dropped columns 'object_name', 'object_homeaddress', 'object_workaddress' in horde.turba_objects table, so restoration mailname addressbook failed.
 
Hi IgorG

Thanks for your swift reply.
Interestingly,

# rpm -qa | grep turba
psa-turba-2.3.3-rhel5.build95101209.08

So should I attempt to remove the columns manually?
 
I'm not sure that it is really the main reason of initial problem. It was just assumption based on my experience. But you can try at least.
 
I looked at the table in question, the turba_objects table, and it does not have the offending fields present. In fact the schema of the table on the source server and destination server look to be identical. So it does not seem to be a missed update script causing the problem.

The turba_objects table in the source server has 1,221 rows while the on the destination server the turba_objects table has zero rows, so it clearly failed to migrate this data.

Actually, all tables on the destination server's 'horde' database are empty. So it failed to migrate any horde data by the looks of it.

Could this be a bug with the migration manager?


Also, is there a way of getting more detailed logging from the migration manager?

It would be useful to see success and failures on a domain by domain basis.

Many thanks.
 
Back
Top