Re: [Systemimager] Re: [Sisuite-users] Flamethrower connectivity test problem]
Thus spake Bas van der Vlies ([EMAIL PROTECTED]):
We at SARA are currently switching to flamethrower setup. If we
enable flamethrower the conenctivity test is different then
with rsync, from /etc/init.d/rcS
# Ping test
ping_test() {
echo
echo ping_test
if [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE=default gateway
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo Pinging your $HOST_TYPE to ensure we have network
connectivity.
echo
My question is why?
I honestly don't remember why, but it definitely looks like it was on
purpose.
It is fine for me ;-). Still strange that the check is different. Maybe
we have to do 2 ping tests if flamethrower is enabled. One to the
gateway and if this fails to the imageserver. Just a thought
Regards
--
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
_
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Systemimager] Re: [Sisuite-users] Flamethrower connectivity test problem
Ah!
It just hit me. The reason we don't ping the IMAGESERVER if
FLAMETHROWER_DIRECTORY_PORTBASE is set, is that the client may never be
given, know, or need to know, the ip address of the imageserver because
the client is receiving _all_ of it's data via multicast, which is more
like listening to a channel, as compared with connecting directly to
a server.
I've put this as a comment in there for a future release.
Cheers, -Brian
Thus spake Bas van der Vlies ([EMAIL PROTECTED]):
Brian Elliott Finley wrote:
Thus spake Bas van der Vlies ([EMAIL PROTECTED]):
We at SARA are currently switching to flamethrower setup. If we
enable flamethrower the conenctivity test is different then
with rsync, from /etc/init.d/rcS
# Ping test
ping_test() {
echo
echo ping_test
if [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE=default gateway
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo Pinging your $HOST_TYPE to ensure we have network
connectivity.
echo
My question is why?
I honestly don't remember why, but it definitely looks like it was on
purpose.
It is fine for me ;-). Still strange that the check is different. Maybe
we have to do 2 ping tests if flamethrower is enabled. One to the
gateway and if this fails to the imageserver. Just a thought
Regards
--
--
* *
* Bas van der Vlies e-mail: [EMAIL PROTECTED] *
* SARA - Academic Computing Servicesphone: +31 20 592 8012 *
* Kruislaan 415 fax:+31 20 6683167*
* 1098 SJ Amsterdam *
* *
--
--
Brian Elliott Finley Argonne, MCS Division
Mobile: 630.631.6621 Office: 630.252.4742
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
--
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
Re: [Sisuite-users] Flamethrower connectivity test problem
Thus spake Bas van der Vlies ([EMAIL PROTECTED]):
We at SARA are currently switching to flamethrower setup. If we enable
flamethrower the conenctivity test is different then
with rsync, from /etc/init.d/rcS
# Ping test
ping_test() {
echo
echo ping_test
if [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE=default gateway
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo Pinging your $HOST_TYPE to ensure we have network connectivity.
echo
My question is why?
I honestly don't remember why, but it definitely looks like it was on
purpose.
Our flamethrower server is the same as our rsync-server. If we can ping
it then everything is oke. The other problem we have 2 network cards in
our machines:
- One for booting/sysadm stuff
- The other for the users
The user-lan has an default gateway specified as dhcp-option. This lan
is not up when we install an node. That the reason why we ran into this
problem. We have no gateway and the install will fail.
The code in the current devel release (3.3.2) will not fail the install
if it fails the ping test, but will just print a WARNING message
instead:
ping_test() {
echo
echo ping_test
if [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE=default gateway
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo Pinging your $HOST_TYPE to ensure we have network connectivity.
echo
# Ping test code submitted by Grant Noruschat
# [EMAIL PROTECTED]
# modified slightly by Brian E. Finley.
PING_COUNT=1
ING_EXIT_STATUS=1
while [ $PING_EXIT_STATUS != 0 ]
do
echo PING ATTEMPT $PING_COUNT:
ping -c 1 $PING_DESTINATION
PING_EXIT_STATUS=$?
if [ $PING_EXIT_STATUS = 0 ]; then
echo
echo We have connectivity to your $HOST_TYPE!
fi
PING_COUNT=$(( $PING_COUNT + 1 ))
if [ $PING_COUNT = 4 ]; then
echo
echo WARNING: Failed ping test.
echo Despite this seemingly depressing result, I will attempt
echo to proceed with the install. Your $HOST_TYPE may be
echo configured to not respond to pings, but it wouldn't hurt
echo to double check that your networking equipment is
echo working properly!
echo
sleep 5
PING_EXIT_STATUS=0
fi
done
unset PING_DESTINATION
unset HOST_TYPE
}
Cheers!
-Brian
Regards
---
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
--
--
Brian Elliott Finley Argonne, MCS Division
Mobile: 630.631.6621 Office: 630.252.4742
gpg --keyserver wwwkeys.pgp.net --recv-keys 10F8EE52
--
---
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721alloc_id=10040op=click
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
[Sisuite-users] Flamethrower connectivity test problem
We at SARA are currently switching to flamethrower setup. If we enable
flamethrower the conenctivity test is different then
with rsync, from /etc/init.d/rcS
# Ping test
ping_test() {
echo
echo ping_test
if [ ! -z $FLAMETHROWER_DIRECTORY_PORTBASE ]; then
PING_DESTINATION=$GATEWAY
HOST_TYPE=default gateway
else
PING_DESTINATION=$IMAGESERVER
fi
echo
echo Pinging your $HOST_TYPE to ensure we have network connectivity.
echo
My question is why?
Our flamethrower server is the same as our rsync-server. If we can ping
it then everything is oke. The other problem we have 2 network cards in
our machines:
- One for booting/sysadm stuff
- The other for the users
The user-lan has an default gateway specified as dhcp-option. This lan
is not up when we install an node. That the reason why we ran into this
problem. We have no gateway and the install will fail.
Regards
---
This SF.Net email is sponsored by: GNOME Foundation
Hackers Unite! GUADEC: The world's #1 Open Source Desktop Event.
GNOME Users and Developers European Conference, 28-30th June in Norway
http://2004/guadec.org
___
Sisuite-users mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/sisuite-users
