Two instances of dotCMS on the same server

[Alex]

I need to temporarily set up two instances (one production and another
one testing) of dotCMS on the same server. Production works well, but
the Testing one can not index or bind to port 9013. I changed the
port number, but it still does not find the path to the edata folder.
I hand coded the path into the dotmarketing file, but it still does
not do it.

Any suggestions?

Thanks,

Alex

[Maria Ahues Bouza]

Alex,

What errors are you getting on the logs?

Maria

--
You received this message because you are subscribed to the Google Groups "dotCMS User Group" group.
To post to this group, send email to dot...@googlegroups.com.
To unsubscribe from this group, send email to dotcms+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/dotcms?hl=en.

--
Community Manager

dotCMS
Main: 305.900.2001
Fax: 305.397.2579
www.dotcms.com
http://www.twitter.com/dotCMS
http://www.facebook.com/dotCMS
http://www.twitter.com/mabouza

Please consider the planet before printing this email.

[Swan,Nicole]

Hi Alex,

 

You might already be well past this part, but when I set up two separate instances on the same server I had to make sure each domain name bound to a different IP so there wouldn’t be port conflict.

 

--Nicole

 

From: dot...@googlegroups.com [mailto:dot...@googlegroups.com] On Behalf Of Maria Ahues Bouza
Sent: Thursday, August 23, 2012 4:14 PM
To: dot...@googlegroups.com
Subject: Re: [dotcms] Two instances of dotCMS on the same server

 

Alex,

 

What errors are you getting on the logs?

Maria

 

On Thu, Aug 23, 2012 at 3:02 PM, Alex <alex.t...@ambix.net> wrote:

I need to temporarily set up two instances (one production and another one testing) of dotCMS on the same server.  Production works well, but the Testing one can not index or bind to port 9013.  I changed the port number, but it still does not find the path to the edata folder.  I hand coded the path into the dotmarketing file, but it still does not do it.

Any suggestions?

Thanks,

Alex

--
You received this message because you are subscribed to the Google Groups "dotCMS User Group" group.
To post to this group, send email to dot...@googlegroups.com.

To unsubscribe from this group, send email to dotcms+un...@googlegroups.com.

For more options, visit this group at http://groups.google.com/group/dotcms?hl=en.

 

--
Community Manager

dotCMS
Main: 305.900.2001
Fax: 305.397.2579
www.dotcms.com
http://www.twitter.com/dotCMS
http://www.facebook.com/dotCMS
http://www.twitter.com/mabouza

Please consider the planet before printing this email.

--

You received this message because you are subscribed to the Google Groups "dotCMS User Group" group.
To post to this group, send email to dot...@googlegroups.com.

To unsubscribe from this group, send email to dotcms+un...@googlegroups.com.

[Alex]

Here is the error.  

[22/08/12 21:06:14:322 EDT] ERROR cmsmaintenance.index_005fstats_jsp]: Servlet.service() for servlet org.apache.jsp.html.portlet.ext.cmsmaintenance.index_005fstats_jsp threw exception

org.elasticsearch.ElasticSearchIllegalStateException: Failed to obtain node lock, is the following location writable?: [/opt/dotcms.html2/dotserver2/dotCMS/dotsecure/esdata/dotCMSContentIndex]

at org.elasticsearch.env.NodeEnvironment.<init>(NodeEnvironment.java:123)

at org.elasticsearch.node.internal.InternalNode.<init>(InternalNode.java:120)

at org.elasticsearch.node.NodeBuilder.build(NodeBuilder.java:159)

at com.dotcms.content.elasticsearch.util.ESClient.initNode(ESClient.java:38)

at com.dotcms.content.elasticsearch.util.ESClient.getClient(ESClient.java:25)

at com.dotcms.content.elasticsearch.business.ESContentletIndexAPI.listDotCMSIndices(ESContentletIndexAPI.java:478)

at org.apache.jsp.html.portlet.ext.cmsmaintenance.index_005fstats_jsp._jspService(index_005fstats_jsp.java:338)

at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:70)

at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at com.dotmarketing.filters.CMSFilter.doFilter(CMSFilter.java:128)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at com.dotmarketing.filters.AutoLoginFilter.doFilter(AutoLoginFilter.java:61)

at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:235)

at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206)

at com.dotmarketing.cms.urlmap.filters.URLMapFilter.doFilter(URLMapFilter.java:86)

at org.apache.catalina.core.Application

To unsubscribe from this group, send email to dotcms+un...@googlegroups.com.

[Alex]

Hi, Nicole:

It has worked before on 1.9.5, but now on 2.0.1 it has issues with the indexing only.

Alex

[Maria Ahues Bouza]

Is this the same path the other server is using?

[Will Ezell]

Alex:

One thing to be mindful of  - if these servers are supposed to be running totally separate installs, you will need to change the ElasticSearch ports and the cluster name.  Otherwise, I think the default for Elasticsearch is to run on the same ports and discover other servers running the same cluster name and try to join them.

Make sure these dotmarketing-config.properties are different and don't conflict for each of the installs:

es.cluster.name=xxxxxxxxxxx

es.transport.tcp.port=9301

es.network.port=9302

es.http.port=9200

I am not sure that this is your issue, but this is important.

Will

----
Will Ezell
http://dotcms.com
phone: (305) 900-2001 ext. 7010
direct: (978) 294-9429
skype: wezell1

[Alex]

I think this is the issue.  I was battling with those ports last night. Let me play with it.

[Alex]

Yes, it is.  Let me make the changes that Will is pointing out.  I think that will fix the issue.

[Alex]

Thank you Will!  That solved the issue!

Alex

On Aug 23, 2012, at 5:20 PM, Will Ezell wrote: