Redis .service 文件

按照这些说明在 Ubuntu 16.04 上安装 Redis 。我通过收集它make，配置它，一切正常，但是：当通过该行的输出启动/重新启动时sudo service redis restart，它会“挂起”一定的超时时间，也就是说，据我所知，“从内部”它有效像这样 - 成功启动/重启后，返回某种类型的状态true，控制台提示您输入新命令。我有这个身份，相对来说，回不去了。命令输出sudo service redis status：

root@ubuntu-xenial:~# service redis status
● redis-server.service - Redis In-Memory Data Store
   Loaded: loaded (/lib/systemd/system/redis-server.service; enabled; vendor preset: enabled)
   Active: activating (start-post) since Ср 2017-06-28 07:17:09 UTC; 14s ago
   Docs: http://redis.io/documentation,
       man:redis-server(1)
   Process: 15864 ExecStopPost=/bin/run-parts --verbose /etc/redis/redis-server.post-down.d (code=exited, status=0/SUCCESS)
   Process: 15882 ExecStartPost=/bin/run-parts --verbose /etc/redis/redis-server.post-up.d (code=exited, status=0/SUCCESS)
   Process: 15878 ExecStart=/usr/local/bin/redis-server /etc/redis/redis.conf (code=exited, status=0/SUCCESS)
   Process: 15874 ExecStartPre=/bin/run-parts --verbose /etc/redis/redis-server.pre-up.d (code=exited, status=0/SUCCESS)
     Tasks: 3
    Memory: 10.2M
       CPU: 89ms
    CGroup: /system.slice/redis-server.service
            └─15881 /usr/local/bin/redis-server 127.0.0.1:6379       

июн 28 07:17:09 ubuntu-xenial systemd[1]: Starting Redis In-Memory Data Store...
июн 28 07:17:09 ubuntu-xenial run-parts[15874]: run-parts: executing /etc/redis/redis-server.pre-up.d/00_example
июн 28 07:17:09 ubuntu-xenial redis-server[15878]: 15878:C 28 Jun 07:17:09.164 # systemd supervision requested, but NOTIFY_SOCKET not found
июн 28 07:17:09 ubuntu-xenial run-parts[15882]: run-parts: executing /etc/redis/redis-server.post-up.d/00_example
июн 28 07:17:09 ubuntu-xenial systemd[1]: redis-server.service: PID file /var/run/redis/redis-server.pid not readable (yet?) after start-post: No such file or directory

状态activating即 相对而言，这是我所说的状态，它显然不会返回，但没有它状态就不会设置active。

怎么修？