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
+2
person also asked this
people also asked this
Replies
4 replies
Subscribers
10 subscribers
Views
3249 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Administration
Appian engine in FATAL status
octavianp
over 7 years ago
Hello,
Recently we faced an issue on the production server of one of our customers, in terms that while running Appian, multiple users where seeing weird error messages.
This led us to the idea that maybe one of the Appian engines was down which was true: Process Exec 01 >>>> Status: FATAL! No gateway is active.
As a solution, we tried getting an elder version (latest working version) of the .KDB file for Process Execution 01 and duplicate it, renaming the copy with +1 name. This did not work for a couple of the elder versions as the Process engine was still in a FATAL status.
Then, we tried to repair the .KDB file that was active while we first noticed that the engine is down and this worked.
Now we have three questions:
1. What could case in the first place such event and on which log file we could see the error? – We really want to avoid this event happening again, especially since we are talk...
OriginalPostID-271926
Discussion posts and replies are publicly visible
0
octavianp
over 7 years ago
...ing about the production environment.
2. Now the application is up, but somehow some tasks that have been submitted appear to be in a previous state - why did this happen since we did not used an elder KDB file but just repaired the last one?
3. We noticed the following error in the application-server.log after successfully starting Appian:
“ERROR com.appiancorp.process.runtime.monitoring.GetTaskDetailsAction - Task request info: null
java.lang.IllegalArgumentException: Activity must be attended”
Can this have anything to do with the issue we faced? Should we be worried?
Thanks in advance,
Octav
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
AppianCTO
Appian Employee
over 7 years ago
Troubleshooting a production system should be done with our support team. Please open a case.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
octavianp
over 7 years ago
From what I have detailed, is there something different form the standard procedure? Also this kind of events can happen also in other environments, different than the production one and is definitely not nice, so it would be useful to do whatever it takes to avoid it.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
0
Jim Schweitzer
Certified Lead Developer
over 7 years ago
This is not a common occurance. Any time you roll back to previous versions of KDBs, especially exec KDBs, you're basically reverting back part of the system to a previous snapshot in time.
Also, when starting up engines after a failure, sometimes you just need to allow time (hours) for the transactions to replay. Rolling back KDBs should be a last resort and done with help of Appian Support.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel