Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lisk Core Should Start Without Redis #3176

Closed
ManuGowda opened this issue Mar 25, 2019 · 0 comments

Comments

Projects
2 participants
@ManuGowda
Copy link
Member

commented Mar 25, 2019

Expected behavior

REDIS is optional, so Lisk Core should start without redis

Actual behavior

App was unable to connect to Cache server - {"errno":"ECONNREFUSED","code":"ECONNREFUSED","syscall":"connect","address":"127.0.0.1","port":6380}
System error: unhandledRejection : - {"message":"Redis connection to 127.0.0.1:6380 failed - connect ECONNREFUSED 127.0.0.1:6380","stack":"Error: Redis connection to 127.0.0.1:6380 failed - connect ECONNREFUSED 127.0.0.1:6380\n    at TCPConnectWrap.afterConnect [as oncomplete] (net.js:1113:14)"}

Steps to reproduce

stop redis and run npm start

Which version(s) does this affect? (Environment, OS, etc...)

1.6.0

@ManuGowda ManuGowda added this to To do in Version 1.6.0 via automation Mar 25, 2019

@MaciejBaj MaciejBaj moved this from To do to In progress in Version 1.6.0 Mar 25, 2019

@MaciejBaj MaciejBaj changed the title Lisk Core Should Start Without REDIS Lisk Core Should Start Without Redis Mar 25, 2019

Version 1.6.0 automation moved this from In progress to Done Mar 25, 2019

MaciejBaj added a commit that referenced this issue Mar 25, 2019

Merge pull request #3184 from LiskHQ/3176-ignore_error_from_redis
Lisk Core should start without Redis - Closes #3176
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.