Date   

Java Buildpack: Stale Files Outside of WEB-INF

Daniel Jones
 

Hi all,

If one pushes a .war containing files outside of WEB-INF, deletes the app,
then pushes a new version where those files outside of WEB-INF have been
changed, these changes are not reflected in the running app. Is this
expected behaviour? The buildpack is forked, from commit 71ab82a
<https://github.com/cloudfoundry/java-buildpack/commit/71ab82af4cd95465dcbc35eb89f3ac9dc9431e9a>
.

I was just about to go about creating a repeatable test case and raising a
GitHub issue, but figured it'd be best to check that this isn't the way
it's *supposed* to work.

For the record I realise that resources should be in WEB-INF by convention,
but the users where I am are expecting feature parity with non-CF Tomcat
which unpacks the whole .war.

Many thanks in advance,

Daniel Jones
EngineerBetter.com


CCDB: deleting records in service_instance_operations where state "in progress"

Lukas Lehner <weblehner@...>
 

Hi

ccdb=> select COUNT(*) from service_instance_operations where state !=
'succeeded' and updated_at < NOW() - INTERVAL '1 days';


count

-------

28


is it ok to delete all those records?
What does that mean for the consistency of CF?

we are using those releases:

+---------------------+----------+-------------+
| Name | Versions | Commit Hash |
+---------------------+----------+-------------+
| cf-rabbitmq | 90* | 386bec6a+ |
| cf-redis | 316 | ca081301+ |
| | 319* | 0aa09571+ |
| cf-services-contrib | 6* | 57fd2098+ |
+---------------------+----------+-------------+

Lukas


Re: metron_agent.deployment

王小锋 <zzuwxf at gmail.com...>
 

Thanks, it works now!

2015-06-11 6:01 GMT+08:00 CF Runtime <cfruntime(a)gmail.com>:

There is a closed issue in the cf-release repo related to this:
https://github.com/cloudfoundry/cf-release/issues/690

Make sure you have a meta.environment section defined in your manifest
stub.

meta:
environment: YOUR_ENVIRONMENT_NAME


On Wed, Jun 10, 2015 at 1:34 AM, 王小锋 <zzuwxf(a)gmail.com> wrote:

Hi, Ivan and Diego

I met the same issue when I try to upgrade cf version from 205 to 210. I
did no quite understand how to add the property "metron_agent.deployment"
to cf-deployment.yml, could you help paste the cf deployment snippets?
thanks a lot

2015-05-27 11:49 GMT+08:00 Diego Lapiduz <diego(a)lapiduz.com>:

Thanks Ivan! That is exactly what I was looking for.

On Tue, May 26, 2015 at 10:47 PM, Ivan Sim <ivans(a)activestate.com>
wrote:

For all the loggregator processes, you will be able to find their
configuration properties in their respective spec and ERB files in the loggregator
repository
<https://github.com/cloudfoundry/loggregator/tree/develop/bosh/jobs>[1].
In your case, the metron_agent.deployment property is seen here
<https://github.com/cloudfoundry/loggregator/blob/27490d3387566f42fb71bab3dc760ca1b5c1be6d/bosh/jobs/metron_agent/spec#L47>
[2]

[1] https://github.com/cloudfoundry/loggregator/tree/develop/bosh/jobs
[2]
https://github.com/cloudfoundry/loggregator/blob/27490d3387566f42fb71bab3dc760ca1b5c1be6d/bosh/jobs/metron_agent/spec#L47
.

On Tue, May 26, 2015 at 7:40 PM, Diego Lapiduz <diego(a)lapiduz.com>
wrote:

Hi all,

I've been trying to figure out an issue here while upgrading to 210
from 208.

It seems that a requirement has been added to the deployment manifests
for a "metron_agent.deployment" property but I can't find it anywhere in
the cf-release manifests.

From what I can tell the only manifest with that setting is
https://github.com/cloudfoundry/cf-release/blob/master/example_manifests/minimal-aws.yml#L327
.

Is there a place to look for canonical manifests other than
cf-release? Should I just rely on the release notes?

I just added that property to cf-properties.yml and seems to work fine.

Thanks for understanding as we are going through our first couple of
big upgrades.

Cheers,
Diego

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Ivan Sim

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: CfSummit slides

CF Events <events@...>
 

Hello Guillaume,

On Wed, Jun 10, 2015 at 5:09 AM, Guillaume Berche <bercheg(a)gmail.com> wrote:

Hi,

Thanks again to the CF Foundation for the great cf summit, and for
publishing so promptly the video recordings on youtube. The sessions
content is great to watch, and I'm sometimes lacking the high resolution
slides display, and ability to use the slides as a reference.

There is currently 12 slide decks onto [1] over the 38 sessions presented.
Is there somewhere else they can be accessed, or any way for the foundation
to publish the ones speakers have already posted on the CFP system ?
I will double check with our content manager, but typically if slides are
missing it is because the speakers did not share the with us. If we do
still have some that have not been posted, I'll make sure that happens by
Monday.

Thank you,

Angela


Thanks in advance,

Guillaume.

[1] http://www.cfsummit.com/program/slides


--
Cloud Foundry Summit Events Team
Cloud Foundry Foundation
events(a)cloudfoundry.org


Re: metron_agent.deployment

CF Runtime
 

There is a closed issue in the cf-release repo related to this:
https://github.com/cloudfoundry/cf-release/issues/690

Make sure you have a meta.environment section defined in your manifest stub.

meta:
environment: YOUR_ENVIRONMENT_NAME

On Wed, Jun 10, 2015 at 1:34 AM, 王小锋 <zzuwxf(a)gmail.com> wrote:

Hi, Ivan and Diego

I met the same issue when I try to upgrade cf version from 205 to 210. I
did no quite understand how to add the property "metron_agent.deployment"
to cf-deployment.yml, could you help paste the cf deployment snippets?
thanks a lot

2015-05-27 11:49 GMT+08:00 Diego Lapiduz <diego(a)lapiduz.com>:

Thanks Ivan! That is exactly what I was looking for.

On Tue, May 26, 2015 at 10:47 PM, Ivan Sim <ivans(a)activestate.com> wrote:

For all the loggregator processes, you will be able to find their
configuration properties in their respective spec and ERB files in the loggregator
repository
<https://github.com/cloudfoundry/loggregator/tree/develop/bosh/jobs>[1].
In your case, the metron_agent.deployment property is seen here
<https://github.com/cloudfoundry/loggregator/blob/27490d3387566f42fb71bab3dc760ca1b5c1be6d/bosh/jobs/metron_agent/spec#L47>
[2]

[1] https://github.com/cloudfoundry/loggregator/tree/develop/bosh/jobs
[2]
https://github.com/cloudfoundry/loggregator/blob/27490d3387566f42fb71bab3dc760ca1b5c1be6d/bosh/jobs/metron_agent/spec#L47
.

On Tue, May 26, 2015 at 7:40 PM, Diego Lapiduz <diego(a)lapiduz.com>
wrote:

Hi all,

I've been trying to figure out an issue here while upgrading to 210
from 208.

It seems that a requirement has been added to the deployment manifests
for a "metron_agent.deployment" property but I can't find it anywhere in
the cf-release manifests.

From what I can tell the only manifest with that setting is
https://github.com/cloudfoundry/cf-release/blob/master/example_manifests/minimal-aws.yml#L327
.

Is there a place to look for canonical manifests other than cf-release?
Should I just rely on the release notes?

I just added that property to cf-properties.yml and seems to work fine.

Thanks for understanding as we are going through our first couple of
big upgrades.

Cheers,
Diego

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Ivan Sim

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: Issue with etcd since v211

CF Runtime
 

It looks like you are trying to run with two etcd instances. etcd requires
either one instance, or three or more. You can see details here:
https://github.com/coreos/etcd/blob/master/Documentation/admin_guide.md#fault-tolerance-table

The default cf-release templates normally have two instances in one zone,
and a single instance in the other zone.

CF Runtime Team
Joseph & Marc

On Wed, Jun 10, 2015 at 9:33 AM, Scott Taggart <staggart(a)skyscapecloud.com>
wrote:

Hi folks,



Just upgraded from v210 to v211 and seem to have failures within etcd…
they won’t start



On the etc.d box (10.2.0.40 in this instance, I also have one on
10.3.0.40), I get…



Under etcd_ctl.err.log:

[2015-06-10 16:29:51+0000] + /var/vcap/packages/etcd/etcdctl -C
http://10.2.0.40:4001 ls

[2015-06-10 16:29:51+0000] Error: cannot sync with the cluster using
endpoints http://10.2.0.40:4001

[2015-06-10 16:29:51+0000] + sleep 1

[2015-06-10 16:29:52+0000] + false

[2015-06-10 16:29:52+0000] + safe_teardown 'af244208330117aa:
name=etcd_z2-0 peerURLs=http://10.3.0.40:7001 clientURLs=
http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name= peerURLs=
http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] + prior_cluster_had_other_nodes
'af244208330117aa: name=etcd_z2-0 peerURLs=http://10.3.0.40:7001
clientURLs=http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name= peerURLs=
http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] ++ wc -l

[2015-06-10 16:29:52+0000] + '[' 2 -ne 1 ']'

[2015-06-10 16:29:52+0000] ++ extract_my_id 'af244208330117aa:
name=etcd_z2-0 peerURLs=http://10.3.0.40:7001 clientURLs=
http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name= peerURLs=
http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] ++ sed 's/:.*//'

[2015-06-10 16:29:52+0000] ++ grep 10.2.0.40

[2015-06-10 16:29:52+0000] ++ echo 'af244208330117aa: name=etcd_z2-0
peerURLs=http://10.3.0.40:7001 clientURLs=http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name= peerURLs=
http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] + my_id=c2e63d26f18f2cd2

[2015-06-10 16:29:52+0000] + '[' '!' -z c2e63d26f18f2cd2 ']'

[2015-06-10 16:29:52+0000] + member_remove c2e63d26f18f2cd2

[2015-06-10 16:29:52+0000] + /var/vcap/packages/etcd/etcdctl -C
http://10.2.0.40:4001,http://10.3.0.40:4001 member remove c2e63d26f18f2cd2



Under etcd.stderr.log:

2015/06/10 16:30:32 etcd: listening for peers on http://0.0.0.0:7001

2015/06/10 16:30:32 etcd: listening for client requests on
http://0.0.0.0:4001

2015/06/10 16:30:32 etcd: stopping listening for client requests on
http://0.0.0.0:4001

2015/06/10 16:30:32 etcd: stopping listening for peers on
http://0.0.0.0:7001

2015/06/10 16:30:32 etcd: error validating peerURLs =http://10.2.0.40:7001
,etcd_z2-0=http://10.3.0.40:7001: member count is unequal



Any tips at all?

Notice:
This message contains information that may be privileged or confidential
and is the property of Skyscape. It is intended only for the person to whom
it is addressed. If you are not the intended recipient, you are not
authorised to read, print, retain, copy, disseminate, distribute, or use
this message or any part thereof. If you receive this message in error,
please notify the sender immediately and delete all copies of this message.
Skyscape reserves the right to monitor all e-mail communications through
its networks. Skyscape Cloud Services Limited is registered in England and
Wales: Company No: 07619797. Registered office: Hartham Park, Hartham,
Corsham, Wiltshire SN13 0RP.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: Syslog Drain to Logstash Problems

Steve Wall <steve.wall@...>
 

I was able submit a log entry from the loggregator VM using -

nc -w0 10.xx.xx.xx 5000 <<< "logging from loggregator"

and to test UDP

nc -u -w0 10.xx.xx.xx 5000 <<< "logging from loggregator"


Which leads me to believe the networking is working properly. Any other
thoughts?
Thanks!
Steve

On Wed, Jun 3, 2015 at 6:14 PM, Josh Ghiloni <jghiloni(a)ecsteam.com> wrote:

We’ll check that, thanks!

Josh Ghiloni
Senior Consultant
303.932.2202 o | 303.590.5427 m | 303.565.2794 f
jghiloni(a)ecsteam.com

ECS Team
Technology Solutions Delivered
ECSTeam.com





On Jun 3, 2015, at 15:41, John Tuley <jtuley(a)pivotal.io> wrote:

Steve,

Until recently (cf-release v198), binding a syslog service required
restarting the app. If you're post-v198, it *should* Just Work.

However, one of the things that could be in your way is network
security. In order to forward logs to your drain, your loggregator servers
must be able to access that server. This is the most common cause we see of
systems failing to forward to syslog drains.

Please let us know if you have more questions.

– John Tuley

On Wed, Jun 3, 2015 at 12:37 PM, Steve Wall <
steve.wall(a)primetimesoftware.com> wrote:

Hello,
We are having problems draining log messages to Logstash. The drain is
setup as a user provided service.

cf cups logstash-drain -l syslog://xx.xx.xx.xx:5000

And then bound to the service.

cf bind-service myapp logstash-drain

But no log messages are coming through to Logstash. Or more
specifically, we are using ELK and the messages aren't seen through Kibana.

We were able to log into the DEA and using netcat (nc), messages were
successfully submitted to the ELK stack.

nc -w0 -u xx.xx.xx.xx 5000 <<< "logging from remote"

Any suggestions on how to debug this further?
-Steve


_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev



_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Issue with etcd since v211

Scott Taggart <staggart@...>
 

Hi folks,



Just upgraded from v210 to v211 and seem to have failures within etcd.
they won't start



On the etc.d box (10.2.0.40 in this instance, I also have one on
10.3.0.40), I get.



Under etcd_ctl.err.log:

[2015-06-10 16:29:51+0000] + /var/vcap/packages/etcd/etcdctl -C
http://10.2.0.40:4001 ls

[2015-06-10 16:29:51+0000] Error: cannot sync with the cluster using
endpoints http://10.2.0.40:4001

[2015-06-10 16:29:51+0000] + sleep 1

[2015-06-10 16:29:52+0000] + false

[2015-06-10 16:29:52+0000] + safe_teardown 'af244208330117aa:
name=etcd_z2-0 peerURLs=http://10.3.0.40:7001
clientURLs=http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name=
peerURLs=http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] + prior_cluster_had_other_nodes
'af244208330117aa: name=etcd_z2-0 peerURLs=http://10.3.0.40:7001
clientURLs=http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name=
peerURLs=http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] ++ wc -l

[2015-06-10 16:29:52+0000] + '[' 2 -ne 1 ']'

[2015-06-10 16:29:52+0000] ++ extract_my_id 'af244208330117aa:
name=etcd_z2-0 peerURLs=http://10.3.0.40:7001
clientURLs=http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name=
peerURLs=http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] ++ sed 's/:.*//'

[2015-06-10 16:29:52+0000] ++ grep 10.2.0.40

[2015-06-10 16:29:52+0000] ++ echo 'af244208330117aa: name=etcd_z2-0
peerURLs=http://10.3.0.40:7001 clientURLs=http://10.3.0.40:4001

[2015-06-10 16:29:52+0000] c2e63d26f18f2cd2: name=
peerURLs=http://10.2.0.40:7001 clientURLs='

[2015-06-10 16:29:52+0000] + my_id=c2e63d26f18f2cd2

[2015-06-10 16:29:52+0000] + '[' '!' -z c2e63d26f18f2cd2 ']'

[2015-06-10 16:29:52+0000] + member_remove c2e63d26f18f2cd2

[2015-06-10 16:29:52+0000] + /var/vcap/packages/etcd/etcdctl -C
http://10.2.0.40:4001,http://10.3.0.40:4001 member remove c2e63d26f18f2cd2



Under etcd.stderr.log:

2015/06/10 16:30:32 etcd: listening for peers on http://0.0.0.0:7001

2015/06/10 16:30:32 etcd: listening for client requests on
http://0.0.0.0:4001

2015/06/10 16:30:32 etcd: stopping listening for client requests on
http://0.0.0.0:4001

2015/06/10 16:30:32 etcd: stopping listening for peers on
http://0.0.0.0:7001

2015/06/10 16:30:32 etcd: error validating peerURLs
=http://10.2.0.40:7001,etcd_z2-0=http://10.3.0.40:7001: member count is
unequal



Any tips at all?



Notice:
This message contains information that may be privileged or confidential and is the property of Skyscape. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorised to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. Skyscape reserves the right to monitor all e-mail communications through its networks. Skyscape Cloud Services Limited is registered in England and Wales: Company No: 07619797. Registered office: Hartham Park, Hartham, Corsham, Wiltshire SN13 0RP.

______________________________________________________________________
This email has been scanned by the Symantec Email Security.cloud service.
______________________________________________________________________


Re: CF CAB call on Wednesday, June 10th, 2015 @ 8a PDT

Dieu Cao <dcao@...>
 

Link to the chat room for the CAB call:
http://webconf.soaphub.org/conf/room/CF-CAB-OpenForum

On Mon, Jun 8, 2015 at 3:54 PM, Michael Maximilien <maxim(a)us.ibm.com> wrote:

Hi, all,

It's been about a month since CF summit 2015 and two months since the last
CAB call.

Please make plan to join the call this Wednesday as we surely will have a
jam pack update from all teams and from community at large.

------------
*Agenda (working)*:
https://docs.google.com/document/d/1SCOlAquyUmNM-AQnekCOXiwhLs6gveTxAcduvDcW_xI/edit#

*CF community* *call @ 8AM PDT*

*USA, Canada, and Mexico: *1-888-426-6840 or USA 1-215-861-6239
*All other countries* can find dial-in numbers here:
*http://goo.gl/RnNfc1* <http://goo.gl/RnNfc1>
*Participant code*: 1985291
------------

If you are a PM then make sure to update your highlights on the
appropriate section in the doc above.

If you are not a PM and have something to share, then add to agenda in
Others section or send to us by replying to this email.

Talk to you all soon. Best,

Chip, James, and Max

------
dr.max
ibm cloud labs
silicon valley, ca
maximilien.org
_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: how to set JSON format data in user provider env variable in cloudfoundry ??

Lingesh Mouleeshwaran
 

oops ,, this is the correct format cf set-env <app-name> somekey { "KEY" :
["value1","value2"] }

On Wed, Jun 10, 2015 at 9:38 AM, Lingesh Mouleeshwaran <
lingeshmouleeshwaran(a)gmail.com> wrote:

Hello Team ,

cf set-env is allowing only key pair value for setting any ENV variable ,
but I need to set value as JSON format.

for example ,,

cf set-env <app-name> { "KEY" : ["value1","value2"] }

but I am able to assign above json data into environment variable . even I
set with single quotes it;s not a valid json format.

Please some one help with this ??


how to set JSON format data in user provider env variable in cloudfoundry ??

Lingesh Mouleeshwaran
 

Hello Team ,

cf set-env is allowing only key pair value for setting any ENV variable ,
but I need to set value as JSON format.

for example ,,

cf set-env <app-name> { "KEY" : ["value1","value2"] }

but I am able to assign above json data into environment variable . even I
set with single quotes it;s not a valid json format.

Please some one help with this ??


CfSummit slides

Guillaume Berche
 

Hi,

Thanks again to the CF Foundation for the great cf summit, and for
publishing so promptly the video recordings on youtube. The sessions
content is great to watch, and I'm sometimes lacking the high resolution
slides display, and ability to use the slides as a reference.

There is currently 12 slide decks onto [1] over the 38 sessions presented.
Is there somewhere else they can be accessed, or any way for the foundation
to publish the ones speakers have already posted on the CFP system ?

Thanks in advance,

Guillaume.

[1] http://www.cfsummit.com/program/slides


Re: CF most relevant metrics

Daniel Mikusa
 

I've found this article to be helpful. How you capture the metrics might
be different, but it talks about some of the important metrics and what
they mean.

http://blog.pivotal.io/pivotal-cloud-foundry/products/monitoring-pivotal-cloud-foundry-health-and-status-hybrid-models-kpis-and-more

Dan

On Wed, Jun 10, 2015 at 4:17 AM, Pablo Alonso Rodriguez <palonsoro(a)gmail.com
wrote:
Good morning.

Recently, we have started having a look at CF metrics to monitorize our
instance and we would like to determine which are the most important ones
to determine whether there is (or there is going to be) a service
degradation or interruption.

Could you please help us with this? Do you have any suggestions?

Thank you in advance

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: metron_agent.deployment

王小锋 <zzuwxf at gmail.com...>
 

Hi, Ivan and Diego

I met the same issue when I try to upgrade cf version from 205 to 210. I
did no quite understand how to add the property "metron_agent.deployment"
to cf-deployment.yml, could you help paste the cf deployment snippets?
thanks a lot

2015-05-27 11:49 GMT+08:00 Diego Lapiduz <diego(a)lapiduz.com>:

Thanks Ivan! That is exactly what I was looking for.

On Tue, May 26, 2015 at 10:47 PM, Ivan Sim <ivans(a)activestate.com> wrote:

For all the loggregator processes, you will be able to find their
configuration properties in their respective spec and ERB files in the loggregator
repository
<https://github.com/cloudfoundry/loggregator/tree/develop/bosh/jobs>[1].
In your case, the metron_agent.deployment property is seen here
<https://github.com/cloudfoundry/loggregator/blob/27490d3387566f42fb71bab3dc760ca1b5c1be6d/bosh/jobs/metron_agent/spec#L47>
[2]

[1] https://github.com/cloudfoundry/loggregator/tree/develop/bosh/jobs
[2]
https://github.com/cloudfoundry/loggregator/blob/27490d3387566f42fb71bab3dc760ca1b5c1be6d/bosh/jobs/metron_agent/spec#L47
.

On Tue, May 26, 2015 at 7:40 PM, Diego Lapiduz <diego(a)lapiduz.com> wrote:

Hi all,

I've been trying to figure out an issue here while upgrading to 210 from
208.

It seems that a requirement has been added to the deployment manifests
for a "metron_agent.deployment" property but I can't find it anywhere in
the cf-release manifests.

From what I can tell the only manifest with that setting is
https://github.com/cloudfoundry/cf-release/blob/master/example_manifests/minimal-aws.yml#L327
.

Is there a place to look for canonical manifests other than cf-release?
Should I just rely on the release notes?

I just added that property to cf-properties.yml and seems to work fine.

Thanks for understanding as we are going through our first couple of big
upgrades.

Cheers,
Diego

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


--
Ivan Sim

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


CF most relevant metrics

Pablo Alonso Rodriguez <palonsoro@...>
 

Good morning.

Recently, we have started having a look at CF metrics to monitorize our
instance and we would like to determine which are the most important ones
to determine whether there is (or there is going to be) a service
degradation or interruption.

Could you please help us with this? Do you have any suggestions?

Thank you in advance


Re: UAA SAML2 Federation

Pablo Alonso Rodriguez <palonsoro@...>
 

I see.

Then, until ECP profile is implemented (someone at Daniel's link mentioned
that it is on the roadmap), the browser is must.

Thank you very much for your answers.



2015-06-09 17:03 GMT+02:00 Sree Tummidi <stummidi(a)pivotal.io>:

Hi,
The browser interaction is a must because the actual SAML Auth with the
IDP happens via the browser. UAA implements the SAML POST profile which
involves a browser.
The code itself is generated as a one time token by the UAA after the SAML
auth is complete.

Thanks,
Sree


Sent from my iPad

On Jun 9, 2015, at 6:26 AM, Pablo Alonso Rodriguez <palonsoro(a)gmail.com>
wrote:

Ok. I see.

Then, would it be possible to request a temporary access code to the UAA
by means of a REST API or another more programmatic way?

What I would like to avoid is our users having to manually copy and paste
a code from the browser.

Thank you very much

2015-06-09 13:46 GMT+02:00 Daniel Mikusa <dmikusa(a)pivotal.io>:


On Tue, Jun 9, 2015 at 4:45 AM, Pablo Alonso Rodriguez <
palonsoro(a)gmail.com> wrote:

Good morning.

Recently, we have successfully federated the UAA to an external identity
provider via SAML2.

However, we are only able to log in via cf login --sso, so that we can
get a temporary code by loging in the idp web page.

Is there any way to directly pass the credentials to the identity
provider from the cf cli?
I don't think so, I think that's a limitation of SAML. Check out this
thread for some more info on this.


http://cf-dev.70369.x6.nabble.com/cf-dev-UAA-SAML-and-LDAP-questions-td62.html

Dan



Thank you in advance.

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


Re: cloud foundry - 413 Request Entity Too Large

James Bayer
 

since this is commercial software you can always open a support case with
pivotal to get help with an SLA.

cf doesn't limit the body size, but i think the max upload size is
somewhere around 1GB or so. is the 413 error code coming from tomcat or
some other middleware? what kind of app do you have and how is it packaged?
do you have any of the logs to share? what kind of REST call, is it a GET
with large headers, a POST or PUT?

On Tue, Jun 9, 2015 at 10:04 AM, Ohana, Avia <Avia.Ohana(a)emc.com> wrote:

Hello,



I'm using Cloud Foundry v2, pivotal v1.4 distribution.

All my apps are written in java, build pack is java_buildpack_offline_v3.0.



Trying to make REST call with ~12MB body size to one of my apps, and
getting error 413 Request Entity Too Large with the following headers:

X-Cf-Requestid c80a7e06-7102-459e-721a-251189596ece

Date Sun, 07 Jun 2015 08:20:45 GMT

Content-Length 0

Content-Type text/plain; charset=utf-8



What is the default body size limit in cloud foundry? How can I configure
it?

Any idea?



Thanks in advanced,

Avia

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

--
Thank you,

James Bayer


Re: Is there any officail Chinese docs?

Kim Hoffman <khoffman@...>
 

The CF documentation team isn't aware of any Chinese docs. There's nothing
official out there, and as far as I know the docs that you referenced were
extremely out of date even back when they were available.

Sorry we couldn't be of more help!

On Sun, Jun 7, 2015 at 8:51 PM, tan_bw(a)163.com <tan_bw(a)163.com> wrote:

I can't open the Chinese doc website http://cndocs.cloudfoundry.com
<http://cndocs.cloudfoundry.com/deploy/bosh-docs.html>.Is this website
closed?Is there any other substitute?


_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev


cloud foundry - 413 Request Entity Too Large

avia <Avia.Ohana@...>
 

Hello,

I'm using Cloud Foundry v2, pivotal v1.4 distribution.
All my apps are written in java, build pack is java_buildpack_offline_v3.0.

Trying to make REST call with ~12MB body size to one of my apps, and getting error 413 Request Entity Too Large with the following headers:
X-Cf-Requestid c80a7e06-7102-459e-721a-251189596ece
Date Sun, 07 Jun 2015 08:20:45 GMT
Content-Length 0
Content-Type text/plain; charset=utf-8

What is the default body size limit in cloud foundry? How can I configure it?
Any idea?

Thanks in advanced,
Avia


(No subject)

Arbi Akhina
 

no I meant the source is for the company I work for, not my personal
project.

On Tue, Jun 9, 2015 at 6:58 PM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:

On Tue, Jun 9, 2015 at 12:43 PM, Arbi Akhina <arbi.akhina(a)gmail.com>
wrote:

I don't own the source, but here is the jar file
http://tempsend.com/6D745B7B07/7033/modules.jar
you can try to run it locally with java -jar modules.jar then connect to
localhost:8080
Hmm, OK. I thought you had a minimal example from you last note. I'm not
really up for running untrusted binary code. If you can put a minimal code
sample together, I'll give it a try.



An here is the manifest.yml i'm using:
---
applications:
- name: modules
memory: 4G
disk_quota: 2G
timeout: 180
instances: 1
host: modules-${random-word}
path: modules.jar
buildpack: https://github.com/cloudfoundry/java-buildpack
command: sleep 2 &&
CALCULATED_MEMORY=$($PWD/.java-buildpack/open_jdk_jre/bin/java-buildpack-memory-calculator-1.1.1_RELEASE
-memorySizes=metaspace:64m..
-memoryWeights=heap:75,metaspace:10,stack:5,native:10
-totMemory=$MEMORY_LIMIT) && $PWD/.java-buildpack/open_jdk_jre/bin/java -cp
$PWD/. -Djava.io.tmpdir=$TMPDIR
-XX:OnOutOfMemoryError=$PWD/.java-buildpack/open_jdk_jre/bin/killjava.sh
$CALCULATED_MEMORY com.heavenize.osmoze.kernel.HelloHandler
# env:
# JAVA_OPTS: "$JAVA_OPTS -agentlib:jdwp=transport=dt_socket,address=
192.168.2.8:8000"

I'm having both files in the same folder modules/ and I push with cf push
That seems OK. Is this app designed to run on CF? By that, I mean is it
configure to log to STDOUT / STDERR and is it going to listen on the right
port (i.e $PORT)?

Dan




Thanks a lot

On Tue, Jun 9, 2015 at 6:25 PM, Daniel Mikusa <dmikusa(a)pivotal.io> wrote:

I'd be happy to try the demo and see if it works for me. Can you post a
complete project on github so I can just `git clone` & build?

Dan

On Tue, Jun 9, 2015 at 12:21 PM, Arbi Akhina <arbi.akhina(a)gmail.com>
wrote:

I've tried with a simple app that just launches an embedded jetty that
listen on the vcap port and it worked (I can connect to the app url from
curl and chrome)
then I moved this single file into my modules.jar (the real app) and
configure it as main class, but here it doesn't work.

here is the class in question:
public class HelloHandler extends AbstractHandler
{
public static void main(String[] args)
{
int VCAP_APP_PORT =
Integer.parseInt((System.getenv("VCAP_APP_PORT") != null ?
System.getenv("VCAP_APP_PORT") : "8080"));

Server server = new Server(VCAP_APP_PORT);
server.setHandler(new HelloHandler());

try
{
server.start();
server.join();
}
catch (Exception exception)
{
System.out.println("Failed to start embedded jetty server.");
exception.printStackTrace();
}
}

final String greeting;
final String body;

public HelloHandler()
{
this("Hello World");
}

public HelloHandler( String greeting )
{
this(greeting, null);
}

public HelloHandler( String greeting, String body )
{
this.greeting = greeting;
this.body = body;
}

public void handle( String target,
Request baseRequest,
HttpServletRequest request,
HttpServletResponse response ) throws IOException,
ServletException
{
response.setContentType("text/html; charset=utf-8");
response.setStatus(HttpServletResponse.SC_OK);

PrintWriter out = response.getWriter();

out.println("<h1>" + greeting + "</h1>");
out.println("<p>Current directory: " + getCurrentDirectory() +
"</p>");
out.println("<p> Parent directory: " + getParentDirectory() +
"</p>");
for(File file: getFiles()) {
out.println("<p>" + file.getAbsolutePath() + "</p>");
}

if (body != null)
{
out.println(body);
}

baseRequest.setHandled(true);
}
private List<File> getFiles() {
return Arrays.asList(new File(".").listFiles());
}

private String getCurrentDirectory()
{
String directory = null;
try
{
directory = new File(".").getCanonicalPath();
}
catch (Exception e)
{
e.printStackTrace();
}
return directory;
}

private String getParentDirectory()
{
String directory = null;
try
{
directory = new File("..").getCanonicalPath();
}
catch (Exception e)
{
e.printStackTrace();
}
return directory;
}
}


On Tue, Jun 9, 2015 at 5:34 PM, Daniel Mikusa <dmikusa(a)pivotal.io>
wrote:

Double check that your app is configured to log to STDOUT / STDER. If
it's logging to a file, you won't see the messages since the system only
captures STDOUT & STDERR.

Also, you might try a demo app like spring-music, just to make sure
your install is working OK.

https://github.com/cloudfoundry-samples/spring-music

Dan

On Tue, Jun 9, 2015 at 10:40 AM, Arbi Akhina <arbi.akhina(a)gmail.com>
wrote:

Same logs I still can't see what went wrong!

On Tue, Jun 9, 2015 at 3:58 PM, Daniel Mikusa <dmikusa(a)pivotal.io>
wrote:

And so you'd want to set `command` to `sleep 2 &&
CALCULATED_MEMORY=$($PWD/.java-buildpack/open_jdk_jre/
bin/java-buildpack-memory-calculator-1.1.1_RELEASE
-memorySizes=metaspace:64m.. -memoryWeights=heap:75,metaspace:10,stack:5,native:10
-totMemory=$MEMORY_LIMIT) && $PWD/.java-buildpack/open_jdk_jre/bin/java
-cp $PWD/. -Djava.io.tmpdir=$TMPDIR -XX:OnOutOfMemoryError=$PWD/.
java-buildpack/open_jdk_jre/bin/killjava.sh $CALCULATED_MEMORY
-agentlib:jdwp=transport=dt_socket,address=192.168.2.8:8000
com.heavenize.osmoze.kernel.HelloHandler`.

Dan

On Tue, Jun 9, 2015 at 9:29 AM, Arbi Akhina <arbi.akhina(a)gmail.com>
wrote:

Here is the content of *detected_start_command*:
$ CF_TRACE=true cf app modules | grep "detected_start_command"
"detected_start_command":
"CALCULATED_MEMORY=$($PWD/.java-buildpack/open_jdk_jre/bin/java-buildpack-memory-calculator-1.1.1_RELEASE
-memorySizes=metaspace:64m..
-memoryWeights=heap:75,metaspace:10,stack:5,native:10
-totMemory=$MEMORY_LIMIT) && $PWD/.java-buildpack/open_jdk_jre/bin/java -cp
$PWD/. -Djava.io.tmpdir=$TMPDIR
-XX:OnOutOfMemoryError=$PWD/.java-buildpack/open_jdk_jre/bin/killjava.sh
$CALCULATED_MEMORY -agentlib:jdwp=transport=dt_socket,address=
192.168.2.8:8000 com.heavenize.osmoze.kernel.HelloHandler",

{"guid":"2dabf3c6-1736-4eb4-9bb7-40dc58bce246","name":"modules","routes":[{"guid":"014f77ed-e450-4209-be23-40e4a8257cfc","host":"modules-rhythmic-uvulatomy","domain":{"guid":"a77afa99-76d6-4f3f-9e07-27775597709f","name":"
10.244.0.34.xip.io
"}}],"running_instances":0,"services":[],"available_domains":[{"guid":"a77afa99-76d6-4f3f-9e07-27775597709f","name":"
10.244.0.34.xip.io
"}],"name":"modules","production":false,"space_guid":"381707f7-88d4-4f6e-bd7c-80d7f0699b0f","stack_guid":"3431865a-f165-4e75-9221-4f418e9de889","buildpack":"
https://github.com/cloudfoundry/java-buildpack","detected_buildpack":null,"environment_json":{"JAVA_OPTS":"$JAVA_OPTS
-agentlib:jdwp=transport=dt_socket,address=192.168.2.8:8000"},"memory":4096,"instances":1,"disk_quota":2048,"state":"STARTED","version":"e8f0e18e-7c09-4143-a17c-83a6e32eed84","command":null,"console":false,"debug":null,"staging_task_id":"1249276465c64c1884d401452d2365af","package_state":"STAGED","health_check_type":"port","health_check_timeout":180,"staging_failed_reason":null,"diego":false,"docker_image":null,"package_updated_at":"2015-06-08T07:56:44Z","detected_start_command":"CALCULATED_MEMORY=$($PWD/.java-buildpack/open_jdk_jre/bin/java-buildpack-memory-calculator-1.1.1_RELEASE
-memorySizes=metaspace:64m..
-memoryWeights=heap:75,metaspace:10,stack:5,native:10
-totMemory=$MEMORY_LIMIT) && $PWD/.java-buildpack/open_jdk_jre/bin/java -cp
$PWD/. -Djava.io.tmpdir=$TMPDIR
-XX:OnOutOfMemoryError=$PWD/.java-buildpack/open_jdk_jre/bin/killjava.sh
$CALCULATED_MEMORY -agentlib:jdwp=transport=dt_socket,address=
192.168.2.8:8000 com.heavenize.osmoze.kernel.HelloHandler"}


On Tue, Jun 9, 2015 at 1:35 PM, Daniel Mikusa <dmikusa(a)pivotal.io>
wrote:

On Tue, Jun 9, 2015 at 5:05 AM, Arbi Akhina <arbi.akhina(a)gmail.com
wrote:
Hi, thanks for the hint, I tried to add to the manifest the
following entry:
command: sleep 2 && java -jar modules.jar
The Java build pack does not put Java on the path, which is what
you're seeing in the error below. I will usually run `CF_TRACE=true cf app
<app-name> | grep "detected_start_command"` which shows the command the
build pack detected and then just copy & paste that into my custom command.



but it looks like it's not appropriate as I see in the logs:
2015-06-08T05:34:03.71+0200 [App/0] ERR bash: java: command
not found

On Mon, Jun 8, 2015 at 6:32 PM, Daniel Mikusa <dmikusa(a)pivotal.io
wrote:
On Mon, Jun 8, 2015 at 12:03 PM, Arbi Akhina <
arbi.akhina(a)gmail.com> wrote:

I'm trying to push an executable JAR to a bosh-lite instance,
on the logs I see CF trying many times to restart the app and eventually
fail.

I can't find out why the app crashes as there is no app logs
returned by CF. I tried to remotely debug the app (as described in [1]) but
nothing happens on eclipse. Any hint to solve this issue is appreciated.
There's a known issue that occurs when an app starts and fails
in rapid succession and results in the log entries being missed. If you
add a couple second pause into the app, it will give the system enough time
to attach the logger and you'll see the output generated by the crashing
app.

You can do this with a custom start command `cf push -c 'sleep 2
&& <normal-cmd>'` or with a `.profile.d` script that sleeps for a couple
seconds.

Dan




1. I'm launching the app with:
*cf push -t 180*

2. Here is the manifest.yml content:
---
applications:
- name: modules
memory: 4G
instances: 1
host: modules-${random-word}
path: modules.jar
buildpack: https://github.com/cloudfoundry/java-buildpack
env:
JAVA_OPTS: "$JAVA_OPTS
-agentlib:jdwp=transport=dt_socket,address=192.168.2.8:8000"

3. Here is the log:
Connecté, le dumping journaux récents pour application modules
en org heavenize / espace dev comme admin...

2015-06-07T12:05:15.69+0200 [API] OUT Created app with guid
1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:05:16.10+0200 [API] OUT Updated app with guid
1fbf3378-6512-46de-bae4-02ee30275464
({"route"=>"68e27d8d-4ff6-443b-a3e0-416c40d325d3"})
2015-06-07T12:12:21.55+0200 [DEA] OUT Got staging request
for app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:12:25.40+0200 [API] OUT Updated app with guid
1fbf3378-6512-46de-bae4-02ee30275464 ({"state"=>"STARTED"})
2015-06-07T12:12:38.08+0200 [STG] OUT -----> Downloaded app
package (163M)
2015-06-07T12:13:40.93+0200 [STG] ERR Cloning into
'/tmp/buildpacks/java-buildpack'...
2015-06-07T12:14:01.67+0200 [STG] OUT -----> Java
Buildpack Version: c862ac8 |
https://github.com/cloudfoundry/java-buildpack#c862ac8
2015-06-07T12:14:13.89+0200 [STG] OUT -----> Downloading
Open Jdk JRE 1.8.0_45 from
https://download.run.pivotal.io/openjdk/lucid/x86_64/openjdk-1.8.0_45.tar.gz
(11.6s)
2015-06-07T12:14:15.34+0200 [STG] OUT Expanding Open
Jdk JRE to .java-buildpack/open_jdk_jre (1.4s)
2015-06-07T12:14:15.89+0200 [STG] OUT -----> Downloading
Open JDK Like Memory Calculator 1.1.1_RELEASE from
https://download.run.pivotal.io/memory-calculator/lucid/x86_64/memory-calculator-1.1.1_RELEASE
(0.5s)
2015-06-07T12:14:15.90+0200 [STG] OUT Memory
Settings: -XX:MaxMetaspaceSize=419430K -XX:MetaspaceSize=419430K -Xss1M
-Xmx3G -Xms3G
2015-06-07T12:15:43.44+0200 [STG] OUT -----> Uploading
droplet (151M)
2015-06-07T12:16:07.51+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:16:29.66+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"9d55c5f791324d358bffb4c961a4c7ee", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672189}
2015-06-07T12:17:14.18+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:17:31.10+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"2ae0c26f33864f40989ee870a1b9e3db", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672251}
2015-06-07T12:17:38.48+0200 [DEA] OUT Removing crash for
app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:17:38.48+0200 [DEA] OUT Stopping app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:17:38.48+0200 [DEA] OUT Stopped app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:17:55.31+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:18:11.82+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"dc872d38f3324af481c82ba67f0e216c", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672291}
2015-06-07T12:18:18.69+0200 [DEA] OUT Removing crash for
app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:18:18.69+0200 [DEA] OUT Stopping app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:18:18.69+0200 [DEA] OUT Stopped app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:18:34.06+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:18:50.98+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"623c3af7e3e84801b6fd44eeee9c0a12", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672330}
2015-06-07T12:18:58.80+0200 [DEA] OUT Removing crash for
app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:18:58.80+0200 [DEA] OUT Stopping app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:18:58.80+0200 [DEA] OUT Stopped app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:19:34.08+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:19:50.36+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"40727eea293146948af197e13443843c", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672390}
2015-06-07T12:19:59.01+0200 [DEA] OUT Removing crash for
app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:19:59.01+0200 [DEA] OUT Stopping app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:19:59.01+0200 [DEA] OUT Stopped app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:21:04.12+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:21:20.61+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"f7ffff55692a418c847f4f37be574ddf", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672480}
2015-06-07T12:21:29.43+0200 [DEA] OUT Removing crash for
app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:21:29.43+0200 [DEA] OUT Stopping app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:21:29.47+0200 [DEA] OUT Stopped app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:23:34.16+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:23:49.97+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"4581e97c6b0f4504b8d64a5c69d6787b", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672629}
2015-06-07T12:23:50.29+0200 [DEA] OUT Removing crash for
app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:23:50.29+0200 [DEA] OUT Stopping app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:23:50.29+0200 [DEA] OUT Stopped app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:28:14.24+0200 [DEA] OUT Starting app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:28:29.82+0200 [API] OUT App instance exited
with guid 1fbf3378-6512-46de-bae4-02ee30275464 payload:
{"cc_partition"=>"default",
"droplet"=>"1fbf3378-6512-46de-bae4-02ee30275464",
"version"=>"703f793c-e388-41ac-b1f1-c564b301ca70",
"instance"=>"f98749490a6743598f57d3848eb06177", "index"=>0,
"reason"=>"CRASHED", "exit_status"=>-1, "exit_description"=>"failed to
start", "crash_timestamp"=>1433672909}
2015-06-07T12:28:31.73+0200 [DEA] OUT Removing crash for
app with id 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:28:31.73+0200 [DEA] OUT Stopping app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464
2015-06-07T12:28:31.73+0200 [DEA] OUT Stopped app instance
(index 0) with guid 1fbf3378-6512-46de-bae4-02ee30275464



[1]
http://docs.cloudfoundry.org/buildpacks/java/java-tips.html#debugging



_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

_______________________________________________
cf-dev mailing list
cf-dev(a)lists.cloudfoundry.org
https://lists.cloudfoundry.org/mailman/listinfo/cf-dev

9021 - 9040 of 9421