Support Questions
Find answers, ask questions, and share your expertise

unable to connect to node1:2812

unable to connect to node1:2812

I did a successful deployment of metron(I guess at least) following is the screenshot after sanity check

11330-sanity-passed.png

however, I am unable to connect to node1:2812.

results of monit commands:

sudo monit status
The Monit daemon 5.14 uptime: 14m 

Process 'snort'
  status                            Running
  monitoring status                 Monitored
  pid                               4282
  parent pid                        1
  uid                               1003
  effective uid                     1003
  gid                               503
  uptime                            8m 
  children                          0
  memory                            118.9 MB
  memory total                      118.9 MB
  memory percent                    1.5%
  memory percent total              1.5%
  cpu percent                       0.0%
  cpu percent total                 0.0%
  data collected                    Thu, 12 Jan 2017 04:02:06

Process 'snort-producer'
  status                            Running
  monitoring status                 Monitored
  pid                               4287
  parent pid                        1
  uid                               0
  effective uid                     0
  gid                               0
  uptime                            8m 
  children                          2
  memory                            1.3 MB
  memory total                      117.2 MB
  memory percent                    0.0%
  memory percent total              1.4%
  cpu percent                       0.0%
  cpu percent total                 0.5%
  data collected                    Thu, 12 Jan 2017 04:02:06

Process 'pcap-service'
  status                            Running
  monitoring status                 Monitored
  pid                               4383
  parent pid                        1
  uid                               0
  effective uid                     0
  gid                               0
  uptime                            8m 
  children                          0
  memory                            299.2 MB
  memory total                      299.2 MB
  memory percent                    3.8%
  memory percent total              3.8%
  cpu percent                       0.0%
  cpu percent total                 0.0%
  data collected                    Thu, 12 Jan 2017 04:02:06

Process 'pcap-replay'
  status                            Running
  monitoring status                 Monitored
  pid                               4531
  parent pid                        1
  uid                               0
  effective uid                     0
  gid                               0
  uptime                            8m 
  children                          0
  memory                            5.6 MB
  memory total                      5.6 MB
  memory percent                    0.0%
  memory percent total              0.0%
  cpu percent                       16.3%
  cpu percent total                 16.3%
  data collected                    Thu, 12 Jan 2017 04:02:06

Program 'pcap-parser'
  status                            Not monitored
  monitoring status                 Not monitored
  data collected                    Thu, 12 Jan 2017 03:53:08

Program 'yaf-parser'
  status                            Not monitored
  monitoring status                 Not monitored
  data collected                    Thu, 12 Jan 2017 03:53:08

Program 'bro-parser'
  status                            Execution failed
  monitoring status                 Monitored
  last started                      Thu, 12 Jan 2017 04:02:06
  last exit value                   1
  data collected                    Thu, 12 Jan 2017 04:03:44

Program 'snort-parser'
  status                            Execution failed
  monitoring status                 Monitored
  last started                      Thu, 12 Jan 2017 04:03:44
  last exit value                   1
  data collected                    Thu, 12 Jan 2017 04:05:20

Process 'mysql'
  status                            Running
  monitoring status                 Monitored
  pid                               1761
  parent pid                        1547
  uid                               27
  effective uid                     27
  gid                               27
  uptime                            13m 
  children                          0
  memory                            152.6 MB
  memory total                      152.6 MB
  memory percent                    1.9%
  memory percent total              1.9%
  cpu percent                       0.0%
  cpu percent total                 0.0%
  data collected                    Thu, 12 Jan 2017 04:05:21

Process 'kibana'
  status                            Running
  monitoring status                 Monitored
  pid                               4580
  parent pid                        1
  uid                               496
  effective uid                     496
  gid                               0
  uptime                            12m 
  children                          0
  memory                            101.4 MB
  memory total                      101.4 MB
  memory percent                    1.2%
  memory percent total              1.2%
  cpu percent                       0.2%
  cpu percent total                 0.2%
  data collected                    Thu, 12 Jan 2017 04:05:21

Program 'indexing'
  status                            Execution failed
  monitoring status                 Monitored
  last started                      Thu, 12 Jan 2017 04:05:21
  last exit value                   1
  data collected                    Thu, 12 Jan 2017 04:06:48

Program 'enrichment'
  status                            Execution failed
  monitoring status                 Monitored
  last started                      Thu, 12 Jan 2017 04:06:48
  last exit value                   1
  data collected                    Thu, 12 Jan 2017 04:07:55

Process 'elasticsearch'
  status                            Running
  monitoring status                 Monitored
  pid                               4740
  parent pid                        1
  uid                               497
  effective uid                     497
  gid                               492
  uptime                            14m 
  children                          0
  memory                            282.5 MB
  memory total                      282.5 MB
  memory percent                    3.5%
  memory percent total              3.5%
  cpu percent                       0.5%
  cpu percent total                 0.5%
  data collected                    Thu, 12 Jan 2017 04:07:56

Process 'bro'
  status                            Running
  monitoring status                 Monitored
  pid                               5242
  parent pid                        5236
  uid                               0
  effective uid                     0
  gid                               0
  uptime                            14m 
  children                          1
  memory                            59.0 MB
  memory total                      98.2 MB
  memory percent                    0.7%
  memory percent total              1.2%
  cpu percent                       4.2%
  cpu percent total                 4.2%
  data collected                    Thu, 12 Jan 2017 04:07:56

System 'node1'
  status                            Not monitored
  monitoring status                 Not monitored
  data collected                    Thu, 12 Jan 2017 03:53:08

[vagrant@node1 ~]$ sudo service monit status
monit (pid  4232) is running...
[vagrant@node1 ~]$ sudo services monit restart
sudo: services: command not found
[vagrant@node1 ~]$ sudo service monit restart
Shutting down monit:                                       [  OK  ]
Starting monit:                                            [  OK  ]

Still, I am getting unable to connect when I put node1:2812 in firefox, any suggestion would be helpful, Thanks!

2 REPLIES 2

Re: unable to connect to node1:2812

Explorer

Hi,

Can you connect to port node1:5000 which is "Kibana" ? I have a similar problem which I cannot connect to port 2182 and port 5000. You probably know port 2182 is the web interface for Monit which is a control interface to several servers, can you run Monit from inside your vagrant virtualBox and confirm that it is running ? You can run "monit status" or something like that and see the list of running servers managed by monit.

Re: unable to connect to node1:2812

@Maziar Tasbihi

Hi, thanks actually I could access the monit from CLI but browser was not working. I commented

#127.0.0.1      node1   node1

in my /etc/hosts in node1 and it started working, thanks to @Michael Young for his POST