Not able to load MIB File. Getting exception: "Reading/Parsing MIB:java.io.FileNotFoundException: Could not find the file "
Solution: Follow the steps below:
For example, you are not able to load the file "STARHOME-Traps-v21.mib".
1. Open the STARHOME-Traps-v21.mib file and check for this content "DEFINITIONS ::= BEGIN"
Starhome-MIB DEFINITIONS ::= BEGIN
- Here file name and DEFINITIONS are different.
- Update the file name as Starhome-MIB(This is DEFINITIONS name).
- Try to load the Starthome-MIB file. You should be able to load this MIB file now.
New to ADSelfService Plus?
Related Articles
LDAP - Unable to find valid SSL Certificate
If there is an error while adding LDAP Server Monitor with the message "Unable to find valid SSL Certificate", then please try the below steps to troubleshoot the issue. When the error occurs we can find the below traces in the "stderr.txt.*" log ...Adding APM Insight Java agent in a Kubernetes environment
There are three methods for installing the APM Insight Java agent in a Kubernetes environment. Using Dockerfile Using InitContainers Using Persistent Volumes Prerequisites Download the latest APM Insight Java agent (apminsight-javaagent.zip) file. ...How to find the protocol and hostname used by OpManager to load APM Plugin under Applications tab
Login to OpManager Open Network tab of browser developer tools by pressing Ctrl + Shift + I Click on Applications -> Dashboard tab and search for MyPage in search bar of Network tab Click on the first result which has document as value for Type ...How to add an APM Insight Java agent in Kubernetes via InitContainers?
Step 1. Create a secret to access the APM Insight license key in your application namespace: kubectl create secret generic app-secret --from-literal=s247licensekey='your_APMInsight_license_key' -n petclinic The license key can be obtained from the ...Update on the Apache Log4j Vulnerability
A high severity vulnerability ( CVE-2021-44228 ) impacting multiple versions of the Apache Log4j2 utility was disclosed publicly on December 9, 2021. The vulnerability impacts Apache Log4j2 versions below 2.15.0. You can find the details of this ...