I was taking a look at this particular install from the hosting side and noticed some interesting spikes in the DB CPU utilization, some of which even lined up with previous tests as far as timing. Your other sites on FW aren’t utilizing the same instances, so I’m curious if you’re able to test pulling, pushing, or migrating those at all to see if they run into any of the same problems you’ve been having these last couple of weeks with this install. Understandable if you don’t want to do any of this on live sites so you could also enable Staging and test there as an alternative. No rush at all, just keep us posted either way
I don’t know what changed but, the past few pushes have been successful. Strange. I don’t know if it was an update (running Version 9.0.4+6699 now) but, it’s working. Knock on wood.
I’ve tried all the usual stuff, shutting down, restarting, logging in/out, I even upgraded to the latest version of local (which I was scared to do). I would really appreciate a nudge in the right direction. Thanks!
Something else I wanted to clarify is if this is happening to a specific install (you don’t have to share the name here), or if it is happening across all of your installs? I mentioned some curious activity I noticed server side for one of your installs last time, but this wouldn’t impact all of your sites that you interact with since they are not all on the same Fleet from an infrastructure standpoint. Just trying to narrow our focus here!
I took a look at that install and made a few changes to see if they can help out from the server side of things. When you’re ready could you give it another test and let me know?
I’m not 100% on the root cause. I noticed one Local job was still “stuck” so I errored that out, but also the site was hitting some resource and timeout limits, which could also maybe have been contributing. I gave it a little boost which seemed to do the trick. Again I’m not positive that’s all that was the problem, but it does seem to be something unique to only this install. The DB CPU I mentioned previously has been completely quiet, so not sure if that was a problem before but not now. It could be that there were multiple culprits here.
In either case, I’ve double-checked and can see the Local job finished up as complete on the FW side and not stuck or in any other state! Keep us posted of course if anything should change and we’ll continue to help out!
If my adjustments did indeed fix things up then no it wouldn’t be anything you could impact from your end. You’d still have to reach out here or directly to Flywheel support to have them look. As I’ve mentioned though their free migration plugin works going from Local to Flywheel, so you can always use that as an alternative if you’re stuck and in a rush.
