A issue has been created for this
problem https://github.com/cloudfoundry/loggregator_emitter/issues/1
On Wednesday, September 11, 2013 3:36:42 AM UTC+2, Orson wrote:

Hi all.

Having an issue with cf release 140, dea_next and loggregator

from:
https://github.com/cloudfoundry/cf-release/blob/master/templates/cf-jobs.yml#L240-L243

loggregator:
router: (( jobs.loggregator_router_z1.networks.cf1.static_ips.[0]
":3456" ))
servers:
- (( jobs.loggregator_z1.networks.cf1.static_ips.[0] ":3456" ))


My config (snippet):
loggregator:
router: 0.loggregator.default.charlie.microbosh:3456
servers:
- 0.loggregator.default.charlie.microbosh:3456

After deploy, the dea node is reported as failing in bosh vms - so,
investigation ensues:

$ bosh ssh dea_next

$ tail /var/vcap/sys/log/dea_next/dea.stderr.log:

/var/vcap/packages/dea_next/vendor/bundle/ruby/1.9.1/gems/loggregator_emitter-0.0.9.pre/lib/loggregator_emitter/emit.rb:9:in
`initialize': Must provide IP address for loggregator server:
0.loggregator.default.charlie.microbosh:3456 (RuntimeError)
from /var/vcap/packages/dea_next/lib/dea/bootstrap.rb:161:in `new'
from /var/vcap/packages/dea_next/lib/dea/bootstrap.rb:161:in
`setup_loggregator'
from /var/vcap/packages/dea_next/lib/dea/bootstrap.rb:72:in `setup'
from /var/vcap/packages/dea_next/bin/dea:29:in `block in <main>'
from
/var/vcap/packages/dea_next/vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`call'
from
/var/vcap/packages/dea_next/vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`run_machine'
from
/var/vcap/packages/dea_next/vendor/bundle/ruby/1.9.1/gems/eventmachine-1.0.3/lib/eventmachine.rb:187:in
`run'
from /var/vcap/packages/dea_next/bin/dea:28:in `<main>'

$ sudo vi /var/vcap/jobs/dea_next/config/dea.yml

Change:

loggregator:
router: 0.loggregator.default.charlie.microbosh:3456

To:

loggregator:
router: 10.158.39.132:3456 # (where 10.158.39.132 is the IP of the
loggregator server as reported by bosh vms charlie)

(ie, the error message says it needs an IP address, so I give it an IP
address)

Kill the dea processes, watch the logs as they get restarted, no error,
bosh vms reports dea_next as 'running' instead of 'failing', all is right
in the state of the universe, etc.

So. With that as background:

What change do I need to make to my manifest so that dea_next's dea.yml
gets the IP of the loggregator server rather than its hostname (as is in
the template)?

Many thanks,

Orson
--

------------------------------

Have an innovative day

*Innovation Factory *Pilotenstraat 45* *1059 CH Amsterdam* *+31 20
7787008 www.innovationfactory.eu

*
Disclaimer*
*The information transmitted is intended only for the person or entity to
which it is addressed and may contain confidential and/or privileged
material. Any use of, or taking of any action in reliance upon, this
information by persons or entities other than the intended recipient is
prohibited. If you received this in error, please contact the sender and
delete the material from any computer. Innovation Factory does not accept
liability for any errors, viruses or omissions in the contents of this
message, which may arise as a result of e-mail transmission. No employee or
agent is authorized to conclude any binding agreement on behalf of
Innovation Factory with another party by email.*

To unsubscribe from this group and stop receiving emails from it, send an email to vcap-dev+unsubscribe@cloudfoundry.org.

Search Discussions

Discussion Posts

Previous

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 2 of 2 | next ›
Discussion Overview
groupvcap-dev @
postedSep 11, '13 at 1:36a
activeSep 23, '13 at 6:25p
posts2
users2

2 users in discussion

Orson: 1 post Ruben Koster: 1 post

People

Translate

site design / logo © 2021 Grokbase