MySQL Plugin Migration Crashed
I used the automated plugin migration/upgrade option. Did this for multiple projects of the exact same type (Ghost blog) and all worked but this one. The migration crashed part way through and looks like it failed to add the correct variables to the new the migration task node. Not sure how to proceed from here.
28 Replies
Project ID:
0f9105b2-9d4d-4bc3-9922-92407d96c9f50f9105b2-9d4d-4bc3-9922-92407d96c9f5
the migration service would never have those variables, you seeing that message on the migration service is perfectly normal.
check it's logs for an error message
There is no logs tab for the migration node. This was about a month ago and i was ready to mess around with it any further as the service is still working. This is where i stand:
the migration service is the same as any other service, it has logs, please check them
not tab like the others
click the deployment and then click logs, same as any other service
there we go
so looks like it never actually ran? Looking for guide to proceed here.
before I tag in a team member, does your legacy database have more than 5gb of data in it?
no def not, i think its just 256MB but again im not 100% which node is the prime for the app right now. The node structure kinda feels like i got feet in two boats
no no, in your legacy database
again, this is why i say i have feet in two boats as there is no longer a volume disk under the legacy DB node and therefore under metrics there is no storage amount or a volume to click on. The only volumes i have are the main Ghost node which is just for media content (also like 500MB currently) and the new empty DB with i guess a default 256MB. Either way, i'm pretty sure the DB pre migration was no where near 5GB in total.
there has never been a volume on legacy databases
please confirm that your legacy database uses under 5gb of storage space
yes it was not using more than 5 GB
may I ask what command you ran that helped you come to that conclusion?
i didn't run a command but for a standard Ghost DB even in the extreme it would not hit 5GB in size. This is a very small Ghost intance usage wise
I also compared to other Ghost projects i have that had a successful migration and have a similar amount of usage/scale (number of members/posts) and this is the MySQL volume DB size
can you delete the new databases and failed migration service and run another migration? if that fails I will tag in the person on call
ok attempting migration again now
ok looks like it migrated correctly this time and the Ghost site is working still after the final deployments. I will monitor for any issues over the next couple days before deleting the migration node.
you can delete the migration service, just don't delete the legacy database until everything is confirmed working
I only have 3 after the migration
you can change the name of the database with a volume to just
MySQL
your ghost service is using variable references right?yes
okay great!
thanks for your help
no problem!