Version is 5.6.8+4514
I am pushing a site from Local to WP Engine and it is stuck on this step " Checking remote table prefix". This is the first time this has happened so I am wondering if it might be a bug in the latest version?
Any insight into the issue is appreciated, thank you!
Hey Zola –
There have been a few people that have reported an issue similar to this one. To help us zero in on what exactly is happening, can you please provide your Local Log? See this Community Forum post for instructions on how to do so:
Sure thing, please find attached my log. Thank you for the quick response!
local-lightning.log (347.1 KB)
Thanks for that log!
It does appear to be related to the bug that we’re currently investigating. In the meantime, can you try downloading and installing a slightly older version of Local?
I think that the 5.6.6 version should be good:
Sure thing, do I need to remove the current version before I do that or just replace it with this older version? TY again.
You can install the older version over the existing installation. No need to uninstall first.
same issue, here’s a copy of my loglocal-lightning.log (378.2 KB)
same issue here, here is my log local-lightning.log (989.0 KB)
Hey everyone – Local 5.6.10 has been released and should help with a number of issues that have come about when pushing to WP Engine.
Can you all try installing that latest version and let us know if it allows you to successfully push the site?
Hey @erianz – you liked the above post! I just wanted to make sure that things are working for you with that latest release?
Is everything good on your end?
I’m suddenly having the same issue and I’m on version 5.6.10.
local-lightning.log (2.9 KB)
Hey @jasonones, Welcome to the Local Community Forums!
Taking a look at that Local log, I’m thinking that this might be a slightly different issue that is causing Local to stall out at the same screen. For reference, here are the couple of error lines in the Local log:
{"thread":"main","class":"CAPIService","message":"Flushing page cache for install f25d7f79-3f7a-43c6-91f7-8a9bd1a21102","level":"info","timestamp":"2020-08-18T00:01:03.509Z"}
{"thread":"main","class":"CAPIService","message":"Error flushing page cachePage cache purges are rate-limited to one request every 300 seconds for each install","level":"warn","timestamp":"2020-08-18T00:01:04.082Z"}
{"thread":"main","class":"CAPIService","message":"Error flushing cdn cacheCDN cache purges are rate-limited to one request every 120 seconds for each install","level":"warn","timestamp":"2020-08-18T00:01:04.215Z"}
{"thread":"main","class":"","message":"client_loop: send disconnect: Broken pipe\r\n","level":"warn","timestamp":"2020-08-18T00:04:53.662Z"}
{"thread":"main","class":"","message":"rsync: connection unexpectedly closed (0 bytes received so far) [sender]\nrsync error: error in rsync protocol data stream (code 12) at /AppleInternal/BuildRoot/Library/Caches/com.apple.xbs/Sources/rsync/rsync-54.120.1/rsync/io.c(453) [sender=2.6.9]\n","level":"warn","timestamp":"2020-08-18T00:04:53.662Z"}
{"thread":"main","class":"","level":"info","message":"\u001b[1;31m\rError: \u001b[0mUnable to push: exit status 12\n","timestamp":"2020-08-18T00:04:53.668Z"}
Note that it seems like the WP Engine side of things is having problems flushing the cache on the remote server. Since the error seems to relate to the cache request being throttled, can you try pushing one more time and let us know if that allows you to push?
I have the same issue
is it going to be fixed?
Hey @betalocal –
Because of the general nature of this, there’s a number of things that should have been fixed with the recent version of Local. Can you describe in a little more detail what you are seeing?
In at least one instance here:
The user wasn’t able to finish pushing the site because the Hotel Wifi was preventing the push from finishing. When they switched to their phone hotspot, it started working.
As a test, can you try pushing over a different network? If that doesn’t work, can you please provide your Local Log? See this Community Forum post for instructions on how to do so:
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.