Posts

Showing posts from 2015

Puppet : Addinng additional Client Nodes

In my initial blog at http://zaman4linux.blogspot.com/2014/11/quick-howto-puppet-installation-and.html , we had seen how to install and configure Puppet Server and Client.

Now we will see further in adding additional clients to the puppet server .

The steps are as follows:

1.  Edit puppet.conf on server to add the entry for new client as shown below
     dns_alt_names = xqa2.example.com , xqa3.example.com

2. Edit site.pp to add the entry for new host with the rule to add a file

      node "xqa3.example.com" {
            file { "/home/blaskar/zamanhosts.txt":
                             ensure => file,
                             owner  => "root",
                             group  => "root",
                             mode   => 0644
                            content => "Node1.example.com"
                   }
           } 


On puppet client we will execute the following steps

1. First install the puppet software

yum …

NFS: Change ownership issue

We are accessing NFS mounts across three hosts in our QA environment. The issue for us is that when we change the ownership of a directory on NFS mount on the server, the ownership changes are not taking place on the client. It is getting changed to nobody on the client. The issue can be seen for a particular user , for other users it is working fine. The user in question is the following user content .

If we change the ownership to content manually on the client, it is getting changed to nobody user. But if changed to some other user, it works fine.

Please find  /etc/exports for the particular directory on the server.


/shared/share *(rw,no_root_squash,sync) On the client machine, it is mounted as follows

car-lnx:/shared/share /data/share nfs vers=3,rw 0 0Example on the Server:


$ sudo chown content test
$ ls -l -rw-rw-r-- 1 content admin 0 Aug 20 23:08 test 

Example on the Client:

$ ls -l -rw-rw-r-- 1 nobody admin 0 Aug 20 23:08 test

This is the issue where the owne…