Skip to content

Fix service's installation path for CentOS 8#4060

Merged
chemamartinez merged 1 commit into3.11from
323-wp-fix-systemd-installation-path
Oct 8, 2019
Merged

Fix service's installation path for CentOS 8#4060
chemamartinez merged 1 commit into3.11from
323-wp-fix-systemd-installation-path

Conversation

@BraulioV
Copy link
Copy Markdown
Contributor

@BraulioV BraulioV commented Oct 8, 2019

Related issue
wazuh/wazuh-packages#323

Description

Hi team,

This PR closes wazuh/wazuh-packages#323 by installing the services files in /usr/lib/systemd/system/. This allows using systemd to manage the service of the manager and the agent in CentOS 8.

Configuration options

Not needed.

Logs/Alerts example

  • Agent:
[root@centos8 wazuh]# systemctl start wazuh-agent          
[root@centos8 wazuh]# systemctl status wazuh-agent      
● wazuh-agent.service - Wazuh agent
   Loaded: loaded (/usr/lib/systemd/system/wazuh-agent.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-10-08 09:11:48 UTC; 2s ago
  Process: 12620 ExecStart=/usr/bin/env ${DIRECTORY}/bin/ossec-control start (code=exited, status=0/SUCCESS)
    Tasks: 22 (limit: 24014)
   Memory: 12.1M
   CGroup: /system.slice/wazuh-agent.service
           ├─12647 /var/ossec/bin/ossec-execd
           ├─12652 /var/ossec/bin/ossec-agentd
           ├─12659 /var/ossec/bin/ossec-syscheckd
           ├─12664 /var/ossec/bin/ossec-logcollector
           └─12674 /var/ossec/bin/wazuh-modulesd

  • Manager
[root@centos8 vagrant]# systemctl status wazuh-manager
● wazuh-manager.service - Wazuh manager
   Loaded: loaded (/usr/lib/systemd/system/wazuh-manager.service; enabled; vendor preset: disabled)
   Active: active (running) since Tue 2019-10-08 09:21:26 UTC; 10s ago
  Process: 4948 ExecStart=/usr/bin/env ${DIRECTORY}/bin/ossec-control start (code=exited, status=0/SUCCESS)
    Tasks: 85 (limit: 24014)
   Memory: 47.5M
   CGroup: /system.slice/wazuh-manager.service
           ├─5013 /var/ossec/bin/ossec-authd
           ├─5022 /var/ossec/bin/wazuh-db
           ├─5039 /var/ossec/bin/ossec-execd
           ├─5047 /var/ossec/bin/ossec-analysisd
           ├─5054 /var/ossec/bin/ossec-syscheckd
           ├─5062 /var/ossec/bin/ossec-remoted
           ├─5087 /var/ossec/bin/ossec-logcollector
           ├─5092 /var/ossec/bin/ossec-monitord
           └─5098 /var/ossec/bin/wazuh-modulesd

Oct 08 09:21:24 centos8 env[4948]: Started wazuh-db...
Oct 08 09:21:24 centos8 env[4948]: Started ossec-execd...
Oct 08 09:21:24 centos8 env[4948]: Started ossec-analysisd...
Oct 08 09:21:24 centos8 env[4948]: Started ossec-syscheckd...
Oct 08 09:21:24 centos8 env[4948]: Started ossec-remoted...
Oct 08 09:21:24 centos8 env[4948]: Started ossec-logcollector...
Oct 08 09:21:24 centos8 env[4948]: Started ossec-monitord...
Oct 08 09:21:24 centos8 env[4948]: Started wazuh-modulesd...
Oct 08 09:21:26 centos8 env[4948]: Completed.
Oct 08 09:21:26 centos8 systemd[1]: Started Wazuh manager.

Tests

  • Compilation without warnings in every supported platform
    • Linux
  • Source installation
  • Package installation
  • Source upgrade
  • Package upgrade
  • Review logs syntax and correct language

@BraulioV BraulioV added type/bug Something isn't working module/service labels Oct 8, 2019
@BraulioV BraulioV requested a review from alberpilot October 8, 2019 09:23
@BraulioV BraulioV self-assigned this Oct 8, 2019
@BraulioV BraulioV changed the base branch from master to 3.11 October 8, 2019 09:23
Copy link
Copy Markdown
Contributor

@alberpilot alberpilot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@chemamartinez chemamartinez merged commit b2376fc into 3.11 Oct 8, 2019
@chemamartinez chemamartinez deleted the 323-wp-fix-systemd-installation-path branch October 8, 2019 14:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

module/service type/bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants