Skip to content
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

Closed
rHorsey opened this issue Jan 4, 2018 · 11 comments
Closed

Database backup on server returns an error #250

rHorsey opened this issue Jan 4, 2018 · 11 comments

Comments

@rHorsey
Copy link
Contributor

rHorsey commented Jan 4, 2018

From @ljbrackney on March 16, 2017 19:52

Please make it work gooder.

Copied from original issue: NREL/OpenStudio#2523

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

FYI @ljbrackney this milestone should be 2.1.1

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

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.

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

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.

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

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?

  • larry

From: rHorsey <[email protected]mailto:[email protected]>
Reply-To: NREL/OpenStudio <[email protected]mailto:[email protected]>
Date: Wednesday, May 10, 2017 at 6:21 PM
To: NREL/OpenStudio <[email protected]mailto:[email protected]>
Cc: Larry Brackney <[email protected]mailto:[email protected]>, Mention <[email protected]mailto:[email protected]>
Subject: Re: [NREL/OpenStudio] Database backup on server returns an error (#2523)

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.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNREL%2FOpenStudio%2Fissues%2F2523%23issuecomment-300655967&data=02%7C01%7Clarry.brackney%40nrel.gov%7C2d085e85eca245129dde08d4980bfe27%7Ca0f29d7e28cd4f5484427885aee7c080%7C1%7C0%7C636300624654221372&sdata=yfZhQujCRKXX%2BOSabOI8d1odmxZ1CZvVZhHl5V04GY4%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACIHhpHtLC7ozuYvJ404OlZ0zcJlQtg2ks5r4mKAgaJpZM4MfzDU&data=02%7C01%7Clarry.brackney%40nrel.gov%7C2d085e85eca245129dde08d4980bfe27%7Ca0f29d7e28cd4f5484427885aee7c080%7C1%7C0%7C636300624654221372&sdata=JpPZNCcNyJTp4tbHpWc%2Fzy5xcYiMczHwogLv%2FxtpxZo%3D&reserved=0.

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

@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.

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

From @macumber on June 28, 2017 15:54

@ljbrackney can you test and close once 2.2.0 is out?

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

From @ljbrackney on June 28, 2017 16:53

Yes

From: Dan Macumber <[email protected]mailto:[email protected]>
Reply-To: NREL/OpenStudio <[email protected]mailto:[email protected]>
Date: Wednesday, June 28, 2017 at 8:54 AM
To: NREL/OpenStudio <[email protected]mailto:[email protected]>
Cc: Larry Brackney <[email protected]mailto:[email protected]>, Mention <[email protected]mailto:[email protected]>
Subject: Re: [NREL/OpenStudio] Database backup on server returns an error (#2523)

@ljbrackneyhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fljbrackney&data=02%7C01%7Clarry.brackney%40nrel.gov%7C4593aa518ae1448fb21708d4be3df660%7Ca0f29d7e28cd4f5484427885aee7c080%7C1%7C0%7C636342620709376422&sdata=bsPcDPXanRPxBpoanpoK6ctAxqlYmiN7gNufto5g17g%3D&reserved=0 can you test and close once 2.2.0 is out?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNREL%2FOpenStudio%2Fissues%2F2523%23issuecomment-311704135&data=02%7C01%7Clarry.brackney%40nrel.gov%7C4593aa518ae1448fb21708d4be3df660%7Ca0f29d7e28cd4f5484427885aee7c080%7C1%7C0%7C636342620709376422&sdata=wOyUdkhdIoYWP%2BVZqyfaMDjppWjBhzgq82XNwJCWFf8%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FACIHhkPDPd0pLLG5WNvlorRBMxlqMRV-ks5sIncxgaJpZM4MfzDU&data=02%7C01%7Clarry.brackney%40nrel.gov%7C4593aa518ae1448fb21708d4be3df660%7Ca0f29d7e28cd4f5484427885aee7c080%7C1%7C0%7C636342620709376422&sdata=4Ey9pqoNU1y0BPrxWNBmMkTWCxeDFytBPCRGAtXtWeg%3D&reserved=0.

@rHorsey
Copy link
Contributor Author

rHorsey commented Jan 4, 2018

This is working for me now. Can someone confirm?

@lgentile
Copy link

@ljbrackney is this working?

@ljbrackney
Copy link

Download works. Restore doesn't return error, but doesn't work either. Just attempted to backup/restore from 24a to 24b.

@brianlball
Copy link
Contributor

only took 4 years... not bad

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants