【等保工具箱】jumpserver好用的开源堡垒机系统

1. 前言

2.说明

JumpServer 是全球首款开源的堡垒机，使用 GNU GPL v2.0 开源协议，是符合 4A 规范的运维安全审计系统。
JumpServer 使用 Python / Django 为主进行开发，遵循 Web 2.0 规范，配备了业界领先的 Web Terminal 方案，交互界面美观、用户体验好。
JumpServer 采纳分布式架构，支持多机房跨区域部署，支持横向扩展，无资产数量及并发限制。
改变世界，从一点点开始。

3.环境说明

JumpServer 由于开源的堡垒机，故在安装会有很多问题，本人经过调试，目前测试稳定可用的环境如下（建议各位采用以下环境部署堡垒机）：

1. 采用CentOS-7.3.1611-x86_64-DVD-1611版本的linux系统
2. 本次堡垒机版本：jumpserver-offline-installer-v2.16.3-amd64-54.tar.gz

4.安装步骤

1. 安装centos 7.3.1611虚拟机（略）
2. 安装docker系统 （yum install docker）
3. 执行yum update 更新系统
4. 重启服务器reboot

重启服务器后：

$ systemctl daemon-reload
$ sudo service docker restart

开始安装堡垒机：

1. 下载堡垒机程序

链接：https://pan.baidu.com/s/15Z-o2xAq1cHZ51p89gWlXw
提取码：xy2p

2. 堡垒机安装

cd /opt
tar -xf jumpserver-offline-installer-v2.16.3-amd64-53.tar.gz
cd jumpserver-offline-installer-v2.16.3-amd64-53

安装
./jmsctl.sh install

启动
./jmsctl.sh start

安装完成后配置文件 /opt/jumpserver/config/config.txt
cd /cd jumpserver-offline-installer-v2.16.3-amd64-53 （此目录是你解压缩文件的目录，不是Jumpserver安装目录）

启动
./jmsctl.sh start

停止
./jmsctl.sh down

卸载
./jmsctl.sh uninstall

帮助
./jmsctl.sh -h

5.问题处理

如果提示以下信息：

Creating network "jms_net" with driver "bridge"
Creating jms_mysql ... done
Creating jms_redis ... done
Creating jms_core  ... done
ERROR: for celery  Container "76b2e315f69d" is unhealthy.
ERROR: for lina  Container "76b2e315f69d" is unhealthy.
ERROR: for luna  Container "76b2e315f69d" is unhealthy.
ERROR: for lion  Container "76b2e315f69d" is unhealthy.
ERROR: for koko  Container "76b2e315f69d" is unhealthy.
ERROR: Encountered errors while bringing up the project.

请尝试执行以下操作：

如果出现上面的错误, 执行下面的命令, 直到出现 Check service status 为止
docker logs -f jms_core --tail 200  # 如果没有报错就等表结构合并完毕后然后重新 start 即可

2021-02-08 14:58:53 Mon Feb  8 14:58:53 2021
2021-02-08 14:58:53 JumpServer version v2.16.3, more see https://www.jumpserver.org

- Start Gunicorn WSGI HTTP Server
2021-02-08 14:58:53 Check database connection ...
users
  [ ] 0001_initial
  [ ] 0002_auto_20171225_1157_squashed_0019_auto_20190304_1459 (18 squashed migrations)
  [ ] 0020_auto_20190612_1825
  [ ] 0021_auto_20190625_1104
  [ ] 0022_auto_20190625_1105
  [ ] 0023_auto_20190724_1525
  [ ] 0024_auto_20191118_1612
  [ ] 0025_auto_20200206_1216
  [ ] 0026_auto_20200508_2105
  [ ] 0027_auto_20200616_1503
  [ ] 0028_auto_20200728_1805
  [ ] 0029_auto_20200814_1650
  [ ] 0030_auto_20200819_2041
  [ ] 0031_auto_20201118_1801
  2021-02-08 14:58:58 Database connect success
  Operations to perform:
    Apply all migrations: admin, applications, assets, audits, auth, authentication, captcha, common, contenttypes, django_cas_ng, django_celery_beat, jms_oidc_rp, ops, orgs, perms, sessions, settings, terminal, tickets, users
  Running migrations:
    Applying contenttypes.0001_initial... OK
    Applying contenttypes.0002_remove_content_type_name... OK
    Applying auth.0001_initial... OK
    Applying auth.0002_alter_permission_name_max_length... OK
    Applying auth.0003_alter_user_email_max_length... OK
    Applying auth.0004_alter_user_username_opts... OK
    Applying auth.0005_alter_user_last_login_null... OK
    Applying auth.0006_require_contenttypes_0002... OK
    Applying auth.0007_alter_validators_add_error_messages... OK
    Applying auth.0008_alter_user_username_max_length... OK
    ... 省略
    Applying tickets.0001_initial... OK
    Applying tickets.0002_auto_20200728_1146... OK
    Applying tickets.0003_auto_20200804_1551... OK
    Applying tickets.0004_ticket_comment... OK
    Applying tickets.0005_ticket_meta_confirmed_system_users... OK
    Applying tickets.0006_auto_20201023_1628... OK
    Applying tickets.0007_auto_20201224_1821... OK
    Applying users.0031_auto_20201118_1801... OK
    # 确定这上面都是显示 ok，不能有 error
  2021-02-08 14:59:31 [cache INFO] CACHE: Send refresh task <orgs.caches.OrgResourceStatisticsCache object at 0x7fb9122ce0d0>.('nodes_amount',)
  Operations to perform:
    Apply all migrations: admin, applications, assets, audits, auth, authentication, captcha, common, contenttypes, django_cas_ng, django_celery_beat, jms_oidc_rp, ops, orgs, perms, sessions, settings, terminal, tickets, users
  Running migrations:
    No migrations to apply.

  - Start Flower as Task Monitor

  - Start Daphne ASGI WS Server
  2021-02-08 15:01:02 Check service status: gunicorn -> running at 38
  2021-02-08 15:01:02 Check service status: flower -> running at 44
  2021-02-08 15:01:02 Check service status: daphne -> running at 54

确定上面都是 ok 的没有报错, 提示 Check service status 后就可以重新启动其他组件
./jmsctl.sh start