-
Notifications
You must be signed in to change notification settings - Fork 15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
snmp-mongodb and snmp-redis-master in CrashLoopBackOff status #894
Comments
Could you share the output of |
When I search repo snmp I see the following app version. This was what I redeployed yesterday trying to troubleshoot the issue. NAME CHART VERSION APP VERSION DESCRIPTION Below is the output snmp-redis-master-0
snmp-mongodb-75b89b595f-qftj9
|
Can you reinstall the sc4snmp and then collect the logs and pvc information for redis and mongo with commands:
|
Got it. I uninstalled microk8s to remove all of the pods. I'm following this guide for installation - https://splunk.github.io/splunk-connect-for-snmp/main/gettingstarted/sc4snmp-installation/ Here are the requested outputs after reinstalling -
|
From what I saw about redis it's about permission and in this issue it's mentioned that it can be solved by enabling volumePermissions. To do it you can add it into yours value.yaml like this:
And reinstall the snmp, you can uninstall with the mentioned link. If that doesn't work you can look at those links for more informations: About mongodb, I found that mongo above version 5 requires to run on cpu with avx. Please check if your environment supports that, as we are currently running mongodb in v6 in sc4snmp. |
This worked. The redis pod is now running. I'm working with the VI team to understand why my virtual device doesn't have an AVX flag from the CPU. I'll update the issue when I hear back from them on a solution. Thanks. |
Is there a way or can you provide any information on downgrading the MongoDB package to version 4? It appears that was the solution for a lot of individuals that were not able to provide AVX support for a guest device. In our case the virtualization platform will not pass the AVX instruction set from the VI host to the guest. If it turns out we can't use an older MongoDB version we may have to scrap this sc4snmp project. |
First option is to run the last version of sc4snmp that used mongo v4, which is 1.8.4. I'm not sure if the latest version of code will be compatible with the older mongo but you can try to update it.
Run: |
This got all of the pods running, However, there is now some fuss from the trap pods that appears to be a similar open issue from a year ago
When I run
That's for both traps pods. Curling my Splunk instance with the assigned HEC token generates an event. Sending a test SNMP trap generates an event in TCPDump on the sc4snmp host. But the trap event does not get sent to Splunk Cloud nor do I see the port 443 traffic that would suggest it's being sent. I'm thinking that trap pod isn't running and won't receive trap events. Here is
|
I wanted to add that I have been able to get the pods running effectively with the latest and greatest code. VI team was able to pass the AVX instruction set to my SNMP server. However, after reinstalling the above issue still exists with the "Still waiting for redis-headless" log events from traps. And SNMP traps are not getting sent to Splunkcloud. i believe as a result of the "Still waiting..." issue. |
The "Still waiting ..." most of the times is caused by the kubernetes dns issues. It was similar with the issue you referenced above.
|
Issue during initial configuration. Followed steps to run
microk8s helm3 upgrade --install snmp -f values.yaml splunk-connect-for-snmp/splunk-connect-for-snmp --namespace=sc4snmp --create-namespace
After running
microk8s kubectl get pods -n sc4snmp
to verify deployment I seesnmp-redis-master-0
andsnmp-mongodb-...
are in a CrashLoopBackOff status.I'm running on an ESXi hosted Rocky linux VM with plenty of resources.
The text was updated successfully, but these errors were encountered: