Environment
Filr 4.0 All-In-One deployment upgrade from Filr 3.4.3
Situation
After an otherwise successful upgrade to Filr 4.0 from a Filr deployment which started as an early version (e.g. 1.2), a user can login as vaadmin and as root on https://<IP>:9443. But when attempting to login as admin on https://<IP> or https://<IP>:8443, an error appears:
(kablink) Could not open index writer
Resolution
1. Remove the old index directory (assuming the old directory is already backed up as backing up the vastorage disk is a necessary step for the upgrade to Filr 4.0.)
rm -rf /vastorage/filr/lucene/*
2. Restart the Filr service.
rcfilr restart
Cause
The problem is caused by a Lucene version mismatch, as reflected in the /var/opt/novell/tomcat-filr/logs/appserver.log.