Wazuh-Indexer service script not executable on SysV init

[juliancnn]

Related issues:

• Migration to OpenSearch's Debian scripts #564

Description

When Wazuh-Indexer is installed on systems that do not use systemd, the service script is not recognized due to missing execute permissions on the /etc/init.d/wazuh-indexer file. As a result, commands like service wazuh-indexer start or service wazuh-indexer status report that wazuh-indexer is an unrecognized service.

Current Behavior:

# service wazuh-indexer start
wazuh-indexer: unrecognized service

# service --status-all
...
[ + ] wazuh-server
...

After manually adding execute permissions:

# chmod +x /etc/init.d/wazuh-indexer
# service --status-all
...
[ + ] wazuh-indexer
[ + ] wazuh-server
...

This confirms that the issue lies in the file permissions assigned at installation time.

Objective

Ensure that the /etc/init.d/wazuh-indexer script is installed with executable permissions so that the service command can properly list and manage the Wazuh-Indexer service on non-systemd systems.

Tasks

1. Review Packaging Scripts:

   • Check the Debian and RPM packaging scripts used to install Wazuh-Indexer.
   • Identify where /etc/init.d/wazuh-indexer is copied or created.

2. Set Executable Permissions:

   • Modify the packaging process to ensure chmod +x /etc/init.d/wazuh-indexer is applied post-installation.
   • Confirm that this change does not affect systemd-based installs, where systemd units are primarily used.

3. Testing:

   • Rebuild Wazuh-Indexer packages with the updated packaging scripts.
   • Install on a non-systemd environment (e.g., SysVinit or Upstart-based system).
   • Verify that service wazuh-indexer start, status, and other commands now work as intended.