Changing the default xymon port
list Roland Soderstrom
Hi,
I'm running Hobbit server version 4.3.0-0.beta2 on Solaris 10 X86.
I'm running Hobbit client version 4.3.0-0.beta2 on Solaris 9 SPARC.
Currently we have a BB server running on port 1984
To test and migrate to Xymon I tried to run Xymon on port 1985
But it doesn't seem to work.
It uses default 1984 even though I specify port 1985.
bash-2.05$ bin/bb --debug 192.168.34.72 test
2010-01-25 11:42:55 Transport setup is:
2010-01-25 11:42:55 bbdportnumber = 1984
2010-01-25 11:42:55 bbdispproxyhost = NONE
2010-01-25 11:42:55 bbdispproxyport = 0
2010-01-25 11:42:55 Recipient listed as '192.168.34.72'
2010-01-25 11:42:55 Standard BB protocol on port 1984
2010-01-25 11:42:55 Will connect to address 192.168.34.72 port 1984
2010-01-25 11:42:55 Connect status is 0
2010-01-25 11:42:55 Sent 4 bytes
2010-01-25 11:42:55 Closing connection
bash-2.05$ pwd
/usr/local/xymon/client
bash-2.05$ ls etc
clientlaunch.cfg hobbitclient.cfg localclient.cfg
bash-2.05$ grep 198 etc/hobbitclient.cfg
etc/hobbitclient.cfg:BBPORT="1985" # Portnumber where hobbitd listens
Any ideas why this isn't working.
I'm running Hobbit server version 4.3.0-0.beta2 on Solaris 10 X86.
I'm running Hobbit client version 4.3.0-0.beta2 on Solaris 9 SPARC.
Currently we have a BB server running on port 1984
To test and migrate to Xymon I tried to run Xymon on port 1985
But it doesn't seem to work.
It uses default 1984 even though I specify port 1985.
bash-2.05$ bin/bb --debug 192.168.34.72 test
2010-01-25 11:42:55 Transport setup is:
2010-01-25 11:42:55 bbdportnumber = 1984
2010-01-25 11:42:55 bbdispproxyhost = NONE
2010-01-25 11:42:55 bbdispproxyport = 0
2010-01-25 11:42:55 Recipient listed as '192.168.34.72'
2010-01-25 11:42:55 Standard BB protocol on port 1984
2010-01-25 11:42:55 Will connect to address 192.168.34.72 port 1984
2010-01-25 11:42:55 Connect status is 0
2010-01-25 11:42:55 Sent 4 bytes
2010-01-25 11:42:55 Closing connection
bash-2.05$ pwd
/usr/local/xymon/client
bash-2.05$ ls etc
clientlaunch.cfg hobbitclient.cfg localclient.cfg
bash-2.05$ grep 198 etc/hobbitclient.cfg
etc/hobbitclient.cfg:BBPORT="1985" # Portnumber where hobbitd listens
Any ideas why this isn't working.
--
Best Regards,
Roland
Soderstrom
list Dominique Frise
You probably want the SERVER to listen to port 1985 too... [bb at iris etc]$ pwd /usr/local/xymon/server/etc [bb at iris etc]$ grep 198 hobbitserver.cfg BBPORT="1985" # Portnumber where hobbitd/bbd listens Dominique
▸
Roland Soderstrom wrote:Hi, I'm running Hobbit server version 4.3.0-0.beta2 on Solaris 10 X86. I'm running Hobbit client version 4.3.0-0.beta2 on Solaris 9 SPARC. Currently we have a BB server running on port 1984 To test and migrate to Xymon I tried to run Xymon on port 1985 But it doesn't seem to work. It uses default 1984 even though I specify port 1985. bash-2.05$ bin/bb --debug 192.168.34.72 test 2010-01-25 11:42:55 Transport setup is: 2010-01-25 11:42:55 bbdportnumber = 1984 2010-01-25 11:42:55 bbdispproxyhost = NONE 2010-01-25 11:42:55 bbdispproxyport = 0 2010-01-25 11:42:55 Recipient listed as '192.168.34.72' 2010-01-25 11:42:55 Standard BB protocol on port 1984 2010-01-25 11:42:55 Will connect to address 192.168.34.72 port 1984 2010-01-25 11:42:55 Connect status is 0 2010-01-25 11:42:55 Sent 4 bytes 2010-01-25 11:42:55 Closing connection bash-2.05$ pwd /usr/local/xymon/client bash-2.05$ ls etc clientlaunch.cfg hobbitclient.cfg localclient.cfg bash-2.05$ grep 198 etc/hobbitclient.cfg etc/hobbitclient.cfg:BBPORT="1985" # Portnumber where hobbitd listens Any ideas why this isn't working. -- Best Regards, *Roland Soderstrom*
list Malcolm Hunter
▸
I'm running Hobbit server version 4.3.0-0.beta2 on Solaris 10 X86. I'm running Hobbit client version 4.3.0-0.beta2 on Solaris 9 SPARC. Currently we have a BB server running on port 1984 To test and migrate to Xymon I tried to run Xymon on port 1985 But it doesn't seem to work. It uses default 1984 even though I specify port 1985. bash-2.05$ bin/bb --debug 192.168.34.72 test 2010-01-25 11:42:55 Transport setup is: 2010-01-25 11:42:55 bbdportnumber = 1984 2010-01-25 11:42:55 bbdispproxyhost = NONE 2010-01-25 11:42:55 bbdispproxyport = 0 2010-01-25 11:42:55 Recipient listed as '192.168.34.72' 2010-01-25 11:42:55 Standard BB protocol on port 1984 2010-01-25 11:42:55 Will connect to address 192.168.34.72 port 1984 2010-01-25 11:42:55 Connect status is 0 2010-01-25 11:42:55 Sent 4 bytes 2010-01-25 11:42:55 Closing connection bash-2.05$ pwd /usr/local/xymon/client bash-2.05$ ls etc clientlaunch.cfg hobbitclient.cfg localclient.cfg bash-2.05$ grep 198 etc/hobbitclient.cfg etc/hobbitclient.cfg:BBPORT="1985" #
Portnumber wherehobbitd listens
Any ideas why this isn't working.Try: bin/bb --debug 192.168.34.72:1985 test Malcolm -- Technical copy-editor & proofreader KDE Proofreading Team KDE British English Translation Team http://l10n.kde.org/team-infos.php?teamcode=en_GB Facebook: http://www.facebook.com/FriendlyAtheist Haiti-Nothilfe! Helfen Sie per SMS: Sende UIHAITI an die Nummer 81190. Von 5 Euro je SMS (zzgl. SMS-Gebühr) gehen 4,83 Euro an UNICEF.
list Reinartz Ralf AII.Pforzheim
Hello all, Did anyone build an initscript for Suse 11.x for the Xymon Server? Unfortunally the Debian Scripts are a little bit different from the Suses Way. If not, we'll try to make one. Thanks Ralf applied international informatics GmbH Sitz der Gesellschaft: Berlin; Registergericht: Berlin-Charlottenburg HRB 77891B Geschaeftsfuehrung: Josef Duermoser, Michael Bihn Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen koennen Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt. Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail und loeschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System. Ebenso duerfen Sie diese E-Mail oder ihre Anlagen nicht kopieren oder an Dritte weitergeben. Vielen Dank! Important Note: This e-mail and any attachment are confidential and may contain trade secrets or otherwise protected from disclosure. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this e-mail and any attachment from your system. If you are not the intended recipient please understand that you must not copy this e-mail or any attachment or disclose the contents to any other person. Thank you!
list Malcolm Hunter
▸
Did anyone build an initscript for Suse 11.x for the Xymon Server? Unfortunally the Debian Scripts are a little bit different from the Suses Way. If not, we'll try to make one.
I use CentOS and just made the init script call hobbit.sh as the xymon user. Seems to work perfectly. Apart from the chkconfig commented section it's a one-liner.
▸
Malcolm -- Technical copy-editor & proofreader KDE Proofreading Team KDE British English Translation Team http://l10n.kde.org/team-infos.php?teamcode=en_GB Facebook: http://www.facebook.com/FriendlyAtheist
Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
list Gé Janssen
He Ralf, Hereby my version for opensuse 11.x. See attachment. please mind my not standard installation of xymon in /opt/monitor/xymon. This requires some editing. You can install it using insserv or chkconfig: callisto:/opt/monitor/xymon/server/etc # cp xymon.opensuse11 /etc/init.d/xymon callisto:/opt/monitor/xymon/server/etc # cd /etc/init.d/ callisto:/etc/init.d # chmod a+x xymon callisto:/etc/init.d # chkconfig --add xymon xymon 0:off 1:off 2:off 3:on 4:off 5:on 6:off callisto:/etc/init.d # chkconfig --list xymon xymon 0:off 1:off 2:off 3:on 4:off 5:on 6:off callisto:/etc/init.d # service xymon start Starting xymon: Hobbit started Hobbit client for linux started on callisto callisto:/etc/init.d # Regards, Gé
▸
Reinartz Ralf AII.Pforzheim wrote:Hello all, Did anyone build an initscript for Suse 11.x for the Xymon Server? Unfortunally the Debian Scripts are a little bit different from the Suses Way. If not, we'll try to make one. Thanks Ralf
Attachments (1)
list Rich Smrcina
Although not specifically for SLES 11, I've used a variation of this on
SLES 9, 10 and 11. It should live in /etc/rc.d and works with chkconfig.
#! /bin/sh
### BEGIN INIT INFO
# Provides: xymon
# Required-Start: network
# Required-Stop: network
# Default-Start: 3 5
# Default-Stop: 3
# Description: Start the Xymon network monitor
### END INIT INFO
case "$1" in
start)
echo "Starting Xymon"
su - xymon -c "cd /home/xymon/server; ./hobbit.sh start"
;;
stop)
echo "Stopping Xymon"
su - xymon -c "cd /home/xymon/server; ./hobbit.sh stop"
;;
restart)
$0 stop
$0 start
rc_status
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
;;
esac
▸
On 01/25/2010 10:04 AM, Reinartz Ralf AII.Pforzheim wrote:Hello all, Did anyone build an initscript for Suse 11.x for the Xymon Server? Unfortunally the Debian Scripts are a little bit different from the Suses Way. If not, we'll try to make one. Thanks Ralf applied international informatics GmbH Sitz der Gesellschaft: Berlin; Registergericht: Berlin-Charlottenburg HRB 77891B Geschaeftsfuehrung: Josef Duermoser, Michael Bihn Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen koennen Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt. Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail und loeschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System. Ebenso duerfen Sie diese E-Mail oder ihre Anlagen nicht kopieren oder an Dritte weitergeben. Vielen Dank! Important Note: This e-mail and any attachment are confidential and may contain trade secrets or otherwise protected from disclosure. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this e-mail and any attachment from your system. If you are not the intended recipient please understand that you must not copy this e-mail or any attachment or disclose the contents to any other person. Thank you!
--
Rich Smrcina Phone: XXX-XXX-XXXX http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2010 - Apr 9-13, 2010 Covington, KY
list Malcolm Hunter
▸
Although not specifically for SLES 11, I've used a variation of this on
SLES 9, 10 and 11. It should live in /etc/rc.d and works with chkconfig.
#! /bin/sh
### BEGIN INIT INFO
# Provides: xymon
# Required-Start: network
# Required-Stop: network
# Default-Start: 3 5
# Default-Stop: 3
# Description: Start the Xymon network monitor
### END INIT INFO
case "$1" in
start)
echo "Starting Xymon"
su - xymon -c "cd /home/xymon/server; ./hobbit.sh start"
;;
stop)
echo "Stopping Xymon"
su - xymon -c "cd /home/xymon/server; ./hobbit.sh stop"
;;
restart)
$0 stop
$0 start
rc_status
;;
*)
echo "Usage: $0 {start|stop|restart}"
exit 1
;;
esacAh, slightly different to CentOS/Redhat - with those you don't need the "Starting Xymon" / "Stopping Xymon" as these are displayed anyway. What's the reason for changing directory? What's rc_status in this context? Is there a reason for not using "./hobbit.sh restart" instead of "stop / start"?
▸
Malcolm -- Technical copy-editor & proofreader KDE Proofreading Team KDE British English Translation Team http://l10n.kde.org/team-infos.php?teamcode=en_GB Facebook: http://www.facebook.com/FriendlyAtheist Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/chbrowser
list Malcolm Hunter
Hereby my version for opensuse 11.x. See attachment.
From your script:
start() {
# Check if xymon is already running
echo -n $"Starting $prog: "
su - xymon -c "/opt/monitor/xymon/server/hobbit.sh start"
su - xymon -c "/opt/monitor/xymon/client/runclient.sh start"
}
Isn't the Xymon client configured to start from your hobbitlaunch.cfg then?
▸
Malcolm -- Technical copy-editor & proofreader KDE Proofreading Team KDE British English Translation Team http://l10n.kde.org/team-infos.php?teamcode=en_GB Facebook: http://www.facebook.com/FriendlyAtheist
Nur noch bis 31.01.2010: DSL-Komplettpaket für 16,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02
list Rich Smrcina
▸
On 01/25/2010 05:47 PM, Malcolm Hunter wrote:
Ah, slightly different to CentOS/Redhat - with those you don't need the "Starting Xymon" / "Stopping Xymon" as these are displayed anyway.
I just 'borrowed' another script and tailored it to work the way I needed. As to the display of messages at boot time, I don't recall checking if they come out without the echo statements. I've been using this script for several years.
What's the reason for changing directory? What's rc_status in this context? Is there a reason for not using "./hobbit.sh restart" instead of "stop / start"?
1. cd? hobbit.sh lives in $HOME/server 2. rc_status? I don't know. 3. hobbit.sh restart? Because at boot time I want Xymon to start (./hobbit.sh start) and at shutdown I want xymon to stop (./xymon.sh stop).
▸
-- Rich Smrcina Phone: XXX-XXX-XXXX http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2010 - Apr 9-13, 2010 Covington, KY
list Andreas Kunberger
Am 25.01.2010 17:04, schrieb Reinartz Ralf AII.Pforzheim:
▸
Hello all, Did anyone build an initscript for Suse 11.x for the Xymon Server? Unfortunally the Debian Scripts are a little bit different from the Suses Way. If not, we'll try to make one. Thanks Ralf
Hello,
I use the following script:
==================================
#! /bin/sh
#
# xymon This shell script takes care of starting and stopping
# xymon(the former Hobbit network monitor)
#
# chkconfig: 2345 80 20
# description: xymon is a network monitoring tool that allows \
# you to monitor hosts and services. The monitor status is available \
# via a webpage.
### BEGIN INIT INFO
# Provides: yxmon
# Required-Start: $remote_fs
# Should-Start: $named
# Required-Stop:
# Default-Start: 3 5
# Default-Stop:
# Description: Start xymon monitoring
### END INIT INFO
PATH=/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin
DAEMON=/usr/lib/xymon/server/hobbit.sh
NAME=xymon
DESC=xymon
USER=xymon
test -x $DAEMON || exit 0
# Include xymon defaults if available
if [ -f /etc/sysconfig/xymon ] ; then
. /etc/sysconfig/xymon
fi
set -e
case "$1" in
start)
echo -n "Starting $DESC: "
su -c "$DAEMON start" - $USER
echo "$NAME."
;;
stop)
echo -n "Stopping $DESC: "
su -c "$DAEMON stop" - $USER
echo "$NAME."
;;
status)
echo -n "Status of $DESC: "
su -c "$DAEMON status" - $USER
echo "$NAME."
;;
reload|force-reload)
echo "Reloading $DESC configuration files."
su -c "$DAEMON reload" - $USER
echo "$NAME."
;;
restart)
echo -n "Restarting $DESC: "
su -c "$DAEMON restart" - $USER
echo "$NAME."
;;
rotate)
echo -n "Rotating logs for $DESC: "
su -c "$DAEMON rotate" - $USER
echo "$NAME."
;;
*)
N=/etc/init.d/$NAME
# echo "Usage: $N {start|stop|restart|reload|force-reload}" >&2
echo "Usage: $N
{start|stop|status|restart|(force-)reload|rotate}" >&2
exit 1
;;
esac
exit 0
==================================
mfg
Andreas
--
Institut für Textil- und Verfahrenstechnik
der Deutschen Institute für Textil- und Faserforschung Denkendorf
list Reinartz Ralf AII.Pforzheim
Hi Ge and all the others, Thank you very much. Was exactly what I needed :) Have a nice Day Ralf
▸
-----Ursprüngliche Nachricht-----
Von: Gé Janssen [mailto:user-876f637131f0@xymon.invalid]
Gesendet: Montag, 25. Jänner 2010 22:40
An: user-ae9b8668bcde@xymon.invalid
Betreff: Re: [hobbit] Initscript for Suse?
He Ralf,
Hereby my version for opensuse 11.x. See attachment.
please mind my not standard installation of xymon in /opt/monitor/xymon.
This requires some editing.
You can install it using insserv or chkconfig:
callisto:/opt/monitor/xymon/server/etc # cp xymon.opensuse11
/etc/init.d/xymon
callisto:/opt/monitor/xymon/server/etc # cd /etc/init.d/
callisto:/etc/init.d # chmod a+x xymon
callisto:/etc/init.d # chkconfig --add xymon
xymon 0:off 1:off 2:off 3:on 4:off 5:on 6:off
callisto:/etc/init.d # chkconfig --list xymon
xymon 0:off 1:off 2:off 3:on 4:off 5:on 6:off
callisto:/etc/init.d # service xymon start
Starting xymon: Hobbit started
Hobbit client for linux started on callisto
callisto:/etc/init.d #
Regards,
Gé
Reinartz Ralf AII.Pforzheim wrote:Hello all, Did anyone build an initscript for Suse 11.x for the Xymon Server? Unfortunally the Debian Scripts are a little bit different from the Suses Way. If not, we'll try to make one. Thanks Ralf
applied international informatics GmbH Sitz der Gesellschaft: Berlin; Registergericht: Berlin-Charlottenburg HRB 77891B Geschaeftsfuehrung: Josef Duermoser, Michael Bihn Wichtiger Hinweis: Diese E-Mail und etwaige Anlagen koennen Betriebs- oder Geschaeftsgeheimnisse oder sonstige vertrauliche Informationen enthalten. Sollten Sie diese E-Mail irrtuemlich erhalten haben, ist Ihnen der Status dieser E-Mail bekannt. Bitte benachrichtigen Sie uns in diesem Fall sofort durch Antwort-Mail und loeschen Sie diese E-Mail nebst etwaigen Anlagen von Ihrem System. Ebenso duerfen Sie diese E-Mail oder ihre Anlagen nicht kopieren oder an Dritte weitergeben. Vielen Dank! Important Note: This e-mail and any attachment are confidential and may contain trade secrets or otherwise protected from disclosure. If you have received it in error, you are on notice of its status. Please notify us immediately by reply e-mail and then delete this e-mail and any attachment from your system. If you are not the intended recipient please understand that you must not copy this e-mail or any attachment or disclose the contents to any other person. Thank you!
list Andreas Kunberger
Am 26.01.2010 03:52, schrieb Rich Smrcina:
On 01/25/2010 05:47 PM, Malcolm Hunter wrote:
<<<<>>
2. rc_status? I don't know.
rc_status just writes a formated (colored) message on the screen, whether teh start succeded or failed.
▸
Andreas
--
Institut für Textil- und Verfahrenstechnik
der Deutschen Institute für Textil- und Faserforschung Denkendorf
list Rich Smrcina
▸
On 01/26/2010 02:03 AM, Andreas Kunberger wrote:
rc_status just writes a formated (colored) message on the screen, whether teh start succeded or failed. Andreas
Thank you, Andreas.
▸
-- Rich Smrcina Phone: XXX-XXX-XXXX http://www.linkedin.com/in/richsmrcina Catch the WAVV! http://www.wavv.org WAVV 2010 - Apr 9-13, 2010 Covington, KY
list Roland Soderstrom
Hi,
Found the problem.
First, the server is running on port 1985.
But, used the full name in bb-hosts so I didn't get a match.
After changing that all the normal hobbitclient.sh tests came through.
I though the problem was the port....
My manual test still didn't work.
The manual test fault was because the hobbitclient.cfg don't export variables and so didn't get the BBPORT setting.
Just a simple "export BBPORT=1985" made the trick.
bash-2.05$ export BBPORT=1985
bash-2.05$ ./bb --debug 192.168.34.72 test
2010-01-27 08:41:59 Transport setup is:
2010-01-27 08:41:59 bbdportnumber = 1985
2010-01-27 08:41:59 bbdispproxyhost = NONE
2010-01-27 08:41:59 bbdispproxyport = 0
2010-01-27 08:41:59 Recipient listed as '192.168.34.72'
2010-01-27 08:41:59 Standard BB protocol on port 1985
2010-01-27 08:41:59 Will connect to address 192.168.34.72 port 1985
2010-01-27 08:41:59 Connect status is 0
2010-01-27 08:41:59 Sent 4 bytes
2010-01-27 08:41:59 Closing connection
bash-2.05$
Malcoms test will also do the trick
bash-2.05$ ./bb --debug 192.168.34.72:1986 test
2010-01-27 08:44:10 Transport setup is:
2010-01-27 08:44:10 bbdportnumber = 1985
2010-01-27 08:44:10 bbdispproxyhost = NONE
2010-01-27 08:44:10 bbdispproxyport = 0
2010-01-27 08:44:10 Recipient listed as '192.168.34.72:1986'
2010-01-27 08:44:10 Standard BB protocol on port 1986
2010-01-27 08:44:10 Will connect to address 192.168.34.72 port 1986
- Roland
Found the problem.
First, the server is running on port 1985.
But, used the full name in bb-hosts so I didn't get a match.
After changing that all the normal hobbitclient.sh tests came through.
I though the problem was the port....
My manual test still didn't work.
The manual test fault was because the hobbitclient.cfg don't export variables and so didn't get the BBPORT setting.
Just a simple "export BBPORT=1985" made the trick.
bash-2.05$ export BBPORT=1985
bash-2.05$ ./bb --debug 192.168.34.72 test
2010-01-27 08:41:59 Transport setup is:
2010-01-27 08:41:59 bbdportnumber = 1985
2010-01-27 08:41:59 bbdispproxyhost = NONE
2010-01-27 08:41:59 bbdispproxyport = 0
2010-01-27 08:41:59 Recipient listed as '192.168.34.72'
2010-01-27 08:41:59 Standard BB protocol on port 1985
2010-01-27 08:41:59 Will connect to address 192.168.34.72 port 1985
2010-01-27 08:41:59 Connect status is 0
2010-01-27 08:41:59 Sent 4 bytes
2010-01-27 08:41:59 Closing connection
bash-2.05$
Malcoms test will also do the trick
bash-2.05$ ./bb --debug 192.168.34.72:1986 test
2010-01-27 08:44:10 Transport setup is:
2010-01-27 08:44:10 bbdportnumber = 1985
2010-01-27 08:44:10 bbdispproxyhost = NONE
2010-01-27 08:44:10 bbdispproxyport = 0
2010-01-27 08:44:10 Recipient listed as '192.168.34.72:1986'
2010-01-27 08:44:10 Standard BB protocol on port 1986
2010-01-27 08:44:10 Will connect to address 192.168.34.72 port 1986
- Roland
▸
On 25/01/10 07:49 PM, Malcolm Hunter wrote:I'm running Hobbit server version 4.3.0-0.beta2 on Solaris 10 X86. I'm running Hobbit client version 4.3.0-0.beta2 on Solaris 9 SPARC. Currently we have a BB server running on port 1984 To test and migrate to Xymon I tried to run Xymon on port 1985 But it doesn't seem to work. It uses default 1984 even though I specify port 1985. bash-2.05$ bin/bb --debug 192.168.34.72 test 2010-01-25 11:42:55 Transport setup is: 2010-01-25 11:42:55 bbdportnumber = 1984 2010-01-25 11:42:55 bbdispproxyhost = NONE 2010-01-25 11:42:55 bbdispproxyport = 0 2010-01-25 11:42:55 Recipient listed as '192.168.34.72' 2010-01-25 11:42:55 Standard BB protocol on port 1984 2010-01-25 11:42:55 Will connect to address 192.168.34.72 port 1984 2010-01-25 11:42:55 Connect status is 0 2010-01-25 11:42:55 Sent 4 bytes 2010-01-25 11:42:55 Closing connection bash-2.05$ pwd /usr/local/xymon/client bash-2.05$ ls etc clientlaunch.cfg hobbitclient.cfg localclient.cfg bash-2.05$ grep 198 etc/hobbitclient.cfg etc/hobbitclient.cfg:BBPORT="1985" # Portnumber wherehobbitd listens Any ideas why this isn't working.Try: bin/bb --debug 192.168.34.72:1985 test Malcolm
--
Best Regards,
|
Roland
Soderstrom | Senior
System
Administrator |
|
Disclaimer: This message contains privileged and confidential
information intended only for the use of the addressee named above.
If you are not the intended recipient of this message you must not
disseminate, copy or take any action in reliance on it.
Any views expressed in this message are those of the individual sender,
except where the sender specifically states them to be the views of the
company.
list Malcolm Hunter
▸
My manual test still didn't work. The manual test fault was because the hobbitclient.cfg don't
exportvariables and so didn't get the BBPORT setting.
Just a simple "export BBPORT=1985" made the trick.Or like I said, specify the port as well as the IP address on the command line:
▸
bin/bb --debug 192.168.34.72:1985 test Malcolm -- Technical copy-editor & proofreader KDE Proofreading Team KDE British English Translation Team http://l10n.kde.org/team-infos.php?teamcode=en_GB Facebook: http://www.facebook.com/FriendlyAtheist Nur noch bis 31.01.2010: DSL-Komplettpaket für 16,99 Euro/mtl.!* http://portal.gmx.net/de/go/dsl02