Building ELK on CentOS 7

[JaredBusch]

You should at least tell the user that you are asking for the kibana password.

htpasswd -c /etc/nginx/htpasswd.users kibanauser

[JaredBusch]

I had this error.

[JaredBusch]

Looks like maybe you forgot to start firewalld?

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   814  100   814    0     0   1370      0 --:--:-- --:--:-- --:--:--  1372
{
  "acknowledged" : true
}
FirewallD is not running
FirewallD is not running
[root@elk ~]# yum install firewalld
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirror.oss.ou.edu
 * epel: fedora-epel.mirror.lstn.net
 * extras: centos.mirrors.wvstateu.edu
 * updates: centos.mirrors.wvstateu.edu
Package firewalld-0.3.9-14.el7.noarch already installed and latest version
Nothing to do
[root@elk ~]# systemctl start firewalld
[root@elk ~]# systemctl status firewalld
● firewalld.service - firewalld - dynamic firewall daemon
   Loaded: loaded (/usr/lib/systemd/system/firewalld.service; enabled; vendor preset: enabled)
   Active: active (running) since Tue 2016-02-23 23:55:11 CST; 14s ago
 Main PID: 11482 (firewalld)
   CGroup: /system.slice/firewalld.service
           └─11482 /usr/bin/python -Es /usr/sbin/firewalld --nofork --nopid

Feb 23 23:55:09 elk systemd[1]: Starting firewalld - dynamic firewall daemon...
Feb 23 23:55:11 elk systemd[1]: Started firewalld - dynamic firewall daemon.
[root@elk ~]#

[JaredBusch]

Yeah, you set it to install, but you never start or enable it.

[JaredBusch]

Line 109 needs commented out.

add this right after the yum install to fix the firewall.

yum -y install wget firewalld epel-release
systemctl enable firewalld
systemctl start firewalld
yum -y install nginx httpd-tools unzip

I would just remove line 109 it serves no purpose.

Edit: Some dumbass forgot to snapshot the image so he could repeat the install...

[JaredBusch]

Why lock out with .htaccess? There is no hint what is needed to log in here.

I hate this level of authentication.

Using kibanauser and the password I chose, results in Kibana setup.

[scottalanmiller]

@JaredBusch said:

@scottalanmiller so what do you setup your disk partitioning like in CentOS 7?

If I'm doing this for product, I do 20GB for the OS and 200GB+ on a second VHD for the data. I put it all under LVM and make a XFS filesystem on the secondary mount and mount it to data and make a symlink for the Elasticsearch database directory into there.

[scottalanmiller]

@JaredBusch said:

Why lock out with .htaccess? There is no hint what is needed to log in here.

It's how Digital Ocean does it as well. Kibana doesn't have a built in authentication scheme that I know of. HTAccess is very simple for someone to just get started.

[scottalanmiller]

And simple to remove when you want to move to something else.

[scottalanmiller]

@JaredBusch said:

Line 109 needs commented out.

add this right after the yum install to fix the firewall.

yum -y install wget firewalld epel-release
systemctl enable firewalld
systemctl start firewalld
yum -y install nginx httpd-tools unzip

I would just remove line 109 it serves no purpose.

Edit: Some dumbass forgot to snapshot the image so he could repeat the install...

Thanks. That was formatting I had originally put in before scripting it.

[scottalanmiller]

@JaredBusch said:

Looks like maybe you forgot to start firewalld?

Fixed

[JaredBusch]

@scottalanmiller said:

@JaredBusch said:

@scottalanmiller so what do you setup your disk partitioning like in CentOS 7?

If I'm doing this for product, I do 20GB for the OS and 200GB+ on a second VHD for the data. I put it all under LVM and make a XFS filesystem on the secondary mount and mount it to data and make a symlink for the Elasticsearch database directory into there.

SO this mean you need to make one of your linux admin setrups on drive settings because that is not what CentOS does by dfault.

[Dashrender]

@JaredBusch said:

@scottalanmiller said:

@JaredBusch said:

@scottalanmiller so what do you setup your disk partitioning like in CentOS 7?

If I'm doing this for product, I do 20GB for the OS and 200GB+ on a second VHD for the data. I put it all under LVM and make a XFS filesystem on the secondary mount and mount it to data and make a symlink for the Elasticsearch database directory into there.

SO this mean you need to make one of your linux admin setrups on drive settings because that is not what CentOS does by dfault.

Would CentOS do what Scott does if you had two drives you provide CentOS to use? i.e. a 20 GB and a 200+ GB one? Would CentOS install the OS and everything fully on the 20, and then just mount the 200 on some point?

[JaredBusch]

@Dashrender said:

@JaredBusch said:

@scottalanmiller said:

@JaredBusch said:

@scottalanmiller so what do you setup your disk partitioning like in CentOS 7?

If I'm doing this for product, I do 20GB for the OS and 200GB+ on a second VHD for the data. I put it all under LVM and make a XFS filesystem on the secondary mount and mount it to data and make a symlink for the Elasticsearch database directory into there.

SO this mean you need to make one of your linux admin setrups on drive settings because that is not what CentOS does by dfault.

Would CentOS do what Scott does if you had two drives you provide CentOS to use? i.e. a 20 GB and a 200+ GB one? Would CentOS install the OS and everything fully on the 20, and then just mount the 200 on some point?

Than answer is not by default. It tries to make it's own magic.

You can see here I created a 20gb and a 200GB vhdx and told the install to handle it all for me.

Guess what, you still end up with a 50GB and a 170GB partitions scheme

[root@elk ~]# df -h
Filesystem                   Size  Used Avail Use% Mounted on
/dev/mapper/centos_elk-root   50G  882M   50G   2% /
devtmpfs                     906M     0  906M   0% /dev
tmpfs                        916M     0  916M   0% /dev/shm
tmpfs                        916M  8.3M  907M   1% /run
tmpfs                        916M     0  916M   0% /sys/fs/cgroup
/dev/sda2                    494M   99M  395M  21% /boot
/dev/sda1                    200M  9.5M  191M   5% /boot/efi
/dev/mapper/centos_elk-home  168G   33M  168G   1% /home
tmpfs                        184M     0  184M   0% /run/user/0
[root@elk ~]#

[JaredBusch]

CentOS 7 has a thing for 50GB root mounts.

[scottalanmiller]

Yeah, the defaults suck a bit.

[JaredBusch]

@scottalanmiller Why are you using Oracle's Java SDK and not just java from the repo?

I had read in another write up on the install that it works fine even if it is not the "official" method.

[scottalanmiller]

@JaredBusch said:

@scottalanmiller Why are you using Oracle's Java SDK and not just java from the repo?

I had read in another write up on the install that it works fine even if it is not the "official" method.

Even if it "works", Elasticsearch tests against and only officially supports the Oracle one. Just because I can get the OpenJDK to work, I'd hate to have it be buggy or problematic for someone down the line because I used one that wasn't tested against.

[JaredBusch]

@scottalanmiller said:

@JaredBusch said:

@scottalanmiller Why are you using Oracle's Java SDK and not just java from the repo?

I had read in another write up on the install that it works fine even if it is not the "official" method.

Even if it "works", Elasticsearch tests against and only officially supports the Oracle one. Just because I can get the OpenJDK to work, I'd hate to have it be buggy or problematic for someone down the line because I used one that wasn't tested against.

I am not a fan of Oracle when it comes to Java

[JaredBusch]

@scottalanmiller

You hardcoded a DNS name in that script...

openssl req -subj '/CN=elk.lab.ntg.co/' -x509 -days 3650 -batch -nodes -newkey rsa:2048 -keyout private/logstash-forwarder.key -out certs/logstash-forwarder.crt

You also used a different port here for logstash than in the logstash forwarder example.

cat > /etc/logstash/conf.d/02-beats-input.conf <<EOF
input {
  beats {
    port => 5044
    ssl => true
    ssl_certificate => "/etc/pki/tls/certs/logstash-forwarder.crt"
    ssl_key => "/etc/pki/tls/private/logstash-forwarder.key"
  }
}
EOF

You used 5000 in that other post.