Issue #2731 has been updated by Markus Roberts. Subject changed from mount on linux does not recognize errror code 32 meaning already mounted to problem communicating with processes in SELinux Category changed from mount to SELinux
---------------------------------------- Bug #2731: problem communicating with processes in SELinux http://projects.reductivelabs.com/issues/2731 Author: Jonathan Stanton Status: Investigating Priority: Normal Assigned to: Category: SELinux Target version: 0.25.2 Affected version: 0.24.8 Keywords: Branch: On a Centos 5.3 system with NFS mounting home directories, every time puppet runs it tries to update the status of the nfs mount from "present" to "mounted" but fails because the call to mount returns -32 not 0. But as documented on the man page -32 means 'already mounted' and so should be treated as success. Here is the logged message from puppetd. <pre> Oct 16 10:28:07 savage-file puppetd[11739]: (//Node[savage-file.livetimenet.com]/nfs_moose_client/Mount[/mnt/moose_home]/ensure) change from present to mounted failed: Execution of '/bin/mount -o rw,async /mnt/moose_home' returned 32: </pre> This has been going on for awhile (certainly back several versions of puppet) and I've tried some ideas with restarting it, and letting puppet do the original mount instead of the OS mounting it directly. -- You have received this notification because you have either subscribed to it, or are involved in it. To change your notification preferences, please click here: http://reductivelabs.com/redmine/my/account -- You received this message because you are subscribed to the Google Groups "Puppet Bugs" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-bugs?hl=en.
