Database is erased on pull

Support
1

Issue Summary

On pulling a site down, when it comes time to pull the database an error is given and the local database is erased.

Troubleshooting Questions

  • Does this happen for all sites in Local, or just one in particular?
    Yes, all sites

  • Are you able to create a new, plain WordPress site in Local and access it in a Browser?
    Yes

Replication

Doing any pull from WPEngine, whether a fresh site or update to existing.

System Details

  • Which version of Local is being used?
    7.0.1+6387

  • What Operating System (OS) and OS version is being used?
    Mac OS Ventura 13.4.1

  • Attach the Local Log. See this Help Doc for instructions on how to do so:

local-logs.zip (85.8 KB)

Security Reminder

Local does a pretty good job of scrubbing private info from the logs and the errors it produces, however there’s always the possibility that something private can come through. Because these are public forums, always review the screenshots you are sharing to make sure there isn’t private info like passwords being displayed.

2

Hi @tilla

Here is what I’m seeing in your Local Log:

{"thread":"main","class":"Process","process":"nginx","level":"warn","message":"nginx: [emerg] bind() to 0.0.0.0:443 failed (48: Address already in use)","timestamp":"2023-06-28T00:09:58.751Z"}
{"thread":"main","class":"Process","process":"nginx","level":"warn","message":"nginx: [emerg] still could not bind()","timestamp":"2023-06-28T00:09:59.256Z"}
{"thread":"main","class":"RsyncService","message":"rsync: [sender] opendir \"/sites/koelschsenior/.git\" failed: Permission denied (13)\n","level":"warn","timestamp":"2023-06-28T00:48:13.569Z"}
{"thread":"main","class":"RsyncService","message":"rsync error: some files/attrs were not transferred (see previous errors) (code 23) at main.c(1679)

Here are some steps to help us identify and address this:

  • Stop all sites that are running in Local

  • Force quit Local

  • (If using Mac) Run the command lsof -nP -iTCP -sTCP:LISTEN

  • (If using Windows) Run the command netstat -ano

What you’ll be looking for here is to see when sites are stopped and Local is properly shut down if there are still programs running on ports 80 and 443. These may be conflicting with Local or the system may be reporting Local is still running.

Once you run that command you should see a list of listening ports. If you see a particular program making use of those ports, you can then kill that process by running sudo kill -9 XXX where XXX is the PID number of that process. (On Windows you will use taskkill /F /pid XXX where XXX is the PID number of that process)

After that, you should be able to retry. Keep us posted if you have any questions or continuing issues.

There are also some more details around this and other troubleshooting steps at this link if needed: Stopping Whatever Is Listening On Port 80.

As another workaround, check and see if you can manually download a backup and direct import that.

3

Ok thank you for looking into this! I’m not seeing anything on 80 or 443. I might try downloading a backup to see if I can use that as a workaround. I was able to delete a site and re-import afresh so I may just need to do that instead of trying to update existing sites.

4

Sounds good Tilla! I know that WPE made a platform change recently that required all Local Connect users wanting to push/pull with WPE to be on Local version 7 or higher. It’s possible something became disconnected through those changes, but I’m glad you’re seeing functionality return again. Keep us posted if you hit any other snags!

5

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.