Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Not Answered
Replies
24 replies
Subscribers
7 subscribers
Views
9582 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
I have started Appian by start-suite.sh , checked the status using checkengine.s
lilyc
over 11 years ago
I have started Appian by start-suite.sh , checked the status using checkengine.sh and then started Jboss 7.1 by standalone.sh
JBoss starts and then is stuck at this line forever: and I can't access my Appian... i.e : localhost:8080/suite/designer
[02:00:35,257 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) JBAS018559: Deployed "suite.ear"]
has anyone encountered this situation before? any help? thanks a million in advance...
OriginalPostID-72876
OriginalPostID-72876
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 11 years ago
Let's first fix the engines:
Using the proper user account:
1. Stop JBoss (all instances)
2. On server 2 (bpm104) navigate to <APPIAN_HOME>\\server\\_scripts\\
3. Create a copy of stop-suite.sh and call it stop-suite-localhost.sh
4. Open stop-suite-localhost.sh and change this line from:
$APPIAN_EXEC admin shutdown
to read:
$APPIAN_EXEC admin stop localhost
5. Execute this NEW script: stop-suite-localhost.sh
6. Access bpm104 and delete any writing*.kdb file under each gw2 directory <APPIAN_HOME>\\server\\*****\\gw2
7. On server 1 (bpm103) run the OUT OF THE BOX stop-suite.sh
8. Wait for the engines to stop and for the CPU usage to go down ~0%
9. Run:
ps -ef | grep /k
to make sure Appian processes are no longer running
10. Compare gw1 and gw2 directories. Make sure the highest numbered engine database file (*.kdb) is the same on BOTH.
**** Your reference should be GW1, this is the server that you should use to synchronize, therefore you need to check gw2 is basically in sync (the last engine database file *.kdb) with gw1
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 11 years ago
Let's first fix the engines:
Using the proper user account:
1. Stop JBoss (all instances)
2. On server 2 (bpm104) navigate to <APPIAN_HOME>\\server\\_scripts\\
3. Create a copy of stop-suite.sh and call it stop-suite-localhost.sh
4. Open stop-suite-localhost.sh and change this line from:
$APPIAN_EXEC admin shutdown
to read:
$APPIAN_EXEC admin stop localhost
5. Execute this NEW script: stop-suite-localhost.sh
6. Access bpm104 and delete any writing*.kdb file under each gw2 directory <APPIAN_HOME>\\server\\*****\\gw2
7. On server 1 (bpm103) run the OUT OF THE BOX stop-suite.sh
8. Wait for the engines to stop and for the CPU usage to go down ~0%
9. Run:
ps -ef | grep /k
to make sure Appian processes are no longer running
10. Compare gw1 and gw2 directories. Make sure the highest numbered engine database file (*.kdb) is the same on BOTH.
**** Your reference should be GW1, this is the server that you should use to synchronize, therefore you need to check gw2 is basically in sync (the last engine database file *.kdb) with gw1
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data