You usually get these error message in
/var/log/syslog if the FMS user (the one specified in fms.ini with the
SERVER.PROCESS_UID and
SERVER.PROCESS_GID parameters) has no write permission to the
${FMS_DIR}/tmp directory (where
${FMS_DIR} is the directory where you installed FMS in - usually
/opt/adobe/fms). Don't forget to check the whole path leading to that
tmp directory!
If the user has no permission to enter eg.
/opt/adobe, then it will not be able to reach the
/opt/adobe/fms/tmp directory either.
To check the permissions on your setup, run the following command sequence as root (replace
${FMS_USER} with the name of the OS user that FMS is running with and
${FMS_TMP_DIR} with the path of the
tmp subdir in your FMS directory):
su - ${FMS_USER} -s /bin/bash
for path_element in $(echo "${FMS_TMP_DIR}" | tr '/' ' '); do fms_path=${fms_path}/${path_element}; if [ ! -x "${fms_path}" ]; then echo "Error: execute permission is needed on directory ${fms_path}"; fi; done
This sets the current user to
${FMS_USER} and checks each directory in the path of
${FMS_TMP_DIR} for accessibility by that user. Repeat running the script each time you fix a permission error. Keep repeating until you can run the script without any error messages.
You can mimic the script's behaviour manually with something like this (assuming the user is
fms and the directory is
/opt/adobe/fms/tmp):
su - fms -s /bin/bash
cd /opt
cd /opt/adobe
cd /opt/adobe/fms
cd /opt/adobe/fms/tmp
If any of the "cd" commands gives a "permission denied", then fix it by adding the required permissions. Usually you would set something like this (executed as root):
chown root.root /opt /opt/adobe
chmod u=rwx,go=rx /opt /opt/adobe
chown -R fms.fms /opt/adobe/fms
chmod -R u+rwX,go+rX /opt/adobe/fms
And of course to create a file in that
tmp dir, the FMS user has to have write permissions to the
tmp dir too.
Recent comments
1 day 15 hours ago
1 day 20 hours ago
3 days 4 hours ago
3 days 7 hours ago
3 days 12 hours ago
5 days 9 hours ago
1 week 10 hours ago
1 week 2 days ago
1 week 5 days ago
2 weeks 1 hour ago