Sorry for delay in responding, but I was able to identify the root cause and fix the problem. It turned out to be trivial!
The problem was that the person who created the output config file for Logstash to write syslog messages to hard drive, wrote the path for the directory where the messages were to be written without the initial forward slash, thus making the path relative, instead of absolute. This caused Logstash to attempt to write files to a non existing directory (using /usr/share/logstash as starting point, which was not as intended) which of course resulted in the access permission error.
Once I converted the paths to absolute and restarted logstash the problem disappeared.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.