Shulou(Shulou.com)06/02 Report--

Deploy jumpserver

The entire deployment fully refers to the following documentation and will not go into more detail:

Https://www.jishuchi.com/read/Jumpserver-148/2111

The note here is to record several problems during installation.

The first question is that you often time out during pip install.

The company's network environment is not good, which requires a re-installation or a change to a domestic source.

Second problem, mysql_config can't find it.

For binary installation of mysql, you need to set the environment variable to the execution file under the bin of mysql.

The third problem is that when installing a dependency, the pip version is too low.

Upgrade the pip version, the upgrade command prompt has been given

The fourth question, In file included from Modules/LDAPObject.c:8:0:

Modules/constants.h:7:18: fatal error: lber.h: there is no such file or directory

Yum install-y openldap-devells

The fifth question, ImportError: libmysqlclient.so.20: cannot open shared object file: No such file or directory

Or because of the binary deployment of mysql, the library libmysqlclient can not be found, do a soft link to ln-s / mdata/mysql/lib/libmysqlclient.so.20 / usr/lib64/libmysqlclient.so.20

The sixth question, TypeError: connect () argument 3 must be str, not int

Quote pure numeric parameters in config.yml

Seventh, after deploying jumpserver, it is found that there is no user name and password. The possible reason is that the initial data imported into the database was incomplete when the error was started, and the error was later resolved. The previously imported data was ignored when the data was re-imported, or there was a cache, and the specific reason could not be reproduced.

Solution: after solving the fifth and sixth problems, delete the database, recreate the database, restart the redis at the same time, and clean up the data directory in the jumpserver directory. The media directory does not need to be cleaned, there is no data in it, and the initial data directory also has this media directory.

The eighth problem is that after entering the page, the terminal management of session management cannot see the coco component and the component at the beginning of gua, and ssh admin@IP cannot log in.

Solution: first check to make sure that the Token of Token and jumpserver are the same, and then restart the docker container. After I rebooted, the component at the beginning of gua could be displayed normally, but coco still didn't work. I restarted it several times during testing, or even deleted the container and rebuilt it. Finally, I downloaded the package and deployed it directly, and then solved the problem. There is also a derivative problem here. When downloading the python dependency package of coco components, there is a place where it is stuck for a long time. This is due to the problem of domestic sources. The two sources have been stuck in the same place, and then changed to the default official source. Although the download is slower, it has finished downloading normally.

The ninth question is that when creating a system user, in the sudo option, according to the official document, one command per line, and then after the creation, log in to the resource machine and find that you still need a password to execute the command set by sudo.

Go back to check, click on the system user, there will be a small test window next to (be sure to allow the browser pop-up window), click the push command to test, and find that ansible reports a format error in the last step of the push. Finally, write the command of the sudo option into a line, separated by commas, and the test will be successful again. Then return to the login resource machine and you can use the command normally.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.