Hi Matt, I have been doing some digging and this is where I am at so far... - on homestead, I turned on debugging - the last message I saw was "Creating private ID" [under crest provisioning] - I added 2 new debug statements after each yield in models.py, line 302 - neither of those is printed...so the yield to modify_columns is the never returned
Not sure if that helps...more digging to do... -John On Thu, Oct 24, 2013 at 10:19 AM, John Letourneau <[email protected]>wrote: > Hi Matt, > bottom line is...no love on my EC2 deployment. > > - I deleted the old deployment > - I noticed the security groups remained, so I removed those manually > - on the chef-client I did a "git pull"...it indicated I was already on > the latest chef > - I resized a new deployment; also restarted cassandra > - I checked the homestead changelog...it shows a build from 23 Oct. [fresh > stuff!] > - I did a signup on ellis web, and watched the logs on ellis and > homestead...same messages as before > - I tried an apt-get update/upgrade and reboot on ellis and homestead > - I went back to the ellis web page...same result > > What should we look at next? > -John > > > On Thu, Oct 24, 2013 at 9:21 AM, Matt Williams < > [email protected]> wrote: > >> On Thu, Oct 24, 2013 at 12:22:42, John Letourneau wrote: >> > in regards to my issue of ellis having a timeout with homestead, >> > should I try to reinstall my EC2 instance with today's new release? >> > [per Alex's post yesterday] If yes, would you happen to know if the >> > chef cookbooks need to be updated on the client? [I will likely pull >> > changes regardless 8-) ] >> >> I think this may have been caused by >> https://github.com/Metaswitch/crest/issues/74. >> >> Yes, I think the best bet is to reinstall all your nodes with today's >> release. (Since you're using chef, this should be reasonably >> straight-forward.) >> >> Yes, I'd recommend updating the chef cookbooks as there are some changes. >> These might not affect you immediately, but they'll reduce the chance of >> you being tripped up in future. >> >> Thanks, >> >> Matt >> > >
_______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
