I noticed that filebeat agent is not shipping the logs, when I tried restarting the service I found the following error. Also, when I run sudo ./filebeat -e output returns nothing. By looking at the logs "permission denied", I re-checked the file permission for the source route but I still see the issue even after modifying the user permissions and group permissions. Can somebody suggest what could be the root cause for the following?
registrar.go:152: Failed to create tempfile (/.filebeat.new) for writing: open /.filebeat.new: permission denied
registrar.go:110: Writing of registry returned error: open /.filebeat.new: permission denied. Continuing..
registrar.go:152: Failed to create tempfile (/.filebeat.new) for writing: open /.filebeat.new: permission denied
registrar.go:110: Writing of registry returned error: open /.filebeat.new: permission denied. Continuing..
registrar.go:152: Failed to create tempfile (/.filebeat.new) for writing: open /.filebeat.new: permission denied
registrar.go:110: Writing of registry returned error: open /.filebeat.new: permission denied. Continuing..
registrar.go:152: Failed to create tempfile (/.filebeat.new) for writing: open /.filebeat.new: permission denied
registrar.go:110: Writing of registry returned error: open /.filebeat.new: permission denied. Continuing..
registrar.go:152: Failed to create tempfile (/.filebeat.new) for writing: open /.filebeat.new: permission denied
registrar.go:110: Writing of registry returned error: open /.filebeat.new: permission denied. Continuing..
Filebeat and filebeat.yml is installed in the same location
-rw-r--r-- 1 xyz xyz 814 Jan 7 10:08 filebeat.template.json
-rwxr-xr-x 1 xyz xyz 12386344 Jan 7 10:08 filebeat
-rw-r--r-- 1 xyz xyz 8992 Jan 7 10:08 filebeat.yml