HOWTO migrate stuff automatically from WebFaction!

allrite

klynton It appears to have completed successfully now. I also removed the .webfaction.com from the server address.

allrite

A couple of notes based on my migration of WordPress using the script:

Disable the Wordfence plugin first before migration if you are using it (if you forget you will probably need to manually edit the .htaccess and .user.ini files and maybe delete the plugin from wp-contents/plugins/).
Don't forget to assign any SSL certificate under Site Routes afterwards.

urbanian

Thanks allrite for flagging the problem with Wordfence, however, in my case it wasn't sufficient to simply disable Wordfence - this still caused a 500 error (blank screen) when I migrated the wordpress site, so I still had to manually edit the htaccess and .user.ini files to remove the Wordfence code.

ysli

Great tool! Thank you so much for this handy migration tool. One question tho - I am trying to migrate multiple databases under one user, but the simulation is telling me that (on the second database migration)
2020-11-01 10:17:38 : WARNING : Psqluser the_user already exists; it will be DELETED!
2020-11-01 10:17:39 : WARNING : Psqldb first_database is owned by the_user; it will be DELETED!

Is there a way to not delete user and the associated first_database during migration, but instead alter the user or use the existing user to create the second_database? Thanks!

sean

ysli Is there a way to not delete user and the associated first_database during migration, but instead alter the user or use the existing user to create the second_database?

I've brought this to the attention of our migration tool developer. Thanks!

dmeehan

ysli I am having this exact same issue. This is a great tool and hopefully can find a solution for this issue.

soto97

Thanks for putting together this migration script.

I am trying to migrate a Wordpress site, but I keep getting a "lost connection" error. When I run the simulation, it tests fine. But when I actually run the script, I get a "lost connection" error. Here's the debug output:

wfmigrate wordpress ./config.ini --mode do

. . . lots of output . . .
. . . then it asks me for my webfaction password . . 

2020-11-01 15:19:45 : DEBUG : Got stdout: "", stderr: "lost connection", retcode: 1
Traceback (most recent call last):
  File "/usr/local/bin/wfmigrate", line 67, in <module>
    migrator.run()
  File "/opt/app_migrators-1.3.1/wf_wordpress/migrator.py", line 189, in run
    self.migrate()
  File "/opt/app_migrators-1.3.1/wf_wordpress/migrator.py", line 157, in migrate
    self.wf_migrator_maria.export_db()
  File "/opt/app_migrators-1.3.1/lib/wf_migrator_maria.py", line 104, in export_db
    scp(self.remote_sqlpasswd_filename, self.wf_cfg.wf_userhost+':', self.ssh_cfg.ssh_privkey_path)
  File "/opt/app_migrators-1.3.1/lib/utils.py", line 34, in scp
    return run(cmd)
  File "/opt/app_migrators-1.3.1/lib/utils.py", line 11, in run
    raise RuntimeError(f'Command "{cmd_str}" exited with status {retcode}, stderr: "{stderr}"')
RuntimeError: Command "/usr/bin/scp -q -i /home/xxx/.ssh/id_rsa_opalmigration -o PasswordAuthentication=no -o StrictHostKeyChecking=no xxx_xxx.opalmigration-remote.passwd xxx@web516.webfaction.com:" exited with status 1, stderr: "lost connection"

Any idea what is wrong? I have this same problem with two different Wordpress sites.

sean

soto97 It sounds to me like your processes are being killed on WF's side. Maybe you're going over your memory limit there?

webscience

sean Thank you Sean. I think i filled out everything correctly but do get this error:
Traceback (most recent call last): File "/usr/local/bin/wfmigrate", line 66, in <module> migrator = __import__(COMPONENTS[args.component]['module']).Migrator(cfg, args) File "/opt/app_migrators-1.3.1/wf_wordpress/migrator.py", line 27, in __init__ self.wf_cfg = WfCfg(cfg['webfaction']) File "/opt/app_migrators-1.3.1/lib/config_types/wf_cfg.py", line 12, in __init__ self.update_derived_attrs() File "/opt/app_migrators-1.3.1/lib/config_types/wf_cfg.py", line 16, in update_derived_attrs self.wf_session_id, self.wf_account_cfg = self.wf_api.login(self.wf_account, self.wf_password, self.wf_server.capitalize(), 2) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1112, in __call__ return self.__send(self.__name, args) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1452, in __request verbose=self.__verbose File "/usr/lib64/python3.6/xmlrpc/client.py", line 1154, in request return self.single_request(host, handler, request_body, verbose) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1170, in single_request return self.parse_response(resp) File "/usr/lib64/python3.6/xmlrpc/client.py", line 1342, in parse_response return u.close() File "/usr/lib64/python3.6/xmlrpc/client.py", line 656, in close raise Fault(**self._stack[0]) xmlrpc.client.Fault: <Fault 1: 'LoginError'>

My password contains various characters which are not alphanummerical, might that be it?

sean

webscience we'll do some testing on our end and fix if necessary.

webscience

sean did you have looked into this issue? Thank you Sean for your help.

sean

webscience dmeehan we have not been able to reproduce the password issue that you've reported.

If you're still hitting this problem then please email support with to let us know the location of the config that you're trying to use. We'll also need your permission to actually run the migrator with that config.

sean

webscience I don't think the migrator dev has got to this just yet but most likely will within the next day or two

jwvanderbeck

One thing I wanted to post to help others that might get confused as I did. The config asks for your Opal and WF server names. Do NOT include the full domain name, only the first part. IE Opal4 or web556 and nothing else. If you include the rest it will cause issues. Unfortunately this isn't really stated anywhere that I saw so it hung me up for a while.

sean

jwvanderbeck Do NOT include the full domain name, only the first part.

The examples in the boilerplate config show that, eg:

server = opal1
...
server = web1

Follow the examples as provided and you should be good 🙂

jwvanderbeck The info in the OP says that the password will not be migrated, and so we should update the password to match our original password on WF.. however, the MariaDB won't let me use the same password because it doesn't have a number in it.

In that case you should use the second option in the instructions, ie "update your application settings to use the new DB password".

jwvanderbeck

On the issue of Wordpress database passwords..The info in the OP says that the password will not be migrated, and so we should update the password to match our original password on WF.. however, the MariaDB won't let me use the same password because it doesn't have a number in it.

I'm waiting for the DNS propagation so I can see if I can figure out how to update the password on the WordPress side, but not 100% familiar with that setup so we'll see.

jwvanderbeck

sean Yes the boilerplate shows it that way and maybe that made it obvious to you, but it was not obvious to me. I am simply sharing my experience in case others run into the same misleading errors.

jwvanderbeck

sean

The info in the OP says that the password will not be migrated, and so we should update the password to match our original password on WF.. however, the MariaDB won't let me use the same password because it doesn't have a number in it.
In that case you should use the second option in the instructions, ie "update your application settings to use the new DB password".

Yes, I just need to figure out HOW to do this 🙂

sean

jwvanderbeck Yes, I just need to figure out HOW to do this

For Wordpress, that would be changing the DB_PASSWORD option in your app's wp-config.php once the migration is complete.

jwvanderbeck

Ok just a follow up for information on the Database Password thing.. it appears that the Wordpress migrator at least DOES take care of the password for you. I finally found information on how to edit it, it is inside a PHP file, but the proper password was already in there.

So if you are migrating Wordpress it seems that this amazing script does it 100% for you. All I had to do by hand was update my domain's nameservers to point to Opalstack.

jwvanderbeck

sean Yep I found it, but it appears the migration script had already changed it for me, so all was good!

leehinde

Just to confirm the obvious, this is a read-only action on the WebFaction side and won't modify anything there. Right?

And second, will this work with the private Maria instances? I'm assuming so, just set the right target info.

sean

leehinde Just to confirm the obvious, this is a read-only action on the WebFaction side and won't modify anything there. Right?

yes 🙂

leehinde And second, will this work with the private Maria instances? I'm assuming so, just set the right target info.

probably not 🙁

I don't believe our MariaDB setup has drop-in binary compatibility with the DB store used by a private MySQL instance at WF. If you do migrate it over and it doesn't seem to work, then build a new private MariaDB instance on Opalstack and import your data into that manually.

« Previous Page Next Page »