Error using monit to monitor mosquitto, grafana and influxdb [closed]
Clash Royale CLAN TAG#URR8PPP
up vote
1
down vote
favorite
I've setup monit to monitor Mosquitto, Grafana and Influxdb. However, I'm getting the errors when monit starts up:
root@TB-IOT01:/etc/init.d# monit reload
/etc/monit/monitrc:218: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:219: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:222: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:223: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:226: Program does not exist: '/etc.init.d/grafana-server'
/etc/monit/monitrc:227: Program does not exist: '/etc.init.d/grafana-server'
The files exist in the location specified, can anyone tell me what the problem is please?
File listing below of /etc/init.d :
> root@IOT01:/etc/init.d# ls -l
> -rwxr-xr-x 1 root root 5336 Feb 1 2016 alsa-utils
> -rwxr-xr-x 1 root root 2014 May 29 2017 anacron
> -rwxr-xr-x 1 root root 2401 Jan 23 2017 avahi-daemon
> -rwxr-xr-x 1 root root 2948 Oct 24 2016 bluetooth
> -rwxr-xr-x 1 root root 1232 Apr 7 2017 console-setup.sh
> -rwxr-xr-x 1 root root 3049 May 3 2015 cron
> -rwxr-xr-x 1 root root 2816 Jan 18 2017 cups
> -rwxr-xr-x 1 root root 1961 Jan 19 2017 cups-browsed
> -rwxr-xr-x 1 root root 2813 Apr 5 2017 dbus
> -rwxr-xr-x 1 root root 3033 May 20 2014 gdm3
> -rwxrwxr-x 1 root root 3346 Aug 7 09:57 grafana-server
> -rwxr-xr-x 1 root root 3809 Mar 22 2017 hwclock.sh
> -rwxr-xr-x 1 root root 3635 Oct 25 2016 influxdb
> -rwxr-xr-x 1 root root 1479 May 19 2016 keyboard-setup.sh
> -rwxr-xr-x 1 root root 2044 Dec 26 2016 kmod
> -rwxr-xr-x 1 root root 2241 Apr 26 2017 minissdpd
> -rwxr-xr-x 1 root root 2664 Jan 11 2017 monit
> -rwxr-xr-x 1 root root 3323 Nov 3 2016 mosquitto
> -rwxr-xr-x 1 root root 4597 Sep 16 2016 networking
> -rwxr-xr-x 1 root root 1757 Mar 18 2017 network-manager
> -rwxr-xr-x 1 root root 612 Dec 4 2015 pppd-dns
> -rwxr-xr-x 1 root root 1191 Nov 22 2016 procps
> -rwxr-xr-x 1 root root 2868 Jan 18 2017 rsyslog
> -rwxr-xr-x 1 root root 2330 May 21 2017 saned
> -rwxr-xr-x 1 root root 2117 Jan 9 2017 speech-dispatcher
> -rwxr-xr-x 1 root root 4033 Jun 18 01:08 ssh
> -rwxr-xr-x 1 root root 6087 Jul 5 21:31 udev
> -rwxr-xr-x 1 root root 1391 May 6 2017 unattended-upgrades
> -rwxr-xr-x 1 root root 2757 Nov 23 2016 x11-common
> -rwxr-xr-x 1 root root 7183 Apr 27 2017 xrdp
debian monitoring monit
asked Nov 27 '17 at 11:47
resolver101
1113
closed as unclear what you're asking by Jeff Schaller, Hunter.S.Thompson, sebasth, Stephen Rauch, peterh Nov 27 '17 at 22:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
 |Â
show 3 more comments
up vote
1
down vote
favorite
I've setup monit to monitor Mosquitto, Grafana and Influxdb. However, I'm getting the errors when monit starts up:
root@TB-IOT01:/etc/init.d# monit reload
/etc/monit/monitrc:218: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:219: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:222: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:223: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:226: Program does not exist: '/etc.init.d/grafana-server'
/etc/monit/monitrc:227: Program does not exist: '/etc.init.d/grafana-server'
The files exist in the location specified, can anyone tell me what the problem is please?
File listing below of /etc/init.d :
> root@IOT01:/etc/init.d# ls -l
> -rwxr-xr-x 1 root root 5336 Feb 1 2016 alsa-utils
> -rwxr-xr-x 1 root root 2014 May 29 2017 anacron
> -rwxr-xr-x 1 root root 2401 Jan 23 2017 avahi-daemon
> -rwxr-xr-x 1 root root 2948 Oct 24 2016 bluetooth
> -rwxr-xr-x 1 root root 1232 Apr 7 2017 console-setup.sh
> -rwxr-xr-x 1 root root 3049 May 3 2015 cron
> -rwxr-xr-x 1 root root 2816 Jan 18 2017 cups
> -rwxr-xr-x 1 root root 1961 Jan 19 2017 cups-browsed
> -rwxr-xr-x 1 root root 2813 Apr 5 2017 dbus
> -rwxr-xr-x 1 root root 3033 May 20 2014 gdm3
> -rwxrwxr-x 1 root root 3346 Aug 7 09:57 grafana-server
> -rwxr-xr-x 1 root root 3809 Mar 22 2017 hwclock.sh
> -rwxr-xr-x 1 root root 3635 Oct 25 2016 influxdb
> -rwxr-xr-x 1 root root 1479 May 19 2016 keyboard-setup.sh
> -rwxr-xr-x 1 root root 2044 Dec 26 2016 kmod
> -rwxr-xr-x 1 root root 2241 Apr 26 2017 minissdpd
> -rwxr-xr-x 1 root root 2664 Jan 11 2017 monit
> -rwxr-xr-x 1 root root 3323 Nov 3 2016 mosquitto
> -rwxr-xr-x 1 root root 4597 Sep 16 2016 networking
> -rwxr-xr-x 1 root root 1757 Mar 18 2017 network-manager
> -rwxr-xr-x 1 root root 612 Dec 4 2015 pppd-dns
> -rwxr-xr-x 1 root root 1191 Nov 22 2016 procps
> -rwxr-xr-x 1 root root 2868 Jan 18 2017 rsyslog
> -rwxr-xr-x 1 root root 2330 May 21 2017 saned
> -rwxr-xr-x 1 root root 2117 Jan 9 2017 speech-dispatcher
> -rwxr-xr-x 1 root root 4033 Jun 18 01:08 ssh
> -rwxr-xr-x 1 root root 6087 Jul 5 21:31 udev
> -rwxr-xr-x 1 root root 1391 May 6 2017 unattended-upgrades
> -rwxr-xr-x 1 root root 2757 Nov 23 2016 x11-common
> -rwxr-xr-x 1 root root 7183 Apr 27 2017 xrdp
debian monitoring monit
asked Nov 27 '17 at 11:47
resolver101
1113
closed as unclear what you're asking by Jeff Schaller, Hunter.S.Thompson, sebasth, Stephen Rauch, peterh Nov 27 '17 at 22:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
Please don't post images of text
– Jeff Schaller
Nov 27 '17 at 12:00
1
If you're sure those files exist, perhaps you could show anls -llisting of them? (After you paste the actual monit startup errors)
– Jeff Schaller
Nov 27 '17 at 12:01
apologies for the images, i only had vmware console access and screen shot was the best way i could think to get the issue across. Anyway, i now have ssh and added the relevant details.
– resolver101
Nov 29 '17 at 11:07
1
Is that an actual typo in the monitrc of /etc.init.d instead of /etc/init.d ?
– Jeff Schaller
Nov 29 '17 at 11:40
Yeah its a typo, thanks. I dont know how many times I've looked at that. Thank you, when I run monitrc it now starts without error. How do i accept a answer on this. Thanks again
– resolver101
Nov 29 '17 at 11:49
 |Â
show 3 more comments
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I've setup monit to monitor Mosquitto, Grafana and Influxdb. However, I'm getting the errors when monit starts up:
root@TB-IOT01:/etc/init.d# monit reload
/etc/monit/monitrc:218: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:219: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:222: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:223: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:226: Program does not exist: '/etc.init.d/grafana-server'
/etc/monit/monitrc:227: Program does not exist: '/etc.init.d/grafana-server'
The files exist in the location specified, can anyone tell me what the problem is please?
File listing below of /etc/init.d :
> root@IOT01:/etc/init.d# ls -l
> -rwxr-xr-x 1 root root 5336 Feb 1 2016 alsa-utils
> -rwxr-xr-x 1 root root 2014 May 29 2017 anacron
> -rwxr-xr-x 1 root root 2401 Jan 23 2017 avahi-daemon
> -rwxr-xr-x 1 root root 2948 Oct 24 2016 bluetooth
> -rwxr-xr-x 1 root root 1232 Apr 7 2017 console-setup.sh
> -rwxr-xr-x 1 root root 3049 May 3 2015 cron
> -rwxr-xr-x 1 root root 2816 Jan 18 2017 cups
> -rwxr-xr-x 1 root root 1961 Jan 19 2017 cups-browsed
> -rwxr-xr-x 1 root root 2813 Apr 5 2017 dbus
> -rwxr-xr-x 1 root root 3033 May 20 2014 gdm3
> -rwxrwxr-x 1 root root 3346 Aug 7 09:57 grafana-server
> -rwxr-xr-x 1 root root 3809 Mar 22 2017 hwclock.sh
> -rwxr-xr-x 1 root root 3635 Oct 25 2016 influxdb
> -rwxr-xr-x 1 root root 1479 May 19 2016 keyboard-setup.sh
> -rwxr-xr-x 1 root root 2044 Dec 26 2016 kmod
> -rwxr-xr-x 1 root root 2241 Apr 26 2017 minissdpd
> -rwxr-xr-x 1 root root 2664 Jan 11 2017 monit
> -rwxr-xr-x 1 root root 3323 Nov 3 2016 mosquitto
> -rwxr-xr-x 1 root root 4597 Sep 16 2016 networking
> -rwxr-xr-x 1 root root 1757 Mar 18 2017 network-manager
> -rwxr-xr-x 1 root root 612 Dec 4 2015 pppd-dns
> -rwxr-xr-x 1 root root 1191 Nov 22 2016 procps
> -rwxr-xr-x 1 root root 2868 Jan 18 2017 rsyslog
> -rwxr-xr-x 1 root root 2330 May 21 2017 saned
> -rwxr-xr-x 1 root root 2117 Jan 9 2017 speech-dispatcher
> -rwxr-xr-x 1 root root 4033 Jun 18 01:08 ssh
> -rwxr-xr-x 1 root root 6087 Jul 5 21:31 udev
> -rwxr-xr-x 1 root root 1391 May 6 2017 unattended-upgrades
> -rwxr-xr-x 1 root root 2757 Nov 23 2016 x11-common
> -rwxr-xr-x 1 root root 7183 Apr 27 2017 xrdp
debian monitoring monit
asked Nov 27 '17 at 11:47
resolver101
1113
I've setup monit to monitor Mosquitto, Grafana and Influxdb. However, I'm getting the errors when monit starts up:
root@TB-IOT01:/etc/init.d# monit reload
/etc/monit/monitrc:218: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:219: Program does not exist: '/etc.init.d/mosquitto'
/etc/monit/monitrc:222: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:223: Program does not exist: '/etc.init.d/influxdb'
/etc/monit/monitrc:226: Program does not exist: '/etc.init.d/grafana-server'
/etc/monit/monitrc:227: Program does not exist: '/etc.init.d/grafana-server'
The files exist in the location specified, can anyone tell me what the problem is please?
File listing below of /etc/init.d :
> root@IOT01:/etc/init.d# ls -l
> -rwxr-xr-x 1 root root 5336 Feb 1 2016 alsa-utils
> -rwxr-xr-x 1 root root 2014 May 29 2017 anacron
> -rwxr-xr-x 1 root root 2401 Jan 23 2017 avahi-daemon
> -rwxr-xr-x 1 root root 2948 Oct 24 2016 bluetooth
> -rwxr-xr-x 1 root root 1232 Apr 7 2017 console-setup.sh
> -rwxr-xr-x 1 root root 3049 May 3 2015 cron
> -rwxr-xr-x 1 root root 2816 Jan 18 2017 cups
> -rwxr-xr-x 1 root root 1961 Jan 19 2017 cups-browsed
> -rwxr-xr-x 1 root root 2813 Apr 5 2017 dbus
> -rwxr-xr-x 1 root root 3033 May 20 2014 gdm3
> -rwxrwxr-x 1 root root 3346 Aug 7 09:57 grafana-server
> -rwxr-xr-x 1 root root 3809 Mar 22 2017 hwclock.sh
> -rwxr-xr-x 1 root root 3635 Oct 25 2016 influxdb
> -rwxr-xr-x 1 root root 1479 May 19 2016 keyboard-setup.sh
> -rwxr-xr-x 1 root root 2044 Dec 26 2016 kmod
> -rwxr-xr-x 1 root root 2241 Apr 26 2017 minissdpd
> -rwxr-xr-x 1 root root 2664 Jan 11 2017 monit
> -rwxr-xr-x 1 root root 3323 Nov 3 2016 mosquitto
> -rwxr-xr-x 1 root root 4597 Sep 16 2016 networking
> -rwxr-xr-x 1 root root 1757 Mar 18 2017 network-manager
> -rwxr-xr-x 1 root root 612 Dec 4 2015 pppd-dns
> -rwxr-xr-x 1 root root 1191 Nov 22 2016 procps
> -rwxr-xr-x 1 root root 2868 Jan 18 2017 rsyslog
> -rwxr-xr-x 1 root root 2330 May 21 2017 saned
> -rwxr-xr-x 1 root root 2117 Jan 9 2017 speech-dispatcher
> -rwxr-xr-x 1 root root 4033 Jun 18 01:08 ssh
> -rwxr-xr-x 1 root root 6087 Jul 5 21:31 udev
> -rwxr-xr-x 1 root root 1391 May 6 2017 unattended-upgrades
> -rwxr-xr-x 1 root root 2757 Nov 23 2016 x11-common
> -rwxr-xr-x 1 root root 7183 Apr 27 2017 xrdp
debian monitoring monit
asked Nov 27 '17 at 11:47
resolver101
1113
edited Nov 29 '17 at 11:06
asked Nov 27 '17 at 11:47
resolver101
1113
asked Nov 27 '17 at 11:47
resolver101
1113
asked Nov 27 '17 at 11:47
resolver101
1113
1113
closed as unclear what you're asking by Jeff Schaller, Hunter.S.Thompson, sebasth, Stephen Rauch, peterh Nov 27 '17 at 22:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
closed as unclear what you're asking by Jeff Schaller, Hunter.S.Thompson, sebasth, Stephen Rauch, peterh Nov 27 '17 at 22:41
Please clarify your specific problem or add additional details to highlight exactly what you need. As it's currently written, it’s hard to tell exactly what you're asking. See the How to Ask page for help clarifying this question. If this question can be reworded to fit the rules in the help center, please edit the question.
1
Please don't post images of text
– Jeff Schaller
Nov 27 '17 at 12:00
1
If you're sure those files exist, perhaps you could show anls -llisting of them? (After you paste the actual monit startup errors)
– Jeff Schaller
Nov 27 '17 at 12:01
apologies for the images, i only had vmware console access and screen shot was the best way i could think to get the issue across. Anyway, i now have ssh and added the relevant details.
– resolver101
Nov 29 '17 at 11:07
1
Is that an actual typo in the monitrc of /etc.init.d instead of /etc/init.d ?
– Jeff Schaller
Nov 29 '17 at 11:40
Yeah its a typo, thanks. I dont know how many times I've looked at that. Thank you, when I run monitrc it now starts without error. How do i accept a answer on this. Thanks again
– resolver101
Nov 29 '17 at 11:49
 |Â
show 3 more comments
1
Please don't post images of text
– Jeff Schaller
Nov 27 '17 at 12:00
1
If you're sure those files exist, perhaps you could show anls -llisting of them? (After you paste the actual monit startup errors)
– Jeff Schaller
Nov 27 '17 at 12:01
apologies for the images, i only had vmware console access and screen shot was the best way i could think to get the issue across. Anyway, i now have ssh and added the relevant details.
– resolver101
Nov 29 '17 at 11:07
1
Is that an actual typo in the monitrc of /etc.init.d instead of /etc/init.d ?
– Jeff Schaller
Nov 29 '17 at 11:40
Yeah its a typo, thanks. I dont know how many times I've looked at that. Thank you, when I run monitrc it now starts without error. How do i accept a answer on this. Thanks again
– resolver101
Nov 29 '17 at 11:49
1
1
Please don't post images of text
– Jeff Schaller
Nov 27 '17 at 12:00
Please don't post images of text
– Jeff Schaller
Nov 27 '17 at 12:00
1
1
If you're sure those files exist, perhaps you could show an
ls -l listing of them? (After you paste the actual monit startup errors)– Jeff Schaller
Nov 27 '17 at 12:01
If you're sure those files exist, perhaps you could show an
ls -l listing of them? (After you paste the actual monit startup errors)– Jeff Schaller
Nov 27 '17 at 12:01
apologies for the images, i only had vmware console access and screen shot was the best way i could think to get the issue across. Anyway, i now have ssh and added the relevant details.
– resolver101
Nov 29 '17 at 11:07
apologies for the images, i only had vmware console access and screen shot was the best way i could think to get the issue across. Anyway, i now have ssh and added the relevant details.
– resolver101
Nov 29 '17 at 11:07
1
1
Is that an actual typo in the monitrc of /etc.init.d instead of /etc/init.d ?
– Jeff Schaller
Nov 29 '17 at 11:40
Is that an actual typo in the monitrc of /etc.init.d instead of /etc/init.d ?
– Jeff Schaller
Nov 29 '17 at 11:40
Yeah its a typo, thanks. I dont know how many times I've looked at that. Thank you, when I run monitrc it now starts without error. How do i accept a answer on this. Thanks again
– resolver101
Nov 29 '17 at 11:49
Yeah its a typo, thanks. I dont know how many times I've looked at that. Thank you, when I run monitrc it now starts without error. How do i accept a answer on this. Thanks again
– resolver101
Nov 29 '17 at 11:49
 |Â
show 3 more comments
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Please don't post images of text
– Jeff Schaller
Nov 27 '17 at 12:00
1
If you're sure those files exist, perhaps you could show an
ls -llisting of them? (After you paste the actual monit startup errors)– Jeff Schaller
Nov 27 '17 at 12:01
apologies for the images, i only had vmware console access and screen shot was the best way i could think to get the issue across. Anyway, i now have ssh and added the relevant details.
– resolver101
Nov 29 '17 at 11:07
1
Is that an actual typo in the monitrc of /etc.init.d instead of /etc/init.d ?
– Jeff Schaller
Nov 29 '17 at 11:40
Yeah its a typo, thanks. I dont know how many times I've looked at that. Thank you, when I run monitrc it now starts without error. How do i accept a answer on this. Thanks again
– resolver101
Nov 29 '17 at 11:49