-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Not working #17
Comments
@ptlab-la Can you please share:
|
@ptlab-la Based on the image you sent via email, this appears to be a configuration issue. The first failure comes from the SCP step due to the db_dump.sql.tar.gz file not existing at the specified path. I would check the paths on your staging server configuration and see where the db_dump is actually being created. |
@abryrath thank you. I'm trying to run this on my local to sync with the staging server. One thing to note: the database is hosted on Amazon RDS and not directly on the staging server. Does the plugin work still work this? I don't believe it's even doing the db dump as it shows the log immediately and no file is created at the location. Here is the info:
|
@ptlab-la I have used the plugin with AWS/RDS before, so that shouldn't be a problem. You do need to connect directly to a linux server with mysqldump installed and the server must be able to connect to the DB using your |
I see the same error.
|
Getting the following output...
[2021-02-23T20:16:54.159483-08:00] sync.NOTICE: Starting database sync [] [] [2021-02-23T20:16:54.165338-08:00] sync.INFO: Beginning remote dump [] [] [2021-02-23T20:16:55.744867-08:00] sync.INFO: Beginning remote download [] [] [2021-02-23T20:16:55.812963-08:00] sync.ERROR: return non-zero: 1 [] []
The text was updated successfully, but these errors were encountered: