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

Proxies not being added #6

Open
anthonyspiteri opened this issue Mar 10, 2019 · 4 comments
Open

Proxies not being added #6

anthonyspiteri opened this issue Mar 10, 2019 · 4 comments

Comments

@anthonyspiteri
Copy link

When trying to automatically add proxies, they never get added to the VBR instance.

terraform apply -var proxy_count=2

I'm not sure where to start looking for the logs to see what's happening and why the proxies are not being added.

@goodrum
Copy link
Collaborator

goodrum commented Mar 10, 2019

Anthony,

There is an option in the Variables "should_register_proxy" which if set to "false" will prevent the registration of the proxy.

variable "should_register_proxy" {
type = "string"
description = "Should the Veeam Proxy Server be registered to the Veeam VBR Server. If false then the proxy server will not register. This is handy for creating fast launch templates."
default = "true"
}

Double check that you didn't configure this as "false" in your tfvars.

Otherwise, please check and provide the following:

  • Which terraform template are you using?
  • If the servers are being created, could you share a copy of the terraform log?

@anthonyspiteri
Copy link
Author

Hey Jeremy.

Yes, the should_register_proxy flag is set to true.

I'm using the latest terraform no_chef.

Servers are being created, the terraform is completing without errors. Any logs on the created servers I can reference?

@goodrum
Copy link
Collaborator

goodrum commented Mar 13, 2019

Anthony,

I pushed a minor update to a new branch feature/add_chef_log_location which will change the bootstrap process to log to a file 'C:/chef/client.log' by default. This should give you the details from the Chef execution and will be logged in the Proxy server.

Also, could you scrub the terraform stdout log and post it here that would help see what is happening?

@goodrum
Copy link
Collaborator

goodrum commented Mar 23, 2019

Checking on the status of this issue. Have you had a chance to try to branch that I pushed to include the chef_log_location setting?

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

No branches or pull requests

2 participants