Hello,
I have the same problem. I would like to add the following error
messages to the issue that appear when the client freezes up on the
install with FC3 and OSCAR. From the /var/log/systemimager/rsyncd log
on the server:
2005/06/21 10:18:21 [525] rsync on
boot/i386/standard/boel_binaries.tar.gz from
node2.gausscluster (10.0.1.2)
2005/06/21 14:18:22 [525] wrote 3370466 bytes read 116 bytes total
size 336993
5
2005/06/21 10:18:23 [526] rsync on scripts/ from node2.gausscluster
(10.0.1.2)
2005/06/21 14:18:23 [526] wrote 18030 bytes read 167 bytes total size
17421
2005/06/21 10:18:47 [32765] rsync: writefd_unbuffered failed to write
4096 bytes
: phase "unknown" [sender]: Connection reset by peer (104)
2005/06/21 10:18:47 [32765] rsync error: error in rsync protocol data
stream (code 12) at io.c(909)
2005/06/21 10:21:15 [568] rsync on oscarimage/ from node2.gausscluster
(10.0.1.2)
2005/06/21 10:31:27 [568] rsync error: timeout in data send/receive
(code 30) at io.c(153)
2005/06/21 10:32:27 [568] rsync error: timeout in data send/receive
(code 30) at io.c(153)
2005/06/21 10:33:27 [568] rsync error: timeout in data send/receive
(code 30) at io.c(153)
2005/06/21 10:34:27 [568] rsync error: timeout in data send/receive
(code 30) at io.c(153)
2005/06/21 10:35:27 [568] rsync error: timeout in data send/receive
(code 30) at io.c(153)
2005/06/21 10:36:27 [568] rsync error: timeout in data send/receive
(code 30) at io.c(153)
2005/06/21 10:36:53 [568] rsync: writefd_unbuffered failed to write 69
bytes: phase "unknown" [sender]: Connection timed out (110)
2005/06/21 10:36:53 [568] rsync error: error in rsync protocol data
stream (code 12) at io.c(909)
Thanks,
Mark
[EMAIL PROTECTED] wrote:
By the packages upload, I mean the part where the image is uploaded to the
node. The nodes started off installing OK, the disks were formatted etc,
and then the install failed during the part when the list of file names
that whizz by are written to the screen. They failed in different places
(at least the last file name written to the screen was different for each
node). The network was still up OK, as other installed nodes worked
correctly.
I didn't use the patched version for FC2, I assumed that was just for FC3.
The install went OK once the modprobe.conf was updated, so I'll going to
stick with that for now.
Quoting Bernard Li <[EMAIL PROTECTED]>:
Hey Martin:
For FC3, what do you mean by 'packages upload' stage?
For FC2, did you use the same patched version of OSCAR 4.1 or is it just
the official 4.1 tarball? If you use the patched version (the one which
will work for FC3) with FC2, you may not need to put modprobe.conf in the
image as the patched version provides a newer version of
SystemConfigurator.
Cheers,
Bernard
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Sat 04/06/2005 12:57 PM
To: Bernard Li
Cc: [EMAIL PROTECTED]; [email protected]
Subject: RE: [Oscar-users] Oscar installation with supermicro X5DPA-GG
motherboard
I tried FC3, following the steps you noted on the website. One of the
nodes
installed fine and the networking worked first time around. However, I
tried the others and they all failed during installation. They seemed to
hang part way through installation, during the packages upload (the
screen
did not update for more than one hour, so I assumed the install had
failed). This happened a number of times (I tried 8 nodes and all failed
twice).
I then tried FC2 and the first install went OK, but I needed to do the
modprobe.conf trick you note in the manual. After that, all the newer
nodes
have installed successfully. I haven't tried the older ones yet. I assume
I
remove the modprobe.conf from the image directory for these.
So I'll stick with FC2 for now. I might try a later version of EL3
another
time (we currently have a full site license, so we have access to all
versions). But I want a working machine, so I'll stick for now!
Thanks again for your help,
Martin Bates
Quoting Bernard Li <[EMAIL PROTECTED]>:
Hey Martin:
Remember to read this message if you intend to go with FC3 - it has
important steps to get OSCAR 4.1 working with FC3:
http://sourceforge.net/mailarchive/message.php?msg_id=11812982
BTW, chances are if you have a newer update version of RHEL3 (eg. U4 or
U5), they'll work with your network card too.
Cheers,
Bernard
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Sat 04/06/2005 2:33 AM
To: Bernard Li
Cc: [EMAIL PROTECTED]; [email protected]
Subject: RE: [Oscar-users] Oscar installation with supermicro X5DPA-GG
motherboard
Hopefully it should be sorted.
I tried installing "rocks" and this installed fine on the host and the
nodes, all talk to each other fine, so all the equipment works!
I have then installed FC3 on one of the nodes from CD (minimal
installation)
and this can ssh to the other nodes and the host with no problem.
So I'll strip everything off again, install FC3 on the host and try
again
from there. If it doesn;t work, I guess I'll stick with rocks, although
I'd
prefer to go with something I already know.
Thanks for your help.
Martin Bates
Quoting Bernard Li <[EMAIL PROTECTED]>:
Hi Martin:
I just checked the version of the e1000 driver that came with Fedora
Core
2 and it is 5.2.39 (version which supports your board). Therefore,
you
can try to install your cluster using Fedora Core 2 or 3.
However, I'm not sure whether you still need to update your BIOS or
not...
Good luck,
Bernard
________________________________
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Fri 03/06/2005 12:02 PM
To: Bernard Li
Cc: [email protected]
Subject: RE: [Oscar-users] Oscar installation with supermicro
X5DPA-GG
motherboard
and make sure to have latest bios installed R1.0C
http://www.supermicro.com/support/bios/
Are you running the latest BIOS?
Probably not. I don't know how to update this. These machines are in
rack
mount cases, and do not have CDs or floppy drives in and I cannot
easily
put in an extra ethernet card either to test them. I can take the lot
apart
and put a floppy in each one, one by one, but there seems to be the
problem
that there are no (small) power connectors for floppy drives.
I'm going to have to leave it until after the weekend to decide what
to
do
with these.
I seriously advise anyone considering using OSCAR not to buy this
supermicro
board - I've already wasted two weeks trying to install in them. The
vendor
that sold me these machines said they were fully Linux compliant, but
clearly the supermicro boards are not as easy to use as other boards
by
ASUS or TYAN that I have used in the past.
-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games. How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
_______________________________________________
Oscar-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-users
-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click
_______________________________________________
Oscar-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/oscar-users
