John, It looks as though the schema in your Cassandra database is old but the code is expecting the new schema. The schema is initially set up by the homestead package, but then replaced during the clustering phase of the chef scripts.
Please can you check that your chef scripts are up to date? You'll need to issue "git pull" and then follow the instructions for uploading Clearwater definitions to the Chef Server at https://github.com/Metaswitch/clearwater-docs/wiki/Installing%20a%20Chef%20client#upload-clearwater-definitions-to-chef-server. (I know you did a git pull earlier, but it's possible that the new release code hadn't been cut across at that stage.) Please let me know how you get on. Thanks, Matt ________________________________________ From: John Letourneau [[email protected]] Sent: 24 October 2013 20:38 To: Matt Williams Cc: [email protected] Subject: Re: [Clearwater] New Install, cannot setup new account 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<http://0.0.0.0:9160> 0.0.0.0:* LISTEN 15488/jsvc.exec tcp 0 0 127.0.0.1:47089<http://127.0.0.1:47089> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47091<http://127.0.0.1:47091> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47099<http://127.0.0.1:47099> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47093<http://127.0.0.1:47093> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47095<http://127.0.0.1:47095> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47098<http://127.0.0.1:47098> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47101<http://127.0.0.1:47101> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47096<http://127.0.0.1:47096> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47086<http://127.0.0.1:47086> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT - tcp 0 0 127.0.0.1:47087<http://127.0.0.1:47087> 127.0.0.1:9160<http://127.0.0.1:9160> TIME_WAIT What's next? -John _______________________________________________ Clearwater mailing list [email protected] http://lists.projectclearwater.org/listinfo/clearwater
