• Debian 11 is approaching its end-of-life (vendor EOL date - August 31, 2026). Plesk Obsidian 18.0.80 will be the last release to support it.
    If you are running Plesk Obsidian on Debian 11, we recommend you upgrade those servers to Debian 12 using our dist-upgrade tool.
  • We plan to deprecate and remove the support for XML RPC protocol versions earlier than 1.6.9.1 in Plesk Obsidian 18.0.82. We strongly recommend that you update all existing integrations using earlier versions of the XML RPC protocol to comply with the version 1.6.9.1 specification.

PMM mysql charset problems - pls help

N

next-step

Guest
Big problem during migration:

below is the example of migration results
I'm sure its charset problem

In the original server psa database has cp1251 charset.

Please help how can I rectify this?

Code:
Execution of /usr/local/psa/bin/client --update golden -phone +7\ 923\ 333\ 7838 -city  -company \ - -country RU -zip 633009 -state  failed with return code 1.
Stderr is
An error occured during client update: Unable to update client data: cObject::update() failed: Some fields wrong or has inproper values: 'state' = .

  	Execution of /usr/local/psa/bin/client --update golden -country RU -zip 633009 -state  failed with return code 1.
Stderr is
An error occured during client update: Unable to update client data: cObject::update() failed: Some fields wrong or has inproper values: 'state' = .
 
Plesk (starting from 7.x) stores all records in database in UTF8. If you set system locale on both source and destination hosts to unicode - you greatly reduce probability of encoding problems.

Plesk don't like particular 'state' field. It is limited to just 50 characters and your double-encoded 'Новосибирская' have 54 symbols in it...
 
Back
Top