Postfix: check process postfix with pidfile /var/spool/postfix/pid/master.pid If failed port 22 protocol ssh then restart Sshd: check process sshd with pidfile /var/run/sshd.pid Stop program = "/usr/bin/systemctl stop rvice" Start program = "/usr/bin/systemctl start rvice" Stop program = "/usr/bin/systemctl stop rvice"ĭnsmasq: check process dnsmasq with pidfile /var/run/dnsmasq.pid Mariadb: check process mysql with pidfile "/var/run/mariadb/mariadb.pid" Httpd: check process apache with pidfile "/var/run/httpd/httpd.pid" Openssl x509 -subject -dates -fingerprint -noout -in /var/certs/monit.pemĬonfiguration Examples Amahi 8 or Greater Openssl req -new -x509 -days 365 -nodes -config.
To create a new certificate, do the following steps as root user ( Ubuntu NOTE: prefix commands with sudo except the second openssl requires the actual root user environment sudo su -): Message: This is an $ACTION: $DESCRIPTION, tested remotely from $HOST }Įdit monitrc and add below set httpd port 2812 and (line 116):Ĭreate a directory for the certs, then follow "Create New Certificate" guidance:Ī default certificate is installed by the Amahi application (Ubuntu). NOTE: Replace "MYUSER" and "MYPASSWORD" with your Gmail user name and password.Įnable email notifications by editing monitrc and adding the following lines (Change as needed to match your system):Įdit monitrc and add this text (modify as needed): You can do it in Monit directly by adding the following to monitrc: The Gmail as Relay tutorial is one option.
This will only work if you have set up your HDA to send emails. I have also flushed the iptables both on my Ubuntu machine, and also on the vagrant virtualmachine with Metron.Edit monitrc and change localhost.localdomain to match your system: How I can get around this problem? I have tried forwarding the ports from virtualBox virtual machine so that port 21 are forwarded,but this did not solve this problem. are installed, but very surprisingly the ports 21 which are of Monit and Kibana are only open in the vagrant virtual machine, they are not open from outside the virtual machine!! I somehow can read from Monit web interface from inside virtual machine, but when I open the port 2182 from outside virtual machine by accessing "node1:2182", the port reports as closed (Note: nmap -A, reports the port is closed). I can now bring up the Metron system, and I can see that Kibana, Monit, etc. Next, I run the "./run_ansible_role metron ", and after installation of extensible software,and installation of elastic-search and Kibana and everything else which Metron needs during installation, it came up with a system which had Kibana and Monit installed. After running "vagrant up", I ended up with a Metron system which had only "Ambari" with all the servers installed, but there was no sign of Metron.
MONIT WEB PORT HOW TO
The vagrant machine with Metron is installed in a box just like described in the README of the Metron how to install Metron quickdev configuration.
I am using the Vagrant with the VirtualBox virtual machine on Ubuntu Linux. Could anyone point out what may be the cause of this ? I have also checked the Monit config file and it seems to be configured correctly, is there a configuration for Kibana which I have to double check? Also iptables is flushed on both the vagrant virtualmachine and also on the host server. What has happened that these ports are not accessible outside the virtualmachine ? I want to see these ports which are ofcourse the Monit and Kibana interfaces so I can control the server on the web interface. The strange thing is that if I access the ports 50 on node1 from within the virtual machine, I can see that the ports are running and I can even telnet to these ports. I mean that if I do outside the virtualmachine, I can see the Ambari view, but if I do or from the outside on the host machine, I cannot see these interfaces. The problem is as follows that while I am sure Ambari, Monit and Metron are installed and the various services are functional, I can just see the Ambari port 8080 outside the virtual machine. I have been able to finally run the Metron inside the vagrant virtual machine in the quickdev configuration.
0 kommentar(er)
