[Building Sakai] SiteCache is not alive

[Ryan VanDyke]

Picking through my old log in more detail I found this that I missed before (more importantly the WARN line):

2014-09-18 13:38:13,004  INFO localhost-startStop-1 org.sakaiproject.event.impl.BaseEventTrackingService - org.sakaiproject.event.impl.ClusterEventTracking$$EnhancerByCGLIB$$963f2ec2 at 240e2b96.init()
2014-09-18 13:38:13,004  INFO localhost-startStop-1 org.sakaiproject.event.impl.ClusterEventTracking - org.sakaiproject.event.impl.ClusterEventTracking$$EnhancerByCGLIB$$963f2ec2 at 240e2b96.init() - period: 5 batch: true checkDb: true
2014-09-18 13:38:13,004  INFO localhost-startStop-1 org.sakaiproject.event.impl.ClusterEventTracking - Server Start: serverId=Kratos-Sakai-10.1,serverInstance=1411061892536,serverIdInstance=Kratos-Sakai-10.1-1411061892536,version=10.1/TRUNK
2014-09-18 13:38:13,004  WARN localhost-startStop-1 org.sakaiproject.event.impl.ClusterEventTracking - Legacy memory service is incompatible with event caching, you must use the new memory service (memory.use.legacy=false) with memory.cluster.enabled=true, using legacy (DB based) event propagation instead
2014-09-18 13:38:13,004  INFO localhost-startStop-1 org.sakaiproject.memory.impl.BasicMemoryService - init()
2014-09-18 13:38:13,004  INFO localhost-startStop-1 org.sakaiproject.memory.impl.BaseMemoryService - INIT complete: legacy: BasicMemoryService

Should those lines go into the setenv .bat/.sh? Since I dropped my database and fixed the issue that way I no longer have a test machine to try it on but maybe this will help fix Ahmeds problem.

- Ryan


From: Sam Ottenhoff [mailto:ottenhoff at longsight.com] 
Sent: Thursday, September 18, 2014 2:32 PM
To: Ryan VanDyke
Cc: ahmed adel; Developers Sakai-Dev; pevenson at kratosdefense.com
Subject: Re: [Building Sakai] SiteCache is not alive



On Thu, Sep 18, 2014 at 2:17 PM, Ryan VanDyke <ryan.vandyke at kratosdefense.com> wrote:
Must be bad luck. I had everything working with mysql, compiled source, etc and have been using it for days with no issues. Only now did I shutdown and startup Tomcat again did I start getting these cacheNotAlive errors once more. 


The cache errors are most likely a symptom and not a cause.  You need to look further up in your catalina.out to find out what really failed and caused startup to not succeed.  If anyone posts their full catalina.out somewhere accessible, I'm happy to look, but the cache errors are most likely not your real problem.

 
As I have not touched any of the code or manually touched any data in the database I can only assume there is a problem with one of the core tools in Sakai 10.1 which is corrupting data somehow. I was able to fix the problem only through dropping the MySQL 'sakai' database schema and creating a new one from scratch. The log snippet at the end of this email shows the first instance in the tomcat log of a warning occurring (skipping past the few "table already exists" warnings) and its database related. Several more occur after this. Is this hibernate.id.Generator producing keys too large to be stored? 


No

 
Its mentioned as the problem being "mostly harmless" but unless there is a fix aside from dropping an entire database I would disagree.


The key error is also not your problem. 



 --------------------------------------------------------------------------------------------------------------------

***NOTICE*** This e-mail and/or the attached documents may contain technical data within the definition of the International Traffic in Arms Regulations and/or Export Administration Regulations, and are subject to the export control laws of the U.S. Government. Transfer of this data by any means to a foreign person, whether in the United States or abroad, without an export license or other approval from the U.S. Department of State or Commerce, as applicable, is prohibited. No portion of this e-mail or its attachment(s) may be reproduced without written consent of Kratos Defense & Security Solutions, Inc. Any views expressed in this message are those of the individual sender, except where the message states otherwise and the sender is authorized to state them to be the views of any such entity. The information contained in this message and or attachments is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. If you are not the intended recipient or believe that you may have received this document in error, please notify the sender and delete this e-mail and any attachments immediately.