Ubuntu Xymon client – server not showing client data

Used apt-get to install Hobbit client on Ubuntu.
Server can see conn, http, info, ssh, trends but nothing else.
Server configured to watch cmlin01.mydomain.lan
VIA hostname -f, found out ubuntu box thinks it is cmlin01

NO data being received on server for this client:

[xymon@cmlin03 data]$ ls /opt/cmtools/xymon/datahostdata
cmlin02.mydomain.lan  cmlin03.mydomain.lan

BUT data exists on the client:

root@cmlin01:/usr/lib/hobbit/client# pwd
/usr/lib/hobbit/client
root@cmlin01:/usr/lib/hobbit/client# ls -l tmp/*
-rw-r--r-- 1 hobbit hobbit   235 2012-05-24 14:29 tmp/hobbit_vmstat.cmlin01.mydomain.lan.18697
-rw-r--r-- 1 hobbit hobbit    41 2012-05-24 14:29 tmp/logfetch.cmlin01.mydomain.lan.cfg
-rw-r--r-- 1 hobbit hobbit    32 2012-05-24 14:29 tmp/logfetch.cmlin01.mydomain.lan.status
-rw-r--r-- 1 hobbit hobbit 53089 2012-05-24 14:29 tmp/msg.cmlin01.mydomain.lan.txt

THUS, DATA IS GENERATED ON CLIENT BUT NOT SERVER NOT GETTING IT.

root@cmlin01:/usr/lib/hobbit/client# more /etc/hostname
cmlin01.mydomain.lan
root@cmlin01:/usr/lib/hobbit/client# hostname -f
cmlin01

MORE /etc/hosts

...
192.168.0.26   cmlin01 cmlin01.mydomain.lan
...

EDIT /etc/hosts

...
192.168.0.26    cmlin01.mydomain.lan
...
root@cmlin01:/usr/lib/hobbit/client# hostname -f
cmlin01.mydomain.lan
root@cmlin01:/usr/lib/hobbit/client# /etc/init.d/hobbit-client restart
 * Stopping Hobbit Client hobbitclient                                                                                                                                                                                                                            [ OK ] 
 * Starting Hobbit Client hobbitclient

However, data still not showing up on server.

DATA IS BEING GENERATED.

root@cmlin01:/usr/lib/hobbit/client/logs# ps -ef | grep obbit
hobbit   15311     1  0 13:47 ?        00:00:00 /usr/lib/hobbit/client/bin/hobbitlaunch --config=/etc/hobbit/clientlaunch.cfg --log=/var/log/hobbit/clientlaunch.log --pidfile=/var/run/hobbit/clientlaunch.pid
hobbit   15729     1  0 13:52 ?        00:00:00 sh -c vmstat 300 2 1>/var/lib/hobbit/tmp/hobbit_vmstat.cmlin01.mydomain.lan.15700 2>&1; mv /var/lib/hobbit/tmp/hobbit_vmstat.cmlin01.mydomain.lan.15700 /var/lib/hobbit/tmp/hobbit_vmstat.cmlin01.mydomain.lan
hobbit   15731 15729  0 13:52 ?        00:00:00 vmstat 300 2
root     15747 14251  0 13:54 pts/0    00:00:00 grep --color=auto obbit
root@cmlin01:/usr/lib/hobbit/client# ls -l tmp/*
-rw-r--r-- 1 hobbit hobbit   235 2012-05-24 13:52 tmp/hobbit_vmstat.cmlin01.mydomain.lan.15700
-rw-r--r-- 1 hobbit hobbit   235 2012-05-24 13:56 tmp/hobbit_vmstat.cmlin01.mydomain.lan.16150
-rw-r--r-- 1 hobbit hobbit 53286 2012-05-24 13:56 tmp/msg.cmlin01.mydomain.lan.txt

BUT DATA IS NOT BEING SEEN BY SERVER.

root@cmlin01:/usr/lib/hobbit/client# echo hobbitdboard | nc 192.168.0.32 1984
cmlin01.mydomain.lan|trends|green||0|0|0|0|0|||
cmlin01.mydomain.lan|info|green||0|0|0|0|0|||
cmlin01.mydomain.lan|dns|green|OrdastLe|1337293141|1337893088|1337894888|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 13:58:08 2012 dns ok 
cmlin01.mydomain.lan|http|green||1337293562|1337893088|1337894888|0|0|127.0.0.1||green Thu May 24 13:58:08 2012: OK ; OK
cmlin01.mydomain.lan|ssh|green|OrdastLe|1337292539|1337893088|1337894888|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 13:58:08 2012 ssh ok 
cmlin01.mydomain.lan|conn|green|OrdAstLe|1337292539|1337893088|1337894888|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Thu May 24 13:58:08 2012 conn ok 
cmlin02.mydomain.lan|trends|green||0|0|0|0|0|||
cmlin02.mydomain.lan|info|green||0|0|0|0|0|||
cmlin02.mydomain.lan|memory|green||1337795314|1337892949|1337894749|0|0|192.168.0.25||green Thu May 24 13:55:43 PDT 2012 - Memory OK
cmlin02.mydomain.lan|files|clear||1337795314|1337892949|1337894749|0|0|192.168.0.25||clear Files status at Thu May 24 13:55:43 PDT 2012
cmlin02.mydomain.lan|msgs|green||1337798193|1337892949|1337894749|0|0|192.168.0.25||green System logs at Thu May 24 13:55:43 PDT 2012
cmlin02.mydomain.lan|ports|clear||1337795314|1337892949|1337894749|0|0|192.168.0.25||clear Thu May 24 13:55:43 PDT 2012 - Ports NOT ok
cmlin02.mydomain.lan|procs|clear||1337795314|1337892949|1337894749|0|0|192.168.0.25||clear Thu May 24 13:55:43 PDT 2012 - Processes NOT ok
cmlin02.mydomain.lan|disk|green||1337795314|1337892949|1337894749|0|0|192.168.0.25||green Thu May 24 13:55:43 PDT 2012 - Filesystems OK
cmlin02.mydomain.lan|cpu|green||1337795314|1337892949|1337894749|0|0|192.168.0.25||green Thu May 24 13:55:43 PDT 2012 up: 58 days, 2 users, 259 procs, load=0.00
cmlin02.mydomain.lan|http|green||1337297352|1337893088|1337894888|0|0|127.0.0.1||green Thu May 24 13:58:08 2012: OK ; OK
cmlin02.mydomain.lan|ssh|green|OrdastLe|1337297352|1337893088|1337894888|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 13:58:08 2012 ssh ok 
cmlin02.mydomain.lan|conn|green|OrdAstLe|1337297352|1337893088|1337894888|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Thu May 24 13:58:08 2012 conn ok 
cmlin03.mydomain.lan|trends|green||0|0|0|0|0|||
cmlin03.mydomain.lan|info|green||0|0|0|0|0|||
cmlin03.mydomain.lan|xymond|green||1337288925|1337892844|1337894644|0|0|xymond||green
cmlin03.mydomain.lan|xymongen|green||1337288390|1337893063|1337894863|0|0|127.0.0.1||green Thu May 24 13:57:43 2012
cmlin03.mydomain.lan|memory|green||1337288335|1337892888|1337894688|0|0|127.0.0.1||green Thu May 24 13:54:42 PDT 2012 - Memory OK
cmlin03.mydomain.lan|files|clear||1337288335|1337892888|1337894688|0|0|127.0.0.1||clear Files status at Thu May 24 13:54:42 PDT 2012
cmlin03.mydomain.lan|msgs|green||1337288636|1337892888|1337894688|0|0|127.0.0.1||green System logs at Thu May 24 13:54:42 PDT 2012
cmlin03.mydomain.lan|ports|clear||1337288335|1337892888|1337894688|0|0|127.0.0.1||clear Thu May 24 13:54:42 PDT 2012 - Ports NOT ok
cmlin03.mydomain.lan|procs|clear||1337288335|1337892888|1337894688|0|0|127.0.0.1||clear Thu May 24 13:54:42 PDT 2012 - Processes NOT ok
cmlin03.mydomain.lan|disk|green||1337288335|1337892888|1337894688|0|0|127.0.0.1||green Thu May 24 13:54:42 PDT 2012 - Filesystems OK
cmlin03.mydomain.lan|cpu|green||1337288335|1337892888|1337894688|0|0|127.0.0.1||green Thu May 24 13:54:42 PDT 2012 up: 7 days, 0 users, 185 procs, load=0.00
cmlin03.mydomain.lan|xymonnet|green||1337288329|1337893088|1337894888|0|0|127.0.0.1||green Thu May 24 13:58:08 2012
cmlin03.mydomain.lan|http|green||1337288329|1337893088|1337894888|0|0|127.0.0.1||green Thu May 24 13:58:08 2012: OK
cmlin03.mydomain.lan|bbd|green|OrdastLe|1337288329|1337893088|1337894888|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 13:58:08 2012 bbd ok 
cmlin03.mydomain.lan|conn|green|OrdAstLe|1337288329|1337893088|1337894888|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Thu May 24 13:58:08 2012 conn ok 

NO FIREWALL PROBLEMS (CLIENT CAN TALK TO SERVER)

root@cmlin01:/usr/lib/hobbit/client# telnet cmlin03 1984
Trying 192.168.0.32...
Connected to cmlin03.mydomain.lan.
Escape character is '^]'.
^]

telnet> quit
Connection closed.

BOX NAME IS GOOD ON BOX.

root@cmlin01:/usr/lib/hobbit/client# hostname -f
cmlin01.mydomain.lan
root@cmlin01:/usr/lib/hobbit/client# uname -n
cmlin01.mydomain.lan

root@cmlin01:/usr/lib/hobbit/client# more /etc/hosts
127.0.0.1	localhost
192.168.0.26	cmlin01.mydomain.lan
...

CHECK OUT HOBBIT CLIENT CONFIG SCRIPT – WHY IS THIS NOT REFERENCED IN /usr/lib/hobbit/client?????

root@cmlin01:/usr/lib/hobbit/client# more /etc/default/hobbit-client 
# Configure the Hobbit client settings.

# You MUST set the list of Hobbit servers that this
# client reports to.
# It is good to use IP-adresses here instead of DNS
# names - DNS might not work if there's a problem.
# (Internally this will be translated to BBDISP and BBDISPLAYS
# variables in /var/run/hobbit/bbdisp-include.cfg)
#
# E.g. (a single Hobbit server)
#   HOBBITSERVERS="192.168.1.1"
# or (multiple servers)
#   HOBBITSERVERS="10.0.0.1 192.168.1.1"

HOBBITSERVERS="192.168.0.32"

# Hostname used by the client for its reports.
# Must match the name for this host in the Hobbit servers'
# bb-hosts file.

CLIENTHOSTNAME="cmlin01"

—- THIS CLIENTHOSTNAME IS INCORRECT!!!!!!

CHANGE TO:

...
# Hostname used by the client for its reports.
# Must match the name for this host in the Hobbit servers'
# bb-hosts file.

CLIENTHOSTNAME="cmlin01.mydomain.lan"

RESTART

root@cmlin01:/usr/lib/hobbit/client# /etc/init.d/hobbit-client restart
 * Stopping Hobbit Client hobbitclient                                                                                                                                                                                                                            [ OK ] 
 * Starting Hobbit Client hobbitclient                   

CHECK SERVER

root@cmlin01:/usr/lib/hobbit/client# echo hobbitdboard | nc 192.168.0.32 1984
cmlin01.mydomain.lan|trends|green||0|0|0|0|0|||
cmlin01.mydomain.lan|info|green||0|0|0|0|0|||
cmlin01.mydomain.lan|memory|green||1337894077|1337894077|1337895877|0|0|192.168.0.26||green Thu May 24 14:14:31 PDT 2012 - Memory OK
cmlin01.mydomain.lan|files|clear||1337894077|1337894077|1337895877|0|0|192.168.0.26||clear Files status at Thu May 24 14:14:31 PDT 2012
cmlin01.mydomain.lan|msgs|clear||1337894077|1337894077|1337895877|0|0|192.168.0.26||clear System logs at Thu May 24 14:14:31 PDT 2012 : No log data available
cmlin01.mydomain.lan|ports|clear||1337894077|1337894077|1337895877|0|0|192.168.0.26||clear Thu May 24 14:14:31 PDT 2012 - Ports NOT ok
cmlin01.mydomain.lan|procs|clear||1337894077|1337894077|1337895877|0|0|192.168.0.26||clear Thu May 24 14:14:31 PDT 2012 - Processes NOT ok
cmlin01.mydomain.lan|disk|green||1337894077|1337894077|1337895877|0|0|192.168.0.26||green Thu May 24 14:14:31 PDT 2012 - Filesystems OK
cmlin01.mydomain.lan|cpu|green||1337894077|1337894077|1337895877|0|0|192.168.0.26||green Thu May 24 14:14:31 PDT 2012 up: 58 days, 1 users, 123 procs, load=0.15
cmlin01.mydomain.lan|dns|green|OrdastLe|1337293141|1337894051|1337895851|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 14:14:11 2012 dns ok 
cmlin01.mydomain.lan|http|green||1337293562|1337894051|1337895851|0|0|127.0.0.1||green Thu May 24 14:14:11 2012: OK ; OK
cmlin01.mydomain.lan|ssh|green|OrdastLe|1337292539|1337894051|1337895851|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 14:14:11 2012 ssh ok 
cmlin01.mydomain.lan|conn|green|OrdAstLe|1337292539|1337894051|1337895851|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Thu May 24 14:14:11 2012 conn ok 
cmlin02.mydomain.lan|trends|green||0|0|0|0|0|||
cmlin02.mydomain.lan|info|green||0|0|0|0|0|||
cmlin02.mydomain.lan|memory|green||1337795314|1337893851|1337895651|0|0|192.168.0.25||green Thu May 24 14:10:45 PDT 2012 - Memory OK
cmlin02.mydomain.lan|files|clear||1337795314|1337893851|1337895651|0|0|192.168.0.25||clear Files status at Thu May 24 14:10:45 PDT 2012
cmlin02.mydomain.lan|msgs|green||1337798193|1337893851|1337895651|0|0|192.168.0.25||green System logs at Thu May 24 14:10:45 PDT 2012
cmlin02.mydomain.lan|ports|clear||1337795314|1337893851|1337895651|0|0|192.168.0.25||clear Thu May 24 14:10:45 PDT 2012 - Ports NOT ok
cmlin02.mydomain.lan|procs|clear||1337795314|1337893851|1337895651|0|0|192.168.0.25||clear Thu May 24 14:10:45 PDT 2012 - Processes NOT ok
cmlin02.mydomain.lan|disk|green||1337795314|1337893851|1337895651|0|0|192.168.0.25||green Thu May 24 14:10:45 PDT 2012 - Filesystems OK
cmlin02.mydomain.lan|cpu|green||1337795314|1337893851|1337895651|0|0|192.168.0.25||green Thu May 24 14:10:45 PDT 2012 up: 58 days, 2 users, 259 procs, load=0.00
cmlin02.mydomain.lan|http|green||1337297352|1337894051|1337895851|0|0|127.0.0.1||green Thu May 24 14:14:11 2012: OK ; OK
cmlin02.mydomain.lan|ssh|green|OrdastLe|1337297352|1337894051|1337895851|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 14:14:11 2012 ssh ok 
cmlin02.mydomain.lan|conn|green|OrdAstLe|1337297352|1337894051|1337895851|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Thu May 24 14:14:11 2012 conn ok 
cmlin03.mydomain.lan|trends|green||0|0|0|0|0|||
cmlin03.mydomain.lan|info|green||0|0|0|0|0|||
cmlin03.mydomain.lan|xymond|green||1337288925|1337894048|1337895848|0|0|xymond||green
cmlin03.mydomain.lan|xymongen|green||1337288390|1337894086|1337895886|0|0|127.0.0.1||green Thu May 24 14:14:46 2012
cmlin03.mydomain.lan|memory|green||1337288335|1337894091|1337895891|0|0|127.0.0.1||green Thu May 24 14:14:46 PDT 2012 - Memory OK
cmlin03.mydomain.lan|files|clear||1337288335|1337894091|1337895891|0|0|127.0.0.1||clear Files status at Thu May 24 14:14:46 PDT 2012
cmlin03.mydomain.lan|msgs|green||1337288636|1337894091|1337895891|0|0|127.0.0.1||green System logs at Thu May 24 14:14:46 PDT 2012
cmlin03.mydomain.lan|ports|clear||1337288335|1337894091|1337895891|0|0|127.0.0.1||clear Thu May 24 14:14:46 PDT 2012 - Ports NOT ok
cmlin03.mydomain.lan|procs|clear||1337288335|1337894091|1337895891|0|0|127.0.0.1||clear Thu May 24 14:14:46 PDT 2012 - Processes NOT ok
cmlin03.mydomain.lan|disk|green||1337288335|1337894091|1337895891|0|0|127.0.0.1||green Thu May 24 14:14:46 PDT 2012 - Filesystems OK
cmlin03.mydomain.lan|cpu|green||1337288335|1337894091|1337895891|0|0|127.0.0.1||green Thu May 24 14:14:46 PDT 2012 up: 7 days, 1 users, 190 procs, load=0.00
cmlin03.mydomain.lan|xymonnet|green||1337288329|1337894051|1337895851|0|0|127.0.0.1||green Thu May 24 14:14:11 2012
cmlin03.mydomain.lan|http|green||1337288329|1337894051|1337895851|0|0|127.0.0.1||green Thu May 24 14:14:11 2012: OK
cmlin03.mydomain.lan|bbd|green|OrdastLe|1337288329|1337894051|1337895851|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Thu May 24 14:14:11 2012 bbd ok 
cmlin03.mydomain.lan|conn|green|OrdAstLe|1337288329|1337894051|1337895851|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Thu May 24 14:14:11 2012 conn ok 

THE DATA IS GOING TO THE SERVER NOW!!!!