Hi @ston1th

I was able to reproduce this error, so we are working in a solution to fix this issue. I will back to you with a solution as soon as possible.

Thank you so much for your feedback :)

Regards,
Braulio.

Hello team,
This problem still happens, I have been investigating a better way of checking if the system where the package is being installed uses systemd or not.
I have tested several options:

if [ systemctl enable wazuh-agent ]

if command -v systemctl >/dev/null 

if [ $(file /sbin/init =~ systemd ]

Regards,
Daniel Folch

Hello

Ubuntu 14.04 LTS is End-Of-Life since Apr 2019. But there are paid security updates from Canonical until Apr 2022.
https://ubuntu.com/about/release-cycle

@DFolchA @BraulioV so a fix for this is IMHO only nessecery if the Wazuh-Team wants to continue to support the paid Ubutnu 14.04 LTS?
Otherwise people should upgrade their systems to Ubuntu 16.04 LTS or later (which ships with systemd).

Hi @ston1th,

Sorry for the late response. Currently, Wazuh supports pretty old systems such as CentOS 5, AIX 5.3, Debian 7, etc. So we will include the fix to support those systems even if they are not supported anymore by their distributors.

Thank you for your patience.

Hello team,

I have tested the new package generated within docker containers of the following versions to see if it worked properly:

• Ubuntu 14 LTS with run/systemd/system created
• Ubuntu 14 LTS without run/systemd/system
• Ubuntu 16 LTS
• Ubuntu 18 LTS

I have run intall, uninstall, upgrade, remove and purge tests for every system.

During these tests, I found that this same problem appeared while uninstalling and fixed it in this commit:

aca0c5d

Regards