You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@usergrid.apache.org by "Prerak Rustagi (JIRA)" <ji...@apache.org> on 2017/12/07 13:07:00 UTC
[jira] [Commented] (USERGRID-1321) Usergrid 2.2 Master, Tomcat
Startup Error: unconfigured columnfamily Data_Migration_Info
[ https://issues.apache.org/jira/browse/USERGRID-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16281817#comment-16281817 ]
Prerak Rustagi commented on USERGRID-1321:
------------------------------------------
This error is thrown because the usergrid startup code requires / expects some tables in the "Usergrid_Applications" keyspace.
The earlier 2.1.0 version doesn't check for these tables and starts the server.
In v2.1.0 - PUT http://localhost:8080/system/database/setup, creates "Usergrid_Applications" keyspace along with the required tables.
Try these steps (only if you are using fresh installation of cassandra)
1. Clear data (if any).
2. Create the Locks keyspace.
3. Run usergrid v2.1.0 and execute the above database setup API.
4. Remove the above usergrid version from Tomcat.
5. Now add the latest (master branch) usergrid ROOT.war and restart tomcat.
> Usergrid 2.2 Master, Tomcat Startup Error: unconfigured columnfamily Data_Migration_Info
> ----------------------------------------------------------------------------------------
>
> Key: USERGRID-1321
> URL: https://issues.apache.org/jira/browse/USERGRID-1321
> Project: Usergrid
> Issue Type: Story
> Components: Stack
> Affects Versions: 2.2.0
> Environment: OS: Ubuntu 14.04;
> Cassandra version: 2.2.6 (DataStax);
> Elasticsearch version: 1.4.4;
> Tomcat version: 7;
> JDK version: 1.8.0_65 (Oracle);
> Usergrid version: 2.2.0 Master branch
> Reporter: Jaskaran
> Fix For: 2.2.0
>
>
> We have been encountering INSTALLATION issues with Usergrid 2.2 Master (Since September 3, 2016).
> Specifically tomcat fails to start, giving errors which indicate that usergrid application was expecting certain keyspaces/columns, BUT did not find them. We have tried to setup the database via the standard calls (below), but apparatently it does not help. As stated, the problem started occuring after the commit on September 3, 2016 (hash tag 461076c389ba8413cbbb1b596dba9439af35a8b9)
> Tomcat startup logs - specifically, we see two types of errors
> *(A) unconfigured columnfamily Data_Migration_Info*
> {code}
> 10:47:45,021 INFO Schema:339 - Registering class org.apache.usergrid.persistence.entities.Receipt
> 10:47:45,028 INFO Schema:339 - Registering class org.apache.usergrid.persistence.DynamicEntity
> 10:47:45,034 INFO Schema:275 - Schema initialized
> 10:47:45,159 WARN Slf4jConnectionPoolMonitorImpl:31 - BadRequestException: [host=172.31.32.243(172.31.32.243):9160, latency=53(85), attempts=1]InvalidRequestException(why:unconfigured columnfamily Data_Migration_Info)
> 10:47:45,200 WARN Slf4jConnectionPoolMonitorImpl:31 - BadRequestException: [host=172.31.32.243(172.31.32.243):9160, latency=21(21), attempts=1]InvalidRequestException(why:unconfigured columnfamily Entity_Version_Data)
> 10:47:45,206 WARN Slf4jConnectionPoolMonitorImpl:31 - BadRequestException: [host=172.31.32.243(172.31.32.243):9160, latency=0(0), attempts=1]InvalidRequestException(why:unconfigured columnfamily Entity_Version_Data)
> 10:47:45,211 INFO XmlWebApplicationContext:1376 - Bean 'entityManagerFactory' of type [class org.apache.usergrid.corepersistence.CpEntityManagerFactory] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
> {code}
> *(B) keyspace 'Locks' does not exist*
> {code}
> 10:47:47.842 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [http-nio-8080]
> 10:47:47.853 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler [ajp-nio-8009]
> 10:47:47.854 INFO [main] org.apache.catalina.startup.Catalina.start Server startup in 19119 ms
> 10:47:51,331 WARN Slf4jConnectionPoolMonitorImpl:31 - BadRequestException: [host=172.31.32.243(172.31.32.243):9160, latency=0(0), attempts=1]InvalidRequestException(why:Keyspace 'Locks' does not exist)
> 10:47:56,333 WARN Slf4jConnectionPoolMonitorImpl:31 - BadRequestException: [host=172.31.32.243(172.31.32.243):9160, latency=1(1), attempts=1]InvalidRequestException(why:Keyspace 'Locks' does not exist)
> 10:48:01,334 WARN Slf4jConnectionPoolMonitorImpl:31 - BadRequestException: [host=172.31.32.243(172.31.32.243):9160, latency=1(1), attempts=1]InvalidRequestException(why:Keyspace 'Locks' does not exist)
> {code}
> *Database Setup & Init calls* (we use these, but they do not help the problem)
> If we try hit the http://localhost:8080/system/database/setup API (after we see the above error), the API fails with the following error/response
> {code}
> {"error":"runtime","timestamp":1234567890,"duration":0,"error_description":"Error migrating Core Persistence","exception":"java.lang.RuntimeException"}
> {code}
> While the issue appear to link to the discussion in JIRA-https://issues.apache.org/jira/browse/USERGRID-1316 - we have tried different configurations (including Cas , Es and tomcat version changes) and that does not help.
> Would appreciate your help in resolving this
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)