Re: clientupdate related bug?! need a debug switch for clientupdate

["Asif Iqbal" <vadud3 (at) gmail.com>]

On Tue, Jan 6, 2009 at 11:44 AM, Asif Iqbal <vadud3 (at) gmail.com> wrote:
> On Mon, Jan 5, 2009 at 4:32 PM, Asif Iqbal <vadud3 (at) gmail.com> wrote:
>> On Wed, Dec 31, 2008 at 3:24 PM, Asif Iqbal <vadud3 (at) gmail.com> wrote:
>>> Hi
>>>
>>> I have a list of hosts with CLASS:myclass and I have a tar file
>>> newimage.tar file in ~hobbit/server/download dir
>>>
>>> In my ~hobbit/server/etc/client-local.cfg file I added this entry
>>>
>>>    [myclass]
>>>    clientversion:newimage
>>>
>>> This image suppose to add a new service called `mytest` in the status
>>> column for all hosts in that particular group
>>>
>>> I noticed only few hosts got that new service column `mytest' , after
>>> a little wait, and most did not create the new column
>>> I have a total of 40 hosts in that group
>>>
>>> I also noticed all of the hosts have the [clientversion] section in
>>> the client data showing the `newimage' as the version name.
>>> So hobbit server at least instructed the client correctly to pickup
>>> the new image and the clients were able to run the clientupdate
>>> command.
>>>
>>> All the clients have the new ext/newscript.sh and the
>>> etc/clientversion.cfg file (with content newimage)
>>>
>>> However, the clients that did not show the new service column is
>>> _still_ carrying have the old etc/clientlaunch.cfg file. It does not
>>> have an entry of the [newservice] section. So that explains why new
>>> service column is not showing in status page for those hosts.
>>>
>>> A working and non-working clients' hobbitclient.log file has same
>>> 'tar: blocksize = 0' . So tar xf probably did not fail.
>>> They all are same OS, solaris 8. So something in the non-working hosts
>>> preventing it from overwriting the old etc/clientlaunch.cfg file
>>>
>>> How do I debug this?
>>
>> I made another update and same issue. Some of the hosts did not get
>> the new clientlaunch.cfg file.
>> I had to manually go through each of them just to add the snippet
>> related to the new extension script.
>>
>> Would be nice if I could avoid that, afterall `clientupdate' claims to
>> do just that
>
> I ran the following on two hosts, one where clientupdate works and one
> where it does not.
> I did not see it ever touched the clientlaunch.cfg file for either of
> them. I am probably
> not using the correct switches with truss.
>
> (hobbit):~/client$ rm etc/clientversion.cfg
>
> (hobbit)myhost:~/client$ export HOBBITCLIENTHOME=`pwd`
>
> (hobbit)myhost:~/client$ truss -f ./bin/bbcmd
> --env=etc/hobbitclient.cfg ./bin/clientupdate --update=newversion
>
> This really begs a debug switch for clientupdate

I took the tar file from ~hobbit/server/download dir and untar'd it
(as hobbit user) on the hosts ~hobbit/client dir
and all went just fine. I am guessing the clientupdate has a bug then.
clientupdate pulls the necessary files
for some servers and fail to overwrite the clientlaunch.cfg file

>
>>
>>
>>>
>>>
>>>
>>> --
>>> Asif Iqbal
>>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>>>
>>
>>
>>
>> --
>> Asif Iqbal
>> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>>
>
>
>
> --
> Asif Iqbal
> PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu
>



-- 
Asif Iqbal
PGP Key: 0xE62693C5 KeyServer: pgp.mit.edu