yes...i did but didn't work
[root@SI3417-9 ~]# sudo systemctl start elasticsearch.service
Job for elasticsearch.service failed because the control process exited with error code. See "systemctl status elasticsearch.service" and "journalctl -xe" for details.
[root@SI3417-9 ~]# sudo systemctl status elasticsearch.service
● elasticsearch.service - Elasticsearch
Loaded: loaded (/usr/lib/systemd/system/elasticsearch.service; enabled; vendor preset: disabled)
Active: failed (Result: exit-code) since Thu 2023-07-27 14:00:17 KST; 20s ago
Docs: https://www.elastic.co
Process: 21675 ExecStart=/usr/share/elasticsearch/bin/systemd-entrypoint -p ${PID_DIR}/elasticsearch.pid --quiet (code=exited, status=1/FAILURE)
Main PID: 21675 (code=exited, status=1/FAILURE)
Jul 27 14:00:17 SI3417-9 systemd[1]: Starting Elasticsearch...
Jul 27 14:00:17 SI3417-9 systemd-entrypoint[21675]: /usr/share/elasticsearch/bin/elasticsearch-env: line 78: /etc/sysconfig/elasticsearch: Permission denied
Jul 27 14:00:17 SI3417-9 systemd[1]: elasticsearch.service: main process exited, code=exited, status=1/FAILURE
Jul 27 14:00:17 SI3417-9 systemd[1]: Failed to start Elasticsearch.
Jul 27 14:00:17 SI3417-9 systemd[1]: Unit elasticsearch.service entered failed state.
Jul 27 14:00:17 SI3417-9 systemd[1]: elasticsearch.service failed.type or paste code here