On Mar 26, 2010, at 2:46 PM, Eric Shamow wrote:
> Puppet sees the same thing -- with debug logging turned on:
>
> err: //mod-ssf3-testing/Mount[nfs_var_www]/ensure: change from present
> to mounted failed: Execution of '/bin/mount -o
> vers=3,rsize=32768,wsize=32768,tcp,noatime,nocto,hard,intr,timeo=60,retrans=2,actimeo=30
> /var/www/' returned 32: mount.nfs: /var/www is already mounted or busy
>
> This suggests to me that the mount command itself is ok and that
> Puppet's handling is wrong....it's looking for a successful mount
> message even though it should accept "is already mounted or busy."
Right, but the code I quoted, which is the piece that causes puppet to think
the state needs to change from 'present' (in fstab but not active) to 'mounted'
(in fstab and accessible), just runs 'mount' without any options and parses the
output. This happens before the point in execution you pasted but doesn't emit
any output. If that succeeded, which it should do for this filesystem but is
not doing, puppet wouldn't even attempt to execute this command.
But I think I see from the output what's going on -- It looks like you are
defining your mount resources like:
mount { "nfs_var_www": path => "/var/www", device => "server:/www", ensure =>
mounted }
and maybe puppet's grepping for nfs_var_www instead of "/var/www". Does putting
the path up into the name change things for you?
I'm eric0 on freenode irc, feel free to ping me if you want to step through it
realtime.
-=Eric
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" 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-dev?hl=en.
