KB-0374: Errors in mapper.error because of AD user logins
Applies to: Centrify DirectControl all versions on all OS's
You might notice that the mapper.error file has lots of mount errors and all those errors gets written everytime an AD user tries to log onto the server.
Sample errors from mapper.error file:
mount: 0506-324 Cannot mount /dev/hd1 on /home: The requested resource is busy.
mount: 0506-324 Cannot mount /proc on /proc: The requested resource is busy.
mount: 0506-324 Cannot mount /dev/hd10opt on /opt: The requested resource is busy.
At regular intervals ie., every 90 mins, at the time of ADUser login: Centrify agent fetches and updates the group policies from the AD domain. Centrify agent runmappers script runs all the *.pl files under the directories /usr/share/centrifydc/mappers/machine/ and /usr/share/centrifydc/mappers/user/
And filemounts.pl is one such perl file which executes "mount -a" as a part of the script. Which tries to mount the filesystem which are already mounted on the system which cause the above errors to be logged into the mapper.error.
Please do the following to make Centrify runmappers to stop executing the perl file filemounts.pl:
chmod ugo-x /usr/share/centrifydc/mappers/machine/filemounts.pl
chmod ugo-x /usr/share/centrifydc/mappers/user/filemounts.pl
By doing this filemounts.pl file will not be executed and you shouldn't see the errors that you have mentioned.
The above explains why you are seeing this behavior for ADUsers and not for local users.