We're running openLCA collaboration server on: Windows 2012 R2 6.3, Tomcat 8.5.31 as a service, and elasticsearch 6.3.1 as a service (recently upgraded but were having the issues with 6.2.4).
I think we're at the point now where fetches won't work even with starting with an empty local database. Our server database is rather small - just a few processes, reference flows, select impact assessment, and some intermediate flows. When we fetch we get to the "Fetching data" window where it will freeze at the very end. Since this started occurring late last week, I've had one successful fetch after restarting both tomcat and elasticsearch, but it hasn't worked since that one time even after restarts.
Updating this question
- Possible resolution - After much troubleshooting and digging through log files, I still didn't see any red flags (there were a couple of instances where the elasticsearch wasn't running as noted in the answer below but that was not the problem in the vast majority of cases). I think there may be an issue with trying to fetch more than 1 or 2 commits into an empty database (that is a locally created database using the "Empty database" option). So far, we've been successful if we create the local database with "Complete reference data" before fetching data from collaboration server.
- Removed the issue with commits - I'm not sure we ever really had a problem
- While we did have some instances where elasticsearch wasn't running, that was really my error as the sys