Waiting for Database Startup

[sbarrera]

Hi,
I´m getting this problem while loading the Log Server.

Captura1.PNG

* The logstash.service status is excited and display me this:

Code: Select all

Logstash Daemon● logstash.service - LSB: Logstash
   Loaded: loaded (/etc/rc.d/init.d/logstash; bad; vendor preset: disabled)
   Active: active (exited) since Thu 2018-04-26 07:51:48 UTC; 2min 39s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 7280 ExecStop=/etc/rc.d/init.d/logstash stop (code=exited, status=0/SUCCESS)
  Process: 7291 ExecStart=/etc/rc.d/init.d/logstash start (code=exited, status=0/SUCCESS)

Apr 26 07:51:47 ip-172-31-1-24.eu-west-1.compute.internal systemd[1]: Starting LSB: Logstash...
Apr 26 07:51:47 ip-172-31-1-24.eu-west-1.compute.internal runuser[7301]: pam_unix(runuser:session): session opened for user nagios by (uid=0)
Apr 26 07:51:48 ip-172-31-1-24.eu-west-1.compute.internal logstash[7291]: Starting Logstash Daemon: [  OK  ]
Apr 26 07:51:48 ip-172-31-1-24.eu-west-1.compute.internal systemd[1]: Started LSB: Logstash.
Apr 26 07:52:14 ip-172-31-1-24.eu-west-1.compute.internal runuser[7301]: pam_unix(runuser:session): session closed for user nagios

* The elasticsearch.service status is excited too:

Code: Select all

 elasticsearch.service - LSB: This service manages the elasticsearch daemon
   Loaded: loaded (/etc/rc.d/init.d/elasticsearch; bad; vendor preset: disabled)
   Active: active (exited) since Thu 2018-04-26 07:51:36 UTC; 10min ago
     Docs: man:systemd-sysv-generator(8)
  Process: 7153 ExecStop=/etc/rc.d/init.d/elasticsearch stop (code=exited, status=0/SUCCESS)
  Process: 3138 ExecReload=/etc/rc.d/init.d/elasticsearch reload (code=exited, status=7)
  Process: 7163 ExecStart=/etc/rc.d/init.d/elasticsearch start (code=exited, status=0/SUCCESS)

Apr 26 07:51:36 ip-172-31-1-24.eu-west-1.compute.internal systemd[1]: Unit elasticsearch.service entered failed state.
Apr 26 07:51:36 ip-172-31-1-24.eu-west-1.compute.internal systemd[1]: elasticsearch.service failed.
Apr 26 07:51:36 ip-172-31-1-24.eu-west-1.compute.internal systemd[1]: Starting LSB: This service manages the elasticsearch daemon...
Apr 26 07:51:36 ip-172-31-1-24.eu-west-1.compute.internal runuser[7180]: pam_unix(runuser:session): session opened for user nagios by (uid=0)
Apr 26 07:51:36 ip-172-31-1-24.eu-west-1.compute.internal elasticsearch[7163]: Starting elasticsearch: [  OK  ]
Apr 26 07:51:36 ip-172-31-1-24.eu-west-1.compute.internal systemd[1]: Started LSB: This service manages the elasticsearch daemon.

If someone could help me about this, would be appreciate.

[cdienger]

How much free space and ram are on the machine:

df -h
free -m

Is this an install of the OVA? If so, the default memory allocation(2GB) can be too small and can/should be increased.

[sbarrera]

This is a free machine from AWS.So maybe is it the free space? or is it the ram?.

Code: Select all

[ec2-user@ip-172-31-1-24 ~]$ df -h
Filesystem      Size  Used Avail Use% Mounted on
/dev/xvda2       10G  3.0G  7.1G  30% /
devtmpfs        474M     0  474M   0% /dev
tmpfs           496M     0  496M   0% /dev/shm
tmpfs           496M   57M  439M  12% /run
tmpfs           496M     0  496M   0% /sys/fs/cgroup
tmpfs           100M     0  100M   0% /run/user/1001
tmpfs           100M     0  100M   0% /run/user/1000

Code: Select all

[ec2-user@ip-172-31-1-24 ~]$ free -m
              total        used        free      shared  buff/cache   available
Mem:            990         163         432          56         394         612
Swap:             0           0           0

[mcapra]

I would start with adding more memory to the machine. The system requirements for Nagios Log Server list 2GB as the minimum.

[tmcdonald]

Oh yeah, definitely the RAM. 2GB minimum, but 4GB is what I usually go with to be safe.

[sbarrera]

Is it valid to do it whit swap? because if not i need to pay for the increase of ram. It´s only for testing if it could fit into my boss enterprise.You know?.

[mcapra]

If this is a prototyping machine with incredibly low load, you could probably get away with using swap.

However, Elasticsearch really super duper performs poorly when segments are held in swap. Swap in any sort of production environment will keep ElasticSearch running quite sluggishly if at all.

Network restrictions notwithstanding, rolling a simple lab machine on your local box with the official Nagios Log Server OVF and VirtualBox is probably a better option for reviewing the product.

[tmcdonald]

I definitely have to agree with @mcapra on using your workstation. That way you can allocate more RAM (most likely) without having to have that conversation with your boss.

[sbarrera]

Ok thank you all for the support the ticket can be close.