Linux
281

How to fix run systemd service slow and no response






  14-Dec-2022 03:01:13



I was setting configuration web server (success), setting ip to static and others then run systemd service but nothing respon any can diagnostic. Web server can success but i wan't try setup wazuh and other help i struggle to fix them

my conf


nodes:
  # Wazuh indexer nodes
  indexer:
    - name: test-mynode
      ip: 192.168.X.X.X.X #MY IP
    #- name: node-2
    #  ip: <indexer-node-ip>
    #- name: node-3
    #  ip: <indexer-node-ip>

  # Wazuh server nodes
  # If there is more than one Wazuh server
  # node, each one must have a node_type
  server:
    - name: wazuh-1
      ip: 192.168.X.X.X.X #MY IP
    #  node_type: master
    #- name: wazuh-2
    #  ip: <wazuh-manager-ip>
    #  node_type: worker
    #- name: wazuh-3
    #  ip: <wazuh-manager-ip>
    #  node_type: worker

  # Wazuh dashboard nodes
  dashboard:
    - name: dashboard
      ip: 192.168.X.X.X.X #MY IP
Run systemd

systemctl daemon-reload
systemctl enable wazuh-indexer
systemctl start wazuh-indexer
Why no respon?

*Beware click the link!


DISCUSSION

Did you set this up on your virtual machine or VPS? Hmmm I can see it could be an error in the configuration. Make sure you do it properly and read the doc, if it's slow it could happen to your device specifications, but I'm not sure about these specifications (it might be) Try reading the doc properly, or use this command to see the running status log

journalctl -f

The f option is used to view to view a live log of new messages as they are aggregated

The key command from less is not available while in this mode. Enter Control-C on your keyboard to return to your command prompt from this mode

Read the log, if it's still slow try to wait patiently it could be your device is not qualified if there is an error message during the systemd process such as a conf error or timeout you can make these changes, it is difficult to do maintenance or troubleshooting if I do not see or try directly. Try reading here

help

- https://www.linode.com/docs/guides/how-to-use-journalctl/ 

- https://discuss.elastic.co/t/request-timeout-after-30000-kibana-process-getting-killed/54457 

- https://www.digitalocean.com/community/tutorials/how-to-troubleshoot-common-elk-stack-issues 

- https://discuss.elastic.co/t/debian-elasticsearch-service-start-operation-timed-out-terminating/223262 

- https://sleeplessbeastie.eu/2020/02/29/how-to-prevent-systemd-service-start-operation-from-timing-out/ 

- https://unix.stackexchange.com/questions/227017/how-to-change-systemd-service-timeout-value 

- https://www.freedesktop.org/software/systemd/man/systemd.service.html 




Reply

Make sure everything is installed then check again your node and your IP, this is the same as my previous mistake I made  wrong IP configuration check operating system version with wazuh




Reply

Login for report, comment and join discussion
Login Here
Sponsored

Popular Posts
Gps Tracker Seccodeid Free Too...
General
21354
204
Top


Djie sam soe Djie sam soe
Complete Basic Course in Kali...
Linux
14373
4
Top


Djie sam soe Djie sam soe
Komintod (Ministry of Communic...
Data Leak
6511
94
Top


Murtad methamphetamine Murtad methamphetamine
Free Proxy List
Networking
3625
3
Top


Sandidi Sandidi
Mass Reverse IP Unlimited
Tools Hacking
3392
15
Top


ImamWawe ImamWawe

Related Post

Youtube Video

Subscribe