-
Notifications
You must be signed in to change notification settings - Fork 20
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 on server returns an error #250
Comments
FYI @ljbrackney this milestone should be 2.1.1 |
From @ljbrackney on May 6, 2017 16:16 mongodump.tar.gz downloads from the server have been working for a bit, but I tried uploading a tarball to both 24b and AWS without success. The upload itself appears to work, but I believe it fails upon extraction or processing thereafter. |
I redeployed 24b yesterday and upload / download works fine there. I believe you're hitting the same limitations imposed by compose as we're seeing.... in pivotal tickets, gah. On AWS we deploy with swarm, and we really should on bball as well. I'm working to transition us over to that locally. It's tested and implemented, but the takeaways aren't disseminated yet. The network becomes far more stable when we run everything through swarmkit, which saves us a lot of pain here. Have you seen this since 2.1.1 on AWS? If so, them this needs to stay open. |
From @ljbrackney on May 11, 2017 14:16 I'm still using 2.1.0 so I can test/respond to user queries. Perhaps someone on 2.1.1 could try a mongodump save/restore on AWS?
From: rHorsey <[email protected]mailto:[email protected]> I redeployed 24b yesterday and upload / download works fine there. I believe you're hitting the same limitations imposed by compose as we're seeing.... in pivotal tickets, gah. On AWS we deploy with swarm, and we really should on bball as well. I'm working to transition us over to that locally. It's tested and implemented, but the takeaways aren't disseminated yet. The network becomes far more stable when we run everything through swarmkit, which saves us a lot of pain here. Have you seen this since 2.1.1 on AWS? If so, them this needs to stay open. You are receiving this because you were mentioned. |
@ljbrackney I'll test this next time I spin up a 2.1.1. The new (correct OpenStudio version) 2.1.1 AMI has a lot of fixes in it, which should catch what we were seeing locally, at least. |
From @macumber on June 28, 2017 15:54 @ljbrackney can you test and close once 2.2.0 is out? |
This is working for me now. Can someone confirm? |
@ljbrackney is this working? |
Download works. Restore doesn't return error, but doesn't work either. Just attempted to backup/restore from 24a to 24b. |
only took 4 years... not bad |
From @ljbrackney on March 16, 2017 19:52
Please make it work gooder.
Copied from original issue: NREL/OpenStudio#2523
The text was updated successfully, but these errors were encountered: