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.
toggle quoted message
Show quoted text
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
|
