#Installation and Administration of Appian 7.9 in Linux Getting the

vamsib over 8 years ago

#Installation and Administration of Appian 7.9 in Linux

Getting the following error during JBOSS EAP 6.3 Application Server Startup
===========================================================================
09:24:36,151 ERROR [org.jboss.as.controller.management-operation] (Controller Boot Thread) JBAS013412: Timeout after [300] seconds waiting for service container stability. Operation will roll back. Step that first updated the service container was 'add' at address '[
("core-service" => "management"),
("management-interface" => "native-interface")
]'
09:24:41,162 ERROR [org.jboss.as.controller.client] (Controller Boot Thread) JBAS014781: Step handler org.jboss.as.server.DeployerChainAddHandler$FinalRuntimeStepHandler@42b41d88 for operation {"operation" => "add-deployer-chains","address" => []} at address [] failed handling operation rollback -- java.util.concurrent.TimeoutException
09:24:43,924 ERROR [org.apache.catalina.c...

files.7z

Discussion posts and replies are publicly visible

0 Eduardo Fuentes
Appian Employee
over 8 years ago

Definitely something happened with your standalone.conf. Can you find it in your repository and manually deploy it to <JBOSS_HOME>\\standalone\\bin?

If you look at the one you sent me, that's the JBoss default one, it's not the one with the Appian settings (see _admin\\_scripts\\configure\ emplates\\bin\\jboss\\jboss-eap-6.3\\bin\\standalone.conf.example). I don't know yours was replaced with the out of the box one but that's the root cause.

If you can't find it, simply copy _admin\\_scripts\\configure\ emplates\\bin\\jboss\\jboss-eap-6.3\\bin\\standalone.conf.example to <JBOSS_HOME>\\standalone\\bin and rename it to standalone.conf, then open it and update the variable APPIAN_HOME_EAR accordingly.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vamsib over 8 years ago

Now the issue got fixed as issues was with primary database schema

But now i am facing issue with the search server where it shows appian search server started :

[root@isv1-0507 search-local]# /usr/local/appian/search-server/bin/start.sh
SS_JAVA_OPTS: -Xms1024m -Xmx1024m -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -Djava.awt.headless=true -Djava.net.preferIPv4Stack=true -Duser.timezone=GMT
Appian Search Server process has been started.
[root@isv1-0507 search-local]#

But ss.pid not getting generated
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 8 years ago

/usr/local/appian/search-server/bin/stop.sh
rm /usr/local/appian/logs/search-server/*.log
/usr/local/appian/search-server/bin/start.sh

and attach /usr/local/appian/logs/search-server/*.log
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vamsib over 8 years ago

Performed the steps as mentioned , but no log file is getting generated related to Search-Server
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vamsib over 8 years ago

I can see only followng log files under /appian/logs/search-server

rw-r--r-- 1 root root 10485984 Jul 7 12:17 search-server-replication.log.5
-rw-r--r-- 1 root root 10486200 Jul 7 12:17 search-server-replication.log.4
-rw-r--r-- 1 root root 10486058 Jul 7 12:17 search-server-replication.log.3
-rw-r--r-- 1 root root 10490326 Jul 8 23:17 search-server.log.1
-rw-r--r-- 1 root root 10486014 Jul 15 02:26 search-server-replication.log.2
-rw-r--r-- 1 root root 10485881 Jul 28 15:55 search-server-replication.log.1
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Eduardo Fuentes
Appian Employee
over 8 years ago

But they are all old, I don't think these are the logs we need. Can you re-copy the appian-topology.xml from suite.ear\\conf to search-server\\conf?
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vamsib over 8 years ago

In our current environment , we haven't set any appian-toplogy.xml , i can see only the file "appian-topology.xml.example" under <Appian_HOME>/ear/suite.ear/conf
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rahulp over 8 years ago

I guess you should go through the below link. The presence of appian-topology.xml.example file indicates you have missed the installation step od configuring apian-topology ...forum.appian.com/.../Post-Install_Configurations.html
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 vamsib over 8 years ago

But initially after applying hotfix , while restarting appian restarted search server and it got restarted successfully .

And the current environment is a standalone environment .
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 rahulp over 8 years ago

Stop everything(Appian Jboss, server-server). Lets do this first configure the appian-topology.xml in <Appian_HOME>/ear/suite.ear/conf
as per step in the above URL shared deploy the same inside your search-server suite.ear\\conf to search-server\\conf and the follow the section Starting the Application Suite on Linux(forum.appian.com/.../Starting_and_Stopping_Appian.html)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel