lme-elasticsearch.service: start operation timed out. Terminating.

[indian-summers]

I am very appreciative of the replies to issue 154, they helped us move forward.

However, we are now stuck with the following issue when executing the sudo -i journalctl -xu $SERVICE_NAME command.

The process' exit code is 'exited' and its exit status is 143.
lme systemd[1]: lme-elasticsearch.service: Failed with result 'timeout'.
Subject: Unit failed
Defined-By: systemd

The unit lme-elasticsearch.service has entered the 'failed' state with result 'timeout'.
lme systemd[1]: Failed to start lme-elasticsearch.service - Elasticsearch Container Service.
Subject: A start job for unit lme-elasticsearch.service has failed
Defined-By: systemd

[aarz-snl]

What part of the installation are you at? This is a basic error that says the install failed. It could be hundreds of different reasons.

see if you have more information in journal:

journalctl -u lme-elasticsearch.service -n 100 --no-pager

were you able to get any logs from the container?

sudo -i podman logs lme-elasticsearch

Do you have enough resources on the machine you're installing this on?

free -h

df -h

[indian-summers]

First and foremost, thank you for the reply!

I get as far as: If something is broken, try restarting the services and making sure failed services reset before starting:
without errors. I wait for at least 30 minutes before proceeding.

I then proceed to sudo -i podman ps --format "{{.Names}} {{.Status}}"

lme-elasticsearch Up About a minute (unhealthy) gets this far, and then it goes back to (starting) after 1 minute.

Something is causing lme-elasticsearch to time out after 1 minute, but I don't know what it is.

I am not an expert on scripts so I must ask.

The lme-environment.env file was updated as follows, but I am not sure if it is formatted properly.

The two IPs are separated by a comma.

IPVAR=127.0.0.1 , and the IP obtained from hostname -I | awk '{print $1}'

The output from the first two command is quite lengthy, I'd be glad to upload the output of the first two commands instead of pasting it here.

LME is running in Hyper-v and has 4 processors assigned to it.

free -h
total used free shared buff/cache available
Mem: 31Gi 17Gi 12Gi 1.8Mi 1.4Gi 13Gi
Swap: 4.0Gi 0B 4.0Gi

df -h
Filesystem Size Used Avail Use% Mounted on
tmpfs 3.2G 1.8M 3.2G 1% /run
/dev/mapper/ubuntu--vg-ubuntu--lv 98G 14G 79G 16% /
tmpfs 16G 84K 16G 1% /dev/shm
tmpfs 5.0M 0 5.0M 0% /run/lock
/dev/sda2 2.0G 95M 1.7G 6% /boot
tmpfs 3.2G 12K 3.2G 1% /run/user/1000

fdisk -l
Disk /dev/sda: 250 GiB, 268435456000 bytes, 524288000 sectors
Disk model: Virtual Disk
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt

[cbaxley]

You may try installing as root. In hyperv we have had problems with cgroups not having permission in virtual machines. Thanks, Clint Baxley

…

On Mon, Jan 13, 2025 at 4:35 PM indian-summers ***@***.***> wrote: First and foremost, thank you for the reply! I get as far as: *If something is broken, try restarting the services and making sure failed services reset before starting:* *without errors*. I wait for at least 30 minutes before proceeding. I then proceed to *sudo -i podman ps --format "{{.Names}} {{.Status}}"* lme-elasticsearch Up About a minute (unhealthy) gets this far, and then it goes back to (starting) after 1 minute. Something is causing lme-elasticsearch to time out after 1 minute, but I don't know what it is. I am not an expert on scripts so I must ask. The lme-environment.env file was updated as follows, but I am not sure if it is formatted properly. The two IPs are separated by a comma. IPVAR=127.0.0.1 , and the IP obtained from *hostname -I | awk '{print $1}'* The output from the first two command is quite lengthy, I'd be glad to upload the output of the first two commands instead of pasting it here. LME is running in Hyper-v and has 4 processors assigned to it. *free -h* total used free shared buff/cache available Mem: 31Gi 17Gi 12Gi 1.8Mi 1.4Gi 13Gi Swap: 4.0Gi 0B 4.0Gi *df -h* Filesystem Size Used Avail Use% Mounted on tmpfs 3.2G 1.8M 3.2G 1% /run /dev/mapper/ubuntu--vg-ubuntu--lv 98G 14G 79G 16% / tmpfs 16G 84K 16G 1% /dev/shm tmpfs 5.0M 0 5.0M 0% /run/lock /dev/sda2 2.0G 95M 1.7G 6% /boot tmpfs 3.2G 12K 3.2G 1% /run/user/1000 *fdisk -l* Disk /dev/sda: 250 GiB, 268435456000 bytes, 524288000 sectors Disk model: Virtual Disk Units: sectors of 1 * 512 = 512 bytes Sector size (logical/physical): 512 bytes / 4096 bytes I/O size (minimum/optimal): 4096 bytes / 4096 bytes Disklabel type: gpt — Reply to this email directly, view it on GitHub <#547 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQY33XUUHFLHAEULPLSU7T2KQWTRAVCNFSM6AAAAABU4Z2FYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBYGI3DQMRZGY> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[indian-summers]

Thank you! Should I uninstall first and reinstall as root, or simple restart the installation as root?

[indian-summers]

is the lme-environment.env sytax correct?

IPVAR=127.0.0.1 , LME IP Address

[cbaxley]

It needs a full reinstall by root, if it is the cgroups problem. The IPVAR line should not have anything but IPVAR=127.0.0.1 Thanks, Clint Baxley

…

On Tue, Jan 14, 2025 at 1:55 PM indian-summers ***@***.***> wrote: is the lme-environment.env sytax correct? IPVAR=127.0.0.1 , LME IP Address — Reply to this email directly, view it on GitHub <#547 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAQY33R2XIKEVEHCYDYQ7RT2KVMR7AVCNFSM6AAAAABU4Z2FYSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOJQHA3TMNRZGQ> . You are receiving this because you commented.Message ID: ***@***.***>

[indian-summers]

same issue on a clean ubuntu installation with su.

I am going to try it on Vbox before throwing in the towel.

Thank you for all your help.

[indian-summers]

Same issue on a clear

[indian-summers]

Yes, same issue on a clean hyperv - vm.

I increased the memory and the number of processors on the new vm.

Distributor ID: Ubuntu
Description: Ubuntu 24.04.1 LTS
Release: 24.04
Codename: noble

I am a bit confused with the following LME installation instructions.

In the new lme-environment.env file, update the following values:

#your host ip as found from the above command
IPVAR=127.0.0.1 #your hosts ip

What is the purpose of the # your host ip if per your reply, the only value in that line should be IPVAR=127.0.0.1

[indian-summers]

Throwing in the towel after installing LME on a different host and a clean Ubuntu VBox VM.

I was very excited to have this resource available to meet our NIST SP 800-171 compliance, and now back to square one.

Same error on the VBox VM

same specs: 32GB, and 4 processors

Firewall has been configure in the LME server per the required ports.

NOTE: I waited 30 minutes before running the command sudo -i journalctl -xu lme-elasticsearch

output of the sudo -i journalctl -xu lme-elasticsearch:

lme systemd[1]: lme-elasticsearch.service: Main process exited, code=exited, status=143/n/a
Subject: Unit process exited
Defined-By: systemd

An ExecStart= process belonging to unit lme-elasticsearch.service has exited.

The process' exit code is 'exited' and its exit status is 143.
lme systemd[1]: lme-elasticsearch.service: Failed with result 'exit-code'.
Subject: Unit failed
Defined-By: systemd

The unit lme-elasticsearch.service has entered the 'failed' state with result 'exit-code'.

lme systemd[1]: Stopped lme-elasticsearch.service - Elasticsearch Container Service.
Subject: A stop job for unit lme-elasticsearch.service has finished
Defined-By: systemd