search for: flamm

...ocfs2 node: ip_port = 7777 ip_address = 141.65.128.112 number = 2 name = mach3 cluster = ocfs2 cluster: node_count = 3 name = ocfs2 What do I do wrong? How may I succes in mounting the volume on all 3 machines? Regards, Werner -- Werner Flamme, Abt. WKDV Helmholtz-Zentrum f?r Umweltforschung GmbH - UFZ Permoserstr. 15 - 04318 Leipzig Tel.: (0341) 235-1921 - Fax (0341) 235-451921 http://www.ufz.de - eMail: werner.flamme at ufz.de

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, simple question: how can I execute a "fsck.ocfs2 /dev/sdf"? All I get is - ---snip--- myhost:~ # fsck.ocfs2 /dev/sdf fsck.ocfs2 1.4.3 Checking OCFS2 filesystem in /dev/sdf: Label: SAP01 UUID: 5969C8CABB854F8EA9C17B5B8DE48EC6 Number of blocks: 183500800 Block size: 4096 Number of

Hello, I created puppet class and I want the file operation to be executed on all servers but not on server with hostname "''server1.domain.com". I tried this class, but it does not work. Is there any other way? Thanks class test { if $hostname != ''server1.domain.com'' { file { "/etc/ntp.conf": owner

Hi, I wonder why the puppet agent on the server itself will not run: ---snip--- # puppet agent --test Error: Could not run Puppet configuration client: Puppet::Node does not respond to from_s; can not intern instances from text/plain Error: Could not run: can''t convert Puppet::Util::Log into Integer ---pins--- whereas the client on a test box tells me: ---snip--- # puppet agent --test

When I try to connect to my new puppet master, I get an error because of a self-signed certificate: ---snip--- # puppet agent --test --noop Warning: Unable to fetch my node definition, but the agent run will continue: Warning: SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed: [self signed certificate in certificate chain for /CN=Puppet CA:

Hi all, I''m trying to find a nice way to model different stages (like: live, test, dev) of puppet modules. Initially I thought of different branches inside one (Git) repository... - either being checked out on one puppetmaster into different directories being used as different puppet environments - or being checked out on different puppetmasters but then colleagues of mine

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi everyone, another problem I did not find a solution for... I ran "o2cb configure" and configured a cluster named "ocfs2". Lazy me, I did not invent a new name. Now this cluster must be renamed to avoid confusion, the name has to change to "sapcluster". I changed /etc/ocfs2/cluster.conf to the new name and ran

Hi, I''m currently trying to debug a performance issue I''m having. Therefore I would need "DEBUG" output. When using one puppetmaster process, this is fairly easy by starting it like this: > puppet master --no-daemonize --debug Now I need to see this debug output when running puppetmaster the way I ususally do - using Apache/Rack/Passenger. After looking

...0:00:00 [back to square one] This test shows the -P has no effect. Am I missing somthing? Thanks in advance for your insight, ("rsync version 2.5.4 protocol version 26" on both sides) -- PHEDRE: Je voulais en mourant prendre soin de ma gloire;, Et d?rober au jour une flamme si noire : Je n'ai pu soutenir tes larmes, tes combats ; (Ph?dre, J-B Racine, acte 1, sc?ne 3)

Hi, I recently updated from puppet 3.1.1 to 3.2.1 and noticed quite a bit of increased load on the puppetmaster machine. I''m using the Apache/passenger/rack way of puppetmastering. Main symptom is: higher load on puppetmaster machine (8 cores): - 3.1.1: around 4 - 3.2.1: around 9-10 Any idea why there''s more load on the machine with 3.2.1? -- You received this

We use puppet with two environments: [main] and [development]. These environments have different locations for their puppet manifests and modules (see puppet.conf below). Whenever I change/update a file in the directories belonging to the “main” environment, puppetmaster notices these changes and reacts to them w/o any hiccups. In contrast to this – if I change/touch a file in a directory