# Cannot restart sensu-server

**URL:** <https://discourse.sensu.io/t/cannot-restart-sensu-server/631>\
**Category:** Sensu Classic (EOL)\
**Created:** [June 28, 2016, 11:16am UTC](https://discourse.sensu.io/t/cannot-restart-sensu-server/631 "2016-06-28T11:16:53Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![NJOM](https://avatars.discourse-cdn.com/v4/letter/n/96bed5/32.png) [@NJOM](https://discourse.sensu.io/u/NJOM)\
**Post date:** [June 28, 2016, 11:16am UTC](https://discourse.sensu.io/t/cannot-restart-sensu-server/631/1 "2016-06-28T11:16:53Z")

</div>

Hi,

I cannot restart sensu-server. Redis, Rabbit, Sensu Server and Sensu client are all installed on the same Centos machine. killing the centos server does not stop the process (unless you put -9 in the command).

If I stop the client, and kill -9 the server will start and restart without any problems. As soon as i start the client and then try a restart of the server I get the following error.

[root@atvpxsensu33-1 redis]# sudo /etc/init.d/sensu-service server restart  
configuration is valid  
Timed out waiting for sensu-server to stop [FAILED]  
[FAIL

[root@atvpxsensu33-1 redis]# tail -f /var/log/sensu/sensu-server.log  
{“timestamp”:“2016-06-28T12:03:56.237522+0100”,“level”:“warn”,“message”:“received signal”,“signal”:“TERM”}  
{“timestamp”:“2016-06-28T12:03:56.237947+0100”,“level”:“warn”,“message”:“stopping”}  
{“timestamp”:“2016-06-28T12:03:56.238042+0100”,“level”:“warn”,“message”:“unsubscribing from keepalive and result queues”}  
{“timestamp”:“2016-06-28T12:03:56.238278+0100”,“level”:“info”,“message”:“completing work in progress”,“in\_progress”:{“check\_results”:17}}

There seems to be no problems with server or client config as both validate ok.

This is the latest version of sensu i am using…  
[root@atvpxsensu33-1 redis]# rpm -qa | grep sensu  
sensu-0.25.3-1.x86\_64  
[root@atvpxsensu33-1 redis]# rpm -qa | grep rabbit  
rabbitmq-server-3.6.0-1.noarch  
[root@atvpxsensu33-1 redis]# rpm -qa | grep redis  
redis-2.4.10-1.el6.x86\_64  
[root@atvpxsensu33-1 redis]#

Any help/suggestions much appreciated.

Regards,

NJ

---

<div class="post-metadata">

**Author:** ![NJOM](https://avatars.discourse-cdn.com/v4/letter/n/96bed5/32.png) [@NJOM](https://discourse.sensu.io/u/NJOM)\
**Post date:** [June 29, 2016, 3:30pm UTC](https://discourse.sensu.io/t/cannot-restart-sensu-server/631/2 "2016-06-29T15:30:42Z")

</div>

Think i found the issue with this. its a standalone configuration with all components installed on the same server. The config files reference “localhost” and not 127.0.0.1. When i made the change the server restart behaved as expected.

NJ

> **···**
>
> On Tuesday, June 28, 2016 at 12:16:53 PM UTC+1, NJOM wrote:
> 
> > Hi,
> > 
> > I cannot restart sensu-server. Redis, Rabbit, Sensu Server and Sensu client are all installed on the same Centos machine. killing the centos server does not stop the process (unless you put -9 in the command).
> > 
> > If I stop the client, and kill -9 the server will start and restart without any problems. As soon as i start the client and then try a restart of the server I get the following error.
> > 
> > [root@atvpxsensu33-1 redis]# sudo /etc/init.d/sensu-service server restart  
> > configuration is valid  
> > Timed out waiting for sensu-server to stop [FAILED]  
> > [FAIL
> > 
> > [root@atvpxsensu33-1 redis]# tail -f /var/log/sensu/sensu-server.log  
> > {“timestamp”:“2016-06-28T12:03:56.237522+0100”,“level”:“warn”,“message”:“received signal”,“signal”:“TERM”}  
> > {“timestamp”:“2016-06-28T12:03:56.237947+0100”,“level”:“warn”,“message”:“stopping”}  
> > {“timestamp”:“2016-06-28T12:03:56.238042+0100”,“level”:“warn”,“message”:“unsubscribing from keepalive and result queues”}  
> > {“timestamp”:“2016-06-28T12:03:56.238278+0100”,“level”:“info”,“message”:“completing work in progress”,“in\_progress”:{“check\_results”:17}}
> > 
> > There seems to be no problems with server or client config as both validate ok.
> > 
> > This is the latest version of sensu i am using…  
> > [root@atvpxsensu33-1 redis]# rpm -qa | grep sensu  
> > sensu-0.25.3-1.x86\_64  
> > [root@atvpxsensu33-1 redis]# rpm -qa | grep rabbit  
> > rabbitmq-server-3.6.0-1.noarch  
> > [root@atvpxsensu33-1 redis]# rpm -qa | grep redis  
> > redis-2.4.10-1.el6.x86\_64  
> > [root@atvpxsensu33-1 redis]#
> > 
> > Any help/suggestions much appreciated.
> > 
> > Regards,
> > 
> > NJ

---

<div class="post-metadata">

**Author:** ![Kyle\_Anderson](https://avatars.discourse-cdn.com/v4/letter/k/e5b9ba/32.png) [@Kyle\_Anderson](https://discourse.sensu.io/u/Kyle_Anderson)\
**Post date:** [June 30, 2016, 3:17am UTC](https://discourse.sensu.io/t/cannot-restart-sensu-server/631/3 "2016-06-30T03:17:25Z")

</div>

Is this the core issue?  
[https://sensuapp.org/docs/latest/reference/redis.html#redis-attributes](https://sensuapp.org/docs/latest/reference/redis.html#redis-attributes)

(see localhost warning)

> **···**
>
> On Wed, Jun 29, 2016 at 8:30 AM, NJOM [njomeara@gmail.com](mailto:njomeara@gmail.com) wrote:
> 
> > Think i found the issue with this. its a standalone configuration with all components installed on the same server. The config files reference “localhost” and not 127.0.0.1. When i made the change the server restart behaved as expected.
> > 
> > NJ
> > 
> > On Tuesday, June 28, 2016 at 12:16:53 PM UTC+1, NJOM wrote:
> > 
> > > Hi,
> > > 
> > > I cannot restart sensu-server. Redis, Rabbit, Sensu Server and Sensu client are all installed on the same Centos machine. killing the centos server does not stop the process (unless you put -9 in the command).
> > > 
> > > If I stop the client, and kill -9 the server will start and restart without any problems. As soon as i start the client and then try a restart of the server I get the following error.
> > > 
> > > [root@atvpxsensu33-1 redis]# sudo /etc/init.d/sensu-service server restart  
> > > configuration is valid  
> > > Timed out waiting for sensu-server to stop [FAILED]  
> > > [FAIL
> > > 
> > > [root@atvpxsensu33-1 redis]# tail -f /var/log/sensu/sensu-server.log  
> > > {“timestamp”:“2016-06-28T12:03:56.237522+0100”,“level”:“warn”,“message”:“received signal”,“signal”:“TERM”}  
> > > {“timestamp”:“2016-06-28T12:03:56.237947+0100”,“level”:“warn”,“message”:“stopping”}  
> > > {“timestamp”:“2016-06-28T12:03:56.238042+0100”,“level”:“warn”,“message”:“unsubscribing from keepalive and result queues”}  
> > > {“timestamp”:“2016-06-28T12:03:56.238278+0100”,“level”:“info”,“message”:“completing work in progress”,“in\_progress”:{“check\_results”:17}}
> > > 
> > > There seems to be no problems with server or client config as both validate ok.
> > > 
> > > This is the latest version of sensu i am using…  
> > > [root@atvpxsensu33-1 redis]# rpm -qa | grep sensu  
> > > sensu-0.25.3-1.x86\_64  
> > > [root@atvpxsensu33-1 redis]# rpm -qa | grep rabbit  
> > > rabbitmq-server-3.6.0-1.noarch  
> > > [root@atvpxsensu33-1 redis]# rpm -qa | grep redis  
> > > redis-2.4.10-1.el6.x86\_64  
> > > [root@atvpxsensu33-1 redis]#
> > > 
> > > Any help/suggestions much appreciated.
> > > 
> > > Regards,
> > > 
> > > NJ