Closed drnic closed 9 years ago
Could you try running telnet IP 6868
? I just deployed redis server based on your manifest.
Btw registry
section can be removed now.
@drnic did you managed to cope with the issue?
I currently use a version from this commit 8c27d326388324349cb5ed18a1536cfa15215b1c and it works for me. Still I want to try to update to a newer version.
Going to get back to this soon. Am working on unrelated docker/bosh/pipeline stuff at moment sorry.
On Thu, Apr 30, 2015 at 3:51 AM, Alexander Lomov notifications@github.com wrote:
@drnic did you managed to cope with the issue?
I currently use version from this commit 8c27d326388324349cb5ed18a1536cfa15215b1c and it works for me. Still I want try to update to a newer version.
Reply to this email directly or view it on GitHub: https://github.com/cloudfoundry/bosh-init/issues/27#issuecomment-97736522
@allomov are you seeing this error with the latest version? it should be ok given correct network configuration.
drnic most likely had a network misconfiguration somewhere.
closing. reopen if problem still occurs.
I'm trying to upgrade https://github.com/cloudfoundry-community/bosh-init-redis to new
bosh-init deploy manifest.yml
and am getting a connection error that I didn't get before. Are there any new manifest.yml attributes I need?I've confirmed that port 6868 is still open to all clients on the security group.
The inputs are all latest releases & aws stemcell & HEAD for bosh-init itself.
For manifest.yml