HOWTO migrate stuff automatically from WebFaction!

orchardandy

I was able to migrate 4 data-rich Wordpress installations and four domains very smoothly. Thank you for providing a great tool and a great avenue to jump ship!

I do really hope that Opalstack is able to stay solvent and independent for decades to come, as Webfaction/GoDaddy isn't even the first host that's screwed me over...

In case this helps anyone, I will note that my first Wordpress migration actually returned a 500 error on Opalstack servers, somewhat disheartening. Looking at the server logs, this was due to a function call in a plugin that was deprecated in PHP7. I changed the application's PHP version to 5 through the Opalstack panel, and everything ran smoothly, easy peasy.

You can check what platform your apps were previously running on in the Webfaction applications panel, if you have compatibility problems like this. I have since noted that there is also an option in the Opalstack migrator configuration to set versions from the outset.

ericxob

sean OK, I'll send an email... I'm getting pretty verbose here. 😉

Thank you!

For others looking for clues... After I remembered there was such thing, I activated php error display by editing .htaccess. After doing that and reloading my site I got no PHP error but I did get a visible message! Eureka! I saw "500 Internal Server Error" And "The server encountered an internal error or misconfiguration and was unable to complete your request." ...

Ah Hah! Reminds me there are things such as log files. I found log files at <sshusername>/logs/). Inspecting them I saw numerous "connection refused" errors. Progress!

odhiambo

wil Sorry just seeing this today. However for those still moving out of webfaction...what I did is to copy the 'wf_archive_delivery' folder that they place in your root (at WF) to your root in opalstack. You then run the rest of the 'email-data' migrator as provided in the instructions here.

wil

odhiambo thank you, i try this yesterday and it works! That was my error.

will13

I'm getting a db error when running the simulation...
"mysqldump: Got error: 2005: Unknown MySQL server host 'localhost:3306' (2) when trying to connect"

sean

will13 I think if you change localhost:3306 to localhost in your WP config at WF prior to running the migration you should be OK.

jaxcode

Why am I getting this error:

RuntimeError: Command ['sshpass', '-f', 'bostonkids@wf-207-38-92-110.webfaction.com.opalmigration.passwd', 'rsync', '-a', '-e', 'ssh -o PasswordAuthentication=yes -o PubkeyAuthentication=no -o StrictHostKeyChecking=no', 'bostonkids@wf-207-38-92-110.webfaction.com:webapps/beyond/', '/home/bostonkids/apps/beyond/'] exited with status 127, stderr: "bash: rsync: command not found
rsync: connection unexpectedly closed (0 bytes received so far) [Receiver]
rsync error: remote command not found (code 127) at io.c(226) [Receiver=3.1.2]"

Is it because my server is server = wf-207-38-92-110
instead of a typical WF server like server = web503

sean

jaxcode server name shouldn't be a problem. Which migrator are you running?

jaxcode

sean I've tried php, wordpress, and mysql.

cleit0n

Guys, can you help me? My error follows:

[cleit0n@opal8 ~]$ wfmigrate wordpress ./config.ini --mode simulate

## The following error was encountered during operation: <Fault 1: 'Not allowed to login to machine "Web534.webfaction.com"'>
##
## Please ensure that you are modifying the latest version of the configuration template:
##
##     /opt/app_migrators/wf_wordpress/config-template.ini
##
## If you have any questions, please contact Support, and include the follwing error information for debugging:

2020-12-12 19:51:47 : ERROR : <Fault 1: 'Not allowed to login to machine "Web534.webfaction.com"'>
Traceback (most recent call last):
  File "/usr/local/bin/wfmigrate", line 101, in <module>
    migrator = __import__(module).Migrator(cfg, args)
  File "/opt/app_migrators-1.10.3/wf_wordpress/migrator.py", line 27, in __init__
    self.wf_cfg = WfCfg(cfg['webfaction'])
  File "/opt/app_migrators-1.10.3/lib/config_types/wf_cfg.py", line 10, in __init__
    self.update_derived_attrs()
  File "/opt/app_migrators-1.10.3/lib/config_types/wf_cfg.py", line 18, in update_derived_attrs
    self.refresh_api_connection()
  File "/opt/app_migrators-1.10.3/lib/config_types/wf_cfg.py", line 14, in refresh_api_connection
    self.api_session_id, self.wf_account_cfg = self.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: 'Not allowed to login to machine "Web534.webfaction.com"'>
[cleit0n@opal8 ~]$

sean

cleit0n The problem is that you have the full WF hostname web534.webfaction.com in your config instead of the short hostname web534.

Our provided template config shows the short hostname as the example.

I've corrected that for you in your config and have corrected a couple of other problems that I mentioned in my reply to your ticket.

sean

jaxcode pretty weird!

I think I sorted out the problems you were having for your sites, but if your'e still having this problem with other migrations then please email support and we'll discuss it there. I'll post back here with whatever solution we arrive at.

phountain

I get this error too
2020-12-15 20:33:13 : ERROR : Unexpected status_code: 400 Traceback (most recent call last): File "/usr/local/bin/wfmigrate", line 102, in <module> migrator.run() File "/opt/app_migrators-1.10.3/wf_wordpress/migrator.py", line 214, in run self.migrate() File "/opt/app_migrators-1.10.3/wf_wordpress/migrator.py", line 185, in migrate self.wf_migrator_maria.create_mariauser() File "/opt/app_migrators-1.10.3/lib/wf_migrator_maria.py", line 67, in create_mariauser created = self.opal_cfg.api.mariausers.ensure(needed) File "/opt/app_migrators-1.10.3/lib/opalapi.py", line 155, in ensure created = self.create(tocreate, wait=wait) File "/opt/app_migrators-1.10.3/lib/opalapi.py", line 143, in create for item in tocreate: create_item(item) File "/opt/app_migrators-1.10.3/lib/opalapi.py", line 135, in create_item create_result = self.api.post(self.model + '/add/', item, ensure_status=[200]) File "/opt/app_migrators-1.10.3/lib/opalapi.py", line 532, in post return self.request_result(urlpath, dataObj, 'POST', ensure_status) File "/opt/app_migrators-1.10.3/lib/opalapi.py", line 525, in request_result resp, result = self.request(urlpath, dataObj, method, ensure_status) File "/opt/app_migrators-1.10.3/lib/opalapi.py", line 521, in request raise RuntimeError(f'Unexpected status_code: {resp.status_code}') RuntimeError: Unexpected status_code: 400 [phountain@opal9 ~]$

Any recommendations?

sean

phountain please email support with the details so we can take a look at your migration config.

cstrombe

First, thank you for setting this up. Second, I have a "cgi" site written in python on wf, uses .htaccess to point to the python file to execute. I'm not sure what type of app this would fall under--which arg would I pass to wfmigrate for this scenario?

sean

cstrombe use the PHP migrator with the Apache-PHP option if you want to migrate a CGI app, thanks.

Weird I know, but we use PHP-CGI for that app type, so CGI is enabled for them. You'll still need to set your CGI handler in htaccess post-migration: https://community.opalstack.com/d/222-howto-run-cgi-scripts-on-opalstack

joelmagalnick

I got an error similar to one above that you thought might be that I didn't have enough memory on the WF side:

> ERROR 1045 (28000): Access denied for user 'username'@'localhost' (using password: YES)

## The following error was encountered during operation: Command "['mysql', '--defaults-extra-file=username.opalmigration-local.passwd', '-u', 'username', 'xx_db']" exited with status 1
##
## Please ensure that you are modifying the latest version of the configuration template:
##
##     /opt/app_migrators/wf_wordpress/config-template.ini
##
## If you have any questions, please contact Support, and include the follwing error information for debugging:

2021-03-15 03:44:14 : ERROR : Command "['mysql', '--defaults-extra-file=joelmagalnick.opalmigration-local.passwd', '-u', 'username', 'xx_db']" exited with status 1
Traceback (most recent call last):
  File "/usr/local/bin/wfmigrate", line 106, in <module>
    migrator.run()
  File "/opt/app_migrators-1.11.0/wf_wordpress/migrator.py", line 214, in run
    self.migrate()
  File "/opt/app_migrators-1.11.0/wf_wordpress/migrator.py", line 190, in migrate
    self.wf_migrator_maria.import_db()
  File "/opt/app_migrators-1.11.0/lib/wf_migrator_maria.py", line 159, in import_db
    raise RuntimeError(f'Command "{cmd}" exited with status {result.returncode}')
RuntimeError: Command "['mysql', '--defaults-extra-file=username.opalmigration-local.passwd', '-u', 'username', 'xx_db']" exited with status 1

Any thoughts on how to increase memory on that side to not have this fail? I've tried twice so far to no avail and I have a few more applications to go.

sean

joelmagalnick If WF is terminating your processes due to high memory usage then that's not something we have any control over from here. You'll need to contact WF to see if they can can increase your memory allowance.

charles

I did the migration script yesterday for wordpress, telling it import into a mariadb that was already created here on opalstack.

The wp-config.php file had an error where the line define('DB_PASSWORD', '"passwword"'); had both single and double quotes around the password.

I'm guessing this is a rare use case, but FYI

sean

charles thanks for the report!

« Previous Page Next Page »