Before you dig into reading this guide, have you tried asking OpsGPT what this log means? You’ll receive a customized analysis of your log.
Try OpsGPT now for step-by-step guidance and tailored insights into your OpenSearch operation.
Briefly, this error occurs when OpenSearch is unable to access the system’s physical memory information. This could be due to insufficient permissions, incorrect configuration, or an unsupported operating system. To resolve this issue, you can try running OpenSearch with administrative privileges, checking your system’s configuration for errors, or ensuring that your operating system is compatible with OpenSearch. Additionally, you may want to update your OpenSearch version to the latest one, as this could also be a bug that has been fixed in a newer release.
For a complete solution to your to your search operation, try for free AutoOps for Elasticsearch & OpenSearch . With AutoOps and Opster’s proactive support, you don’t have to worry about your search operation – we take charge of it. Get improved performance & stability with less hardware.
This guide will help you check for common problems that cause the log ” exception retrieving total physical memory ” to appear. To understand the issues related to this log, read the explanation below about the following OpenSearch concepts: memory, monitor.
Log Context
Log “exception retrieving total physical memory” classname is OsProbe.java.
We extracted the following from OpenSearch source code for those seeking an in-depth context :
logger.debug("OS reported a negative total memory value [{}]"; totalMem);
return 0;
}
return totalMem;
} catch (Exception e) {
logger.warn("exception retrieving total physical memory"; e);
return 0;
}
}
/**
