clientupdate problems 🔗 link

Sveinn G. Gunnarsson wrote:

Hi all.

I am a long time user and fan of Hobbit :-)
So thank you all for your hard work on the project!


I am having trouble with the clientupdate part, and I belive I might have
found a bug, or just misunderstood the whole thing :)


Here is my scenario:

I am installing hobbit client on our ESX3 servers, and I decided to assign
a special class (esx3) to those machines in the bb-hosts file:

192.168.xxx.xxx   VMWARE01        # CLASS:esx3


In client-local.cfg I have a section for the class:

[esx3]
clientversion:hobbit-esx3-v01


When I want to push out a new version, I place a new tarball in
$BBHOME/download, in my case hobbit-esx3-v02.tar, and bump the
clientversion reference in client-local.cfg to:

[esx3]
clientversion:hobbit-esx3-v02


But, what happens, is that only one client will update it self. If I bump
the clientversion again, another one client will update and so on.


I am running the latest Hobbit server, with latest all-in-one patch on AIX
5300-05-03. On the clientside, I am also running latest and greatest, on
ESX 3.0.1.


Best regards,
Svenni

rdeal schrieb:

Does anyone have clientupdate working reliably for a large number of
machines?  I noticed a problem with clientupdate failing on our 4.2.0 server
and tracked it down that once a few clients seem to request the update the
server stops sending the file.  The clients however happily update the
clientversion.cfg and thus never attempt to get the file again.  After
upgrading to 4.2.3, the problem is the same.

Anyone else see this?  I have read some of the back forum messages and it
sounds line several others have run up against this same problem but there
doesn't seem to be a solution.
Butch

From: Alexander Bech <user-bd67b1e4c445@xymon.invalid>
Reply-To: <user-ae9b8668bcde@xymon.invalid>
Date: Sat, 30 May 2009 20:57:02 +0200
To: <user-ae9b8668bcde@xymon.invalid>
Subject: Re: [hobbit] Clientupdate problems

rdeal schrieb:

Does anyone have clientupdate working reliably for a large number of
machines?  I noticed a problem with clientupdate failing on our 4.2.0 server
and tracked it down that once a few clients seem to request the update the
server stops sending the file.  The clients however happily update the
clientversion.cfg and thus never attempt to get the file again.  After
upgrading to 4.2.3, the problem is the same.

Anyone else see this?  I have read some of the back forum messages and it
sounds line several others have run up against this same problem but there
doesn't seem to be a solution.
Butch

Yes.
I commented out the line 1975 in hobbitd.c.

--- hobbitd.c.filecache-bug     2009-05-30 20:46:59.000000000 +0200
+++ hobbitd.c   2009-02-27 13:45:56.000000000 +0100
@@ -1972,7 +1972,7 @@
                        }
                }

-               add_filecache(fullfn, result, st.st_size);
+               /* add_filecache(fullfn, result, st.st_size); */
        }

        msg->buflen = st.st_size;

it works.

rdeal schrieb:

Does anyone have clientupdate working reliably for a large number of
machines?  I noticed a problem with clientupdate failing on our 4.2.0 server
and tracked it down that once a few clients seem to request the update the
server stops sending the file.  The clients however happily update the
clientversion.cfg and thus never attempt to get the file again.  After
upgrading to 4.2.3, the problem is the same.

Anyone else see this?  I have read some of the back forum messages and it
sounds line several others have run up against this same problem but there
doesn't seem to be a solution.
Butch

Yes.
I commented out the line 1975 in hobbitd.c.

--- hobbitd.c.filecache-bug     2009-05-30 20:46:59.000000000 +0200
+++ hobbitd.c   2009-02-27 13:45:56.000000000 +0100
@@ -1972,7 +1972,7 @@
                       }
               }

-               add_filecache(fullfn, result, st.st_size);
+               /* add_filecache(fullfn, result, st.st_size); */
       }

       msg->buflen = st.st_size;

it works.