I am running Scalr 1.0 RC3 on a fedora 7 box with net-snmp and net- snmp-utils (which contains snmptrap) installed.
My farms would start and the logs would show the instances had initialized, but never finished host startup. After some experimentation, I was able to correct this by forcing SendTrap in app/ src/LibWebta/library/NET/SNMP/class.SNMP.php to use port 162 instead of 161. Now things seem to be running just fine, although I'm still testing. I am unfamiliar with snmp and snmptrap - should /usr/bin/snmptrap have defaulted to port 162, making this a fedora-specific issue? While I'm on the subject, I'm sure snmp/snmptrap are configured correctly on the farm instances, but I'm not so sure about my Scalr server. Does snmpd and/or snmptrapd need to be running? Are there any specific configuration settings needed for either of these daemons? I have them running in their default configuration, but the snmptrap problem mentioned above makes me wonder what else I might have missed. Many thanks for your patience! --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "scalr-discuss" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/scalr-discuss?hl=en -~----------~----~----~----~------~----~------~--~---
