dotCMS 2.5.2 64-bit installation

[tornado]

I'm evaluating dotCMS and I can't get it to install correctly.

Environment: Windows Vista 64-bit (6.1.7601), installed with
dotcms_64bit_2_5_2.exe, using all defaults; installed dotCMS as a Windows
service.

The first issue is that the error log complained about the
c:\dotCMS\tomcat\temp folder not existing. Even when I created the folder,
dotCMS had problems. I ended up uninstalling dotCMS, then manually creating
the c:\dotCMS\tomcat\temp folder, and then reinstalling. That worked
better, but I still have problems:

During startup, I get the following error in wrapper_*.log:
2013/12/29 16:43:29 | ERROR: Error parsing system bundle export statement:
org.osgi.framework; version=1.7.0, org.osgi.framework.hooks.bundle;
version=1.1.0, org.osgi.framework.hooks.resolver;.....

The error line is very long and I will upload it here if you want, but it
seems to be a list of many, many class files.

The interesting part of the stack trace that follows the error message is:

2013/12/29 16:43:29 | at
org.apache.felix.framework.Felix.<init>(Felix.java:385)
2013/12/29 16:43:29 | at
org.apache.felix.framework.FrameworkFactory.newFramework(FrameworkFactory.java:28)
2013/12/29 16:43:29 | at
com.dotmarketing.util.OSGIUtil.initializeFramework(OSGIUtil.java:136)
2013/12/29 16:43:29 | at
com.dotmarketing.listeners.OsgiFelixListener.contextInitialized(OsgiFelixListener.java:14)
2013/12/29 16:43:29 | at
org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3972)
2013/12/29 16:43:29 | at
org.apache.catalina.core.StandardContext.start(StandardContext.java:4467)

During startup, I get an error about a ContextIndexationThread not being
available. Here is the log entry (with some context):

[29/12/13 16:43:35:491 EST] INFO startup.StartupTasksExecutor: Starting
upgrade tasks.
[29/12/13 16:43:35:491 EST] INFO startup.StartupTasksExecutor: Database
version: 1075
[29/12/13 16:43:35:493 EST] ERROR reindex.ReindexThread: No
ContentIndexationThread available
[29/12/13 16:43:35:494 EST] INFO reindex.ReindexThread:
ContentIndexationThread ordered to start processing

About one second later, I get:
2013/12/29 16:43:30 | ERROR: Bundle org.apache.felix.bundlerepository [1]
Error starting
file:/C:/dotCMS/tomcat/webapps/../../dotCMS/WEB-INF/felix/bundle/org.apache.felix.bundlerepository-1.6.6.jar
(org.osgi.framework.BundleException: Unresolved constraint in bundle
org.apache.felix.bundlerepository [1]: Unable to resolve 1.0: missing
requirement [1.0] osgi.wiring.package;
(&(osgi.wiring.package=org.osgi.framework)(version>=1.4.0)(!(version>=2.0.0))))
2013/12/29 16:43:30 | org.osgi.framework.BundleException: Unresolved
constraint in bundle org.apache.felix.bundlerepository [1]: Unable to
resolve 1.0: missing requirement [1.0] osgi.wiring.package;
(&(osgi.wiring.package=org.osgi.framework)(version>=1.4.0)(!(version>=2.0.0)))
2013/12/29 16:43:30 | at
org.apache.felix.framework.Felix.resolveBundleRevision(Felix.java:3974)
2013/12/29 16:43:30 | at
org.apache.felix.framework.Felix.startBundle(Felix.java:2037)
2013/12/29 16:43:30 | at
org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1291)
2013/12/29 16:43:30 | at
org.apache.felix.framework.FrameworkStartLevelImpl.run(FrameworkStartLevelImpl.java:304)
2013/12/29 16:43:30 | at java.lang.Thread.run(Thread.java:662)

Moments later, in dotcms.log, I get a warning that shard failed to start.
This sequence repeats around 14 times per second until I shut down the
service:

[29/12/13 16:43:41:921 EST] WARN indices.cluster: [dotCMS_1]
[working_20131218141222][0] failed to start shard
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException:
[working_20131218141222][0] shard allocated for local recovery (post api),
should exists, but doesn't
at
org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:122)
at
org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:177)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
[29/12/13 16:43:41:932 EST] WARN indices.cluster: [dotCMS_1]
[live_20131218141222][0] failed to start shard
org.elasticsearch.index.gateway.IndexShardGatewayRecoveryException:
[live_20131218141222][0] shard allocated for local recovery (post api),
should exists, but doesn't
at
org.elasticsearch.index.gateway.local.LocalIndexShardGateway.recover(LocalIndexShardGateway.java:122)
at
org.elasticsearch.index.gateway.IndexShardGatewayService$1.run(IndexShardGatewayService.java:177)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)

The good news is that despite these errors, I'm able to access the demo site
and I'm able to log in as an administrator. The problem is that the CPU is
churning at 30% to keep up with the error messages being spammed to the
logs.

What do I need to do?



--
View this message in context: http://forumarchive.dotcms.com/dotCMS-2-5-2-64-bit-installation-tp5720526.html
Sent from the dotCMS Users Group mailing list archive at Nabble.com.

[Will Ezell]

Tornado:

Try to run a full reindex from the CMS administrator portlet.  It is under "System > Maintenance > Index"  There should be a button that says "Reindex".  Hit that and see if it completes normally and if your index errors go away.

Also, some questions - have you made any changes to the dotmarketing-config.properties file?  And did you install into the default dotcms windows install directory?

-Will

[cur...@decompile.com]

Will,

Thank you for your reply.

Reindexing did not make any difference.  I have the same result after as I did before.  I even stopped/started the dotCMS service and that made no difference either.

I have also tried created a MySQL database.  It has the exact same problem.  

When I reindexed, the browser asked how many shards I wanted to use.  Not knowing anything, I chose the default (1).  

In MySQL, it went through the motions of reindexing but it had no effect on the spam of warning messages in the dotCMS.log file.

In Postgres, The default (1) caused the reindex process to hang and the warning messages continued to spam.  So I stopped/started dotCMS, and I tried again with 2.  That time I got the same result as in MySQL: it went through the motions of reindexing but nothing changed in the spam of warning messages.

I need to make one correction in my original post: I'm using Windows 7, not Vista.

To answer your questions: I have not made any changes to the dotmarketing-config.properties file and I installed dotcms into the default directory (with the prerequisite of a \dotcms\tomcat\temp folder to make the installation happy).

Curtis

[cur...@decompile.com]

SOLVED: 

1) Stop the dotCMS service

2) Delete the the following folders (and all subfolders and content):

• C:\dotcms_backup\dotCMS\dotsecure\esdata\dotCMSContentIndex\nodes\0\indices\live_20131218141222
  
• C:\dotcms_backup\dotCMS\dotsecure\esdata\dotCMSContentIndex\nodes\0\indices\working_20131218141222
  

3) Restart dotCMS.  The infinite spam of warning messages about shard do not appear anymore.

Curtis

[cur...@decompile.com]

Correction: the path should have been:  c:\dotcms\...,  not c:\dotcms_backup\....