PR#158: Added a faq for 'redis server already running' error - fedora-commops/fedora-happiness-packets

fedora-commops / fedora-happiness-packets

#158 Added a faq for 'redis server already running' error

Merged 5 years ago by jflory7. Opened 5 years ago by sanjana11147.

fedora-commops/ sanjana11147/fedora-happiness-packets faq_redis into master

Added a faq for 'redis server already running' error

Sanjana • 5 years ago

cb9d8f6

docs/faq.rst

file modified

+10

		`@@ -38,3 +38,13 @@`
		`message.save()`

		`Now when you access Archives, the message can be seen.`
		`+`
		`+ ERROR: for fedora-happiness-packets_redis_1 Cannot start service redis: driver failed programming external connectivity on endpoint fedora-happiness-packets_redis_1 starting userland proxy: listen tcp 0.0.0.0:6379: bind: address already in use`
		`+ A redis service is already running on your machine. To see what process is running use::`
		`+`
		`+ sudo netstat -lnp`
		`+`
		+ End the running process run the web server again using ``docker-compose up``.
		+ To see processes running on a particular port (eg: 0.0.0.0:6379) Use ``grep`` to filter for that specific port::
		`+`
		`+ sudo netstat -tulnp \| grep 6379`

sanjana11147 commented 5 years ago

Added a frequently asked question for the Error: listen tcp 0.0.0.0:6379: bind: address already in use

This change would help the users having troubles starting the redis server because it is already running in the machine.

Tested: Locally. Passed test.docs.sh

chetanshinde911 commented 5 years ago

@sanjana11147 what I had done was i changed the port port on which redis server is meant to run from 6379 to 6380 as this port no is not been claimed by any protocol. Can we have that as well added to the FAQ?

Metadata Update from @jflory7:
- Pull-request tagged with: improvement, type - docs, type - summer coding
- Request assigned

5 years ago

jflory7 commented 5 years ago

Added a frequently asked question for the Error: listen tcp 0.0.0.0:6379: bind: address already in use
This change would help the users having troubles starting the redis server because it is already running in the machine.

Thanks @sanjana11147, this change looks good. :thumbsup: Thanks for helping improve the docs! Merging. :checkered_flag:

@sanjana11147 what I had done was i changed the port port on which redis server is meant to run from 6379 to 6380 as this port no is not been claimed by any protocol. Can we have that as well added to the FAQ?

In this case, I think it is better practice for someone to understand why this problem is happening by seeing what processes are running and ending them if necessary. If someone is running a Redis server locally on their machine and need it to continue running, then they can change the port. But in this case, I think these steps provided by @sanjana11147 are sufficient.

Pull-Request has been merged by jflory7

5 years ago