Process: 2424 ExecStart=/usr/bin/redis-server /etc/redis/nf (code=exited, status=0/SUCCESS)ĬGroup: /system.slice/rvice Process: 2421 ExecStop=/bin/kill -s TERM $MAINPID (code=exited, status=0/SUCCESS) Loaded: loaded (/lib/systemd/system/rvice enabled vendor preset: enabled)Īctive: active (running) since Wed 18:48:52 UTC 12s ago If it is running without any errors, this command will produce output similar to the following: Start by checking that the Redis service is running: We will go over a handful of ways to check that Redis is working correctly in this step. Here, you can see that Redis is running and is already enabled, meaning that it is set to start up every time the server boots. In the prompt that follows, test connectivity with the ping command:Įxit out into the shell again when you are finished: To test that Redis is functioning correctly, connect to the server using the command-line client: If, however, you prefer to start up Redis manually every time your server boots, you can configure this with the following command: Note: This setting is desirable for many common use cases of Redis. With that, your Redis installation is fully operational and ready for you to use. However, some of its default configuration settings are insecure and provide malicious actors with opportunities to attack and gain access to your server and its data. The remaining steps in this tutorial cover methods for mitigating these vulnerabilities, as prescribed by the official Redis website. #UBUNTU 18.04 SHADOWSOCKS CLIENT UPDATE#.#UBUNTU 18.04 SHADOWSOCKS CLIENT INSTALL#.#UBUNTU 18.04 SHADOWSOCKS CLIENT HOW TO#.
0 Comments
Leave a Reply. |