Error migrating to Opalstack from Webfaction - Late to the party!

russturley

I am attempting to migrate a handful of websites from webfaction to opalstack. I super late on this considering webfaction shuts down on 9/15.

Anyway, I populated my first migration config with a simple wordpress site as a test and received the following errors.

 [russturley@opal8 ~]$ wfmigrate wordpress config.ini --mode simulate
 
 ## The following error was encountered during operation: Unrecognized deploy_type: (Apache-CGI or Nginx-FPM) (expected one of ['Apache-CGI', 'Nginx-FPM'])
 ##
 ## 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-09-12 18:12:03 : ERROR : Unrecognized deploy_type: (Apache-CGI or Nginx-FPM) (expected one of ['Apache-CGI', 'Nginx-FPM'])
 Traceback (most recent call last):
   File "/usr/local/bin/wfmigrate", line 109, in <module>
     migrator = __import__(module).Migrator(cfg, args)
   File "/opt/app_migrators-1.12.2/wf_wordpress/migrator.py", line 31, in __init__
     self.php_cfg = PhpCfg(cfg['php'])
   File "/opt/app_migrators-1.12.2/lib/config_types/php_cfg.py", line 21, in __init__
     raise ValueError(f'Unrecognized deploy_type: {self.deploy_type} (expected one of {DEPLOY_TYPES})')
 ValueError: Unrecognized deploy_type: (Apache-CGI or Nginx-FPM) (expected one of ['Apache-CGI', 'Nginx-FPM'])

sean

russturley in your migration config set deploy_type to either of the following:

deploy_type = Apache-CGI
deploy_type = Nginx-FPM

russturley

Right. I missed that option. All good.

Thank you.

russturley

The first two Wordpress installs that I migrated completed with a problem. The second two transferred the application, but seem to have hung on transferring the database. The domain name did transfer as well.

What's the best way to proceed in this case?

sean

russturley have a look at ~/logs/apps/name_of_app/install.log to see the cause of the failure.

The usuals suspect is a DB user or DB that already exists. This might happen if you've accidentally run a migration a second time, or if you have 2 apps that use the same DB (unlikely for WP).

If you're not sure how to proceed after checking the log then please email support @ opalstack.com with the details so that we can take a closer look. Thanks!

sean

russturley Actually I think I misunderstood what you wrote. It's possible that the migrator had trouble parsing your WP DB password so it wasn't able to transfer the database. Feel free to email the error message that the migrator give you, including _20ish lines of output from before the error occurred.