You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems logsearch-shipper was relying on the fact that previously there was a ruby interpreter present on the stemcells under /var/vcap/bosh/bin/ruby. This is no longer the case.
logs.control.log:
/bin/bash: /var/vcap/jobs/logsearch-shipper/bin/logs.generate-config: /var/vcap/bosh/bin/ruby: bad interpreter: No such file or directory
metrics.control.log:
/var/vcap/jobs/logsearch-shipper/bin/metrics.control: /var/vcap/jobs/logsearch-shipper/bin/metrics.generate-config: /var/vcap/bosh/bin/ruby: bad interpreter: No such file or directory
# ls -l /var/vcap/bosh/bin/ruby
ls: cannot access /var/vcap/bosh/bin/ruby: No such file or directory
Could you add the needed ruby package to your boshrelease?
Or maybe you might know of an adequate replacement for logsearch-shipper boshrelease?
The text was updated successfully, but these errors were encountered:
dpb587
added a commit
to dpb587/logsearch-shipper-boshrelease
that referenced
this issue
Nov 28, 2016
It seems logsearch-shipper was relying on the fact that previously there was a ruby interpreter present on the stemcells under
/var/vcap/bosh/bin/ruby
. This is no longer the case.Could you add the needed ruby package to your boshrelease?
Or maybe you might know of an adequate replacement for logsearch-shipper boshrelease?
The text was updated successfully, but these errors were encountered: