Bugs item #680172, was opened at 2003-02-04 08:33
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=109368&aid=680172&group_id=9368
Category: Installation
Group: 2.2
>Status: Closed
>Resolution: Works For Me
Priority: 8
Submitted By: Jeff Squyres (jsquyres)
Assigned to: Jason Brechin (brechin)
Summary: Pre-emptive killing background ping
Initial Comment:
During my MAC collection, the networking window somehow
killed my background ping.
It had collected one MAC, and I clicked on it and then
clicked on a node and clicked on "Assign". Since the
auto-DHCP update checkbox was enabled, it restarted the
DHCP server. I then waited for more MAC's to appear in
the window. It wasn't until a little later (when no
more MAC's had appeared, even though the nodes were
pinging away) that I noticed the following output:
-----
=============================================================================
== Running step 6 of the OSCAR wizard: Setup networking
=============================================================================
--> Step 6: Killed background ping
--> Step 6: Launching background ping
--> Step 6: Starting to listen to network:
/usr/sbin/tcpdump -i eth0 -n -e -l
--> Step 6: Launching background ping
^^^^^^^^^^^^ Why does it launch the background ping twice?
WARNING: pinging broadcast address
tcpdump: listening on eth0
--> Step 6: Assigned 00:50:56:db:9c:e8 to oscarnode1
--> Step 6: cleaning hostfile
About to run setup_dhcpd at
/usr/lib/perl5/site_perl/5.6.0/i386-linux/Tk.pm
line 217
--> Step 6: Running command: mkdhcpconf -o
/etc/dhcpd.conf --interface=eth0
--bootfile=pxelinux.0 --gateway=192.168.55.129
--> Step 6: Successfully ran command
--> Step 6: Restarting dhcpd service
Shutting down dhcpd:
[FAILED]
Starting dhcpd:
[ OK ]
--> Step 6: Successfully restarted dhcpd service
tcpdump: pcap_loop: recvfrom: Network is down
Attempting to kill 6140
--> Step 6: Killed background ping
^^^^^^^^^^^^I didn't do this
-----
This actually brings up the minor point of it launching
the background ping twice at the beginning, too (or so
it says).
Note that my network was up and functioning the whole
time -- I'm not sure what the "Network is down" error
message is about.
I definitely did not click on the "Stop collecting"
button -- it still said "Stop collecting", even at this
point (i.e., it had killed the background ping). The
fix was relatively easy -- click on "Stop collecting"
and then click on "Start collecting". But this should
be fixed before release.
----------------------------------------------------------------------
>Comment By: Jeff Squyres (jsquyres)
Date: 2003-02-07 08:50
Message:
Logged In: YES
user_id=11722
I am unable to reproduce it as well. [shrug]
The button very definitely still said "stop collecting", so
I'm quite sure that I didn't click it, even inadvertantly.
Oh well. Let's close those bug until it happens again.
----------------------------------------------------------------------
Comment By: Jason Brechin (brechin)
Date: 2003-02-06 15:20
Message:
Logged In: YES
user_id=274641
I have not been able to reproduce this... perhaps it is a
VMWare issue?
----------------------------------------------------------------------
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=109368&aid=680172&group_id=9368
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
_______________________________________________
Oscar-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/oscar-devel
