I would also check the ghost client report to make sure that the SLES client is sending the correct hostname to the Hobbit server. I have found on some linux clients, it send the hostname and some send the FQDN. I usually just manually modify the client config to send the hostname I want and not rely on the automatic (which I think is uname -n by default ... don't quote me on that though ... not near my Hobbit box right now).

'Nobody goes there anymore. It's too crowded.' --Yogi Berra

On Mon, Dec 1, 2008 at 11:10 PM, Great D Dilla <great.dilla at gmail.com>wrote:

A couple of things to check on the client: [1] Make sure that the hostname of the hobbit server is resolvable from the client side. Or better yet, use the IP address of the hobbit server on the config file ==> BBDISPLAY=[IP_or_HOSTNAME_of_hobbit_server]. [2] Check to see if indeed the master is getting files. Usually there are files in the data directory generated for your client.

Side note: To configure the hobbit client, simply use "./configure.client" and supply the IP of the hobbit server. It should work out of the box.

Hope this helps.

-----Original Message----- From: Brian Catlin [mailto:bcatlin at gmail.com] Sent: Tuesday, December 02, 2008 10:34 AM To: hobbit at hswn.dk Subject: [hobbit] Novell SuSE SLES 10 client issue.

Okay,

I have a few Novell SuSE SLES 10 servers. I compiled the 4.2 client on one of them and tried to get it to talk to the Master running on Solaris 9.

The page shows the Master tests, ping, ssh (and they work! - got paged tonight when the interface on one went AWOL)

On the client side. In client/tmp = the files are created and ready to send The client has a couple probes, and they have good output too.

I can telnet to the master from the clients on port 1984 successfully. The client refuses to publish out to the Master.

My bb-hosts has the proper entries for IP and names (tested that empirically ) and I have a number of graphs spec'd after trends:*

My sun connections all work fine (Solaris 9 mainly, no 10)

I am wondering if something needs to be changed in the compile to make the client work on SLES 10.

I am NOT a programmer, so need some help here...

lurch at inorbit.com

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

On the hobbit main page check reports > ghost clients.

If your server is listed there, it probably uses the wrong host name like geoff said.

In that case you should manually configure the host name in the client config file.

If the server is not in the ghost client list, the solaris box isn't sending so there would be a problem with the client...

Van Liefde Jonathan

FUJITSU

E. Mommaertslaan 16a, 1831 Diegem

Tel.: +32 (0) 2 712.77.25

Mob: +32 (0) 473 89.07.16

Fax: +32 (0) 2 712.77.56

E-mail: jonathan.vanliefde at be.fujitsu.com

Web: http://www.fujitsu.com/be

Fujitsu Services n.v., Registered in Belgium, Brussels no 606497, Registered Office E. Mommaertslaan 16a, 1831 Diegem

This e-mail is only for the use of its intended recipient. Its contents are subject to a duty of confidence and may be privileged. Fujitsu Services does not guarantee that this e-mail has not been intercepted and amended or that

From: Stephen [mailto:Stephen.Mullin at usa.net] Sent: Wednesday, December 10, 2008 3:29 PM To: hobbit at hswn.dk Subject: Re: [hobbit] Novell SuSE SLES 10 client issue.

I've lots of SuSE 9,10,10sp1 clients with no client problems.

? are other clients able to send?

-Steve

Geoff Hallford wrote:

I would also check the ghost client report to make sure that the SLES client is sending the correct hostname to the Hobbit server. I have found on some linux clients, it send the hostname and some send the FQDN. I usually just manually modify the client config to send the hostname I want and not rely on the automatic (which I think is uname -n by default ... don't quote me on that though ... not near my Hobbit box right now).

'Nobody goes there anymore. It's too crowded.' --Yogi Berra

On Mon, Dec 1, 2008 at 11:10 PM, Great D Dilla <great.dilla at gmail.com> wrote:

A couple of things to check on the client: [1] Make sure that the hostname of the hobbit server is resolvable from the client side. Or better yet, use the IP address of the hobbit server on the config file ==> BBDISPLAY=[IP_or_HOSTNAME_of_hobbit_server]. [2] Check to see if indeed the master is getting files. Usually there are files in the data directory generated for your client.

Side note: To configure the hobbit client, simply use "./configure.client" and supply the IP of the hobbit server. It should work out of the box.

Hope this helps.

-----Original Message----- From: Brian Catlin [mailto:bcatlin at gmail.com] Sent: Tuesday, December 02, 2008 10:34 AM To: hobbit at hswn.dk Subject: [hobbit] Novell SuSE SLES 10 client issue.

Okay,

I have a few Novell SuSE SLES 10 servers. I compiled the 4.2 client on one of them and tried to get it to talk to the Master running on Solaris 9.

The page shows the Master tests, ping, ssh (and they work! - got paged tonight when the interface on one went AWOL)

On the client side. In client/tmp = the files are created and ready to send The client has a couple probes, and they have good output too.

I can telnet to the master from the clients on port 1984 successfully. The client refuses to publish out to the Master.

My bb-hosts has the proper entries for IP and names (tested that empirically ) and I have a number of graphs spec'd after trends:*

My sun connections all work fine (Solaris 9 mainly, no 10)

I am wondering if something needs to be changed in the compile to make the client work on SLES 10.

I am NOT a programmer, so need some help here...

lurch at inorbit.com

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk

To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk