Plesk Migration Manager

Včasih se zgodi, da se Plesku zmeša…

Pravilen zapis pri prenosu domene in clienta:

22:18:00 INFO Getting domain IP
22:18:00 INFO Dupming domain status
22:18:00 INFO Dumping domain databases
22:18:00 TRACE SQL: SELECT id FROM data_bases WHERE dom_id=DOMENA_ID
22:18:00 TRACE SQL: SELECT name, type FROM data_bases WHERE id=DOMENA_ID
22:18:00 TRACE SQL: SELECT host,port,ds.type FROM DatabaseServers as ds, data_bases as db WHERE ds.id = db.db_server_id AND db.id = DOMENA_ID
22:18:00 TRACE SQL: SELECT id FROM custom_buttons WHERE level=’LEVEL‘ AND level_id=’ID_LEVEL
22:18:00 INFO Client ‘USERNAME‘ is started
22:18:00 TRACE SQL: SELECT * FROM clients WHERE login = ‘USERNAME
22:18:00 TRACE SQL: SELECT password, type FROM accounts WHERE id = ‘ID
22:18:00 TRACE SQL: SELECT sp.name AS sapp_name, sp.version AS sapp_version, sp.release AS sapp_release FROM clients c INNER JOIN Repository r ON c.sapp_pool_id=r.rep_id LEFT JOIN SiteAppPackages sp ON r.component_id=sp.id WHERE c.id=’ID‘ AND (sp.access_level & 1) <> 0
22:18:00 TRACE SQL: SELECT tmpl_id FROM clients WHERE id=ID

Če pa pride do napake, pa se nam pojavi error:

'undef' value passed to XmlNode::addAttribute for 'type' at XmlNode.pm line 75.

ki nam na lep način pove, da je v vrstici

SELECT host,port,ds.type FROM DatabaseServers as ds, data_bases as db WHERE ds.id = db.db_server_id AND db.id = ID

prišlo do napake … razlog?

Če si pogledamo podatkovno tabelo, je njena običajna zgradba taka:

ID NAME TYPE DB_SERVER_ID
1 baza1 mysql 1
2 baza2 mysql 0

Sprememba je v 1 oz. 0 pri polju db_server_id. In ravno to - da ima nekdo zapisano 0 namesto 1 ali poljubnega naravnega števila povzroči, da se postopek migracije prekine.


Informacije o zapisu