I am seeing permission denied errors to the atomLock.lck document. Any reason why this could happen?
Check if current user is the owner of all directories and files under the atom installation directory, of the atom which is running in right node. check that the permissions on the folders/files are correct accessible for read/write/execute by the atom user.
Strange this is that the issue by resolved by chmod 777 and restarting the atom. But my question is why would this error pop up suddenly when it was working fine all these days.
We actually got permission denied error on atomLock.lck document
and write permission errors on /opt/Boomi_AtomSphere/Atom/Atom_ProductionAtom/work folder
both resolved by chmod777, but question is why would we get this suddenly when it was working fine before?
This could be due to the user not having enough access permissions. Check with your admin whether the user has permissions to access the folder. I have faced this issue and resolved it by granting enough access to the user. To confirm this you can use a different user and try it out.
I am confused.. If a process is set to run on scheduled basis why would a specific user permission matter? Wouldn't the user permission come into picture if he or she was running it manually?
As you rightly said it when a process is scheduled to run the user permission does not matter because it runs on the default. If a user tries to run the process manually it may run on the user permissions and it may fail if the user does not have permissions to access certain atom stuff.
You should double check that the user/group of the file match that of the user/group running the atom process. Sometimes, you can get into this situation if the atom was accidentally started with the wrong user at some point in time. For example, you installed the atom for user "bob", but then accidentally ran the atom process as "root" at one point in time. Some of the files may get created as the "root" user, causing issues when you restart the atom process as the original user "bob".
Retrieving data ...