Question - Issue installing LME

[Bwshort1]

I have run through the install guide for installing LME.
Currently on step 3 - Installing Database (Easy)
When running the commands:

Install Git client to be able to clone the LME repository

sudo apt update
sudo apt install git -y

download a copy of the LME files

sudo git clone https://github.com/ukncsc/lme.git /opt/lme/

Change to the lme directory for the Linux server files

cd /opt/lme/Chapter\ 3\ Files/

execute script with root privileges

sudo ./deploy.sh install

The installation keeps hanging on "Waiting for elasticsearch to be ready"

Here is my screenshot:
ncsclme@lee:$ clear
ncsclme@lee:$ cd /opt/lme/Chapter\ 3\ Files/
ncsclme@lee:/opt/lme/Chapter 3 Files$ sudo ./deploy.sh install
[sudo] password for ncsclme:
[x] Installing prerequisites
Reading package lists...
Building dependency tree...
Reading state information...
net-tools is already the newest version (1.60+git20161116.90da8a0-1ubuntu1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Enter the IP that winlogbeat will use to communicate with this box: 192.168.0.16
Enter the DNS name that winlogbeat uses to communicate with this box: lee
[x] Configuring winlogbeat config and certificates to use 192.168.0.16 as the IP and lee as the DNS
This OS was detected as: ubuntu
[x] Configuring Auto Updates
Reading package lists...
Building dependency tree...
Reading state information...
unattended-upgrades is already the newest version (1.1ubuntu1.18.04.12).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
grep: grep: No such file or directory
grep: APT::Periodic::Update-Package-Lists "1";: No such file or directory
grep: grep: No such file or directory
grep: APT::Periodic::Unattended-Upgrade "1";: No such file or directory
grep: grep: No such file or directory
grep: APT::Periodic::Download-Upgradeable-Packages "1";: No such file or directory
This script will use self signed certificates for communication and encryption, Do you want to continue with self signed certificates? ([y]es/[n]o): y
mkdir: cannot create directory ‘certs’: File exists
[x] making root CA
Generating RSA private key, 4096 bit long modulus (2 primes)
.................................................................................++++
.......................................................++++
e is 65537 (0x010001)
Can't load /home/ncsclme/.rnd into RNG
140068364820928:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/home/ncsclme/.rnd
[x] Signing root CA
Signature ok
subject=C = GB, ST = UK, L = London, O = Docker, CN = Swarm
Getting Private key
[x] Making logstash Cert
Generating RSA private key, 4096 bit long modulus (2 primes)
.......................................................................++++
......................................................................................................................................................................++++
e is 65537 (0x010001)
Can't load /home/ncsclme/.rnd into RNG
139759047717312:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/home/ncsclme/.rnd
[x] Signing logstash cert
Signature ok
subject=C = GB, ST = UK, L = London, O = Docker, CN = lee
Getting CA Private Key
[x] Making wlbclient Cert
Generating RSA private key, 4096 bit long modulus (2 primes)
.................................................................................................................................................................................................................................................++++
..........................................................................................................++++
e is 65537 (0x010001)
Can't load /home/ncsclme/.rnd into RNG
139971302314432:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/home/ncsclme/.rnd
[x] Signing wlbclient cert
Signature ok
subject=C = GB, ST = UK, L = London, O = Docker, CN = wlbclient
Getting CA Private Key
[x] Making logstash Cert
Generating RSA private key, 4096 bit long modulus (2 primes)
....................................++++
........................................................................................................++++
e is 65537 (0x010001)
Can't load /home/ncsclme/.rnd into RNG
140592915624384:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/home/ncsclme/.rnd
[x] Sign elasticsearch cert
Signature ok
subject=C = GB, ST = UK, L = London, O = Docker, CN = elasticsearch
Getting CA Private Key
[x] Making logstash Cert
Generating RSA private key, 4096 bit long modulus (2 primes)
................................................................................................................................................................................................................................++++
...................................................................................................................................................................................................++++
e is 65537 (0x010001)
Can't load /home/ncsclme/.rnd into RNG
139683095110080:error:2406F079:random number generator:RAND_load_file:Cannot open file:../crypto/rand/randfile.c:88:Filename=/home/ncsclme/.rnd
[x] Sign kibana cert
Signature ok
subject=C = GB, ST = UK, L = London, O = Docker, CN = kibana
Getting CA Private Key
[x] Installing curl to get the docker convenience script
Reading package lists...
Building dependency tree...
Reading state information...
curl is already the newest version (7.58.0-2ubuntu3.8).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
[x] Installing docker
Warning: the "docker" command appears to already exist on this system.

If you already have Docker installed, this script can cause trouble, which is
why we're displaying this warning and provide the opportunity to cancel the
installation.

If you installed the current Docker package using this script and are using it
again to update Docker, you can safely ignore this message.

You may press Ctrl+C now to abort this script.

• sleep 20
• sh -c apt-get update -qq >/dev/null
• sh -c DEBIAN_FRONTEND=noninteractive apt-get install -y -qq apt-transport-https ca-certificates curl >/dev/null
• sh -c curl -fsSL "https://download.docker.com/linux/ubuntu/gpg" | apt-key add -qq - >/dev/null
  Warning: apt-key output should not be parsed (stdout is not a terminal)
• sh -c echo "deb [arch=amd64] https://download.docker.com/linux/ubuntu bionic stable" > /etc/apt/sources.list.d/docker.list
• sh -c apt-get update -qq >/dev/null
• [ -n ]
• sh -c apt-get install -y -qq --no-install-recommends docker-ce >/dev/null
• sh -c docker version
  [x] Configuring docker swarm
  Error response from daemon: This node is already part of a swarm. Use "docker swarm leave" to leave this swarm and join another one.
  [x] Adding certificates and keys to Docker
  Error response from daemon: rpc error: code = AlreadyExists desc = secret ca.crt already exists
  Error response from daemon: rpc error: code = AlreadyExists desc = secret logstash.key already exists
  Error response from daemon: rpc error: code = AlreadyExists desc = secret logstash.crt already exists
  Error response from daemon: rpc error: code = AlreadyExists desc = secret elasticsearch.key already exists
  Error response from daemon: rpc error: code = AlreadyExists desc = secret elasticsearch.crt already exists
  Error response from daemon: rpc error: code = AlreadyExists desc = secret kibana.key already exists
  Error response from daemon: rpc error: code = AlreadyExists desc = secret kibana.crt already exists
  open logstash.edited.conf: no such file or directory
  Error response from daemon: rpc error: code = AlreadyExists desc = config osmap.csv already exists
  vm.max_map_count = 262144
  service logstash: config not found: logstash.conf
  [x] Waiting for elasticsearch to be ready

---

Is this a known issue as im not finding a lot of info on this issue.
System is Ubuntu 18.04.3 LTS running on Hyper-V
16GB RAM
4 x CPU

[Bwshort1]

I reverted the VM and tried again.
This time it worked correctly.

I can see that duncan-ncc has made amendments to the deploy.sh file between the time that I logged this issue and no so I'm assuming that what ever has changed in the file has made the difference.

Thanks