So my database server has been terminated 3 times today. In all cases the machine was fine - my application server was merrily reading and writing to it when it suddenly went down, the only indication of trouble was a log entry in scalr.net saying that Scalr was about to terminate it because Scalr figured it was hung.
I'd love to know why Scalr hates my db machine. On Jul 24, 10:02 am, Rod Frey <[email protected]> wrote: > One of my instances on scalr.net is being terminated every day or > two. The log error is always something like: > > ------ > Instance xxxx doesn't respond to SNMP. Scalr was able to open > connection to UDP port 161, but snmp doesn't respond. Most likely > snmpd is hung up. Try to restart it with /etc/init.d/snmpd restart > ------ > > I haven't mucked with any settings relevant to Scalr AFAIK. Any > suggestions? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
