Wazuh Dashboard isnt working

[Zaks Ace]

So everythings seems to up and working but the major error I am facing regrading wazuh-dashboard are in
cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i "WARN"
[2025-02-25T15:35:47,914][WARN ][r.suppressed             ] [node-1] path: /.kibana/_count, params: {index=.kibana}
[2025-02-25T15:35:47,955][WARN ][o.o.c.r.a.AllocationService] [node-1] Falling back to single shard assignment since batch mode disable or multiple custom allocators set
[WARN ][o.o.p.c.ThreadPoolMetricsCollector] [node-1] Fail to read queue capacity via reflection
[WARN ][o.o.s.p.SQLPlugin        ] [node-1] Master key is a required config for using create and update datasource APIs. Please set plugins.query.datasources.encryption.masterkey config in opensearch.yml in all the cluster nodes. More details can be found here: https://github.com/opensearch-project/sql/blob/main/docs/user/ppl/admin/datasources.rst#master-key-config-for-encrypting-credential-information
[WARN ][stderr                   ] [node-1] WARNING: A restricted method in java.lang.foreign.Linker has been called
[2025-02-25T15:32:16,350][WARN ][stderr                   ] [node-1] WARNING: java.lang.foreign.Linker::downcallHandle has been called by the unnamed module
[2025-02-25T15:32:16,350][WARN ][stderr                   ] [node-1] WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for this module
[2025-02-25T15:32:25,705][WARN ][o.o.s.c.Salt             ] [node-1] If you plan to use field masking pls configure compliance salt e1ukloTsQlOgPquJ to be a random string of 16 chars length identical on all nodes
[WARN ][o.a.l.i.v.VectorizationProvider] [node-1] Java vector incubator module is not readable. For optimal vector performance, pass '--add-modules jdk.incubator.vector' to enable Vector API.
[2025-02-25T13:37:29,670][WARN ][stderr                   ] [node-1] WARNING: A restricted method in java.lang.foreign.Linker has been called
[2025-02-25T13:37:29,671][WARN ][stderr                   ] [node-1] WARNING: java.lang.foreign.Linker::downcallHandle has been called by the unnamed module
[2025-02-25T13:37:29,672][WARN ][stderr                   ] [node-1] WARNING: Use --enable-native-access=ALL-UNNAMED to avoid a warning for this module
[2025-02-25T13:37:39,629][WARN ][o.o.s.c.Salt             ] [node-1] If you plan to use field masking pls configure compliance salt e1ukloTsQlOgPquJ to be a random string of 16 chars length identical on all nodes
[2025-02-25T13:37:39,706][WARN ][o.o.s.a.r.AuditMessageRouter] [node-1] No default storage available, audit log may not work properly. Please check configuration.
[2025-02-25T13:37:41,926][WARN ][o.o.s.p.SQLPlugin        ] [node-1] Master key is a required config for using create and update datasource APIs. Please set plugins.query.datasources.encryption.masterkey config in opensearch.yml in all the cluster nodes. More details can be found here: https://github.com/opensearch-project/sql/blob/main/docs/user/ppl/admin/datasources.rst#master-key-config-for-encrypting-credential-information
Also here are the few things :
[ERROR][o.o.s.c.ConfigurationLoaderSecurity7] [node-1] Failure No shard available for [org.opensearch.action.get.MultiGetShardRequest@f2455f1] retrieving configuration for [ACTIONGROUPS, ALLOWLIST, AUDIT, CONFIG, INTERNALUSERS, NODESDN, ROLES, ROLESMAPPING, TENANTS, WHITELIST] (index=.opendistro_security)
[2025-02-25T15:32:48,058][ERROR][o.o.s.a.BackendRegistry  ] [node-1] Not yet initialized (you may need to run securityadmin)
[ERROR][o.o.s.a.BackendRegistry  ] [node-1] Not yet initialized (you may need to run securityadmin)
[ERROR][o.o.p.c.j.GCMetrics      ] [node-1] MX bean missing: G1 Concurrent GC
[2025-02-25T15:32:20,142][ERROR][o.o.p.c.o.OSGlobals      ] [node-1] Error in reading/parsing clk.tck value: java.lang.NumberFormatException: Cannot parse null string
[2025-02-25T15:32:25,782][ERROR][o.o.s.a.s.SinkProvider   ] [node-1] Default endpoint could not be created, auditlog will not work properly.
[2025-02-25T15:32:33,391][ERROR][o.o.s.l.BuiltinLogTypeLoader] [node-1] Failed loading builtin log types from disk!
][o.o.n.Node               ] [node-1] JVM arguments [-Xshare:auto, -Dopensearch.networkaddress.cache.ttl=60, -Dopensearch.networkaddress.cache.negative.ttl=10, -XX:+AlwaysPreTouch, -Xss1m, -Djava.awt.headless=true, -Dfile.encoding=UTF-8, -Djna.nosys=true, -XX:-OmitStackTraceInFastThrow, -XX:+ShowCodeDetailsInExceptionMessages, -Dio.netty.noUnsafe=true, -Dio.netty.noKeySetOptimization=true, -Dio.netty.recycler.maxCapacityPerThread=0, -Dio.netty.allocator.numDirectArenas=0, -Dlog4j.shutdownHookEnabled=false, -Dlog4j2.disable.jmx=true, -Djava.security.manager=allow, -Djava.locale.providers=SPI,COMPAT, -Xms2g, -Xmx2g, -XX:+UseG1GC, -XX:G1ReservePercent=25, -XX:InitiatingHeapOccupancyPercent=30, -Djava.io.tmpdir=/var/log/wazuh-indexer/tmp, -XX:+HeapDumpOnOutOfMemoryError, -XX:HeapDumpPath=/var/lib/wazuh-indexer, -XX:ErrorFile=/var/log/wazuh-indexer/hs_err_pid%p.log, -Xlog:gc*,gc+age=trace,safepoint:file=/var/log/wazuh-indexer/gc.log:utctime,pid,tags:filecount=32,filesize=64m, -Djava.security.manager=allow, -Djava.util.concurrent.ForkJoinPool.common.threadFactory=org.opensearch.secure_sm.SecuredForkJoinWorkerThreadFactory, -XX:MaxDirectMemorySize=1073741824, -Dopensearch.path.home=/usr/share/wazuh-indexer, -Dopensearch.path.conf=/etc/wazuh-indexer, -Dopensearch.distribution.type=rpm, -Dopensearch.bundled_jdk=true]
[2025-02-25T15:36:21,307][WARN ][o.o.c.r.a.AllocationService] [node-1] Falling back to single shard assignment since batch mode disable or multiple custom allocators set


Anyone can help me figure this out?
everything seems to working fine but still finding this issue.

[Roman Luna]

Hi,

Is the dashboard working? And you see all the alerts being shown? If that is the case, when do these errors shows up? What version of Wazuh are you running? Are there any custom plugins that you have installed? It is possible to download plugins from opensearch (as many come by default) for example.

In any case, I would recommend installing the latest version, nonetheless, this does not look like to be a problem in the functioning of the service.

Regards.

[Zaks Ace]

Dashboard isnt working  "Wazuh dashboard server is not ready yet" 
These error are from cat /var/log/wazuh-indexer/wazuh-cluster.log | grep -i "ERROR" "WARN" I got alot of same errors regrading this how ever I have select single so that it wont be an issue. No custom plugins installs. 
My simple issue is wazuh dashboard server is not ready yet 

[Roman Luna]

Please, do an API call with the following:

curl -k -u UserName:Password -XGET "https://localhost:9200/_cluster/health?pretty=true"

This is to check how many shards you have active and the status of the cluster, if it is full you should manually delete older indices first and then you can apply a policy: Index lifecycle management - Wazuh indexer cluster, here is a guide related to how it works.

Here is the delete command:

curl -k -u UserName:Password -XDELETE "https://localhost:9200/<INDEX-NAME>"

[Zaks Ace]

Issue is fixed. However I have changed the password from here 
/usr/share/wazuh-dashboard/data/wazuh/config/wazuh.yml

I have change the setting user and password. i want to make it default back. Can you please tell me how to do it?