[rudder-users] IO on vmware

Wed Sep 25 11:42:57 CEST 2013

Hi,

On a rudder managed node you should use this path:
/var/rudder/cfengine-community/state/

Regards,

Andrew

On Wed, Sep 25, 2013 at 12:37 PM, Prestasit01
<prestasit01 at ouest-france.fr> wrote:
> Hi again,
>
>
>
> We don’t have this folder : /var/cfengine/state/
>
>
>
> And it seems that we don’t have files with this extension : .tcdb
>
>
>
> So I can’t mount a RAM disk on /var/cfengine/state/
>
>
>
> Any other idea ?
>
>
>
> BR
>
>
>
>
>
> De : rudder-users-bounces at lists.rudder-project.org
> [mailto:rudder-users-bounces at lists.rudder-project.org] De la part de
> Prestasit01
> Envoyé : mercredi 25 septembre 2013 11:19
> À : 'Nicolas Charles'; rudder-users at lists.rudder-project.org
>
>
> Objet : Re: [rudder-users] IO on vmware
>
>
>
> Hello,
>
>
>
> Mesured I/O is on the managed node.
>
>
>
> I will try your solution.
>
> Thanks.
>
>
>
> BR
>
>
>
> De : rudder-users-bounces at lists.rudder-project.org
> [mailto:rudder-users-bounces at lists.rudder-project.org] De la part de Nicolas
> Charles
> Envoyé : mercredi 25 septembre 2013 11:10
> À : rudder-users at lists.rudder-project.org
> Objet : Re: [rudder-users] IO on vmware
>
>
>
> Hello,
>
> The mesured I/O is on the Rudder server root, or on a managed node ?
>
> Cfengine uses internally a TokyoCabinet database, and is a bit eager on the
> writing on it. So even if it is not changing anything, it writes (a lot)
> that it checked the system. So if the problem happen on a managed node, you
> can use the workaround suggested in this blog post:
> http://blog.normation.com/en/2013/09/09/speed-up-your-cfengine-by-using-a-ram-disk/
>
>
> Please note that the Rudder Server root centralises all messages, so it is
> expected that he has some I/O
>
> Please tell me if it helps you or solves your issue
>
> Regards,
> Nicolas
>
> On 25/09/2013 10:55, Prestasit01 wrote:
>
> Hello all,
>
>
>
> I found that rudder creates a lot of I/O each 5 minutes.
>
> It seems normal that he works each 5 minutes due to the default
> configuration but I/O creation seems not normal .
>
> We only have 4 rules applied on this node :
>
>
>
> Rudder system policy: basic setup (common) => default
>
> Rudder system policy: daily inventory => default
>
> 00_Constante – myserver => variable definition
>
>
>
> (with theses 3 first rules we have 270Ko/s each 5 mins)
>
>
>
> And when we add another rule we have 778Ko/s each 5 mins :
>
>
>
> 02_Init Système
>
> -----repertoire fichiers => folder creation with enforced permissions
>
> -----SSH => edit ssh configuration
>
> -----Profile Root & Repo => repository file creation with enforced content
>
> -----User perso2 => user creation with « Everytime » option checked
> (corresponding to « How often do you want to want to check the password »)
>
> -----Appli Rsyslog Conf => modification of the rsyslog.conf (no enforced
> content)
>
> -----Permissions /projet => set permission on two folder
>
> -----Sudoers => modification on the sudoers file with « Enforce content of
> the file ONLY at creation » checked
>
> -----Service Rsyslog  => start service on boot, restart service if number of
> process instances less than 0
>
> -----Permission Sources => folder creation with permissions adjusted
> recursively
>
> -----profile user exploit => 2 files creation, with permission set
>
> -----Clés SSH => add two ssh key
>
> -----Permission user => set permission on a file
>
> -----User perso => user creation with « Everytime » option checked
> (corresponding to « How often do you want to want to check the password »)
>
>
>
>
>
> Have you got one idea of what can be write each 5 mins ??? (because normally
> it will only write if values are changed)
>
>
>
> Thanks
>
> BR
>
>
>
> CJARD
>
> -------------------------------------------------------------------------
> Les informations ou pieces jointes contenues dans ce message sont
> confidentielles. Seul le destinataire expressement vise peut en prendre
> connaissance. Toute autre personne qui en divulguera, diffusera ou prendra
> des copies sera passible de poursuites. La societe Ouest-France decline en
> outre, toute responsabilite de quelque nature que ce soit au titre de ce
> message s'il a ete altere, deforme ou falsifie.
>
> _______________________________________________
>
> rudder-users mailing list
>
> rudder-users at lists.rudder-project.org
>
> http://www.rudder-project.org/mailman/listinfo/rudder-users
>
>
>
> --
>
> Nicolas CHARLES
>
> -------------------------------------------------------------------------
> Les informations ou pieces jointes contenues dans ce message sont
> confidentielles. Seul le destinataire expressement vise peut en prendre
> connaissance. Toute autre personne qui en divulguera, diffusera ou prendra
> des copies sera passible de poursuites. La societe Ouest-France decline en
> outre, toute responsabilite de quelque nature que ce soit au titre de ce
> message s'il a ete altere, deforme ou falsifie.
>
> -------------------------------------------------------------------------
> Les informations ou pieces jointes contenues dans ce message sont
> confidentielles. Seul le destinataire expressement vise peut en prendre
> connaissance. Toute autre personne qui en divulguera, diffusera ou prendra
> des copies sera passible de poursuites. La societe Ouest-France decline en
> outre, toute responsabilite de quelque nature que ce soit au titre de ce
> message s'il a ete altere, deforme ou falsifie.
>
> _______________________________________________
> rudder-users mailing list
> rudder-users at lists.rudder-project.org
> http://www.rudder-project.org/mailman/listinfo/rudder-users
>

-- 

 <http://www.layershift.com>

Registered office: Layershift Limited, Delta House, Wavell Road, Manchester, M22 5QZ, United Kingdom
Layershift Limited is a company registered in England and Wales (6036217). EU VAT number: GB 903034962