Last Updated on
First Server starts OK, Secondary Clustered Ephesoft Server’s FAIL Servers utilized the same share credentials, yet logs report network connectivity lost or permission denied issues. If one of the servers was started first, the other would fail to start if started after.
These are the outcomes if you perform the following startup tests. To replicate, be sure to drop all connections to NAS between the two tests.
Server1 started 1st – SUCCESS; Server2 started 2nd – FAIL
Server2 started 1st – SUCCESS; Server1 started 2nd – FAIL
HTTP Status 404 Error Message
184.108.40.206 2014-07-28 12:53:09,151 ERROR main org.springframework.web.context.ContextLoader – Context initialization failed org.springframework.context.ApplicationContextException: Failed to start bean ‘folderMonitorService’; nested exception is com.ephesoft.dcma.core.common.DCMABusinessException: Unable to aquire lock on file :SharedFolders\ephesoft-system-folder\_lock
220.127.116.11 2014-07-28 16:03:59,832 ERROR main com.ephesoft.dcma.monitor.service.FolderMonitorServiceImpl – Unable to aquire lock on file : SharedFolders\ephesoft-system-folder\_lock java.io.IOException: The specified network name is no longer available
Linux based NAS devices using Samba handle locking differently than Windows File Sharing. If access to the same resource from more than one machine is encountered, when using the same credentials, access will be denied. To utilize Ephesoft clustering with Samba Linux shares, “Disable File Locking” in the NAS’s configuration or consult your NAS reseller for best practice recommendations.