[Using Sakai] sakai crash on Generic Dao

[Matthew Jones]

Generally if you have a multi-node cluster, only one of the nodes should
have auto.ddl=true. All the others should be auto.ddl=false, usually in
sakai/local.properties. It could be a condition where one node created the
table while the other was in the process of trying to figure out if it
needed to create the table.

In any case you don't want any race conditions like this to come up.
Perhaps this is the problem here.

On Tue, Sep 16, 2014 at 10:30 AM, Anders Nordkvist <anders.nordqvist at his.se>
wrote:

>  Hi,
>
>
>
> New sakai problem :(
>
> We have two nodes of sakai 2.9.x. The first one was running and when I
> started the second one It halted after a while on this log:
>
>
>
> INFO: [GenericDao] Could not execute first DDL line, skipping the rest:
> StatementCallback; bad SQL grammar [CREATE TABLE ENTITY_PROPERTIES (
> id            bigint(20) AUTO_INCREMENT NOT NULL PRIMARY KEY,
> entityRef       varchar(255) NOT NULL, entityPrefix    varchar(255) NOT
> NULL, propertyName    varchar(255) NOT NULL, propertyValue   text NOT NULL,
> INDEX (entityRef, entityPrefix, propertyName) )]; nested exception is
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'entity_properties' already
> exists:com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'entity_properties' already exists
>
> INFO: [GenericDao] Could not execute first DDL line, skipping the rest:
> StatementCallback; bad SQL grammar [CREATE TABLE ENTITY_TAG_APPLICATIONS (
> id            bigint(20) AUTO_INCREMENT NOT NULL PRIMARY KEY,
> entityRef       varchar(255) NOT NULL, entityPrefix    varchar(255) NOT
> NULL, tag             varchar(255) NOT NULL, INDEX (entityRef,
> entityPrefix, tag) )]; nested exception is
> com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'entity_tag_applications' already
> exists:com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Table
> 'entity_tag_applications' already exists
>
>
>
>
>
>
>
> The even bigger problem was that our first node also halted so for a while
> we didn’t have any node up. I had to kill the process on the nodes and
> startup node one once again. So now we only got one node working. Does
> anyone know of this problem?
>
>
>
>
>
> Regards
>
> Anders Nordkvist
>
> System administrator
>
> University Of Skövde
>
> Sweden
>
>
>
>
>
> _______________________________________________
> sakai-user mailing list
> sakai-user at collab.sakaiproject.org
> http://collab.sakaiproject.org/mailman/listinfo/sakai-user
>
> TO UNSUBSCRIBE: send email to
> sakai-user-unsubscribe at collab.sakaiproject.org with a subject of
> "unsubscribe"
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-user/attachments/20140916/365f73c3/attachment-0001.html