-DAWS_ACCESS_KEY_ID=someid -DAWS_SECRET_KEY=somekey On Fri, Oct 23, 2015 at 2:02 PM Jaskaran Singh <[email protected]> wrote:
> Hi Shawn, > > Thanks for your inputs. I am also facing an issue in the > SNSQueueManagerImpl class. I found that the UsergridAwsCredentials class > does find the aws credentials in the System class. > Please advise where / how to set the amazon credentials for the SQS and > SNS clients. > Thank you very much for all the help. > > Thanks > Jaskaran > > On 23 Oct 2015 22:23, "Shawn Feldman" <[email protected]> wrote: > >> make sure ES has the correct clustername, usergrid i think >> >> On Fri, Oct 23, 2015 at 10:52 AM Shawn Feldman <[email protected]> >> wrote: >> >>> run PUT /system/database/setup >>> run PUT /system/database/bootstrap >>> run Get /system/superuser/setup >>> >>> On Fri, Oct 23, 2015 at 6:56 AM Harish Singh Bisht < >>> [email protected]> wrote: >>> >>>> HI Shawn, >>>> >>>> I was able to resolve the previous errors in the master branch. The >>>> database had be to be setup using a PUT request, instead of a GET request >>>> (as in Usergrid 1.0). >>>> >>>> However, now i am encountering an exception in the *SNSQueueManagerImpl >>>> *class - it seems it creates Amazon SQS/SNS clients and is unable >>>> to initialize the client libraries. >>>> I also debugged the code and noted that *UsergridAwsCredentials *class >>>> does 'not' find the amazon access key in the System class. >>>> >>>> I suspect, I'm missing certain properties in my >>>> usergrid-deployment.properties file? Would appreciate if you point me in >>>> the right direction please. >>>> >>>> Thanks in advance for your help >>>> Harish >>>> On Tue, Oct 20, 2015 at 6:50 PM, Shawn Feldman <[email protected] >>>> > wrote: >>>> >>>>> You should use the master branch. >>>>> On Tue, Oct 20, 2015 at 3:55 AM Harish Singh Bisht < >>>>> [email protected]> wrote: >>>>> >>>>>> Hello, >>>>>> >>>>>> I have been evaluating usergrid (two-dot-o) branch and everything is >>>>>> mostly great. >>>>>> >>>>>> Ran into a problem with custom collections. It appears entities >>>>>> (custom collections) get saved initially, but after sometime they're >>>>>> automatically deleted? On further investigation of tomcat logs, I noted >>>>>> the following errors/warning which matched with the deleted UUID >>>>>> >>>>>> 2015-09-17 11:17:22 ERROR >>>>>> serialization.impl.MvccLogEntrySerializationStrategyImpl.parseColumn(447)<collectiontasks-1>- >>>>>> DATA CORRUPTION DETECTED when de-serializing entity with Id >>>>>> SimpleId{uuid=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002, type='product'} and >>>>>> version aa7454cb-5d2d-11e5-8d3d-1271726ccb0d. This means the write was >>>>>> truncated. >>>>>> org.apache.usergrid.persistence.collection.exception.DataCorruptionException: >>>>>> Unable to read entity data >>>>>> >>>>>> 2015-09-17 11:17:22 INFO >>>>>> persistence.cassandra.DB.getAllColumns(390)<http-bio-8080-exec-2>- >>>>>> getColumns cf=Entity_Dictionaries >>>>>> key=aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002:connected_types >>>>>> >>>>>> 2015-09-17 11:28:35 WARN >>>>>> corepersistence.results.EntityVerifier.isValid(99)<http-bio-8080-exec-7>- >>>>>> Entity uuid:aa6efcaa-5d2d-11e5-b9f6-4dce0d97b002 version >>>>>> v:Optional.absent() is deleted but indexed, this is a bug >>>>>> >>>>>> Can someone help me understand what might be going on? >>>>>> >>>>>> Regards, >>>>>> Harish >>>>>> >>>>>> -- >>>>>> Regards, >>>>>> Harish Singh Bisht >>>>>> >>>>>> >>>> >>>> >>>> -- >>>> Regards, >>>> Harish Singh Bisht >>>> >>>>
