Basic Tools: VMware12, Centos-7-x86_64-everything-1611.iso, redis-desktop-manager-0.8.0.3841
Needless to say, first of all, about what is Redis, Redis installation, please download this document to read.
Http://pan.baidu.com/s/1bBPYua
After you have read the documentation for the Redis installation, start the Redis display and you are successful!
For front-end and back-end startup commands, be sure to note the path!
After the installation of the document mode is successful, the redis.conf file is copied in and its own Redis directory should look like this: (if not, verify that Redis is successfully installed and can start)
REDIS01 is my own definition of folder name
Then, depending on the document, after the configuration file has been changed, access to Redis through Redis-desktop-manager has encountered various problems:
1. The firewall is not turned on (not described in the documentation)
after you open the /etc/sysconfig/ directory, you do not see the iptables document (there may be iptables-config documents, etc., do not confuse)
At this point, the key comes, the newly installed CentOS system, the firewall is banned by default, so there will be no iptables documents.
Note that you do not create it manually, and let it generate by several commands:
Workaround: 1, write a iptables command configure a firewall rule: iptables-p OUTPUT ACCEPT2, save service iptables Save3,service iptables Restart if the following exception occurs, the service command supports only basic LSB actions (start, stop, restart, Try-restart, Reload, Force-reloa D, status). For other actions, please try to use Systemctl. With RHEL 7/centos 7, FIREWALLD is introduced to manage iptables. IMHO, FIREWALLD is more suited for workstations than for server environments. It's possible to Go, and a more classic iptables setup. First, stop and mask the FIREWALLD service: Please enter the following command consecutively: Systemctl stop firewalld systemctl mask firewalld yum instal L IPTABLES-SERVICESSYSTEMCTL enable Iptablessystemctl stop iptables systemctl start iptables systemctl | Restart Iptables Service iptables Save
At this point, the Iptables file will be present. Next edit the document, you can use VIM or directly with the desktop (desktop support from Windows directly copied into the Iptables document, more convenient)
Enter the usual:
# Generated by Iptables-save v1.4.21 on Sat Apr 06:11:46 2017*filter:input Accept [0:0]:forward Accept [0:0]:output ACC EPT [0:0]-a input-m State--state related,established-j accept-a input-p icmp-j accept-a input-i lo-j ACCEPT-A INPUT -P tcp-m State--state new-m TCP--dport 22-j accept-a input-m State--state new-m tcp-p TCP--dport 3306-j ACCEPT -A input-m state--state new-m tcp-p TCP--dport 8080-j accept-a input-m State--state new-m tcp-p TCP--dport 6379 -j accept-a input-j REJECT--reject-with icmp-host-prohibited-a forward-j REJECT--reject-with Icmp-host-prohibitedcomm it# completed on Sat APR 29 06:11:46 2017
This is mine, is commonly used, can be copied directly.
Next, access via the Redis Desktop Manager tool, please note several questions
First, Host: The IP of Linux is not windows!
Port 6379 is undeniable.
Next, a big paragraph, please read
Redis Desktop Manager is a Redis graphical management tool that makes it easy for managers to manage Redis data more easily and intuitively.
Before using Redis Desktop Manager, however, there are several elements to note:
One, note in the redis.conf file: Bind 127.0.0.1 (in a text before the # number for comment)
Second, set up the Redis password. Before setting a password, you first open the server, then connect with the client, and finally set the password through the client.
1. Create a new terminal to open the service.
2. Open a terminal, connect and set the password.
The part of the smear is because I have previously set the password, in order not to mislead you, so I put the password to erase the steps.
Quit command is to exit the connection, and then I reconnect, through the Auth plus password command to successfully log in, return OK.
The password setting is now complete.
Third, ensure that the network unblocked and 6379 ports open.
The first few steps are in CentOS, and now it's time to return to our Windows test IP and the port is unblocked.
Yes, if you do not know the CentOS IP, or to the CentOS terminal Input ifconfig command to view, the first piece of data returned contains the local IP.
If you return the result is not the same as me, then almost can be sure that your virtual machine network is not open, open the method, click Connect.
After we get the IP, we return to Windows, turn on CMD, and pass the Telnet command to test whether the port is unblocked.
There are three scenarios:
1. You return the same results as me, then don't worry, then look down.
2. The result of your return is a pure black cmd, so congratulations, you can skip this step directly.
3. You return "Telnet is not internal or external command", then Baidu solution (qualified programmers, must use very skilled).
Baidu Link: http://jingyan.baidu.com/article/1e5468f9033a71484961b7d7.html
OK, the result I'm returning now is that CentOS Port 6379 does not have an open result.
So, open the terminal in CentOS and turn on port 6379 via the command:
1. Get Root Permissions
2. Enter Firewall-cmd--query-port=6379/tcp, if the return result is no, then it proves that port 6379 does not turn on.
3. Enter the Firewall-cmd--add-port=6379/tcp, turn on the 6379 port, and return to success.
Then execute the previous command and return yes to prove that the port has been successfully opened.
So far, all the upfront work is ready! We started to connect to CentOS's Redis via Redis Desktop Manager.
bingo!!!
Linux CENTOS7 installation configuration Redis and Redis Desktop Manager tools Connection considerations