Redis_Socketio.1 stopped (rc=0) on OSX
up vote
0
down vote
favorite
When i try bench start it threw below error.
I have already tried redis reinstallation, bench update, service restarts but those have not solved my problem yet.
➜ frappe-bench bench start
... ... ...
09:06:56 socketio.1 | events.js:136
09:06:56 socketio.1 | throw er; // Unhandled 'error' event
09:06:56 socketio.1 | ^
09:06:56 socketio.1 |
09:06:56 socketio.1 | Error: Redis connection to localhost:12000 failed - getaddrinfo ENOTFOUND localhost localhost:12000
09:06:56 socketio.1 | at errnoException (dns.js:55:10)
09:06:56 socketio.1 | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:26)
09:06:56 system | socketio.1 stopped (rc=1)
09:06:56 system | sending SIGTERM to redis_cache.1 (pid 913)
09:06:56 system | sending SIGTERM to redis_socketio.1 (pid 915)
09:06:56 system | sending SIGTERM to redis_queue.1 (pid 916)
09:06:56 system | sending SIGTERM to web.1 (pid 918)
09:06:56 system | sending SIGTERM to watch.1 (pid 922)
09:06:56 system | sending SIGTERM to schedule.1 (pid 924)
09:06:56 system | sending SIGTERM to worker_short.1 (pid 926)
09:06:56 system | sending SIGTERM to worker_long.1 (pid 927)
09:06:56 system | sending SIGTERM to worker_default.1 (pid 928)
09:06:56 redis_cache.1 | 913:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_socketio.1 | 915:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_queue.1 | 916:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 system | worker_long.1 stopped (rc=-15)
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 # User requested shutdown...
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 * Removing the pid file.
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.338 # Redis is now ready to exit, bye bye...
09:06:56 system | watch.1 stopped (rc=-15)
09:06:56 system | redis_queue.1 stopped (rc=0)
09:06:56 system | schedule.1 stopped (rc=-15)
09:06:56 system | web.1 stopped (rc=-15)
09:06:56 system | worker_default.1 stopped (rc=-15)
09:06:56 system | worker_short.1 stopped (rc=-15)
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # User requested shutdown...
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 * Removing the pid file.
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_cache.1 stopped (rc=0)
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 # User requested shutdown...
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 * Removing the pid file.
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.443 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_socketio.1 stopped (rc=0)
python erpnext frappe
add a comment |
up vote
0
down vote
favorite
When i try bench start it threw below error.
I have already tried redis reinstallation, bench update, service restarts but those have not solved my problem yet.
➜ frappe-bench bench start
... ... ...
09:06:56 socketio.1 | events.js:136
09:06:56 socketio.1 | throw er; // Unhandled 'error' event
09:06:56 socketio.1 | ^
09:06:56 socketio.1 |
09:06:56 socketio.1 | Error: Redis connection to localhost:12000 failed - getaddrinfo ENOTFOUND localhost localhost:12000
09:06:56 socketio.1 | at errnoException (dns.js:55:10)
09:06:56 socketio.1 | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:26)
09:06:56 system | socketio.1 stopped (rc=1)
09:06:56 system | sending SIGTERM to redis_cache.1 (pid 913)
09:06:56 system | sending SIGTERM to redis_socketio.1 (pid 915)
09:06:56 system | sending SIGTERM to redis_queue.1 (pid 916)
09:06:56 system | sending SIGTERM to web.1 (pid 918)
09:06:56 system | sending SIGTERM to watch.1 (pid 922)
09:06:56 system | sending SIGTERM to schedule.1 (pid 924)
09:06:56 system | sending SIGTERM to worker_short.1 (pid 926)
09:06:56 system | sending SIGTERM to worker_long.1 (pid 927)
09:06:56 system | sending SIGTERM to worker_default.1 (pid 928)
09:06:56 redis_cache.1 | 913:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_socketio.1 | 915:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_queue.1 | 916:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 system | worker_long.1 stopped (rc=-15)
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 # User requested shutdown...
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 * Removing the pid file.
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.338 # Redis is now ready to exit, bye bye...
09:06:56 system | watch.1 stopped (rc=-15)
09:06:56 system | redis_queue.1 stopped (rc=0)
09:06:56 system | schedule.1 stopped (rc=-15)
09:06:56 system | web.1 stopped (rc=-15)
09:06:56 system | worker_default.1 stopped (rc=-15)
09:06:56 system | worker_short.1 stopped (rc=-15)
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # User requested shutdown...
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 * Removing the pid file.
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_cache.1 stopped (rc=0)
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 # User requested shutdown...
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 * Removing the pid file.
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.443 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_socketio.1 stopped (rc=0)
python erpnext frappe
As strange as it seems, it looks like it cannot resolve 'localhost' to an address. Check your hosts file.
– crafter
Nov 18 at 6:29
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
When i try bench start it threw below error.
I have already tried redis reinstallation, bench update, service restarts but those have not solved my problem yet.
➜ frappe-bench bench start
... ... ...
09:06:56 socketio.1 | events.js:136
09:06:56 socketio.1 | throw er; // Unhandled 'error' event
09:06:56 socketio.1 | ^
09:06:56 socketio.1 |
09:06:56 socketio.1 | Error: Redis connection to localhost:12000 failed - getaddrinfo ENOTFOUND localhost localhost:12000
09:06:56 socketio.1 | at errnoException (dns.js:55:10)
09:06:56 socketio.1 | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:26)
09:06:56 system | socketio.1 stopped (rc=1)
09:06:56 system | sending SIGTERM to redis_cache.1 (pid 913)
09:06:56 system | sending SIGTERM to redis_socketio.1 (pid 915)
09:06:56 system | sending SIGTERM to redis_queue.1 (pid 916)
09:06:56 system | sending SIGTERM to web.1 (pid 918)
09:06:56 system | sending SIGTERM to watch.1 (pid 922)
09:06:56 system | sending SIGTERM to schedule.1 (pid 924)
09:06:56 system | sending SIGTERM to worker_short.1 (pid 926)
09:06:56 system | sending SIGTERM to worker_long.1 (pid 927)
09:06:56 system | sending SIGTERM to worker_default.1 (pid 928)
09:06:56 redis_cache.1 | 913:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_socketio.1 | 915:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_queue.1 | 916:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 system | worker_long.1 stopped (rc=-15)
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 # User requested shutdown...
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 * Removing the pid file.
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.338 # Redis is now ready to exit, bye bye...
09:06:56 system | watch.1 stopped (rc=-15)
09:06:56 system | redis_queue.1 stopped (rc=0)
09:06:56 system | schedule.1 stopped (rc=-15)
09:06:56 system | web.1 stopped (rc=-15)
09:06:56 system | worker_default.1 stopped (rc=-15)
09:06:56 system | worker_short.1 stopped (rc=-15)
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # User requested shutdown...
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 * Removing the pid file.
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_cache.1 stopped (rc=0)
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 # User requested shutdown...
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 * Removing the pid file.
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.443 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_socketio.1 stopped (rc=0)
python erpnext frappe
When i try bench start it threw below error.
I have already tried redis reinstallation, bench update, service restarts but those have not solved my problem yet.
➜ frappe-bench bench start
... ... ...
09:06:56 socketio.1 | events.js:136
09:06:56 socketio.1 | throw er; // Unhandled 'error' event
09:06:56 socketio.1 | ^
09:06:56 socketio.1 |
09:06:56 socketio.1 | Error: Redis connection to localhost:12000 failed - getaddrinfo ENOTFOUND localhost localhost:12000
09:06:56 socketio.1 | at errnoException (dns.js:55:10)
09:06:56 socketio.1 | at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:97:26)
09:06:56 system | socketio.1 stopped (rc=1)
09:06:56 system | sending SIGTERM to redis_cache.1 (pid 913)
09:06:56 system | sending SIGTERM to redis_socketio.1 (pid 915)
09:06:56 system | sending SIGTERM to redis_queue.1 (pid 916)
09:06:56 system | sending SIGTERM to web.1 (pid 918)
09:06:56 system | sending SIGTERM to watch.1 (pid 922)
09:06:56 system | sending SIGTERM to schedule.1 (pid 924)
09:06:56 system | sending SIGTERM to worker_short.1 (pid 926)
09:06:56 system | sending SIGTERM to worker_long.1 (pid 927)
09:06:56 system | sending SIGTERM to worker_default.1 (pid 928)
09:06:56 redis_cache.1 | 913:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_socketio.1 | 915:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 redis_queue.1 | 916:signal-handler (1541905616) Received SIGTERM scheduling shutdown...
09:06:56 system | worker_long.1 stopped (rc=-15)
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 # User requested shutdown...
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.337 * Removing the pid file.
09:06:56 redis_queue.1 | 916:M 11 Nov 2018 09:06:56.338 # Redis is now ready to exit, bye bye...
09:06:56 system | watch.1 stopped (rc=-15)
09:06:56 system | redis_queue.1 stopped (rc=0)
09:06:56 system | schedule.1 stopped (rc=-15)
09:06:56 system | web.1 stopped (rc=-15)
09:06:56 system | worker_default.1 stopped (rc=-15)
09:06:56 system | worker_short.1 stopped (rc=-15)
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # User requested shutdown...
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 * Removing the pid file.
09:06:56 redis_cache.1 | 913:M 11 Nov 2018 09:06:56.344 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_cache.1 stopped (rc=0)
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 # User requested shutdown...
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.438 * Removing the pid file.
09:06:56 redis_socketio.1 | 915:M 11 Nov 2018 09:06:56.443 # Redis is now ready to exit, bye bye...
09:06:56 system | redis_socketio.1 stopped (rc=0)
python erpnext frappe
python erpnext frappe
edited Nov 11 at 6:06
James Z
11.1k71735
11.1k71735
asked Nov 11 at 4:14
0V1
2616
2616
As strange as it seems, it looks like it cannot resolve 'localhost' to an address. Check your hosts file.
– crafter
Nov 18 at 6:29
add a comment |
As strange as it seems, it looks like it cannot resolve 'localhost' to an address. Check your hosts file.
– crafter
Nov 18 at 6:29
As strange as it seems, it looks like it cannot resolve 'localhost' to an address. Check your hosts file.
– crafter
Nov 18 at 6:29
As strange as it seems, it looks like it cannot resolve 'localhost' to an address. Check your hosts file.
– crafter
Nov 18 at 6:29
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53245777%2fredis-socketio-1-stopped-rc-0-on-osx%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
As strange as it seems, it looks like it cannot resolve 'localhost' to an address. Check your hosts file.
– crafter
Nov 18 at 6:29