Rebundle log for all these attempts says 'Instance did not reply on SNMP trap. Make sure that snmpd and snmptrapd are running. '.
snmptrapd is not running on this instance and port 162 is used by another software. On Sat, May 16, 2009 at 11:52 PM, BTE <[email protected]> wrote: > > The rebundle failied again. Any ideas? > > app-bteservice-20090516 was the latest failure. > > > On May 16, 12:11 am, Nickolas Toursky <[email protected]> wrote: >> Rebundle log for this role says "Instance did not reply on SNMP trap. >> Make sure that snmpd and snmptrapd are running.". >> And that's it, snmptrapd on this instance was stuck. >> I've restarted it. There should be no more problem rebundling the instance. >> >> >> >> On Sat, May 16, 2009 at 1:30 AM, BTE <[email protected]> wrote: >> >> > My fault I had the wrong farm id. >> >> > The farm id with the app instance failing rebundling is 1091 >> >> > on the last page of roles: app-bteservice-20090514 >> >> > has failed rebundling... trying again right now... >> >> > On May 15, 12:03 am, Nickolas Toursky <[email protected]> wrote: >> >> Hi, >> >> >> As I can see your app instance was rebundled without problem. >> >> >> Go to Roles->View all (last page), and you can see its status as 'Active'. >> >> >> Nick >> >> >> On Fri, May 15, 2009 at 9:48 AM, BTE <[email protected]> wrote: >> >> >> > the app instance is failing to rebundle. >> >> >> > Can you please help? I am trying to make permanent some recent >> >> > changes.- Hide quoted text - >> >> >> - Show quoted text -- Hide quoted text - >> >> - Show quoted text - > > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
