Скачать или смотреть How to Resolve the Issue of Redis Using Port 6379 After Uninstallation Attempt

Struggling to free up port `6379` used by Redis despite attempts at uninstallation? Discover effective solutions and troubleshooting tips in our detailed guide!
---
This video is based on the question https://stackoverflow.com/q/74455933/ asked by the user 'dhanyn10' ( https://stackoverflow.com/u/2978502/ ) and on the answer https://stackoverflow.com/a/74456182/ provided by the user 'Kevin C' ( https://stackoverflow.com/u/4834431/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Unable to kill the port 6379 used by redis installed with snap

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Troubleshooting Redis Port Locking on Linux

If you're trying to uninstall Redis from your Linux system but find that it's stubbornly still consuming port 6379, you're not alone. This can be a frustrating experience, especially if you believe you have followed all the recommended uninstallation procedures. Let's dive into this common issue and explore effective solutions that will help you resolve it.

Understanding the Problem

Why is Redis Using Port 6379?

The Redis server defaults to using port 6379, and if it's still showing as active, it means that an instance is running on your machine. Even after you attempt to uninstall it, port 6379 can remain busy if the Redis server was installed via a method that may not have properly terminated the service—such as using snap.

Checking for Active Processes

Before we can effectively remove Redis, it’s crucial to identify whether it's indeed running. Here are commands to help you check:

[[See Video to Reveal this Text or Code Snippet]]

This command will show you the processes listening on port 6379. If you see redis-server in the output, it confirms that Redis is still running.

Steps to Resolve the Issue

1. Stopping the Redis Service

If Redis is identified as running, the next step is to stop the service. Depending on how Redis was installed (e.g., via snap), the commands may differ.

Stop Redis Installed via Snap

For Redis instances installed using snap, use the following command to stop it:

[[See Video to Reveal this Text or Code Snippet]]

2. Remove Redis if Still Installed

After stopping the service, we can attempt to remove it. If it remains installed, use the following command:

[[See Video to Reveal this Text or Code Snippet]]

This command can help clear any lingering files and release port 6379.

3. Verify Redis is Uninstalled

Check again if the port is still in use. Run the following command once more:

[[See Video to Reveal this Text or Code Snippet]]

If there is no output that indicates redis-server, then Redis has been successfully uninstalled.

4. Clearing Dependencies

If Redis does not appear to be installed but the port is still active, it could be that remnants of other Redis-related packages are causing conflicts. Run these commands to identify all installed Redis packages:

[[See Video to Reveal this Text or Code Snippet]]

Make sure to remove all instances to ensure a clean uninstall:

[[See Video to Reveal this Text or Code Snippet]]

5. Final Checks

After you've uninstalled Redis and cleared its dependencies, run the following commands to ensure that no redis services are active:

[[See Video to Reveal this Text or Code Snippet]]

These commands help identify any lingering processes related to Redis.

Additional Tips

If all else fails and you cannot identify why Redis is still using port 6379, here are a few more tools at your disposal:

Use mlocate: Install and update mlocate for faster file searches on your system.

[[See Video to Reveal this Text or Code Snippet]]

Search for Redis files:

[[See Video to Reveal this Text or Code Snippet]]

This will give you a comprehensive list of all files associated with Redis on your system.

Conclusion

Dealing with stubborn services like Redis can be frustrating, especially when they persist even after you've attempted to remove them. By following the outlined steps—stopping the service, removing it, and verifying its uninstallation—you should be able to free up port 6379. Remember to run checks after every step to ensure that the issue is being resolved. Happy debugging!