-
Notifications
You must be signed in to change notification settings - Fork 626
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
Database backup fails with exit code 1 #2874
Comments
Running the exact same command in the prompt, removing the defaults-extra-file and adding my user "root", works.
|
Curious... do you get the exact same Maybe production backups are still failing, but it's with a different error message. |
Hi @angrybrad Yes, I'm still getting the exact same error on IIS on a Win Server 2012 r2 setup. Did the same tests without any issues there too, with mysql/bin in the PATH variable. Something that might be worth nothing, this is a site that I upgraded from Craft 2 to 3, keeping the Craft 2 file structure. Might, or might not be part of the equation, but I thought you should know. |
Please note that I am now running Craft 3.0.8 with same issue. |
@echantigny any chance we could get some CP and (s)FTP/SSH credentials to that box to poke around a bit? If so, could you send to support@craftcms.com? |
@angrybrad Sorry, I can't give you access to that box. Confidential information and all that on my client's box. We could do a screen share on my box if you want (I have the same issue), and we can remote in to that box if needed. Not sure how well that would work, but we can try if it helps. You can get me on your Slack team with eric.chantigny if you want to chat live. |
Thanks to Brad, we figured this one out on WAMP. The issue was the PATH variable containing the mysqldump path was the current user's Path, and not the System variables path. Adding mysqldump to the system Path variable solved the issue on WAMP. |
Description
I'm trying to do a database backup, but I keep getting Exit code 1 on both my local (WampServer on Windows 10) and on the production server which is on IIS.
Steps to reproduce
Additional info
The response is:
The log error:
And to get this out of the way, this is what I get if I try to use mysqldump in the command prompt
The text was updated successfully, but these errors were encountered: