Matt,
thanks for those tips, here's what I did with them 8-)
- monit status -> cassandra was not running and would not start
++ classnotfound CassandraDAEMON [case might be wrong]
++ yet I did see log entries where it had run sometime in the past
++ so I surmised that my apt-get update/upgrade might have messed up
something
++ so I decided to start over...
- delete deployment
- resize deployment
- restart cassandra(s)
- I went to homestead and turned on debugging again, and added those logs
- check that cassandra was running 8-) and reproduced failure
- it failed the same, and again the debug messages showed it did not return
from modify_columns
- so I check cassandra...describe keyspace homestead_provisioning....NOT
FOUND !
- Now, keyspace homestead does display several tables, including a
private_ids; not sure which is right
- the netstat shows what I think are normal things...
/usr/share/clearwater/homestead# netstat -anp | grep 9160
tcp 0 0 0.0.0.0:9160 0.0.0.0:* LISTEN
15488/jsvc.exec
tcp 0 0 127.0.0.1:47089 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47091 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47099 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47093 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47095 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47098 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47101 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47096 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47086 127.0.0.1:9160
TIME_WAIT -
tcp 0 0 127.0.0.1:47087 127.0.0.1:9160
TIME_WAIT
What's next?
-John
On Thu, Oct 24, 2013 at 1:04 PM, Matt Williams <[email protected]
> wrote:
> On Thu, Oct 24, 2013 at 17:17:41, John Letourneau wrote:
> > Subject: Re: [Clearwater] New Install, cannot setup new account
> > 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...
>
> Thanks for your email. It seems like you've done some good investigation
> here.
>
> The modify_columns call is a fairly thin wrapper around a call into
> Cassandra. Please can you check that
> - Cassandra is running ("sudo monit status")
> - homestead is connected to Cassandra ("sudo netstat -anp | grep 9160")
> - Cassandra has the correct schema ("cqlsh" and then "describe keyspace
> homestead_provisioning ;")?
>
> Please let me know what you find.
>
> Thanks,
>
> Matt
>
_______________________________________________
Clearwater mailing list
[email protected]
http://lists.projectclearwater.org/listinfo/clearwater
