I’m not sure if this is a bug or not, but we are working with a host who has the /Secure folder locked down / unwritable. I am hitting the big “Deploy Now” button for OttoDeploy via OttoFMS, and it’s failing due to this error:
EPERM: operation not permitted, scandir 'C:\Program Files\FileMaker\FileMaker Server\Data\Secure'
The funny thing is I’m not actually selecting the Secure folder at all when I try to install this file… I’m just going with Default, which appears to be set correctly in FMS Admin:
As part of the deployment we list all of the files on the server and check them against the incoming files. As part of that we scan the database directories to find the filepaths. That is the operation that is likely causing this. I would double check the permissions on the Secure directory and make sure that is is readable by the fmserver user.
So yeah… my server admin is locking down certain folders. It seems obvious that we can’t even see them. I’m trying to get them to change their policies so that such folders are READable at least, but I’m wondering if OttoFMS can be a little more graceful in these circumstances to basically just bypass the folder it can’t get into? It seems odd to fail a deployment for not being able to get into a folder it doesn’t need to begin with. I suppose what you’re trying to do is merely LOOK inside those folders, but still, perhaps we can just carry on and assume there’s nothing in those folders? 'Cause that’s what really is going on here.
I’m just trying to get OttoFMS and my host to work together.
totally fair, we can likely add some handling of this. If I can’t even read the folder I probably don’t care about the files in there. I’ll get this added in one of our upcoming versions. probably not the next one but the one after that.
I see this is still an issue in OttoFMS 4.6.2. I’m working with my hosting provider to relax the /Secure requirement again but it’d be nice to not have to worry about this since we don’t care about /Secure and don’t use /Secure.
Sorry for the lack of updates, I have a fix put together for this that will be releasing with our next version. I’m looking at a release timeline for next week sometime most likely. Thanks Matt!
