wazuh-dashboard is failing to start
2,544 views
Skip to first unread message
Anju Abhi
Jun 6, 2023, 12:32:08 AM6/6/23
to Wazuh mailing list
its giving listen EACCESS: permission denied 0.0.0.0:443
What I had done is I took P - to - V of my siem manager(all in one server) and loaded into a VM in another network zone. all the other services seems to be started. but dashboard is not actve . To be precise ports 443 and 9200 is not getting from outside
Aditya Sharma
Jun 6, 2023, 12:48:16 AM6/6/23
to Wazuh mailing list
Hi Anju, Thanks for using Wazuh!
It seems like the issue is related to permission denied on port 443. Have you checked the firewall settings and ensured that the necessary ports are open? Additionally, have you verified that the user running the service has the necessary permissions to access the port? If the issue persists, please provide more details on the environment and configuration to help us better diagnose the issue.
Please share us the wazuh-dashboard configuration from here: /etc/wazuh-dashboard/opensearch_dashboards.yml
Also, the output of the command: journalctl -xe | grep wazuh-dashboard
Regards
Aditya Sharma
It seems like the issue is related to permission denied on port 443. Have you checked the firewall settings and ensured that the necessary ports are open? Additionally, have you verified that the user running the service has the necessary permissions to access the port? If the issue persists, please provide more details on the environment and configuration to help us better diagnose the issue.
Please share us the wazuh-dashboard configuration from here: /etc/wazuh-dashboard/opensearch_dashboards.yml
Also, the output of the command: journalctl -xe | grep wazuh-dashboard
Regards
Aditya Sharma
Anju Abhi
Jun 6, 2023, 1:05:25 AM6/6/23
to Wazuh mailing list
server.host: 0.0.0.0
server.port: 443
opensearch.hosts: https://localhost:9200
opensearch.ssl.verificationMode: certificate
#opensearch.username:
#opensearch.password:
opensearch.requestHeadersAllowlist: ["securitytenant","Authorization"]
opensearch_security.multitenancy.enabled: false
opensearch_security.readonly_mode.roles: ["kibana_read_only"]
server.ssl.enabled: true
server.ssl.key: "/etc/wazuh-dashboard/certs/dashboard-key.pem"
server.ssl.certificate: "/etc/wazuh-dashboard/certs/dashboard.pem"
opensearch.ssl.certificateAuthorities: ["/etc/wazuh-dashboard/certs/root-ca.pem"]
uiSettings.overrides.defaultRoute: /app/wazuh
server.port: 443
opensearch.hosts: https://localhost:9200
opensearch.ssl.verificationMode: certificate
#opensearch.username:
#opensearch.password:
opensearch.requestHeadersAllowlist: ["securitytenant","Authorization"]
opensearch_security.multitenancy.enabled: false
opensearch_security.readonly_mode.roles: ["kibana_read_only"]
server.ssl.enabled: true
server.ssl.key: "/etc/wazuh-dashboard/certs/dashboard-key.pem"
server.ssl.certificate: "/etc/wazuh-dashboard/certs/dashboard.pem"
opensearch.ssl.certificateAuthorities: ["/etc/wazuh-dashboard/certs/root-ca.pem"]
uiSettings.overrides.defaultRoute: /app/wazuh
Anju Abhi
Jun 6, 2023, 1:07:37 AM6/6/23
to Wazuh mailing list
when I run /usr/share/wazuh-dashboard/bin/opensearch-dashboards "-c /etc/wazuh-dashboard/opensearch_dashboards.yml" --allow-root, then the port 443 I got and dashbord GUI came.
I checked using nc -v <ip> port , 443 and 9200 is not connected; all the other ports seems to be connected
when run explicitly with --allow-root, option 443 got connected but 9200 refused
Anju Abhi
Jun 6, 2023, 1:13:01 AM6/6/23
to Wazuh mailing list
journalctl -xe|grep wazuh-dashboard
Jun 05 22:58:19 siem systemd[1]: wazuh-dashboard.service: Consumed 5.031s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 05 22:58:20 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:58:22 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:58:23 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:58:23 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:59:32 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:59:34 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 05 22:59:39 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 05 22:59:39 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 05 22:59:39 siem systemd[1]: wazuh-dashboard.service: Consumed 5.296s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 05 23:00:00 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 05 23:00:05 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 05 23:00:05 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 05 23:00:05 siem systemd[1]: wazuh-dashboard.service: Consumed 5.053s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 05 23:00:17 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 05 23:00:22 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 05 23:00:22 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 05 23:00:22 siem systemd[1]: wazuh-dashboard.service: Consumed 5.073s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 06 06:01:37 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:01:38 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:04:15 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:04:16 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:05:38 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:05:39 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:03 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:04 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:20 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:21 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:23 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:13:57 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:04 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:04 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:43 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:43 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:44 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:44 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:32 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:37 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:37 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:42 siem sudo[111179]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl enable wazuh-dashboard
Jun 06 15:17:42 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:42 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:48 siem sudo[111218]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl start wazuh-dashboard
Jun 06 15:17:49 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 06 15:17:53 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 06 15:17:53 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 06 15:17:53 siem systemd[1]: wazuh-dashboard.service: Consumed 5.106s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 06 15:18:19 siem sudo[111242]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard
Jun 06 15:18:19 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:28:07 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:28:08 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:31:09 siem sudo[112390]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl stop wazuh-dashboard
Jun 06 15:31:17 siem sudo[112394]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl start wazuh-dashboard
Jun 06 15:31:17 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 06 15:31:21 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 06 15:31:21 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 06 15:31:21 siem systemd[1]: wazuh-dashboard.service: Consumed 5.112s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 06 15:31:21 siem sudo[112419]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard
Jun 06 15:31:21 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:34:32 siem sudo[112474]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard -1
Jun 06 15:34:34 siem sudo[112477]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard -l
Jun 06 15:43:50 siem sudo[112510]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard -l
Jun 06 15:44:17 siem sudo[112526]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/share/wazuh-dashboard/bin/opensearch-dashboards -c /etc/wazuh-dashboard/opensearch_dashboards.yml
Jun 06 15:44:30 siem sudo[112540]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/share/wazuh-dashboard/bin/opensearch-dashboards -c /etc/wazuh-dashboard/opensearch_dashboards.yml --allow-root
Jun 05 22:58:19 siem systemd[1]: wazuh-dashboard.service: Consumed 5.031s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 05 22:58:20 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:58:22 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:58:23 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:58:23 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:59:32 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 05 22:59:34 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 05 22:59:39 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 05 22:59:39 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 05 22:59:39 siem systemd[1]: wazuh-dashboard.service: Consumed 5.296s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 05 23:00:00 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 05 23:00:05 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 05 23:00:05 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 05 23:00:05 siem systemd[1]: wazuh-dashboard.service: Consumed 5.053s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 05 23:00:17 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 05 23:00:22 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 05 23:00:22 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 05 23:00:22 siem systemd[1]: wazuh-dashboard.service: Consumed 5.073s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 06 06:01:37 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:01:38 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:04:15 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:04:16 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:05:38 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:05:39 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:03 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:04 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:20 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:21 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 06:07:23 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:13:57 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:04 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:04 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:43 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:43 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:44 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:14:44 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:32 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:37 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:37 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:42 siem sudo[111179]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl enable wazuh-dashboard
Jun 06 15:17:42 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:42 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:17:48 siem sudo[111218]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl start wazuh-dashboard
Jun 06 15:17:49 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 06 15:17:53 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 06 15:17:53 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 06 15:17:53 siem systemd[1]: wazuh-dashboard.service: Consumed 5.106s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 06 15:18:19 siem sudo[111242]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard
Jun 06 15:18:19 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:28:07 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:28:08 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:31:09 siem sudo[112390]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl stop wazuh-dashboard
Jun 06 15:31:17 siem sudo[112394]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl start wazuh-dashboard
Jun 06 15:31:17 siem systemd[1]: Started wazuh-dashboard.
░░ Subject: A start job for unit wazuh-dashboard.service has finished successfully
░░ A start job for unit wazuh-dashboard.service has finished successfully.
Jun 06 15:31:21 siem systemd[1]: wazuh-dashboard.service: Main process exited, code=exited, status=1/FAILURE
░░ An ExecStart= process belonging to unit wazuh-dashboard.service has exited.
Jun 06 15:31:21 siem systemd[1]: wazuh-dashboard.service: Failed with result 'exit-code'.
░░ The unit wazuh-dashboard.service has entered the 'failed' state with result 'exit-code'.
Jun 06 15:31:21 siem systemd[1]: wazuh-dashboard.service: Consumed 5.112s CPU time.
░░ The unit wazuh-dashboard.service completed and consumed the indicated resources.
Jun 06 15:31:21 siem sudo[112419]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard
Jun 06 15:31:21 siem systemd[1]: Configuration file /etc/systemd/system/wazuh-dashboard.service is marked world-inaccessible. This has no effect as configuration data is accessible via APIs without restrictions. Proceeding anyway.
Jun 06 15:34:32 siem sudo[112474]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard -1
Jun 06 15:34:34 siem sudo[112477]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard -l
Jun 06 15:43:50 siem sudo[112510]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/bin/systemctl status wazuh-dashboard -l
Jun 06 15:44:17 siem sudo[112526]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/share/wazuh-dashboard/bin/opensearch-dashboards -c /etc/wazuh-dashboard/opensearch_dashboards.yml
Jun 06 15:44:30 siem sudo[112540]: root : TTY=pts/0 ; PWD=/root ; USER=root ; COMMAND=/usr/share/wazuh-dashboard/bin/opensearch-dashboards -c /etc/wazuh-dashboard/opensearch_dashboards.yml --allow-root
Aditya Sharma
Jun 9, 2023, 3:52:52 AM6/9/23
to Wazuh mailing list
Hi Anju,
Looking for your response soon!
Can you please run the below commands on the wazuh-dashboard server and then try to restart wazuh-dashboard.
Looking for your response soon!
Reply all
Reply to author
Forward
0 new messages