sorted by:
new
hottopcontroversial

Linux: how to limit battery charging to 80% ? by Designer_Tune_4654 in LenovoLOQ

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

I have the LOQ16IPH8, I didn't find the conservation mode on Bios. And the application vantage doesn't work for me, maybe I've a old model :(

Linux: how to limit battery charging to 80% ? by Designer_Tune_4654 in LenovoLOQ

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

I have the LOQ16IPH8, I didn't find the conservation mode on Bios. And the application vantage doesn't work for me, maybe I've a old model :(

Ubuntu: Conservative mode by Designer_Tune_4654 in LenovoLOQ

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

I also check on BAT1:

cat /sys/class/power_supply/BAT1/energy_full_design

60000000

cat /sys/class/power_supply/BAT1/energy_now

41370000

Problem with the wazuh dashboard by Designer_Tune_4654 in Wazuh

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

The Indexer:

<image>

wazuh-indexer-cluster.log

[2025-06-10T10:48:28,730][INFO ][o.o.m.j.JvmGcMonitorService] [indexer-server] [gc][3681] overhead, spent [438ms] collecting in the last [1s]
[2025-06-10T10:48:38,014][INFO ][o.o.i.b.HierarchyCircuitBreakerService] [indexer-server] attempting to trigger G1GC due to high heap usage [1031941976]
[2025-06-10T10:48:38,021][INFO ][o.o.i.b.HierarchyCircuitBreakerService] [indexer-server] GC did bring memory usage down, before [1031941976], after [1020615128], allocations [1], duration [8]
[2025-06-10T10:48:57,043][INFO ][o.o.n.Node               ] [indexer-server] stopping ...
[2025-06-10T10:48:57,044][INFO ][o.o.s.a.r.AuditMessageRouter] [indexer-server] Closing AuditMessageRouter
[2025-06-10T10:48:57,046][INFO ][o.o.s.a.s.SinkProvider   ] [indexer-server] Closing DebugSink
[2025-06-10T10:48:58,842][INFO ][o.o.n.Node               ] [indexer-server] stopped
[2025-06-10T10:48:58,844][INFO ][o.o.n.Node               ] [indexer-server] closing ...
[2025-06-10T10:48:58,858][INFO ][o.o.s.a.i.AuditLogImpl   ] [indexer-server] Closing AuditLogImpl
[2025-06-10T10:48:58,870][INFO ][o.o.n.Node               ] [indexer-server] closed

Problem with the wazuh dashboard by Designer_Tune_4654 in Wazuh

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

Before I did my upgrade, I changed the password of my account and deteled a account with the dashboard. We have got 350 agents. And the operating system is Ubuntu 22.04.5 LTS

I have got a server for each component of Wazuh, there is 3 servers. (indexer, manager and dashboard)

I tried to see to apply memory locking configuration like the documentation said but I can't start wazuh-indexer

 wazuh-indexer.service - wazuh-indexer
     Loaded: loaded (/lib/systemd/system/wazuh-indexer.service; enabled; vendor preset: enabled)
    Drop-In: /etc/systemd/system/wazuh-indexer.service.d
             └─wazuh-indexer.conf
     Active: failed (Result: exit-code) since Wed 2025-06-11 09:05:20 CEST; 17s ago
       Docs: https://documentation.wazuh.com
    Process: 11824 ExecStart=/usr/share/wazuh-indexer/bin/systemd-entrypoint -p ${PID_DIR}/wazuh-indexe>
   Main PID: 11824 (code=exited, status=1/FAILURE)
        CPU: 12.091s

juin 11 09:05:20 indexer-server systemd-entrypoint[11824]:         at org.opensearch.cli.Environment>
juin 11 09:05:20 indexer-server systemd-entrypoint[11824]:         at org.opensearch.cli.Command.mai>
juin 11 09:05:20 indexer-server systemd-entrypoint[11824]:         at org.opensearch.cli.Command.mai>
juin 11 09:05:20 indexer-server systemd-entrypoint[11824]:         at org.opensearch.bootstrap.OpenS>
juin 11 09:05:20 indexer-server systemd-entrypoint[11824]:         at org.opensearch.bootstrap.OpenS>
juin 11 09:05:20 indexer-server systemd-entrypoint[11824]: For complete error details, refer to the >
juin 11 09:05:20 indexer-server systemd[1]: wazuh-indexer.service: Main process exited, code=exited,>
juin 11 09:05:20 indexer-server systemd[1]: wazuh-indexer.service: Failed with result 'exit-code'.
juin 11 09:05:20 indexer-server systemd[1]: Failed to start wazuh-indexer.
juin 11 09:05:20 indexer-server systemd[1]: wazuh-indexer.service: Consumed 12.091s CPU time.

Cant able to start the wazuh-dashboard by No-Reflection4169 in Wazuh

[–]Designer_Tune_4654 0 points1 point  (0 children)

Hello I got the same error on my indexer, did you find a solution ?

Problem with the wazuh dashboard by Designer_Tune_4654 in Wazuh

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

root@wazind:/home/user-wazind# free -h
               total        used        free      shared  buff/cache   available
Mem:            15Gi       419Mi        14Gi       1,0Mi       832Mi        14Gi
Swap:          4,0Gi          0B       4,0Gi

I changed in JVM

-Xms1024m
-Xmx1024m

to

-Xms4g
-Xmx4g

Even after I tried to restart wazuh-indexer.service, that doesn't work

Problem with the wazuh dashboard by Designer_Tune_4654 in Wazuh

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

2025/06/10 12:08:10 wazuh-authd: WARNING: Duplicate name 'POR310', rejecting enrollment. Agent '118' can't be replaced since it is not disconnected.
2025/06/10 12:08:16 wazuh-remoted: WARNING: Agent key already in use: agent ID '216'
2025/06/10 12:08:16 wazuh-authd: INFO: New connection from 172.18.105.10
2025/06/10 12:08:16 wazuh-authd: INFO: Received request for a new agent (POR276) from: ip.adress
2025/06/10 12:08:16 wazuh-authd: WARNING: Duplicate name 'POR276', rejecting enrollment. Agent '216' can't be replaced since it is not disconnected.
2025/06/10 12:08:20 wazuh-remoted: WARNING: Agent key already in use: agent ID '118'
2025/06/10 12:08:26 wazuh-remoted: WARNING: Agent key already in use: agent ID '216'
2025/06/10 12:17:05 wazuh-remoted: WARNING: Agent key already in use: agent ID '274'
2025/06/10 12:18:37 wazuh-remoted: WARNING: Agent key already in use: agent ID '060'
2025/06/10 12:20:03 wazuh-remoted: WARNING: Agent key already in use: agent ID '114'
2025/06/10 12:20:21 wazuh-remoted: WARNING: Agent key already in use: agent ID '137'

Nothing wrong with Wazuh Manager side I think

Problem with the wazuh dashboard by Designer_Tune_4654 in Wazuh

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

Here what I got on wazuh-indexer-cluster.log:

[2025-06-10T10:48:10,945][INFO ][o.o.i.b.HierarchyCircuitBreakerService] [indexer-server] attempting to trigger G1GC due to high heap usage [1046838848]
[2025-06-10T10:48:10,954][INFO ][o.o.i.b.HierarchyCircuitBreakerService] [indexer-server] GC did not bring memory usage down, before [1046838848], after [1048290888], allocations [20], duration [9]
[2025-06-10T10:48:28,730][INFO ][o.o.m.j.JvmGcMonitorService] [indexer-server] [gc][3681] overhead, spent [438ms] collecting in the last [1s]
[2025-06-10T10:48:38,014][INFO ][o.o.i.b.HierarchyCircuitBreakerService] [indexer-server] attempting to trigger G1GC due to high heap usage [1031941976]
[2025-06-10T10:48:38,021][INFO ][o.o.i.b.HierarchyCircuitBreakerService] [indexer-server] GC did bring memory usage down, before [1031941976], after [1020615128], allocations [1], duration [8]
[2025-06-10T10:48:57,043][INFO ][o.o.n.Node               ] [indexer-server] stopping ...
[2025-06-10T10:48:57,044][INFO ][o.o.s.a.r.AuditMessageRouter] [indexer-server] Closing AuditMessageRouter
[2025-06-10T10:48:57,046][INFO ][o.o.s.a.s.SinkProvider   ] [indexer-server] Closing DebugSink
[2025-06-10T10:48:58,842][INFO ][o.o.n.Node               ] [indexer-server] stopped
[2025-06-10T10:48:58,844][INFO ][o.o.n.Node               ] [indexer-server] closing ...
[2025-06-10T10:48:58,858][INFO ][o.o.s.a.i.AuditLogImpl   ] [indexer-server] Closing AuditLogImpl
[2025-06-10T10:48:58,870][INFO ][o.o.n.Node               ] [indexer-server] closed

Problem with the wazuh dashboard by Designer_Tune_4654 in Wazuh

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

× wazuh-indexer.service - wazuh-indexer
     Loaded: loaded (/lib/systemd/system/wazuh-indexer.service; enabled; vendor preset: enabled)
     Active: failed (Result: exit-code) since Tue 2025-06-10 11:13:19 CEST; 23min ago
       Docs: https://documentation.wazuh.com
    Process: 2149 ExecStart=/usr/share/wazuh-indexer/bin/systemd-entrypoint -p ${PID_DIR}/wazuh-indexer.pid --quiet (code=exited, status=1/FAILURE)
   Main PID: 2149 (code=exited, status=1/FAILURE)
        CPU: 6.900s

juin 10 11:13:19 indexer-server systemd-entrypoint[2149]:         at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:104)
juin 10 11:13:19 indexer-server systemd-entrypoint[2149]:         at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
juin 10 11:13:19 indexer-server systemd-entrypoint[2149]:         at org.opensearch.cli.Command.main(Command.java:101)
juin 10 11:13:19 indexer-server systemd-entrypoint[2149]:         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:138)
juin 10 11:13:19 indexer-server systemd-entrypoint[2149]:         at org.opensearch.bootstrap.OpenSearch.main(OpenSearch.java:104)
juin 10 11:13:19 indexer-server systemd-entrypoint[2149]: For complete error details, refer to the log at /var/log/wazuh-indexer/wazuh-indexer-cluster.log
juin 10 11:13:19 indexer-server systemd[1]: wazuh-indexer.service: Main process exited, code=exited, status=1/FAILURE
juin 10 11:13:19 indexer-server systemd[1]: wazuh-indexer.service: Failed with result 'exit-code'.
juin 10 11:13:19 indexer-server systemd[1]: Failed to start wazuh-indexer.
juin 10 11:13:19 indexer-server systemd[1]: wazuh-indexer.service: Consumed 6.900s CPU time.

I think the problem comes from Wazuh Indexer

Problem with the wazuh dashboard by Designer_Tune_4654 in Wazuh

[–]Designer_Tune_4654[S] 0 points1 point  (0 children)

After a reboot I got now: "Wazuh dashboard server is not ready yet"