After a node restart, for some odd reason I can not longer start the sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See ‘systemctl status sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT; 30s ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited, status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered failed state.
···
What does the sensu-client log say?
···
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage <charlie@charliedrage.com> wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service' and 'journalctl -xn' for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT; 30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered failed
state.
--------------------------------------------
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
--------------------------------------------
Well, could be anything, you'll have to run it manually to see the
stdout/err and see why it cant start.
···
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage <charlie@charliedrage.com> wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
--------------------------------------------
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
--------------------------------------------
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson <kyle@xkyle.com> wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage <charlie@charliedrage.com> >> wrote:
> After a node restart, for some odd reason I can not longer start the
> sensu-client service. Any ideas?
>
> root@kvm05:~# service sensu-client start
> Job for sensu-client.service failed. See 'systemctl status
> sensu-client.service' and 'journalctl -xn' for details.
> root@kvm05:~# systemctl status sensu-client.service
> ● sensu-client.service - LSB: Sensu monitoring framework client
> Loaded: loaded (/etc/init.d/sensu-client)
> Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
> 30s
> ago
> Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
> status=5)
>
> Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
> sensu-service.service:
> Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
> exited, code=exited status=5
> Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
> framework client.
> Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
> failed
> state.
>
>
>
> --------------------------------------------
> Charlie Drage
> GPG [FE8E 8D18] [charliedrage.com/public.key]
> --------------------------------------------
Hmmm. It doesn’t even error out. Starting it manually (the /etc/ folder, and conf files) works. Just the Debian service has conked out.
Time to switch to CentOS! Much more stable.
···
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson kyle@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage charlie@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson kyle@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage charlie@charliedrage.com
wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Is this Debian 7? 0.16.0 updated init scripts for Debian fix.
···
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson kyle@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage charlie@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson kyle@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage charlie@charliedrage.com
wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Yes it is, I’ll try that Sean, thank you!
···
On Sun, Nov 2, 2014 at 7:42 PM, Sean Porter portertech@gmail.com wrote:
Is this Debian 7? 0.16.0 updated init scripts for Debian fix.
On Nov 2, 2014 7:51 AM, “Charlie Drage” charlie@charliedrage.com wrote:
Hmmm. It doesn’t even error out. Starting it manually (the /etc/ folder, and conf files) works. Just the Debian service has conked out.
Time to switch to CentOS! Much more stable.
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson kyle@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage charlie@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson kyle@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage charlie@charliedrage.com
wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Hello,
I have the same issue on Debian Sid, Sensu 0.15 and 0.16
Is there a fix ?
thank you
···
Le jeudi 13 novembre 2014 18:24:35 UTC+1, John Brand a écrit :
Charlie,
Didi it work?
John
Op zondag 2 november 2014 23:42:12 UTC+1 schreef Charlie Drage:
Yes it is, I’ll try that Sean, thank you!
On Sun, Nov 2, 2014 at 7:42 PM, Sean Porter porte...@gmail.com wrote:
Is this Debian 7? 0.16.0 updated init scripts for Debian fix.
On Nov 2, 2014 7:51 AM, “Charlie Drage” cha...@charliedrage.com wrote:
Hmmm. It doesn’t even error out. Starting it manually (the /etc/ folder, and conf files) works. Just the Debian service has conked out.
Time to switch to CentOS! Much more stable.
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson ky...@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage cha...@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson ky...@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage cha...@charliedrage.com > > > > > > > > > > >> wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Hey all,
No it did not work, I had upgraded to Debian 7.0 and the newest Sensu client.
I ended up completely re-installing Debian from scratch and re-installing the Sensu client. It seems that this issue occurred when I had experienced a loss of power in Debian. Really really weird. I’m not overly experience with Linux, but perhaps it relates to Debian’s change to systemd?
Anyways, it works now. Let’s just hope it doesn’t conk out again.
To note, there are no indications of failure in any of the logs (sensu logs + kernel / messages).
···
On Saturday, December 27, 2014 8:41:28 AM UTC-5, Doe John wrote:
Hello,
I have the same issue on Debian Sid, Sensu 0.15 and 0.16
Is there a fix ?
thank you
Le jeudi 13 novembre 2014 18:24:35 UTC+1, John Brand a écrit :
Charlie,
Didi it work?
John
Op zondag 2 november 2014 23:42:12 UTC+1 schreef Charlie Drage:
Yes it is, I’ll try that Sean, thank you!
On Sun, Nov 2, 2014 at 7:42 PM, Sean Porter porte...@gmail.com wrote:
Is this Debian 7? 0.16.0 updated init scripts for Debian fix.
On Nov 2, 2014 7:51 AM, “Charlie Drage” cha...@charliedrage.com wrote:
Hmmm. It doesn’t even error out. Starting it manually (the /etc/ folder, and conf files) works. Just the Debian service has conked out.
Time to switch to CentOS! Much more stable.
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson ky...@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage cha...@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson ky...@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage cha...@charliedrage.com > > > > > > > > > > > > >> wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Hi,
There is a fix. You need to edit the /etc/init.d/sensu-service file to make it working again. I did find it somewhere, but can’t find it again at the moment.
Change row number 15. service=sensu-$1 to prog=sensu-$1
Then change every declaration of $service to $prog
And then change this part.
if [ “$system” = “debian” ]; then
## source platform specific external scripts
. /lib/lsb/init-functions
[ -r /etc/default/$prog ] && . /etc/default/$prog
and add prog=sensu-$1 to it.
if [ “$system” = “debian” ]; then
## source platform specific external scripts
. /lib/lsb/init-functions
prog=sensu-$1
[ -r /etc/default/$prog ] && . /etc/default/$prog
Afterwards the problem of not being able to start sensu is resolved.
John
···
Op zaterdag 27 december 2014 14:41:28 UTC+1 schreef Doe John:
Hello,
I have the same issue on Debian Sid, Sensu 0.15 and 0.16
Is there a fix ?
thank you
Le jeudi 13 novembre 2014 18:24:35 UTC+1, John Brand a écrit :
Charlie,
Didi it work?
John
Op zondag 2 november 2014 23:42:12 UTC+1 schreef Charlie Drage:
Yes it is, I’ll try that Sean, thank you!
On Sun, Nov 2, 2014 at 7:42 PM, Sean Porter porte...@gmail.com wrote:
Is this Debian 7? 0.16.0 updated init scripts for Debian fix.
On Nov 2, 2014 7:51 AM, “Charlie Drage” cha...@charliedrage.com wrote:
Hmmm. It doesn’t even error out. Starting it manually (the /etc/ folder, and conf files) works. Just the Debian service has conked out.
Time to switch to CentOS! Much more stable.
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson ky...@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage cha...@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson ky...@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage cha...@charliedrage.com > > > > > > > > > > > > >> wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Albit a late reply, this fixed the issue within Debian.
I’ve upgrade from 0.60 to 0.17.1 but found the issue still persisted. I again had to edit the init.d file.
Any ideas if this will be fixed in the next release?
···
On Saturday, December 27, 2014 at 3:20:59 PM UTC-5, John Brand wrote:
Hi,
There is a fix. You need to edit the /etc/init.d/sensu-service file to make it working again. I did find it somewhere, but can’t find it again at the moment.
Change row number 15. service=sensu-$1 to prog=sensu-$1
Then change every declaration of $service to $prog
And then change this part.
if [ “$system” = “debian” ]; then
## source platform specific external scripts
. /lib/lsb/init-functions
[ -r /etc/default/$prog ] && . /etc/default/$prog
and add prog=sensu-$1 to it.
if [ “$system” = “debian” ]; then
## source platform specific external scripts
. /lib/lsb/init-functions
prog=sensu-$1
[ -r /etc/default/$prog ] && . /etc/default/$prog
Afterwards the problem of not being able to start sensu is resolved.
John
Op zaterdag 27 december 2014 14:41:28 UTC+1 schreef Doe John:
Hello,
I have the same issue on Debian Sid, Sensu 0.15 and 0.16
Is there a fix ?
thank you
Le jeudi 13 novembre 2014 18:24:35 UTC+1, John Brand a écrit :
Charlie,
Didi it work?
John
Op zondag 2 november 2014 23:42:12 UTC+1 schreef Charlie Drage:
Yes it is, I’ll try that Sean, thank you!
On Sun, Nov 2, 2014 at 7:42 PM, Sean Porter porte...@gmail.com wrote:
Is this Debian 7? 0.16.0 updated init scripts for Debian fix.
On Nov 2, 2014 7:51 AM, “Charlie Drage” cha...@charliedrage.com wrote:
Hmmm. It doesn’t even error out. Starting it manually (the /etc/ folder, and conf files) works. Just the Debian service has conked out.
Time to switch to CentOS! Much more stable.
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson ky...@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage cha...@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson ky...@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage cha...@charliedrage.com > > > > > > > > > > > > > > >> wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Hey all, been quite a while since the last reply, any updates?
···
On Thursday, April 2, 2015 at 9:57:31 AM UTC-4, Charlie Drage wrote:
Albit a late reply, this fixed the issue within Debian.
I’ve upgrade from 0.60 to 0.17.1 but found the issue still persisted. I again had to edit the init.d file.
Any ideas if this will be fixed in the next release?
On Saturday, December 27, 2014 at 3:20:59 PM UTC-5, John Brand wrote:
Hi,
There is a fix. You need to edit the /etc/init.d/sensu-service file to make it working again. I did find it somewhere, but can’t find it again at the moment.
Change row number 15. service=sensu-$1 to prog=sensu-$1
Then change every declaration of $service to $prog
And then change this part.
if [ “$system” = “debian” ]; then
## source platform specific external scripts
. /lib/lsb/init-functions
[ -r /etc/default/$prog ] && . /etc/default/$prog
and add prog=sensu-$1 to it.
if [ “$system” = “debian” ]; then
## source platform specific external scripts
. /lib/lsb/init-functions
prog=sensu-$1
[ -r /etc/default/$prog ] && . /etc/default/$prog
Afterwards the problem of not being able to start sensu is resolved.
John
Op zaterdag 27 december 2014 14:41:28 UTC+1 schreef Doe John:
Hello,
I have the same issue on Debian Sid, Sensu 0.15 and 0.16
Is there a fix ?
thank you
Le jeudi 13 novembre 2014 18:24:35 UTC+1, John Brand a écrit :
Charlie,
Didi it work?
John
Op zondag 2 november 2014 23:42:12 UTC+1 schreef Charlie Drage:
Yes it is, I’ll try that Sean, thank you!
On Sun, Nov 2, 2014 at 7:42 PM, Sean Porter porte...@gmail.com wrote:
Is this Debian 7? 0.16.0 updated init scripts for Debian fix.
On Nov 2, 2014 7:51 AM, “Charlie Drage” cha...@charliedrage.com wrote:
Hmmm. It doesn’t even error out. Starting it manually (the /etc/ folder, and conf files) works. Just the Debian service has conked out.
Time to switch to CentOS! Much more stable.
On Sun, Nov 2, 2014 at 4:46 PM, Kyle Anderson ky...@xkyle.com wrote:
Well, could be anything, you’ll have to run it manually to see the
stdout/err and see why it cant start.
On Sun, Nov 2, 2014 at 3:21 AM, Charlie Drage cha...@charliedrage.com wrote:
Absolutely nothing. Only logs from a previous service being started, but
none this time when starting.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
On Sun, Nov 2, 2014 at 3:39 AM, Kyle Anderson ky...@xkyle.com wrote:
What does the sensu-client log say?
On Sat, Nov 1, 2014 at 7:37 PM, Charlie Drage cha...@charliedrage.com > > > > > > > > > > > > > > > > >> wrote:
After a node restart, for some odd reason I can not longer start the
sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See 'systemctl status
sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT;
30s
ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited,
status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting
sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process
exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring
framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered
failed
state.
Charlie Drage
GPG [FE8E 8D18] [charliedrage.com/public.key]
Hi Ravi,
Look at /var/log/sensu/sensu-client.log for details (or run systemctl status sensu-client.service’ )
Regards.
@shankerbalan
···
On 17-Nov-2016, at 9:55 PM, ravi.reddy@minjar.com wrote:
On Sunday, November 2, 2014 at 8:07:53 AM UTC+5:30, Charlie Drage wrote:
After a node restart, for some odd reason I can not longer start the sensu-client service. Any ideas?
root@kvm05:~# service sensu-client start
Job for sensu-client.service failed. See ‘systemctl status sensu-client.service’ and ‘journalctl -xn’ for details.
root@kvm05:~# systemctl status sensu-client.service
● sensu-client.service - LSB: Sensu monitoring framework client
Loaded: loaded (/etc/init.d/sensu-client)
Active: failed (Result: exit-code) since Sat 2014-11-01 22:36:26 EDT; 30s ago
Process: 31390 ExecStart=/etc/init.d/sensu-client start (code=exited, status=5)
Nov 01 22:36:26 kvm05 sensu-client[31390]: Starting sensu-service.service:
Nov 01 22:36:26 kvm05 systemd[1]: sensu-client.service: control process exited, code=exited status=5
Nov 01 22:36:26 kvm05 systemd[1]: Failed to start LSB: Sensu monitoring framework client.
Nov 01 22:36:26 kvm05 systemd[1]: Unit sensu-client.service entered failed state.