wrote:

Okay.. Let me try with it.. Thanks..

On 24 November 2015 at 14:02, ronak banka <ronakbanka.cse(a)gmail.com>
wrote:

Subnet ranges on which your other components are provisioned.

allow_from_entries:
- 192.168.33.0/24




On Tue, Nov 24, 2015 at 5:16 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello Ronak,
Actually, previously i have given the values for
ALLOW_FROM_ENTRIES, after seeing some mail groups only i changed it to
NULL. Could you tell me which IP i need to give their or something else??
Thanks..

On 24 November 2015 at 13:23, ronak banka <ronakbanka.cse(a)gmail.com>
wrote:

Hi Parthiban,

In your manifest , there is a global property block

nfs_server:
address: 192.168.33.53
allow_from_entries:
- null
- null
share: null

allow from entries are provided for cc individual property and not for actual debian nfs server, that is possible reason cc is not able to write to nfs


https://github.com/cloudfoundry/cf-release/blob/master/jobs/debian_nfs_server/spec#L20

Thanks
Ronak



On Tue, Nov 24, 2015 at 3:42 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks Amit for your faster reply. FYI, I have shared my deployment
manifest too. I got struck in this issue for past couple of weeks. Thanks..

On 24 November 2015 at 12:00, Amit Gupta <agupta(a)pivotal.io> wrote:

Hi Parthiban,

Sorry to hear your deployment is still getting stuck. As Warren
points out, based on your log output, it looks like an issue with NFS
configuration. I will ask the CAPI team, who are experts on cloud
controller and NFS server, to take a look at your question.

Best,
Amit

On Thu, Nov 19, 2015 at 8:11 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks for your suggestions Warren. I am attaching the Manifest file
which used for the deployment. Am also suspecting that the problem with the
NFS Server Configuration only.

On 19 November 2015 at 22:32, Warren Fernandes <
wfernandes(a)pivotal.io> wrote:

Hey Parthiban,

It seems that there may be a misconfiguration in your manifest.
Did you configure the nfs_server properties?


https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L19-L22

The api_z1 pulls the above properties in here.
https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L368
.

Is it possible to share your manifest with us via a gist or
attachment? Please remove any sensitive information like passwords, certs
and keys.

Thanks.

Subnet ranges on which your other components are provisioned.

allow_from_entries:
- 192.168.33.0/24




On Tue, Nov 24, 2015 at 5:16 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello Ronak,
Actually, previously i have given the values for
ALLOW_FROM_ENTRIES, after seeing some mail groups only i changed it to
NULL. Could you tell me which IP i need to give their or something else??
Thanks..

On 24 November 2015 at 13:23, ronak banka <ronakbanka.cse(a)gmail.com>
wrote:

Hi Parthiban,

In your manifest , there is a global property block

nfs_server:
address: 192.168.33.53
allow_from_entries:
- null
- null
share: null

allow from entries are provided for cc individual property and not for actual debian nfs server, that is possible reason cc is not able to write to nfs


https://github.com/cloudfoundry/cf-release/blob/master/jobs/debian_nfs_server/spec#L20

Thanks
Ronak



On Tue, Nov 24, 2015 at 3:42 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks Amit for your faster reply. FYI, I have shared my deployment
manifest too. I got struck in this issue for past couple of weeks. Thanks..

On 24 November 2015 at 12:00, Amit Gupta <agupta(a)pivotal.io> wrote:

Hi Parthiban,

Sorry to hear your deployment is still getting stuck. As Warren
points out, based on your log output, it looks like an issue with NFS
configuration. I will ask the CAPI team, who are experts on cloud
controller and NFS server, to take a look at your question.

Best,
Amit

On Thu, Nov 19, 2015 at 8:11 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks for your suggestions Warren. I am attaching the Manifest file
which used for the deployment. Am also suspecting that the problem with the
NFS Server Configuration only.

On 19 November 2015 at 22:32, Warren Fernandes <wfernandes(a)pivotal.io

wrote:

Hey Parthiban,

It seems that there may be a misconfiguration in your manifest.
Did you configure the nfs_server properties?


https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L19-L22

The api_z1 pulls the above properties in here.
https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L368
.

Is it possible to share your manifest with us via a gist or
attachment? Please remove any sensitive information like passwords, certs
and keys.

Thanks.

Hi Parthiban,

In your manifest , there is a global property block

nfs_server:
address: 192.168.33.53
allow_from_entries:
- null
- null
share: null

allow from entries are provided for cc individual property and not for actual debian nfs server, that is possible reason cc is not able to write to nfs


https://github.com/cloudfoundry/cf-release/blob/master/jobs/debian_nfs_server/spec#L20

Thanks
Ronak



On Tue, Nov 24, 2015 at 3:42 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks Amit for your faster reply. FYI, I have shared my deployment
manifest too. I got struck in this issue for past couple of weeks. Thanks..

On 24 November 2015 at 12:00, Amit Gupta <agupta(a)pivotal.io> wrote:

Hi Parthiban,

Sorry to hear your deployment is still getting stuck. As Warren points
out, based on your log output, it looks like an issue with NFS
configuration. I will ask the CAPI team, who are experts on cloud
controller and NFS server, to take a look at your question.

Best,
Amit

On Thu, Nov 19, 2015 at 8:11 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks for your suggestions Warren. I am attaching the Manifest file
which used for the deployment. Am also suspecting that the problem with the
NFS Server Configuration only.

On 19 November 2015 at 22:32, Warren Fernandes <wfernandes(a)pivotal.io>
wrote:

Hey Parthiban,

It seems that there may be a misconfiguration in your manifest.
Did you configure the nfs_server properties?


https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L19-L22

The api_z1 pulls the above properties in here.
https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L368
.

Is it possible to share your manifest with us via a gist or
attachment? Please remove any sensitive information like passwords, certs
and keys.

Thanks.

Hi Parthiban,

Sorry to hear your deployment is still getting stuck. As Warren points
out, based on your log output, it looks like an issue with NFS
configuration. I will ask the CAPI team, who are experts on cloud
controller and NFS server, to take a look at your question.

Best,
Amit

On Thu, Nov 19, 2015 at 8:11 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks for your suggestions Warren. I am attaching the Manifest file
which used for the deployment. Am also suspecting that the problem with the
NFS Server Configuration only.

On 19 November 2015 at 22:32, Warren Fernandes <wfernandes(a)pivotal.io>
wrote:

Hey Parthiban,

It seems that there may be a misconfiguration in your manifest.
Did you configure the nfs_server properties?


https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L19-L22

The api_z1 pulls the above properties in here.
https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L368
.

Is it possible to share your manifest with us via a gist or attachment?
Please remove any sensitive information like passwords, certs and keys.

Thanks.

Looks like most of your VMs are fine, but one of your etcd VM's agent is
unresponsive. Do "bosh cck" and resolve the unresponsive agent by
recreating from the last known apply spec.

On Mon, Oct 26, 2015 at 7:07 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Amit, I already tried that troubleshooting options, always same error. As
you mentioned, I have attached the BOSH VMs and BOSH CCK REPORT. Thanks.

On 26 October 2015 at 09:23, Amit Gupta <agupta(a)pivotal.io> wrote:

Try some of these diagnostics:
https://docs.cloudfoundry.org/running/troubleshooting.html#bound-timeout
Also, run "bosh vms --details" and "bosh cck --report" and share the
outputs.

On Mon, Oct 26, 2015 at 12:16 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Actually, sorry for the previous mails. Since, I have started with CF
v202 release and it thrown some error so am switched to CF v210. But, again
because of some rollback issues we went back with CF v202 itself.
Currently, bosh deploy throws the following, I have attached the Debug Logs
too. Thanks.

Director task 310
Started unknown
Started unknown > Binding deployment. Done (00:00:00)

Started preparing deployment
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done
(00:00:01)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done
(00:00:00)
Started preparing deployment > Binding instance networks. Done
(00:00:00)

Started preparing package compilation > Finding packages to compile.
Done (00:00:00)

Started preparing dns > Binding DNS. Done (00:00:00)

Started creating bound missing vms
Started creating bound missing vms > medium_z1/0
Started creating bound missing vms > medium_z1/1
Started creating bound missing vms > router_z2/0. Done (00:01:09)
Failed creating bound missing vms > medium_z1/1: Timed out sending
`get_task' to f4dfe4e9-c897-4b9b-b7c7-63a908c10190 after 45 seconds
(00:04:03)
Done creating bound missing vms > medium_z1/0 (00:05:14)
Failed creating bound missing vms (00:05:14)

Error 450002: Timed out sending `get_task' to
f4dfe4e9-c897-4b9b-b7c7-63a908c10190 after 45 seconds

On 24 October 2015 at 06:40, Parthiban Annadurai <senjiparthi(a)gmail.com

wrote:

Thanks Amit for your suggestions. Let you know after regenerating the
manifest again.

On 24 October 2015 at 11:47, Amit Gupta <agupta(a)pivotal.io> wrote:

Regenerate your manifest.

On Fri, Oct 23, 2015 at 10:49 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Okay Amit. Yaa, I changed my CF Version from v202 to v210. Could you
share that metron_agent.deployment property of the manifest which is
required in v210? Thanks.

On 24 October 2015 at 10:57, Amit Gupta <agupta(a)pivotal.io> wrote:

Parthiban,

Your log.txt shows that you're using cf-release version 210, but
your subject message says you're trying v202. Perhaps you've checked out
v202 of cf-release and used the spiff tooling to generate the manifests
from that version. v202 doesn't include the metron_agent.deployment
property in its manifest, which is required in v210.

On Fri, Oct 23, 2015 at 10:07 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

I have created the manifest file using SPIFF tool. Any issues with
that?

On 23 October 2015 at 20:49, Amit Gupta <agupta(a)pivotal.io> wrote:

How did you create your manifest in the first place?

On Fri, Oct 23, 2015 at 8:17 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

After trying the suggestions, now its throws the following error,

Started preparing configuration > Binding configuration. Failed:
Error filling in template `metron_agent.json.erb' for `ha_proxy_z1/0' (line
5: Can't find property `["metron_agent.deployment"]') (00:00:00)

Error 100: Error filling in template `metron_agent.json.erb' for
`ha_proxy_z1/0' (line 5: Can't find property `["metron_agent.deployment"]')

Could anyone on this??

On 22 October 2015 at 18:08, Amit Gupta <agupta(a)pivotal.io>
wrote:

Try running "bosh cck" and recreating VMs from last known apply
spec. You should also make sure that the IPs you're allocating to your
jobs are accessible from the BOSH director VM.

On Thu, Oct 22, 2015 at 5:27 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Yaa sure Amit. I have attached both the files with this mail.
Could you please? Thanks.



On 21 October 2015 at 19:49, Amit Gupta <agupta(a)pivotal.io>
wrote:

Can you share the output of "bosh vms" and "bosh task 51
--debug". It's preferable if you copy the terminal outputs and paste them
to Gists or Pastebins and share the links.

On Tue, Oct 20, 2015 at 6:18 AM, James Bayer <
jbayer(a)pivotal.io> wrote:

sometimes a message like that is due to networking issues.
does the bosh director and the VM it is creating have an available network
path to reach each other? sometimes ssh'ing in to the VM that is identified
can yield more debug clues.

On Tue, Oct 20, 2015 at 5:09 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks Bharath and Amit for the helpful solutions. I have
surpassed that error. Now, bosh deploy strucks like in attached image.
Could you anyone please?

Regards

Parthiban A



On 20 October 2015 at 11:57, Amit Gupta <agupta(a)pivotal.io>
wrote:

Bharath, I think you mean to increase the *disk* size on
the compilation VMs, not the memory size.

Parthiban, the error message is happening during
compiling, saying "No space left on device". This means your compilation
VMs are running out of space on disk. This means you need to increase the
allocated disk for your compilation VMs. In the "compilation" section of
your deployment manifest, you can specify "cloud_properties". This is
where you will specify disk size. These "cloud_properties" look the same
as the could_properties specified for a resource pool. Depending on your
IaaS, the structure of the cloud_properties section differs. See here:
https://bosh.io/docs/deployment-manifest.html#resource-pools-cloud-properties

On Mon, Oct 19, 2015 at 11:13 PM, Bharath Posa <
bharathp(a)vedams.com> wrote:

hi parthiban

It seems you are running out of space in your vm in which
you are compiling . try to increase the size of memory in your compilation
vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello All,
Thanks All for the helpful suggestions.
Actually, now we r facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <
bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <
epoelke(a)gmail.com> wrote:

You actually do not need to download it. if you just
run --

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from
bosh.io.

--
Thank you,

James Bayer

Try some of these diagnostics:
https://docs.cloudfoundry.org/running/troubleshooting.html#bound-timeout
Also, run "bosh vms --details" and "bosh cck --report" and share the
outputs.

On Mon, Oct 26, 2015 at 12:16 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Actually, sorry for the previous mails. Since, I have started with CF
v202 release and it thrown some error so am switched to CF v210. But, again
because of some rollback issues we went back with CF v202 itself.
Currently, bosh deploy throws the following, I have attached the Debug Logs
too. Thanks.

Director task 310
Started unknown
Started unknown > Binding deployment. Done (00:00:00)

Started preparing deployment
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done
(00:00:01)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done
(00:00:00)

Started preparing package compilation > Finding packages to compile.
Done (00:00:00)

Started preparing dns > Binding DNS. Done (00:00:00)

Started creating bound missing vms
Started creating bound missing vms > medium_z1/0
Started creating bound missing vms > medium_z1/1
Started creating bound missing vms > router_z2/0. Done (00:01:09)
Failed creating bound missing vms > medium_z1/1: Timed out sending
`get_task' to f4dfe4e9-c897-4b9b-b7c7-63a908c10190 after 45 seconds
(00:04:03)
Done creating bound missing vms > medium_z1/0 (00:05:14)
Failed creating bound missing vms (00:05:14)

Error 450002: Timed out sending `get_task' to
f4dfe4e9-c897-4b9b-b7c7-63a908c10190 after 45 seconds

On 24 October 2015 at 06:40, Parthiban Annadurai <senjiparthi(a)gmail.com>
wrote:

Thanks Amit for your suggestions. Let you know after regenerating the
manifest again.

On 24 October 2015 at 11:47, Amit Gupta <agupta(a)pivotal.io> wrote:

Regenerate your manifest.

On Fri, Oct 23, 2015 at 10:49 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Okay Amit. Yaa, I changed my CF Version from v202 to v210. Could you
share that metron_agent.deployment property of the manifest which is
required in v210? Thanks.

On 24 October 2015 at 10:57, Amit Gupta <agupta(a)pivotal.io> wrote:

Parthiban,

Your log.txt shows that you're using cf-release version 210, but your
subject message says you're trying v202. Perhaps you've checked out v202
of cf-release and used the spiff tooling to generate the manifests from
that version. v202 doesn't include the metron_agent.deployment property in
its manifest, which is required in v210.

On Fri, Oct 23, 2015 at 10:07 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

I have created the manifest file using SPIFF tool. Any issues with
that?

On 23 October 2015 at 20:49, Amit Gupta <agupta(a)pivotal.io> wrote:

How did you create your manifest in the first place?

On Fri, Oct 23, 2015 at 8:17 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

After trying the suggestions, now its throws the following error,

Started preparing configuration > Binding configuration. Failed:
Error filling in template `metron_agent.json.erb' for `ha_proxy_z1/0' (line
5: Can't find property `["metron_agent.deployment"]') (00:00:00)

Error 100: Error filling in template `metron_agent.json.erb' for
`ha_proxy_z1/0' (line 5: Can't find property `["metron_agent.deployment"]')

Could anyone on this??

On 22 October 2015 at 18:08, Amit Gupta <agupta(a)pivotal.io> wrote:

Try running "bosh cck" and recreating VMs from last known apply
spec. You should also make sure that the IPs you're allocating to your
jobs are accessible from the BOSH director VM.

On Thu, Oct 22, 2015 at 5:27 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Yaa sure Amit. I have attached both the files with this mail.
Could you please? Thanks.



On 21 October 2015 at 19:49, Amit Gupta <agupta(a)pivotal.io>
wrote:

Can you share the output of "bosh vms" and "bosh task 51
--debug". It's preferable if you copy the terminal outputs and paste them
to Gists or Pastebins and share the links.

On Tue, Oct 20, 2015 at 6:18 AM, James Bayer <jbayer(a)pivotal.io

wrote:

sometimes a message like that is due to networking issues.
does the bosh director and the VM it is creating have an available network
path to reach each other? sometimes ssh'ing in to the VM that is identified
can yield more debug clues.

On Tue, Oct 20, 2015 at 5:09 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks Bharath and Amit for the helpful solutions. I have
surpassed that error. Now, bosh deploy strucks like in attached image.
Could you anyone please?

Regards

Parthiban A



On 20 October 2015 at 11:57, Amit Gupta <agupta(a)pivotal.io>
wrote:

Bharath, I think you mean to increase the *disk* size on the
compilation VMs, not the memory size.

Parthiban, the error message is happening during compiling,
saying "No space left on device". This means your compilation VMs are
running out of space on disk. This means you need to increase the
allocated disk for your compilation VMs. In the "compilation" section of
your deployment manifest, you can specify "cloud_properties". This is
where you will specify disk size. These "cloud_properties" look the same
as the could_properties specified for a resource pool. Depending on your
IaaS, the structure of the cloud_properties section differs. See here:
https://bosh.io/docs/deployment-manifest.html#resource-pools-cloud-properties

On Mon, Oct 19, 2015 at 11:13 PM, Bharath Posa <
bharathp(a)vedams.com> wrote:

hi parthiban

It seems you are running out of space in your vm in which
you are compiling . try to increase the size of memory in your compilation
vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello All,
Thanks All for the helpful suggestions.
Actually, now we r facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <
bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <
epoelke(a)gmail.com> wrote:

You actually do not need to download it. if you just
run --

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from
bosh.io.

--
Thank you,

James Bayer

wrote:

Actually, sorry for the previous mails. Since, I have started with CF v202
release and it thrown some error so am switched to CF v210. But, again
because of some rollback issues we went back with CF v202 itself.
Currently, bosh deploy throws the following, I have attached the Debug Logs
too. Thanks.

Director task 310
Started unknown
Started unknown > Binding deployment. Done (00:00:00)

Started preparing deployment
Started preparing deployment > Binding releases. Done (00:00:00)
Started preparing deployment > Binding existing deployment. Done
(00:00:01)
Started preparing deployment > Binding resource pools. Done (00:00:00)
Started preparing deployment > Binding stemcells. Done (00:00:00)
Started preparing deployment > Binding templates. Done (00:00:00)
Started preparing deployment > Binding properties. Done (00:00:00)
Started preparing deployment > Binding unallocated VMs. Done (00:00:00)
Started preparing deployment > Binding instance networks. Done (00:00:00)

Started preparing package compilation > Finding packages to compile.
Done (00:00:00)

Started preparing dns > Binding DNS. Done (00:00:00)

Started creating bound missing vms
Started creating bound missing vms > medium_z1/0
Started creating bound missing vms > medium_z1/1
Started creating bound missing vms > router_z2/0. Done (00:01:09)
Failed creating bound missing vms > medium_z1/1: Timed out sending
`get_task' to f4dfe4e9-c897-4b9b-b7c7-63a908c10190 after 45 seconds
(00:04:03)
Done creating bound missing vms > medium_z1/0 (00:05:14)
Failed creating bound missing vms (00:05:14)

Error 450002: Timed out sending `get_task' to
f4dfe4e9-c897-4b9b-b7c7-63a908c10190 after 45 seconds

On 24 October 2015 at 06:40, Parthiban Annadurai <senjiparthi(a)gmail.com>
wrote:

Thanks Amit for your suggestions. Let you know after regenerating the
manifest again.

On 24 October 2015 at 11:47, Amit Gupta <agupta(a)pivotal.io> wrote:

Regenerate your manifest.

On Fri, Oct 23, 2015 at 10:49 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Okay Amit. Yaa, I changed my CF Version from v202 to v210. Could you
share that metron_agent.deployment property of the manifest which is
required in v210? Thanks.

On 24 October 2015 at 10:57, Amit Gupta <agupta(a)pivotal.io> wrote:

Parthiban,

Your log.txt shows that you're using cf-release version 210, but your
subject message says you're trying v202. Perhaps you've checked out v202
of cf-release and used the spiff tooling to generate the manifests from
that version. v202 doesn't include the metron_agent.deployment property in
its manifest, which is required in v210.

On Fri, Oct 23, 2015 at 10:07 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

I have created the manifest file using SPIFF tool. Any issues with
that?

On 23 October 2015 at 20:49, Amit Gupta <agupta(a)pivotal.io> wrote:

How did you create your manifest in the first place?

On Fri, Oct 23, 2015 at 8:17 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

After trying the suggestions, now its throws the following error,

Started preparing configuration > Binding configuration. Failed:
Error filling in template `metron_agent.json.erb' for `ha_proxy_z1/0' (line
5: Can't find property `["metron_agent.deployment"]') (00:00:00)

Error 100: Error filling in template `metron_agent.json.erb' for
`ha_proxy_z1/0' (line 5: Can't find property `["metron_agent.deployment"]')

Could anyone on this??

On 22 October 2015 at 18:08, Amit Gupta <agupta(a)pivotal.io> wrote:

Try running "bosh cck" and recreating VMs from last known apply
spec. You should also make sure that the IPs you're allocating to your
jobs are accessible from the BOSH director VM.

On Thu, Oct 22, 2015 at 5:27 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Yaa sure Amit. I have attached both the files with this mail.
Could you please? Thanks.



On 21 October 2015 at 19:49, Amit Gupta <agupta(a)pivotal.io>
wrote:

Can you share the output of "bosh vms" and "bosh task 51
--debug". It's preferable if you copy the terminal outputs and paste them
to Gists or Pastebins and share the links.

On Tue, Oct 20, 2015 at 6:18 AM, James Bayer <jbayer(a)pivotal.io>
wrote:

sometimes a message like that is due to networking issues. does
the bosh director and the VM it is creating have an available network path
to reach each other? sometimes ssh'ing in to the VM that is identified can
yield more debug clues.

On Tue, Oct 20, 2015 at 5:09 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks Bharath and Amit for the helpful solutions. I have
surpassed that error. Now, bosh deploy strucks like in attached image.
Could you anyone please?

Regards

Parthiban A



On 20 October 2015 at 11:57, Amit Gupta <agupta(a)pivotal.io>
wrote:

Bharath, I think you mean to increase the *disk* size on the
compilation VMs, not the memory size.

Parthiban, the error message is happening during compiling,
saying "No space left on device". This means your compilation VMs are
running out of space on disk. This means you need to increase the
allocated disk for your compilation VMs. In the "compilation" section of
your deployment manifest, you can specify "cloud_properties". This is
where you will specify disk size. These "cloud_properties" look the same
as the could_properties specified for a resource pool. Depending on your
IaaS, the structure of the cloud_properties section differs. See here:
https://bosh.io/docs/deployment-manifest.html#resource-pools-cloud-properties

On Mon, Oct 19, 2015 at 11:13 PM, Bharath Posa <
bharathp(a)vedams.com> wrote:

hi parthiban

It seems you are running out of space in your vm in which
you are compiling . try to increase the size of memory in your compilation
vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello All,
Thanks All for the helpful suggestions.
Actually, now we r facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <
bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <
epoelke(a)gmail.com> wrote:

You actually do not need to download it. if you just run
--

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from
bosh.io.

--
Thank you,

James Bayer

Regenerate your manifest.

On Fri, Oct 23, 2015 at 10:49 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Okay Amit. Yaa, I changed my CF Version from v202 to v210. Could you
share that metron_agent.deployment property of the manifest which is
required in v210? Thanks.

On 24 October 2015 at 10:57, Amit Gupta <agupta(a)pivotal.io> wrote:

Parthiban,

Your log.txt shows that you're using cf-release version 210, but your
subject message says you're trying v202. Perhaps you've checked out v202
of cf-release and used the spiff tooling to generate the manifests from
that version. v202 doesn't include the metron_agent.deployment property in
its manifest, which is required in v210.

On Fri, Oct 23, 2015 at 10:07 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

I have created the manifest file using SPIFF tool. Any issues with that?

On 23 October 2015 at 20:49, Amit Gupta <agupta(a)pivotal.io> wrote:

How did you create your manifest in the first place?

On Fri, Oct 23, 2015 at 8:17 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

After trying the suggestions, now its throws the following error,

Started preparing configuration > Binding configuration. Failed:
Error filling in template `metron_agent.json.erb' for `ha_proxy_z1/0' (line
5: Can't find property `["metron_agent.deployment"]') (00:00:00)

Error 100: Error filling in template `metron_agent.json.erb' for
`ha_proxy_z1/0' (line 5: Can't find property `["metron_agent.deployment"]')

Could anyone on this??

On 22 October 2015 at 18:08, Amit Gupta <agupta(a)pivotal.io> wrote:

Try running "bosh cck" and recreating VMs from last known apply
spec. You should also make sure that the IPs you're allocating to your
jobs are accessible from the BOSH director VM.

On Thu, Oct 22, 2015 at 5:27 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Yaa sure Amit. I have attached both the files with this mail. Could
you please? Thanks.



On 21 October 2015 at 19:49, Amit Gupta <agupta(a)pivotal.io> wrote:

Can you share the output of "bosh vms" and "bosh task 51
--debug". It's preferable if you copy the terminal outputs and paste them
to Gists or Pastebins and share the links.

On Tue, Oct 20, 2015 at 6:18 AM, James Bayer <jbayer(a)pivotal.io>
wrote:

sometimes a message like that is due to networking issues. does
the bosh director and the VM it is creating have an available network path
to reach each other? sometimes ssh'ing in to the VM that is identified can
yield more debug clues.

On Tue, Oct 20, 2015 at 5:09 AM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Thanks Bharath and Amit for the helpful solutions. I have
surpassed that error. Now, bosh deploy strucks like in attached image.
Could you anyone please?

Regards

Parthiban A



On 20 October 2015 at 11:57, Amit Gupta <agupta(a)pivotal.io>
wrote:

Bharath, I think you mean to increase the *disk* size on the
compilation VMs, not the memory size.

Parthiban, the error message is happening during compiling,
saying "No space left on device". This means your compilation VMs are
running out of space on disk. This means you need to increase the
allocated disk for your compilation VMs. In the "compilation" section of
your deployment manifest, you can specify "cloud_properties". This is
where you will specify disk size. These "cloud_properties" look the same
as the could_properties specified for a resource pool. Depending on your
IaaS, the structure of the cloud_properties section differs. See here:
https://bosh.io/docs/deployment-manifest.html#resource-pools-cloud-properties

On Mon, Oct 19, 2015 at 11:13 PM, Bharath Posa <
bharathp(a)vedams.com> wrote:

hi parthiban

It seems you are running out of space in your vm in which you
are compiling . try to increase the size of memory in your compilation vm .

regards
Bharath



On Mon, Oct 19, 2015 at 7:39 PM, Parthiban Annadurai <
senjiparthi(a)gmail.com> wrote:

Hello All,
Thanks All for the helpful suggestions.
Actually, now we r facing the following issue while kicking bosh deploy,

Done compiling packages >
nats/d3a1f853f4980682ed8b48e4706b7280e2b7ce0e (00:01:07)
Failed compiling packages >
buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157: Action Failed
get_task: Task aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling
package buildpack_php: Compressing compiled package: Shelling out to tar:
Running command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe (00:02:41)
Failed compiling packages (00:02:41)

Error 450001: Action Failed get_task: Task
aba21e6a-2031-4a69-5b72-f238ecd07051 result: Compiling package
buildpack_php: Compressing compiled package: Shelling out to tar: Running
command: 'tar czf
/var/vcap/data/tmp/bosh-platform-disk-TarballCompressor-CompressFilesInDir762165297
-C
/var/vcap/data/packages/buildpack_php/9c72be716ab8629d7e6feed43012d1d671720157.1-
.', stdout: '', stderr: '
gzip: stdout: No space left on device
': signal: broken pipe

Could Anyone on this issue?

Regards

Parthiban A

On 19 October 2015 at 14:30, Bharath Posa <
bharathp(a)vedams.com> wrote:

Hi partiban

can u do a checksum of the tar file .


it should come like this *sha1:
b6f596eaff4c7af21cc18a52ef97e19debb00403*

example:

*sha1sum {file}*

regards
Bharath

On Mon, Oct 19, 2015 at 1:12 PM, Eric Poelke <
epoelke(a)gmail.com> wrote:

You actually do not need to download it. if you just run --

`bosh upload release
https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202`
<https://bosh.io/d/github.com/cloudfoundry/cf-release?v=202>

The director will pull in the release directly from bosh.io
.

--
Thank you,

James Bayer