Versions (relevant - OpenSearch/Dashboard/Server OS/Browser): 2.9.0
Describe the issue: Start the single node opensearch1.3.1.tar version node-2 first, and then add a data node nodes-1 of opensearch2.9.0.rpm version. It was found that the data node node-1 reported an error. Please refer to the errorlog for details
Errorlog:
[2023-11-07T17:05:46,005][ERROR][o.o.p.c.e.EventLogFileHandler] [node-1] Error writing entry ‘NOT_INITIALIZED’. Cause:
java.nio.file.AccessDeniedException: /dev/shm/performanceanalyzer/1699347945000.tmp
at sun.nio.fs.UnixException.translateToIOException(UnixException.java:90) ~[?:?]
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:106) ~[?:?]
at sun.nio.fs.UnixException.rethrowAsIOException(UnixException.java:111) ~[?:?]
at sun.nio.fs.UnixFileSystemProvider.newByteChannel(UnixFileSystemProvider.java:218) ~[?:?]
at java.nio.file.spi.FileSystemProvider.newOutputStream(FileSystemProvider.java:484) ~[?:?]
at java.nio.file.Files.newOutputStream(Files.java:228) ~[?:?]
at org.opensearch.performanceanalyzer.commons.event_process.EventLogFileHandler.writeTmpFileWithPrivilege(EventLogFileHandler.java:80) [performance-analyzer-commons-1.0.0.jar:?]
at org.opensearch.performanceanalyzer.commons.event_process.EventLogFileHandler.lambda$writeTmpFile$0(EventLogFileHandler.java:47) [performance-analyzer-commons-1.0.0.jar:?]
at org.opensearch.performanceanalyzer.commons.util.Util.lambda$invokePrivileged$1(Util.java:57) [performance-analyzer-commons-1.0.0.jar:?]
at java.security.AccessController.doPrivileged(AccessController.java:318) [?:?]
at org.opensearch.performanceanalyzer.commons.util.Util.invokePrivileged(Util.java:53) [performance-analyzer-commons-1.0.0.jar:?]
at org.opensearch.performanceanalyzer.commons.event_process.EventLogFileHandler.writeTmpFile(EventLogFileHandler.java:47) [performance-analyzer-commons-1.0.0.jar:?]
at org.opensearch.performanceanalyzer.writer.EventLogQueueProcessor.purgeQueueAndPersist(EventLogQueueProcessor.java:152) [opensearch-performance-analyzer-2.9.0.0.jar:2.9.0.0]
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:539) [?:?]
at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:305) [?:?]
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:305) [?:?]
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136) [?:?]
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635) [?:?]
at java.lang.Thread.run(Thread.java:833) [?:?]
Reason for error reporting：Permission issues
The account used for the 1.3.0 version of Node-2 that was first launched is: elk
The account used for the newly added data node version 2.9.0 of node-1 is: opensearch
After investigation, it was found that the error path of node-1,/dev/shm/performanceanalyzer, belongs to elk. (Previously, an elk account was used to launch a test node for a tar package, resulting in the directory belonging to elk.) Modify the corresponding directory to belong to opensearch, or modify the startup account number of node-1 to elk and simultaneously modify the data, log, and configuration directories to belong to elk
Solution：
Scheme two I used.
Scheme one：
chown -R opensearch:opensearch performanceanalyzer
Scheme two：
chwon -R elk:elk /etc/opensearch/
chwon -R elk:elk /var/log/opensearch/
chwon -R elk:elk /var/lib/opensearch/
OK