Environment
Filr 3
Filr 4
Situation
When attempting to login to the Web Client via the port 8443 interface, the user sees an error in the browser such as:
HTTP Status 500 - Required key 'access.webdav.enable' is not found
type Exception report
message Required key 'access.webdav.enable' is not found
description The server encountered an internal error that prevented it from fulfilling this request
exception
org.kablink.util.PropertyNotFoundException: Required key 'access.webdav.enable' is not found
org.kablnkutil.PropsUtil.getRequired (PropsUtil.java:198)
org.kablnkutil.PropsUtil.getRequired (PropsUtil.java:87)
org.kablink.teaming.webdav.servlet.filter.ResourceDispatchFilter.doFilter(ResourceDispatchFilter.java:112(
note The full stack trace of the root cause is available in the logs.
Resolution
Various possible causes and solutions exist:
Cause 1: /var/opt/novell/tomcat-filr/logs/appserver.log contains an error such as:
2019-06-17 14:11:36,053 INFO [localhost-startStop-1] [org.kablink.teaming.util.SystemProperties] - /config/system-ext.properties does not exist
Fix 1: Reconfigure the Filr server. On the port 9443 Administration console, click "Configuration". See if the "Reconfigure Filr Server" button is visible. If it is, go ahead and reconfigure the Filr server. If not, make a change which will allow for the reconfiguration. For example, under "Net Folders" change the "Max Simultaneous Syncs" from the default of "5" to "4". Click OK and then you'll see the "Reconfigure Filr Server" button and you can reconfigure it. Later, you can change the value back to 5 (and reconfigure again).
Cause 2: /var/opt/novell/tomcat-filr/logs/appserver.log contains an error such as:
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'dataSource' defined in ServletContext resource [/WEB-INF/context/applicationContext.xml]: Invocation of init method failed; nested exception is javax.naming.NamingException: null, message from server: "Host 'filr.myorganization.com' is not allowed to connect to this MySQL server"
Fix 2: This error is indicating that Filr is not able to communicate with the database; the MySQL server is rejecting a request from the host filr.myorganization.com. This may indicated a problem with the MySQL server configuration. Reboot the database appliance from the port 9443 administration console. Examine the database appliance for problems such as insufficient disk space (df -h) and memory (free -m).
Cause 3: The stored value of the encryption key has changed.
/var/opt/novell/tomcat-filr/logs/appserver.log contains an error such as:
Unexpected exception resolving reference [Root exception is org.jasypt.exceptions.EncryptionOperationNotPossibleException]
Fix 3: Edit the /opt/novell/filr/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties/
such that the "kablink.encryption.key=" value is the same as the "kablink.encryption.key.initial=" value. Also, this should match the value of "encryption.key=" in /vashare/filr/conf/sec.properties.
Steps:
>more /opt/novell/filr/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties/
note the lines:
kablink.encryption.key=
and
kablink.encryption.key.initial=
These lines should be the same, and the value should be the "initial" value. (This "initial" value is saved in order to "remember" what the initial value was, in case the value gets changed by accident).
If they are different, use vi to edit the file.
>more /vashare/filr/conf/sec.properties
note the line:
encryption.key=
It should be the same as the "initial" value.
>rcfilr stop
NOTE: You need to stop Filr on all the Filr servers in the cluster.
Now, run vi and edit the ssf-ext.properties file. Copy the "initial" line, removing ".initial", and rem out the old one.
At this point the encryption key value should be the same in all three locations:
/opt/novell/filr/apache-tomcat/webapps/ssf/WEB-INF/classes/config/ssf-ext.properties/
kablink.encryption.key=
kablink.encryption.key.initial=
/vashare/filr/conf/sec.properties
encryption.key=
>rcfilr start
>tailf /var/opt/novell/tomcat-filr/logs/appserver.log
This will allow you to watch the progress of the Filr start.
If Filr loads successfully and is accessable, repeat the above steps on all the Filr servers in the cluster.
Cause 4: (Applies only if the Filr deployment is expandable (i.e. a /vashare is being employed,) The Filr server is unable to logon to the /vashare.
Fix 4: Add sec=ntlmssp to the mount command in /etc/fstab on the Filr server(s). This command sets the security mode to the new default of ntlsmssp. SUSE TID 7015602 discusses this subject:
Before modification:
//IPADDRESS/SHARENAME /vashare cifs credentials=/etc/opt/novell/base/.smbcredentials,rw,nounix,iocharset=utf8,uid=30,gi d=8,file_mode=0777,dir_mode=0777 0 0
After modification:
//IPADDRESS/SHARENAME /vashare cifs credentials=/etc/opt/novell/base/.smbcredentials,rw,nounix,iocharset=utf8,uid=30,gi d=8,sec=ntlmssp,file_mode=0777,dir_mode=0777 0 0