Aaron Trujillo Posted June 15, 2016 Share Posted June 15, 2016 I am using pulseway to monitor many different machines mostly Linux and windows. The windows service notifications if pretty user friendly, however I am having trouble getting my Linux machines configured to alert me when a service goes down. Can I get some guidance please? I am using Debian Jessie. I am trying to monitor when the Freeswitch service stops I have tried editing the config.xml not sure if I am entering the correct information, however. thanks. Link to comment Share on other sites More sharing options...
Staff Mark Posted June 17, 2016 Staff Share Posted June 17, 2016 The configuration of the services depends on the operating system and the init daemon (UPSTART, SYSVINIT or SYSTEMD). Debian Jessie use SYSTEMD as system and service manager. Try to change DaemonType="UPSTART" to DaemonType="SYSTEMD". Mark Paul 1 Link to comment Share on other sites More sharing options...
Aaron Trujillo Posted June 30, 2016 Author Share Posted June 30, 2016 How can I tell if the service is being monitored on a Linux server without actually killing the service and getting the notification? On a windows machine it clearly states in the system pulseway manger via the monitored services tab... There is no such tab on my Linux system pulseway manger. I have configured my conf file for pusleway to monitor the selected services. Link to comment Share on other sites More sharing options...
Staff Mark Posted July 1, 2016 Staff Share Posted July 1, 2016 Hi Aaron, Can you please open a terminal and type: systemctl status haproxy systemctl status keepalived systemctl status nodejs As well please check that the /home/jenkins is actually a script. (Ex: /usr/bin/tcpd) Mark Link to comment Share on other sites More sharing options...
Aaron Trujillo Posted July 1, 2016 Author Share Posted July 1, 2016 root@GP1-STG1-APPLB1:~# systemctl status haproxy ● haproxy.service - HAProxy Load Balancer Loaded: loaded (/lib/systemd/system/haproxy.service; enabled) Active: active (running) since Fri 2016-07-01 08:17:54 MDT; 8min ago Docs: man:haproxy(1) file:/usr/share/doc/haproxy/configuration.txt.gz Process: 893 ExecStartPre=/usr/sbin/haproxy -f ${CONFIG} -c -q $EXTRAOPTS (code=exited, status=0/SUCCESS) Main PID: 901 (haproxy-systemd) CGroup: /system.slice/haproxy.service ├─901 /usr/sbin/haproxy-systemd-wrapper -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid ├─904 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds └─905 /usr/sbin/haproxy -f /etc/haproxy/haproxy.cfg -p /run/haproxy.pid -Ds Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #1 failed: Resource temporarily unavailable (errno=11) Jul 01 08:17:54 GP1-STG1-APPLB1 haproxy-systemd-wrapper[901]: [ALERT] 182/081754 (904) : sendmsg logger #2 failed: Resource temporarily unavailable (errno=11) root@GP1-STG1-APPLB1:~# systemclt status nodejs -bash: systemclt: command not found root@GP1-STG1-APPLB1:~# systemctl status nodejs ● nodejs.service - Total.Care NodeJs App Loaded: loaded (/etc/systemd/system/nodejs.service; enabled) Active: active (running) since Fri 2016-07-01 08:17:52 MDT; 9min ago Main PID: 568 (node) CGroup: /system.slice/nodejs.service └─568 /usr/bin/node /home/totalcare/app.js Jul 01 08:17:56 GP1-STG1-APPLB1 node[568]: Example app listening on port 3000! ● keepalived.service - LSB: Starts keepalived Loaded: loaded (/etc/init.d/keepalived) Active: active (running) since Fri 2016-07-01 08:17:54 MDT; 8min ago Process: 579 ExecStart=/etc/init.d/keepalived start (code=exited, status=0/SUCCESS) CGroup: /system.slice/keepalived.service ├─887 /usr/sbin/keepalived ├─888 /usr/sbin/keepalived └─889 /usr/sbin/keepalived Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_healthcheckers[888]: Opening file '/etc/keepalived/keepalived.conf'. Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: Configuration is using : 63098 Bytes Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_healthcheckers[888]: Configuration is using : 6229 Bytes Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: Using LinkWatch kernel netlink reflector... Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_healthcheckers[888]: Using LinkWatch kernel netlink reflector... Jul 01 08:17:54 GP1-STG1-APPLB1 keepalived[579]: Starting keepalived: keepalived. Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Script(chk_haproxy) succeeded Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Instance(VI_1) Transition to MASTER STATE Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Instance(VI_1) Received higher prio advert Jul 01 08:17:54 GP1-STG1-APPLB1 Keepalived_vrrp[889]: VRRP_Instance(VI_1) Entering BACKUP STATE Link to comment Share on other sites More sharing options...
Aaron Trujillo Posted July 1, 2016 Author Share Posted July 1, 2016 2 hours ago, Mark said: Hi Aaron,inal and type: systemctl status haproxy systemctl status keepalived systemctl status nodejs It looks like all it needed was a simple reboot to get the service recognized in the manager. I am now able to start and stop services from the manager but when I stop a service I am NOT getting notifications. All other notifications work properly... Any other advice? Link to comment Share on other sites More sharing options...
Staff Mark Posted July 1, 2016 Staff Share Posted July 1, 2016 Great to hear that Aaron! You don't need to restart the machine. Restart the pulseway service only. As for notification when a daemon/process is stopped have a look at: <!--Send a notification when a service has stopped for a number of minutes (between 1 and 120)--> <ServiceStopped Priority="1" Minutes="1" Enabled="true"/> in config.xml. Mark Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now