search for: anynode

...9;'m receiving reports like this: ensure changed ''0.22.3-1'' to ''0.20.0-1.fc4'' Here the logs of one of the servers (CentOS 4.3) at the update moment: puppetd[16126]: Starting configuration run yum: Updated: puppet.i386 0.22.3-1 puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure changed ''0.22.2-1'' to ''0.22.3-1'' puppetd[16126]: Finished configuration run in 78.08 seconds puppetd[16126]: Starting configuration run puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure changed ''0.22.3-1...

...d.xml from kbs-CentOS-Extras: [Errno 256] No more mirrors to try. there''s any way to say puppet don''t send that messages? we also receive a lot of messages like that when something goes wrong while getting files from puppetmaster: Fri Jun 08 09:13:29 +0200 2007 //node.domain.com/anynode/bash/remotefile[/usr/local/arxiver/.bashrc]/File[/usr/local/arxiver/.bashrc]/source (err): Could not describe /dist/common/bashrc: End of file reached:

Hi, Our lustre environment is: 2.6.9-55.0.9.EL_lustre.1.6.3smp I would like to change recovery timeout from default value 250s to something longer I tried example from manual: set_timeout <secs> Sets the timeout (obd_timeout) for a server to wait before failing recovery. We performed that experiment on our test lustre installation with one OST. storage02 is our OSS [root at