Hi, We are getting the below error message while trying to save the c

sapnas over 8 years ago

Hi,

We are getting the below error message while trying to save the changes made to various Appian objects -

1) while saving process model changes -> "An Unknown error has occurred while saving the process model"

2) while saving an interface -> The page could not be loaded. [HTTP Code = 504] (APNX-1-4279-001)

On checking the server logs, I see the below error message corresponding to both aforementioned errors

INFO [stdout] (elasticsearch[Client 30F03352][transport_client_worker][T#2]{New I/O worker #2}) 2016-06-08 06:26:07,987 [elasticsearch[Client 30F03352][transport_client_worker][T#2]{New I/O worker #2}] ERROR com.appian.dl.repo.es.LoggingBulkResponseActionListener - Bulk request failures occurred. Summary: [opType=index, index=designer-objects-ia, type=DT-10, status=SERVICE_UNAVAILABLE, count=1, firstMessage=UnavailableShardsException[[designer-objects-ia][0] Primary shard is not active or is...

Error_Logs.txt

Discussion posts and replies are publicly visible

0 prosenjitd
A Score Level 2
over 8 years ago

Can you please try this -
1. Stop App Server
2. Stop Search Server
3. Delete <APPIAN_HOME>\\_admin\\search-local\\search-server\\data
4. Start Search Server
5. confirm that you can see "Current cluster information: [status=GREEN]" in the search-server.log
6. Start App server.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sapnas over 8 years ago

Hi Prosenjit,

Followed the steps exactly as you mentioned. I was able to see "Current cluster information: [status=GREEN" too in search-server.log.

The issue got resolved now. Thanks a lot .. Now am able to save changes made to any Appian object without getting the errors mentioned in my first post.

Just wanted to understand the rationale behind your approach. Could you please explain in brief how you were able to troubleshoot and arrive at the root cause and solution to it ?

Thanks once again.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 prosenjitd
A Score Level 2
over 8 years ago

@sapnas,The errors logged in the App server logs that you had provided clearly pointed to some issues with the Search server. Search-server logs provided more specific details about the error which indicated the root cause being "[Node localhost:9300] All shards failed for phase: [query]
org.elasticsearch.action.NoShardAvailableActionException: [designer-objects-ia][0] null" and after some digging in the Appian and external forum, I found that that this happens when your search server data gets corrupted and can be eliminated by deleting the data.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 sapnas over 8 years ago

That's great !! Thank You for sharing the details Prosenjit.
Thank You for the timely help in resolution.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel