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

Export-RubrikDatabase occasionally issues - TerminatingError(Invoke-WebRequest): "The operation has timed out." #666

Closed
ShodginGitHub opened this issue Jul 29, 2020 · 3 comments
Assignees
Labels

Comments

@ShodginGitHub
Copy link

When using Export-RubrikDatabase, I occasionally get a time-out error (even though the gui shows the export still running).

Waiting for restore to complete - (Wednesday, July 29, 2020 6:24:08 AM) - (41.82%)
PS>TerminatingError(Invoke-WebRequest): "The operation has timed out."

TerminatingError(Invoke-WebRequest): "The operation has timed out."
TerminatingError(Invoke-WebRequest): "The operation has timed out."
TerminatingError(Invoke-WebRequest): "The operation has timed out."


There should be a way to control the Time-Out interval when using Export-RubrikDatabase

Expected Behavior:
Allow the use of a Time-Out parameter that could be set to indefinitely

Steps to Reproduce:
I cannot always reproduce this situation. The event fails occasionally

Context:

I'm using sdk 5.0.2 of the Rubrik sdk

I saw some documentation on the internet about
Set-RubrikModuleOption -OptionName DefaultWebRequestTimeOut -OptionValue 30

I tried that command, but received an error, so I am unclear as to how I can control the default web request time out value for an operation.

DefaultWebRequestTimeOut doesn't exist in options file.

@mwpreston mwpreston self-assigned this Jul 29, 2020
@mwpreston
Copy link
Contributor

Hi @ShodginGitHub - just noticing this issue you filed as well.

You should be able to change the value with the command you ran - can you please post the error message you received?

@ShodginGitHub
Copy link
Author

ShodginGitHub commented Jul 30, 2020 via email

@mwpreston
Copy link
Contributor

This issue should be resolved with #668 to the devel branch - will cut a release to master shortly

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

No branches or pull requests

2 participants