Aris connect server runnables abs_m & copernicus_m stuck in starting state

Last activity on October 1, 2023 - 11:21 26k Views 4 Replies Professional ARIS

JA

Junaid Alam on July 14, 2014

Hi,

I am trying to install Aris connect server 9.6 on a Windows 2008 Service Pack 2 & SQL Server 2008 R2t (2 CPU/ 8Gb RAM). I used non default ports 8080 and 44300 respectively I made sure nothing listening on the ports using the command netstat -aon.

As per the document I customized the script envset.bat based on our requirement by changing the DB name, user name, and DB file path and ran inst.bat which finished successfully and created the database and schemas.

After customization I ran the setup for the ARIS connect server used the 1433 default port, used the option import the license later and selected medium (2-50) user installation. The installation is completing and it is failing when it is try to start the connect server.

when I check ARIS cloud controller --> LIst option all the services are staring and abs_m and copernicus_m are stuck in starting state since a day. i tried the same procedure on 2 servers and I am getting the same result. I dont know were to look at and I am totally new to ARIS components.

Please help and direct me to troubleshoot and fix the issue.

Regards

JA

Sign in or register to reply.

Notify Moderator

4 Replies

GF

Graham Farquharson on July 14, 2014

Hi JA,

We had a lot of issues with components of ARIS 9.6 failing to start up and with components logging frequent errors and/or crashing. Everything became much more stable when we increased our RAM from 8GB to 12GB. Since then we've had no problems. If upgrading RAM isn't an option there is a command to change the amount of RAM available to the different components -- this also helped us in the interim to getting additional RAM but you should probably use with caution and check with global support. I just want to make sure not to steer you in the wrong direction and mess up your configuration! But this is what worked for us in what sounds like a similar situation.

To understand what is going on it is helpful to check the log files. It is a bit painful to figure out where they all are and which have meaningful messages but I think it is worth the time. The easiest way to get the log files is to run the batch file <ARIS9.6>/support/collectLogFiles.bat.

The problem we most typically had was that the cloudsearch component would run out of memory at start up and this caused other components such as abs to fail to start, but it was unpredictable. Our initial configuration was 6cpu/8GB and we increased to 6cpu/12GB and everything is very stable now.

Good luck,

Graham

Like

Sign in
or register to reply.

Notify Moderator
JA

Junaid Alam Author on July 14, 2014

Thanks Graham.

Will try your suggestion.

Regards

JA

Like

Sign in
or register to reply.

Notify Moderator
BM

Bindiya Mittal on December 28, 2017

Hi Junaid,

I know your initial query was 3 years back, I was wandering if your issue was resolved. if yes, how did you resolved. We are facing the same issue (abs_m and copernicus_m getting stuck)

Like

Sign in
or register to reply.

Notify Moderator
LN

Leandro Nogueira on April 3, 2019

Hi guys, I also facing the same problem, I wil be glad if anyone post any news about it.

Like

Sign in
or register to reply.

Notify Moderator

Upcoming events

Thursday, June 12, 2025 - 09:00

ARIS Super User Group Meeting
Wednesday, June 18, 2025 - 13:00

ARIS User Group DACH

Sign in

Reset Password