HOWTO migrate stuff automatically from WebFaction!

pjrobertson

I think I found a workaround for issue #3 above:

pjrobertson wfmigrate wordpress doesn't seem to work for cases where the Wordpress install isn't in the base directory

To use wfmigrate in this case, on your Webfaction server, copy wp-config.php from its wordpress sub-folder to the app's root directory. Then re-run wfmigrate. Once the migration has been complete, on your Opalstack server, move wp-config.php from the root folder back to the wordpress sub-folder.

sean

pjrobertson wfmigrate wordpress doesn't seem to work for cases where the Wordpress install isn't in the base directory

Our WP migrator is designed to work with the standard WP install that WF provided.

debiprasad

Migrating WordPress websites were working fine 2 days ago. But now it's throwing an error:

2020-11-08 14:49:22 : DEBUG : Got stdout: "", stderr: "mysqldump: Got error: 1045: Access denied for user 'debiprasad_oriya'@'localhost' (using password: NO) when trying to connect", retcode: 2

dolomiti

debiprasad @sean
I ran in the same issue. In my case the WF mysql password started with a "#" char, and I suppose that the Opalstack script ignored it supposing it was a comment (hence the message "using password: NO").
Changing the password on the WF side before migrating the worpress app to Opalstack, avoiding the presence of a "#" char at the beginning solved my problem. I wrote my workaround here in case somebody will hit the same issue in the future.

debiprasad

Another error in another WordPress migration:

2020-11-08 14:58:42 : INFO : Extracting DB User credentials from /home/debiprasad/apps/ost_staging/wp-config.php
...
UnicodeDecodeError: 'ascii' codec can't decode byte 0xe2 in position 3205: ordinal not in range(128)

sean

debiprasad Another error in another WordPress migration:

Please email support to let us know the location of the config file that you're using so that we can investigate this.

tinygod

My last two WordPress migrations ended like this:

2020-11-08 16:48:08 : INFO : Checking .htaccess for incompatible directives
Traceback (most recent call last):
  File "/usr/local/bin/wfmigrate", line 67, in <module>
    migrator.run()
  File "/opt/app_migrators-1.3.2/wf_wordpress/migrator.py", line 184, in run
    self.migrate()
  File "/opt/app_migrators-1.3.2/wf_wordpress/migrator.py", line 166, in migrate
    self.wf_migrator_php.check_htaccess()
  File "/opt/app_migrators-1.3.2/lib/wf_migrator_php.py", line 136, in check_htaccess
    for line in fp:
  File "/usr/lib64/python3.6/encodings/ascii.py", line 26, in decode
    return codecs.ascii_decode(input, self.errors)[0]
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc3 in position 87: ordinal not in range(128)

Please advise.

sean

tinygod Thanks for the report, we're looking into it! In the meantime please email our support address to let us know the location of the config file you were using when this happened. Please don't email the file to us since it contains passwords etc.

pjrobertson

Great to see the addition of more options in the Maria/psql migration configs!

Having the ability to now specify the database name, username and password (if the username already exists) on the Opalstack side is great! Keep up the good work ❤️

saebel

OMG! That was amazing. I was able to migrate some of my simpler apps in no time flat.

Now, of course, I have some weird stuff with Laravel which I had to install separately and then use a symbolic link to point to the public directory. I don't get the impression that will be a simple thing to migrate. So I'm guessing I'll need to manually do those sites after installing Laravel, Composer, etc?

Also, I have private MySQL instances. Can those be migrated using the tool? I'm guessing no because it doesn't follow the standard patterns (as in there are no databases or database users in the Webfaction control panel).

webscience

sean Dear Sean, i found the problem. It was a stupid mistake from my side, the client changed the server pw and kept the ssh pw the same. However, now i have another problem. The wordpress install is in de app directory but i still get this:
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.4.0/wf_wordpress/migrator.py", line 32, in __init__ self.wordpress_cfg = WordpressCfg(cfg['wordpress']) File "/opt/app_migrators-1.4.0/wf_wordpress/migrator.py", line 22, in __init__ self.wordpress_path = data['wordpress_path'] File "/usr/lib64/python3.6/configparser.py", line 1233, in __getitem__ raise KeyError(key) KeyError: 'wordpress_path'

sean

webscience and all: we are constantly updating the wfmigrate tool with new features and configuration options.

The instructions above include a step to copy the config template prior to running the migrator.

That step isn't optional - be sure to do it every time to ensure that you have the correct config template.

Thanks!

webscience

sean Thank you Sean, this works!

Sleckie

Sean,
What about web2py apps? As far as migrating?

sean

Sleckie use the "port" app option to migrate your web2py apps.

After the app is migrated you'll need to create a Python env in the app directory, pip install uwsgi into that, and then configure uwsgi to serve the app.

You'll need to migrate any related databases separately.

Axel

Getting the following errors when running the migration script for a PHP 5.6 app. What am I missing ?

[...@opal1 ~]$ wfmigrate php ./config.ini --mode simulate
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.4.0/wf_generic_php/migrator.py", line 12, in init
self.opal_cfg = OpalCfg(cfg['opalstack'])
File "/opt/app_migrators-1.4.0/lib/config_types/opal_cfg.py", line 13, in init
self.update_derived_attrs()
File "/opt/app_migrators-1.4.0/lib/config_types/opal_cfg.py", line 19, in update_derived_attrs
self.opal_shelluserObj = self.opal_api.get_shelluserObj(self.opal_shelluser_name)
File "/opt/app_migrators-1.4.0/lib/opalapi.py", line 460, in get_shelluserObj
return self.get_model('user', 'users', 'name', name)
File "/opt/app_migrators-1.4.0/lib/opalapi.py", line 449, in get_model
result = self.get(f'{model}/list/', ensure_status=[200])
File "/opt/app_migrators-1.4.0/lib/opalapi.py", line 443, in get
return self.request_result(urlpath, None, 'GET', ensure_status)
File "/opt/app_migrators-1.4.0/lib/opalapi.py", line 439, in request_result
resp, result = self.request(urlpath, dataObj, method, ensure_status)
File "/opt/app_migrators-1.4.0/lib/opalapi.py", line 435, in request
raise RuntimeError(f'Unexpected status_code: {resp.status_code}')
RuntimeError: Unexpected status_code: 401

sean

Axel Sounds like your API token might be incorrect. Please check apitoken in your config and ensure the value matches the token you created at https://my.opalstack.com/tokens/ in step 2.

Axel

Correct, that fixed it - thanks.

Axel

Is there a guide wrt. the "fpm_max_children = 5" and "fpm_max_requests = 20" lines in config.ini ? Under what conditions should these be adjusted and how ? I'm migrating mainly PHP 5.6 and Wordpress 4.4.2 apps.

sean

Axel those PHP options will only work on our Nginx+PHP-FPM stack and are not applicable to your Apache+PHP apps (including WP).

I know the UI shows them for Apache+PHP but we'll be removing them soon. They might come back if we can come up with a scalable Apache+PHP-FPM setup.

« Previous Page Next Page »