hobbit-clients.cfg not working?
Hi guys, first post here. I have been searching archives and google all day, but so far have come across nothing.
Scenario: Server has disk with oracle data store, is always on 99% and swap (this is normal for these hosts is always between 50 and 60
modified hobbit-clients.cfg to say
HOST=cypher DISK /data2 IGNORE DISK /data3 IGNORE DISK /data4 IGNORE
HOST=brown,crusher,cypher MEMSWAP 60 80
DEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97
Yet nothing on the display changes. Disk is still red (i had it on 100 101 as well before ignore) and swap still shows yellow.
/data2 (94% used) has reached the WARNING level (90%) red /data3 (99% used) has reached the PANIC level (95%) yellow /data4 (92% used) has reached the WARNING level (90%)
The is being read, because when I make an error it shows up in the log file, but these changes have no effect. What am I missing?
Thanks Stef
What is the hostname of the client machine? Is there anything related to this machine on the Ghost report?
Stefan van der Walt wrote:
Hi guys, first post here. I have been searching archives and google all day, but so far have come across nothing.
Scenario: Server has disk with oracle data store, is always on 99% and swap (this is normal for these hosts is always between 50 and 60
modified hobbit-clients.cfg to say
HOST=cypher DISK /data2 IGNORE DISK /data3 IGNORE DISK /data4 IGNORE
HOST=brown,crusher,cypher MEMSWAP 60 80
DEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97
Yet nothing on the display changes. Disk is still red (i had it on 100 101 as well before ignore) and swap still shows yellow.
/data2 (94% used) has reached the WARNING level (90%) red /data3 (99% used) has reached the PANIC level (95%) yellow /data4 (92% used) has reached the WARNING level (90%)
The is being read, because when I make an error it shows up in the log file, but these changes have no effect. What am I missing?
Thanks Stef
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
The host for the disk usage is "cypher", and it is not in the ghost report. All the other checks are normal and are working fine.
On 24/10/2007, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
What is the hostname of the client machine? Is there anything related to this machine on the Ghost report?
Stefan van der Walt wrote:
Hi guys, first post here. I have been searching archives and google all day, but so far have come across nothing.
Scenario: Server has disk with oracle data store, is always on 99% and swap (this is normal for these hosts is always between 50 and 60
modified hobbit-clients.cfg to say
HOST=cypher DISK /data2 IGNORE DISK /data3 IGNORE DISK /data4 IGNORE
HOST=brown,crusher,cypher MEMSWAP 60 80
DEFAULT # These are the built-in defaults. UP 1h LOAD 5.0 10.0 DISK * 90 95 MEMPHYS 100 101 MEMSWAP 50 80 MEMACT 90 97
Yet nothing on the display changes. Disk is still red (i had it on 100 101 as well before ignore) and swap still shows yellow.
/data2 (94% used) has reached the WARNING level (90%) red /data3 (99% used) has reached the PANIC level (95%) yellow /data4 (92% used) has reached the WARNING level (90%)
The is being read, because when I make an error it shows up in the log file, but these changes have no effect. What am I missing?
Thanks Stef
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
I just wanted to make sure that the IP address that comes back from DNS when you ping cypher is the same as the one that you have in bb-hosts.
Is the IP Address of the Hobbit server correct in the client configuration?
Stefan van der Walt wrote:
The host for the disk usage is "cypher", and it is not in the ghost report. All the other checks are normal and are working fine.
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
Yes, DNS is working fine,
10.254.8.140 cypher # conn cpu disk files memory msgs ports procs
hobbit at hostname:~/server/etc> ping cypher PING cypher.xyz.com (10.254.8.140) 56(84) bytes of data. 64 bytes from cypher.xyz.com (10.254.8.140): icmp_seq=1 ttl=253 time=0.677 ms
On 24/10/2007, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
I just wanted to make sure that the IP address that comes back from DNS when you ping cypher is the same as the one that you have in bb-hosts.
Is the IP Address of the Hobbit server correct in the client configuration?
Stefan van der Walt wrote:
The host for the disk usage is "cypher", and it is not in the ghost report. All the other checks are normal and are working fine.
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
And the second item?
Does the setting for BBDISP in hobbitclient.cfg on the client match the IP Address of the Hobbit server?
Stefan van der Walt wrote:
Yes, DNS is working fine,
10.254.8.140 cypher # conn cpu disk files memory msgs ports procs
hobbit at hostname:~/server/etc> ping cypher PING cypher.xyz.com (10.254.8.140) 56(84) bytes of data. 64 bytes from cypher.xyz.com (10.254.8.140): icmp_seq=1 ttl=253 time=0.677 ms
On 24/10/2007, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
I just wanted to make sure that the IP address that comes back from DNS when you ping cypher is the same as the one that you have in bb-hosts.
Is the IP Address of the Hobbit server correct in the client configuration?
-- Rich Smrcina VM Assist, Inc. Phone: 414-491-6001 Ans Service: 360-715-2467 rich.smrcina at vmassist.com http://www.linkedin.com/in/richsmrcina
Catch the WAVV! http://www.wavv.org WAVV 2008 - Chattanooga - April 18-22, 2008
Yes, the client data is uploaded without any problem and is displayed fine. it's just the new thresholds on the server side config that is not working.
Second item is also properly configured.
On 24/10/2007, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
And the second item?
Does the setting for BBDISP in hobbitclient.cfg on the client match the IP Address of the Hobbit server?
Have you tried adding "CLIENT=cypher.xyz.com" to the bb-hosts entry for cypher?
On 10/24/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes, the client data is uploaded without any problem and is displayed fine. it's just the new thresholds on the server side config that is not working.
Second item is also properly configured.
On 24/10/2007, Rich Smrcina <rsmrcina at wi.rr.com> wrote:
And the second item?
Does the setting for BBDISP in hobbitclient.cfg on the client match the IP Address of the Hobbit server?
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
Yes. 10.254.8.140 cypher # conn cpu disk files memory msgs ports procs CLIENT:cypher It still does not work.
I've checked everything, file permission, syntax, tabs vs. spaces, owner, dropped the host, deleted it, recreated, and I don't know what else I can try, but the values in hobbit-client.cfg is ignored completely, and it's driving me up the wall.
it IS being read because when I put an invalid entry into the cfg file, the errors show up in the logs.
it looks like the warn and panic values are hardcoded into the system. is there any way that I can actually test my config?
On 25/10/2007, Gary Baluha <gumby3203 at gmail.com> wrote:
Have you tried adding "CLIENT=cypher.xyz.com" to the bb-hosts entry for cypher?
On 10/24/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes, the client data is uploaded without any problem and is displayed fine. it's just the new thresholds on the server side config that is not working.
Second item is also properly configured.
On 24/10/2007, Rich Smrcina < rsmrcina at wi.rr.com> wrote:
And the second item?
Does the setting for BBDISP in hobbitclient.cfg on the client match the IP Address of the Hobbit server?
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On 10/30/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes. 10.254.8.140 cypher # conn cpu disk files memory msgs ports procs CLIENT:cypher It still does not work.
That still isn't the FQDN of the machine cypher. If the machine is literally cypher.xyz.com, I meant to add exactly CLIENT=cypher.xyz.com. I have had this bite me a few times myself.
On 25/10/2007, Gary Baluha <gumby3203 at gmail.com > wrote:
Have you tried adding "CLIENT= cypher.xyz.com" to the bb-hosts entry for cypher?
On 10/24/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes, the client data is uploaded without any problem and is displayed fine. it's just the new thresholds on the server side config that is not working.
Second item is also properly configured.
On 24/10/2007, Rich Smrcina < rsmrcina at wi.rr.com> wrote:
And the second item?
Does the setting for BBDISP in hobbitclient.cfg on the client match the IP Address of the Hobbit server?
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
That is the case, but that will typically break the whole reporting of the host, and not just one aspect of a hsot's monitoring?
On 30/10/2007, Gary Baluha <gumby3203 at gmail.com> wrote:
On 10/30/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes. 10.254.8.140 cypher # conn cpu disk files memory msgs ports procs CLIENT:cypher It still does not work.
That still isn't the FQDN of the machine cypher. If the machine is literally cypher.xyz.com, I meant to add exactly CLIENT=cypher.xyz.com . I have had this bite me a few times myself.
On 25/10/2007, Gary Baluha <gumby3203 at gmail.com > wrote:
Have you tried adding "CLIENT= cypher.xyz.com" to the bb-hosts entry for cypher?
On 10/24/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes, the client data is uploaded without any problem and is displayed fine. it's just the new thresholds on the server side config that is not working.
Second item is also properly configured.
On 24/10/2007, Rich Smrcina < rsmrcina at wi.rr.com> wrote:
And the second item?
Does the setting for BBDISP in hobbitclient.cfg on the client match the IP Address of the Hobbit server?
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
I usually start my troubleshooting by making sure I have a "CLIENT:" entry for the host in question, since the host needs to be working properly first. That, and making sure the IP is actually the IP the host is reporting itself as.
Henrik can correct me if I'm wrong, but from my experience, Hobbit matches the data coming in to it from the clients by IP address (as well as using the IP address for network tests). I haven't figured out exactly where the name comes into play, but it seems to use the name from the second field after the IP address is processed. If the name and IP don't match and there isn't a CLIENT: field, it seems to get confused.
My point being, the entry in the bb-hosts file might not be related to the problem you are having, but it's a good starting point.
On 10/30/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
That is the case, but that will typically break the whole reporting of the host, and not just one aspect of a hsot's monitoring?
On 30/10/2007, Gary Baluha <gumby3203 at gmail.com> wrote:
On 10/30/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes. 10.254.8.140 cypher # conn cpu disk files memory msgs ports procs CLIENT:cypher It still does not work.
That still isn't the FQDN of the machine cypher. If the machine is literally cypher.xyz.com , I meant to add exactly CLIENT=cypher.xyz.com . I have had this bite me a few times myself.
On 25/10/2007, Gary Baluha <gumby3203 at gmail.com > wrote:
Have you tried adding "CLIENT= cypher.xyz.com" to the bb-hosts entry for cypher?
On 10/24/07, Stefan van der Walt <skjoldar at gmail.com> wrote:
Yes, the client data is uploaded without any problem and is displayed fine. it's just the new thresholds on the server side config that is not working.
Second item is also properly configured.
On 24/10/2007, Rich Smrcina < rsmrcina at wi.rr.com> wrote:
And the second item?
Does the setting for BBDISP in hobbitclient.cfg on the client match the IP Address of the Hobbit server?
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Tue, Oct 30, 2007 at 10:28:25AM -0400, Gary Baluha wrote:
Henrik can correct me if I'm wrong, but from my experience, Hobbit matches the data coming in to it from the clients by IP address (as well as using the IP address for network tests). I haven't figured out exactly where the name comes into play, but it seems to use the name from the second field after the IP address is processed. If the name and IP don't match and there isn't a CLIENT: field, it seems to get confused.
Actually, Hobbit doesn't use the IP for any matching of client data with the hosts that Hobbit knows about. This all happens based on the hostname that the client reports, and the hostnames in the bb-hosts file.
The client usually picks up the hostname from the "uname -n" command output, and uses this when reporting data to Hobbit. Hobbit then looks for this name in the bb-hosts file (2nd column) and if there's a match, that one is used. However, it often happens that these names do not match - typically there's a fully-qualified hostname in one place, and a plain hostname with no domain in the other. To handle this, you can use the CLIENT tag to tell Hobbit about the "alias" name that the client uses.
Henrik
On 10/30/07, Henrik Stoerner <henrik at hswn.dk> wrote:
On Tue, Oct 30, 2007 at 10:28:25AM -0400, Gary Baluha wrote:
Henrik can correct me if I'm wrong, but from my experience, Hobbit matches the data coming in to it from the clients by IP address (as well as using the IP address for network tests). I haven't figured out exactly where the name comes into play, but it seems to use the name from the second field after the IP address is processed. If the name and IP don't match and there isn't a CLIENT: field, it seems to get confused.
Actually, Hobbit doesn't use the IP for any matching of client data with the hosts that Hobbit knows about. This all happens based on the hostname that the client reports, and the hostnames in the bb-hosts file.
Ah, right. IP is just for network tests then, correct?
The client usually picks up the hostname from the "uname -n" command
output, and uses this when reporting data to Hobbit. Hobbit then looks for this name in the bb-hosts file (2nd column) and if there's a match, that one is used. However, it often happens that these names do not match - typically there's a fully-qualified hostname in one place, and a plain hostname with no domain in the other. To handle this, you can use the CLIENT tag to tell Hobbit about the "alias" name that the client uses.
On Wed, Oct 31, 2007 at 09:29:01AM -0400, Gary Baluha wrote:
Actually, Hobbit doesn't use the IP for any matching of client data with the hosts that Hobbit knows about. This all happens based on the hostname that the client reports, and the hostnames in the bb-hosts file.
Ah, right. IP is just for network tests then, correct?
Yes, and even there Hobbit will - by default - do a DNS lookup on the hostname, and use the IP returned from the DNS server, instead of the one in the bb-hosts file.
The IP in the bb-hosts file is only used if there is a "testip" tag on the host, or the DNS lookup fails.
Henrik
On Wed, Oct 24, 2007 at 02:18:19PM +0200, Stefan van der Walt wrote:
Server has disk with oracle data store, is always on 99% and swap (this is normal for these hosts is always between 50 and 60
modified hobbit-clients.cfg to say
HOST=cypher DISK /data2 IGNORE DISK /data3 IGNORE DISK /data4 IGNORE
HOST=brown,crusher,cypher MEMSWAP 60 80
First, you ARE running the Hobbit client on cypher, right?
If you're using the original Big Brother client, then the client configuration is stored on the client, and modifying the hobbit-clients.cfg file on the Hobbit server has no effect.
If you're using the Hobbit client, then your "disk" status column must have a "Client data" link near the bottom of the webpage, right above the disk graph.
Could you try dumping the hobbit-clients.cfg file so we can have a look at how it is parsed ? Run the command "bbcmd hobbitd_client --test" and at the prompt enter a '?':
$ bbcmd hobbitd_client --test 2007-10-30 12:39:28 Using default environment file /usr/lib/hobbit/server/etc/hobbitserver.cfg Hostname (.=end, ?=dump, !=reload) []: ? DISK / 50% 60% 0 -1 red HOST=redhat (line: 350) DISK / 70% 80% 0 -1 red HOST=mail (line: 353) UP 3600 -1 (line: 357) LOAD 5.00 10.00 (line: 358) DISK / 85% 90% 0 -1 red (line: 359) DISK *IGNORE (line: 360) MEMREAL 100 101 (line: 361) MEMSWAP 50 80 (line: 362) MEMACT 90 97 (line: 363)
After that, try the specific test for cypher:
Hostname (.=end, ?=dump, !=reload) []: cypher Hosttype []: Test (cpu, mem, disk, proc, log, port): disk Filesystem: /data2 Yellow at 50%, red at 60%
Regards, Henrik
The client is running on cypher, but there is no client data link.
The server and client are all clean installs/compiles of hobbit 4.2.0
DISK /dev/vg03/lvol2 99% 100% 0 -1 red HOST=cypher (line: 350) DISK /data3 99% 100% 0 -1 red HOST=cypher (line: 351) DISK /data4 99% 100% 0 -1 red HOST=cypher (line: 352) MEMSWAP 60 80 HOST=cypher (line: 353) MEMSWAP 60 80 HOST=brown,crusher (line: 356) DISK /data3 99% 100% 0 -1 red HOST=bones (line: 359) UP 3600 -1 (line: 363) LOAD 5.00 10.00 (line: 364) DISK * 90% 95% 0 -1 red (line: 365) MEMREAL 100 101 (line: 366) MEMSWAP 50 80 (line: 367) MEMACT 90 97 (line: 368)
Hostname (.=end, ?=dump, !=reload) [?]: cypher Hosttype []: Test (cpu, mem, disk, proc, log, port): disk Filesystem: /data2 Segmentation fault
Eek..
On 30/10/2007, Henrik Stoerner <henrik at hswn.dk> wrote:
On Wed, Oct 24, 2007 at 02:18:19PM +0200, Stefan van der Walt wrote:
Server has disk with oracle data store, is always on 99% and swap (this is normal for these hosts is always between 50 and 60
modified hobbit-clients.cfg to say
HOST=cypher DISK /data2 IGNORE DISK /data3 IGNORE DISK /data4 IGNORE
HOST=brown,crusher,cypher MEMSWAP 60 80
First, you ARE running the Hobbit client on cypher, right?
If you're using the original Big Brother client, then the client configuration is stored on the client, and modifying the hobbit-clients.cfg file on the Hobbit server has no effect.
If you're using the Hobbit client, then your "disk" status column must have a "Client data" link near the bottom of the webpage, right above the disk graph.
Could you try dumping the hobbit-clients.cfg file so we can have a look at how it is parsed ? Run the command "bbcmd hobbitd_client --test" and at the prompt enter a '?':
$ bbcmd hobbitd_client --test 2007-10-30 12:39:28 Using default environment file /usr/lib/hobbit/server/etc/hobbitserver.cfg Hostname (.=end, ?=dump, !=reload) []: ? DISK / 50% 60% 0 -1 red HOST=redhat (line: 350) DISK / 70% 80% 0 -1 red HOST=mail (line: 353) UP 3600 -1 (line: 357) LOAD 5.00 10.00 (line: 358) DISK / 85% 90% 0 -1 red (line: 359) DISK *IGNORE (line: 360) MEMREAL 100 101 (line: 361) MEMSWAP 50 80 (line: 362) MEMACT 90 97 (line: 363)
After that, try the specific test for cypher:
Hostname (.=end, ?=dump, !=reload) []: cypher Hosttype []: Test (cpu, mem, disk, proc, log, port): disk Filesystem: /data2 Yellow at 50%, red at 60%
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
strace ./bbcmd hobbitd_client --test
<snip> write(1, "Filesystem: ", 12Filesystem: ) = 12 read(0, /data2 "/data2\n", 1024) = 7 --- SIGSEGV (Segmentation fault) @ 0 (0) --- +++ killed by SIGSEGV +++ Process 5852 detached <snip>
I saw when I changed the defaults for disk only the server actually changed and accepted the new values
On 30/10/2007, Stefan van der Walt <skjoldar at gmail.com> wrote:
The client is running on cypher, but there is no client data link.
The server and client are all clean installs/compiles of hobbit 4.2.0
DISK /dev/vg03/lvol2 99% 100% 0 -1 red HOST=cypher (line: 350) DISK /data3 99% 100% 0 -1 red HOST=cypher (line: 351) DISK /data4 99% 100% 0 -1 red HOST=cypher (line: 352) MEMSWAP 60 80 HOST=cypher (line: 353) MEMSWAP 60 80 HOST=brown,crusher (line: 356) DISK /data3 99% 100% 0 -1 red HOST=bones (line: 359) UP 3600 -1 (line: 363) LOAD 5.00 10.00 (line: 364) DISK * 90% 95% 0 -1 red (line: 365) MEMREAL 100 101 (line: 366) MEMSWAP 50 80 (line: 367) MEMACT 90 97 (line: 368)
Hostname (.=end, ?=dump, !=reload) [?]: cypher Hosttype []: Test (cpu, mem, disk, proc, log, port): disk Filesystem: /data2 Segmentation fault
Eek..
On 30/10/2007, Henrik Stoerner < henrik at hswn.dk> wrote:
On Wed, Oct 24, 2007 at 02:18:19PM +0200, Stefan van der Walt wrote:
Server has disk with oracle data store, is always on 99% and swap (this is normal for these hosts is always between 50 and 60
modified hobbit-clients.cfg to say
HOST=cypher DISK /data2 IGNORE DISK /data3 IGNORE DISK /data4 IGNORE
HOST=brown,crusher,cypher MEMSWAP 60 80
First, you ARE running the Hobbit client on cypher, right?
If you're using the original Big Brother client, then the client configuration is stored on the client, and modifying the hobbit-clients.cfg file on the Hobbit server has no effect.
If you're using the Hobbit client, then your "disk" status column must have a "Client data" link near the bottom of the webpage, right above the disk graph.
Could you try dumping the hobbit-clients.cfg file so we can have a look at how it is parsed ? Run the command "bbcmd hobbitd_client --test" and at the prompt enter a '?':
$ bbcmd hobbitd_client --test 2007-10-30 12:39:28 Using default environment file /usr/lib/hobbit/server/etc/hobbitserver.cfg Hostname (.=end, ?=dump, !=reload) []: ? DISK / 50% 60% 0 -1 red HOST=redhat (line: 350) DISK / 70% 80% 0 -1 red HOST=mail (line: 353) UP 3600 -1 (line: 357) LOAD 5.00 10.00 (line: 358) DISK / 85% 90% 0 -1 red (line: 359) DISK *IGNORE (line: 360) MEMREAL 100 101 (line: 361) MEMSWAP 50 80 (line: 362) MEMACT 90 97 (line: 363)
After that, try the specific test for cypher:
Hostname (.=end, ?=dump, !=reload) []: cypher Hosttype []: Test (cpu, mem, disk, proc, log, port): disk Filesystem: /data2 Yellow at 50%, red at 60%
Regards, Henrik
To unsubscribe from the hobbit list, send an e-mail to hobbit-unsubscribe at hswn.dk
On Tue, Oct 30, 2007 at 02:00:54PM +0200, Stefan van der Walt wrote:
The client is running on cypher, but there is no client data link.
If you have a "disk" status then for this host, then the status is generated on the client - ie. the client is NOT reporting any data that is analysed by hobbit-clients.cfg; instead, the client determines the status color by itself and just reports a "status" message instead of the raw client data.
There are only two possible explanations: The client is either running the old Big Brother client (not the Hobbit client), or it is running the Hobbit client in the "local" configuration mode where the data is analysed on the client instead of being analysed on the Hobbit server. Check the "clientlaunch.cfg" config file on the client, and see if the [client] section CMD setting includes the "--local" option.
If you do want to run the client in the local-config mode, then changes to the hobbit-clients.cfg file must be done on the client machine, instead of on the Hobbit server.
Henrik
participants (4)
-
gumby3203＠gmail.com
-
henrik＠hswn.dk
-
rsmrcina＠wi.rr.com
-
skjoldar＠gmail.com