How to install Xymon client on OSX

NOTE: This example is on LION

1) download & install macports @ http://www.macports.org/install.php via dpkg file
— I downloaded it to ~/Downloads

cmosx02:Downloads cmuser$ sudo installer -pkg ~/Downloads/MacPorts-2.1.1-10.7-Lion.pkg -target /

cmosx02:Downloads cmuser$ ls /opt/local/bin/port
/opt/local/bin/port

2) regularly run update to ensure you have latest flavor

cmosx01:~ cmuser$ sudo port -v selfupdate

3) install xymon

cmosx02:Downloads cmuser$ sudo /opt/local/bin/port install xymon
...
###########################################################
# A startup item has been generated that will aid in
# starting xymon with launchd. It is disabled
# by default. Execute the following command to start it,
# and to cause it to launch at startup:
#
# sudo port load xymon
###########################################################
--->  Installing xymon @4.3.7_1
--->  Activating xymon @4.3.7_1

Set your Xymon server's IP address with the following command:
    $ sudo vi /opt/local/lib/xymon/client/etc/xymonclient.cfg

If you wish your xymon client to report logfiles to your xymon server
you need to add the user _xymon to the admin group like this:
    $ sudo dscl . -append /Groups/admin GroupMembership _xymon

You can start,stop and restart the xymon client with:
    $ sudo -u _xymon /opt/local/lib/xymon/client/runclient.sh
[start|stop|restart]

--->  Cleaning xymon
--->  Updating database of binaries: 100.0%
--->  Scanning binaries for linking errors: 100.0%
--->  No broken files found.

4) Set server’s IP in client

cmosx01:~ cmuser$ sudo vi /opt/local/lib/xymon/client/etc/xymonclient.cfg
Password:

# Environment settings for the Xymon client.

XYMSRV="192.168.0.32"          # IP address of the Xymon server
...

VERIFY CAN CONNECT

cmosx01:~ cmuser$ telnet 192.168.0.32 1984
Trying 192.168.0.32...
Connected to 192.168.0.32.
Escape character is '^]'.
^]
telnet> quit
Connection closed.

VERIFY BOX NAME

cmosx01:~ cmuser$ uname -n
cmosx01

IF YOU DON’T LIKE YOUR UNAME, CHANGE IT.

sudo scutil --set HostName cmosx04
cmosx04:~ cmuser$ uname -n
cmosx04

ENSURE xymon client to report logfiles to your xymon server

cmosx01:~ cmuser$ sudo dscl . -append /Groups/admin GroupMembership _xymon

CONFIGURE AUTO START

cmosx01:~ cmuser$ sudo -s
bash-3.2# launchctl load -w /Library/LaunchDaemons/org.macports.xymon.plist 
bash-3.2# launchctl start org.macports.xymon
bash-3.2# ps -ef | grep xymon
    0 32210     1   0  3:00PM ??         0:00.01 /opt/local/bin/daemondo --label=xymon --start-cmd /opt/local/etc/LaunchDaemons/org.macports.xymon/xymon.wrapper start ; --stop-cmd /opt/local/etc/LaunchDaemons/org.macports.xymon/xymon.wrapper stop ; --restart-cmd /opt/local/etc/LaunchDaemons/org.macports.xymon/xymon.wrapper restart ; --pid=none
  500 32224     1   0  3:00PM ??         0:00.00 /opt/local/lib/xymon/client/bin/xymonlaunch --config=/opt/local/lib/xymon/client/etc/clientlaunch.cfg --log=/opt/local/lib/xymon/client/logs/clientlaunch.log --pidfile=/opt/local/lib/xymon/client/logs/clientlaunch.cmosx01.pid
    0 32258 32202   0  3:01PM ttys000    0:00.00 grep xymon

REBOOT BOX TO ENSURE xymon IS RUNNING ON STARTUP.

bash-3.2# shutdown -r now
Shutdown NOW!
                                                                               
*** FINAL System shutdown message from cmuser@cmosx02 ***                    
System going down IMMEDIATELY                                                  
                                                                               
                                                                               

System shutdown time has arrived
cmosx01:~ cmuser$ ps -ef | grep xymon
    0    80     1   0  3:02PM ??         0:00.02 /opt/local/bin/daemondo --label=xymon --start-cmd /opt/local/etc/LaunchDaemons/org.macports.xymon/xymon.wrapper start ; --stop-cmd /opt/local/etc/LaunchDaemons/org.macports.xymon/xymon.wrapper stop ; --restart-cmd /opt/local/etc/LaunchDaemons/org.macports.xymon/xymon.wrapper restart ; --pid=none
  500   106     1   0  3:03PM ??         0:00.00 /opt/local/lib/xymon/client/bin/xymonlaunch --config=/opt/local/lib/xymon/client/etc/clientlaunch.cfg --log=/opt/local/lib/xymon/client/logs/clientlaunch.log --pidfile=/opt/local/lib/xymon/client/logs/clientlaunch.cmosx01.pid
  501   276   256   0  3:05PM ttys000    0:00.00 grep xymon

ADD NEW BOX TO SERVER @ server/etc/hosts.cfg

page           OSX                        OSX
192.168.0.29   cmosx01                    # ssh

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!!!!

CentOS Xymon server not showing client data

On CENTOS, Compiled / installed client for xymon.

./configure-server --prefix=/opt/cmtools/xymon

Can see conn, http, info, ssh, trends but nothing else.

1) Verify client can communicate with server:

[root@cmlin02 bin]# echo hobbitdboard | nc 192.168.0.32 1984
cmlin01.freerange360.lan|trends|green||0|0|0|0|0|||
cmlin01.freerange360.lan|info|green||0|0|0|0|0|||
cmlin01.freerange360.lan|dns|green|OrdastLe|1337293141|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:41:27 2012 dns ok
cmlin01.freerange360.lan|http|green||1337293562|1337722887|1337724687|0|0|127.0.0.1||green Tue May 22 14:41:27 2012: OK ; OK
cmlin01.freerange360.lan|ssh|green|OrdastLe|1337292539|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:41:27 2012 ssh ok
cmlin01.freerange360.lan|conn|green|OrdAstLe|1337292539|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:41:27 2012 conn ok
cmlin02|trends|green||0|0|0|0|0|||
cmlin02|info|green||0|0|0|0|0|||
cmlin02|conn|green|OrdAstLe|1337722766|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:41:27 2012 conn ok
cmlin02.freerange360.lan|trends|green||0|0|0|0|0|||
cmlin02.freerange360.lan|info|green||0|0|0|0|0|||
cmlin02.freerange360.lan|http|green||1337297352|1337722887|1337724687|0|0|127.0.0.1||green Tue May 22 14:41:27 2012: OK ; OK
cmlin02.freerange360.lan|ssh|green|OrdastLe|1337297352|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:41:27 2012 ssh ok
cmlin02.freerange360.lan|conn|green|OrdAstLe|1337297352|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:41:27 2012 conn ok
cmlin03.freerange360.lan|trends|green||0|0|0|0|0|||
cmlin03.freerange360.lan|info|green||0|0|0|0|0|||
cmlin03.freerange360.lan|xymond|green||1337288925|1337722926|1337724726|0|0|xymond||green
cmlin03.freerange360.lan|xymongen|green||1337288390|1337722922|1337724722|0|0|127.0.0.1||green Tue May 22 14:42:02 2012
cmlin03.freerange360.lan|memory|green||1337288335|1337722867|1337724667|0|0|127.0.0.1||green Tue May 22 14:41:01 PDT 2012 - Memory OK
cmlin03.freerange360.lan|files|clear||1337288335|1337722867|1337724667|0|0|127.0.0.1||clear Files status at Tue May 22 14:41:01 PDT 2012
cmlin03.freerange360.lan|msgs|green||1337288636|1337722867|1337724667|0|0|127.0.0.1||green System logs at Tue May 22 14:41:01 PDT 2012
cmlin03.freerange360.lan|ports|clear||1337288335|1337722867|1337724667|0|0|127.0.0.1||clear Tue May 22 14:41:01 PDT 2012 - Ports NOT ok
cmlin03.freerange360.lan|procs|clear||1337288335|1337722867|1337724667|0|0|127.0.0.1||clear Tue May 22 14:41:01 PDT 2012 - Processes NOT ok
cmlin03.freerange360.lan|disk|green||1337288335|1337722867|1337724667|0|0|127.0.0.1||green Tue May 22 14:41:01 PDT 2012 - Filesystems OK
cmlin03.freerange360.lan|cpu|green||1337288335|1337722867|1337724667|0|0|127.0.0.1||green Tue May 22 14:41:01 PDT 2012 up: 5 days, 1 users, 193 procs, load=0.00
cmlin03.freerange360.lan|xymonnet|green||1337288329|1337722887|1337724687|0|0|127.0.0.1||green Tue May 22 14:41:27 2012
cmlin03.freerange360.lan|http|green||1337288329|1337722887|1337724687|0|0|127.0.0.1||green Tue May 22 14:41:27 2012: OK
cmlin03.freerange360.lan|bbd|green|OrdastLe|1337288329|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:41:27 2012 bbd ok
cmlin03.freerange360.lan|conn|green|OrdAstLe|1337288329|1337722887|1337724687|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:41:27 2012 conn ok 
[root@cmlin02 bin]# ./xymon 192.168.0.32 hobbitdboard
cmlin01.freerange360.lan|trends|green||0|0|0|0|0|||
cmlin01.freerange360.lan|info|green||0|0|0|0|0|||
cmlin01.freerange360.lan|dns|green|OrdastLe|1337293141|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:43:27 2012 dns ok
cmlin01.freerange360.lan|http|green||1337293562|1337723007|1337724807|0|0|127.0.0.1||green Tue May 22 14:43:27 2012: OK ; OK
cmlin01.freerange360.lan|ssh|green|OrdastLe|1337292539|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:43:27 2012 ssh ok
cmlin01.freerange360.lan|conn|green|OrdAstLe|1337292539|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:43:27 2012 conn ok
cmlin02|trends|green||0|0|0|0|0|||
cmlin02|info|green||0|0|0|0|0|||
cmlin02|conn|green|OrdAstLe|1337722766|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:43:27 2012 conn ok
cmlin02.freerange360.lan|trends|green||0|0|0|0|0|||
cmlin02.freerange360.lan|info|green||0|0|0|0|0|||
cmlin02.freerange360.lan|http|green||1337297352|1337723007|1337724807|0|0|127.0.0.1||green Tue May 22 14:43:27 2012: OK ; OK
cmlin02.freerange360.lan|ssh|green|OrdastLe|1337297352|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:43:27 2012 ssh ok
cmlin02.freerange360.lan|conn|green|OrdAstLe|1337297352|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:43:27 2012 conn ok
cmlin03.freerange360.lan|trends|green||0|0|0|0|0|||
cmlin03.freerange360.lan|info|green||0|0|0|0|0|||
cmlin03.freerange360.lan|xymond|green||1337288925|1337722926|1337724726|0|0|xymond||green
cmlin03.freerange360.lan|xymongen|green||1337288390|1337723042|1337724842|0|0|127.0.0.1||green Tue May 22 14:44:02 2012
cmlin03.freerange360.lan|memory|green||1337288335|1337722867|1337724667|0|0|127.0.0.1||green Tue May 22 14:41:01 PDT 2012 - Memory OK
cmlin03.freerange360.lan|files|clear||1337288335|1337722867|1337724667|0|0|127.0.0.1||clear Files status at Tue May 22 14:41:01 PDT 2012
cmlin03.freerange360.lan|msgs|green||1337288636|1337722867|1337724667|0|0|127.0.0.1||green System logs at Tue May 22 14:41:01 PDT 2012
cmlin03.freerange360.lan|ports|clear||1337288335|1337722867|1337724667|0|0|127.0.0.1||clear Tue May 22 14:41:01 PDT 2012 - Ports NOT ok
cmlin03.freerange360.lan|procs|clear||1337288335|1337722867|1337724667|0|0|127.0.0.1||clear Tue May 22 14:41:01 PDT 2012 - Processes NOT ok
cmlin03.freerange360.lan|disk|green||1337288335|1337722867|1337724667|0|0|127.0.0.1||green Tue May 22 14:41:01 PDT 2012 - Filesystems OK
cmlin03.freerange360.lan|cpu|green||1337288335|1337722867|1337724667|0|0|127.0.0.1||green Tue May 22 14:41:01 PDT 2012 up: 5 days, 1 users, 193 procs, load=0.00
cmlin03.freerange360.lan|xymonnet|green||1337288329|1337723007|1337724807|0|0|127.0.0.1||green Tue May 22 14:43:27 2012
cmlin03.freerange360.lan|http|green||1337288329|1337723007|1337724807|0|0|127.0.0.1||green Tue May 22 14:43:27 2012: OK
cmlin03.freerange360.lan|bbd|green|OrdastLe|1337288329|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdastLe] --> Tue May 22 14:43:27 2012 bbd ok
cmlin03.freerange360.lan|conn|green|OrdAstLe|1337288329|1337723007|1337724807|0|0|127.0.0.1||green <!-- [flags:OrdAstLe] --> Tue May 22 14:43:27 2012 conn ok 

2) Verify your XYMSRV has the correct Xymon server IP address

[root@cmlin02 logs]# more ../etc/xymonclient.cfg
# Environment settings for the Xymon client.

XYMSRV="192.168.0.32"          # IP address of the Xymon server

...

3) Verify your host name matches between client & server.

[root@cmlin02 logs]# more ../etc/hosts.cfg
...
192.168.0.25   cmlin02.freerange360.lan   # ssh http://nexus.freerange360.lan:8081/nexus/index.html#view-repositories http://cmdb.freerange360.lan/ios/
...
[root@cmlin02 client]# hostname -f
cmlin02.freerange360.lan

[root@cmlin02 client]# uname -n
cmlin02.freerange360.lan

4) Check client for data files

[root@cmlin02 tmp]# ls -altr
total 160
drwxrwxr-x. 8 xymon xymon   4096 May 17 16:16 ..
-rw-rw-r--. 1 xymon xymon    244 May 22 16:36 xymon_vmstat.cmlin02.freerange360.lan.25735
-rw-rw-r--. 1 xymon xymon 151315 May 22 16:36 msg.cmlin02.freerange360.lan.txt
drwxrwxr-x. 2 xymon xymon   4096 May 22 16:36 .

5) Check server for data files

[cmuser@cmlin03 cmlin02.freerange360.lan]$ pwd
/opt/cmtools/xymon/data/rrd/cmlin02.freerange360.lan

[cmuser@cmlin03 cmlin02.freerange360.lan]$ ls -altr
total 688
drwxr-xr-x. 6 xymon xymon   4096 May 22 14:39 ..
drwxr-xr-x. 2 xymon xymon   4096 May 22 15:40 .
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:27 tcp.http.nexus.freerange360.lan:8081,nexus,index.html#view-repositories.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:27 tcp.conn.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:29 tcp.ssh.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:35 tcp.http.cmdb.freerange360.lan,ios,.rrd

[root@cmlin02 bin]# sudo -u xymon ./xymoncmd
2012-05-22 15:39:43 Using default environment file /opt/cmtools/xymon/client/etc/xymonclient.cfg
sh-4.1$ /opt/cmtools/xymon/client/bin/xymonclient.sh
[xymon@cmlin02 tmp]$ ls -altr
total 228
drwxrwxr-x. 8 xymon xymon   4096 May 17 16:16 ..
-rw-r--r--. 1 xymon xymon    244 May 22 15:41 xymon_vmstat.cmlin02.freerange360.lan.25109
-rw-r--r--. 1 xymon xymon 216889 May 22 15:41 msg.cmlin02.freerange360.lan.txt
-rw-r--r--. 1 xymon xymon     41 May 22 15:41 logfetch.cmlin02.freerange360.lan.cfg
drwxrwxr-x. 2 xymon xymon   4096 May 22 15:41 .

this created data and pushed it to the server once. the server has not received data since.

cmuser@cmlin03 cmlin02.freerange360.lan]$ ls -altr
total 688
drwxr-xr-x. 6 xymon xymon   4096 May 22 14:39 ..
drwxr-xr-x. 2 xymon xymon   4096 May 22 15:40 .
-rw-rw-r--. 1 xymon xymon  38624 May 22 16:44 disk,boot.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:44 clock.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:44 memory.real.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:44 memory.actual.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:44 la.rrd
-rw-rw-r--. 1 xymon xymon  38624 May 22 16:44 disk,root.rrd
-rw-rw-r--. 1 xymon xymon  38624 May 22 16:44 disk,home.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:44 procs.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:44 memory.swap.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 22 16:44 users.rrd
-rw-rw-r--. 1 xymon xymon  38624 May 22 16:46 ifstat.eth0.rrd
-rw-rw-r--. 1 xymon xymon 304400 May 22 16:46 netstat.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 23 09:32 tcp.http.nexus.freerange360.lan:8081,nexus,index.html#view-repositories.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 23 09:32 tcp.http.cmdb.freerange360.lan,ios,.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 23 09:32 tcp.conn.rrd
-rw-rw-r--. 1 xymon xymon  19640 May 23 09:38 tcp.ssh.rrd
ps -ef | grep xymon | awk '{print $2}' | xargs kill -9

SOLUTION:

vi /opt/cmtools/xymon/client/etc/clientlaunch.cfg

CHANGE:

...
[client]
...
	CMD /opt/cmtools/xymon/client/bin/xymonclient.sh --local
...

TO

...
[client]
...
	CMD /opt/cmtools/xymon/client/bin/xymonclient.sh
...

Rogue Dead Guy Ale Clone

malt & fermentables

% LB OZ MALT OR FERMENTABLE PPG °L
42% 13 0 Pale Malt, 2 Row, US 36 2 ~
35% 11 0 Munich Malt 37 9 ~
23% 7 0 Carastan 34 30 ~
Original Gravity
1.083 / 20.0° Plato

(1.075 to 1.087)
Final Gravity
1.021 / 5.3° Plato

(1.018 to 1.022)
Color
17° SRM / 33° EBC
(Light Brown to Medium Brown)
Mash Efficiency
75%

hops

USE TIME OZ VARIETY FORM AA
boil 60 mins 2.5 Perle leaf 8.0
boil 15 mins 0.5 Perle leaf 8.0
boil 15 mins 0.5 Saaz leaf 3.5
Bitterness
9.4 IBU / 20 HBU
ƒ: Tinseth
BU:GU
0.11

yeast

Wyeast Bavarian Lager (2206)

lager yeast in liquid form with medium to high flocculation and 75% attenuation
Alcohol
8.3% ABV / 6% ABW
Calories
274 per 12 oz.

Nankasi Oatis Oatmeal Stout – clone

malt & fermentables

% LB OZ MALT OR FERMENTABLE PPG °L
67% 24 8 American Two-row Pale 37 1 ~
11% 4 0 Oats, Flaked 37 1 ~
5% 2 0 Chocolate Malt (UK) 34 450 ~
5% 2 0 American Crystal 30L 34 30 ~
5% 2 0 American Crystal 60L 34 60 ~
5% 2 0 Roasted Barley – 550L 34 550 ~
36 8
Original Gravity
1.101 / 24.0° Plato

(1.090 to 1.106)
Final Gravity
1.023 / 5.8° Plato

(1.020 to 1.025)
Color
60° SRM / 119° EBC
(Black)
Mash Efficiency
75%

hops

USE TIME OZ VARIETY FORM AA
boil 60 mins 3.5 Nugget leaf 13.0
boil 45 mins 2.0 Fuggles leaf 4.5
Bitterness
14.9 IBU / 54 HBU
ƒ: Tinseth
BU:GU
0.15

yeast

Rogue Pacman Ale Yeast

Alcohol
10.4% ABV / 8% ABW
Calories
332 per 12 oz.

misc

USE TIME AMOUNT INGREDIENT
boil 15 min 2 ea Whirlfloc Tablet
boil 5 min 2 ea Yeast Nutrient (WYeast)

Bubble Tea Pearls

1 cup Tapioca Pearls
8 cups water
Approximately 6-10 servings

  1. Bring water to a boil
  2. Add tapioca pearls
  3. Stir & return to boil
  4. Cover and boil medium high for 15 minutes
  5. Turn of heat & allow to set for 15 minutes.
  6. Drain & rinse under cold water.
  7. Cover in bubble tea sugar syrup up to 12 hrs before serving

contacts.contacts_to_users: Accessor for field ‘user’ clashes with related field ‘User.contacts_to_users_set’. Add a related_name argument to the definition for ‘user’.

Quote

Model looks like:

class CONTACTS_TO_USERS(models.Model):
   contact = models.ForeignKey('contacts.Contact')
   user = models.ForeignKey('auth.User')
   creator = models.ForeignKey('auth.User')
   destroyer = models.ForeignKey('auth.User')
   date_start = models.DateTimeField(auto_now_add=True)
   date_end = models.DateTimeField(default=datetime.datetime(2999,12,31))
   class Meta:
      db_table='contacts_m2m_users'
[cmuser@cmlin02 cmdb]$ python manage.py syncdb
Error: One or more models did not validate:
contacts.contacts_to_users: Accessor for field 'user' clashes with related field 'User.contacts_to_users_set'. Add a related_name argument to the definition for 'user'.
contacts.contacts_to_users: Accessor for field 'creator_id' clashes with related field 'User.contacts_to_users_set'. Add a related_name argument to the definition for 'creator_id'.

SOLUTION

class CONTACTS_TO_USERS(models.Model):
   contact = models.ForeignKey('contacts.Contact')
   user = models.ForeignKey('auth.User')
   creator_id = models.ForeignKey('auth.User', related_name='creator')
   destroyer_id = models.ForeignKey('auth.User', related_name='destroyer')
   date_start = models.DateTimeField(auto_now_add=True)
   date_end = models.DateTimeField(default=datetime.datetime(2999,12,31))
   class Meta:
      db_table='contacts_m2m_users'

 

In Django: create a user, generate the password, add to a group.

email_address = "foo@bar.com"
admin_uid = "foo"
new_password = User.objects.make_random_password()
# Create the user.
new_user = User(username=admin_uid, email=email_address)
new_user.set_password(new_password)
new_user.is_active = True
new_user.save()

# Add the user to the brand_specific_admin group
g = Group.objects.get(name='brand_specific_admin')
g.user_set.add(new_user)