I have not tested every possible step and any combination of buttons yet but tested very general
default cases (step 3 --> 8 without step 0~2 : download, select, and configure packages).
I did not test the additonal steps (Add OSCAR Clients, Delete OSCAR Clients, and Install/Uninstall OSCAR Packages)
For the general default test, there was no error window to kill oscar wizard.
I don't understand this comment.
I am sorry about my unclear comment.
What I meant is as if a user installed OSCAR 4.0 with quick install manual, I have gone through those step (Step 3~8). And I think those step are for the general default test.
And there was no red, evil error messages window that stops(?) oscar wizard.
Oh, right. The red error message window does not kill the oscar wizard. It just says that
the corresponding step has an error.
Is this more confusing?
So, just to confirm, the cluster successfully installed. Correct?
Yes,
Regards,
DongInn. David N. Lombard wrote:
From: DongInn Kim; Friday, November 5, 2004 11:42 AM
Hi all,
I tested OSCAR 4.0 on real(?) FC2 which is running on the physical computer.
I have not tested every possible step and any combination of buttons yet but tested very general
default cases (step 3 --> 8 without step 0~2 : download, select, and configure packages).
I did not test the additonal steps (Add OSCAR Clients, Delete OSCAR Clients, and Install/Uninstall OSCAR Packages)
For the general default test, there was no error window to kill oscar wizard.
I don't understand this comment.
Even though there were unhappy messages on the log, all processes are successfully completed to create OSCAR cluster.
The unhappy messages are following.
These messages happened in the step 4 "Build OSCAR Client Images.."
=================================================================
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
ls: readlink:: No such file or directory
ls: file: No such file or directory
ls: expected: No such file or directory
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
These annoying and need to be fixed so they don't appear. They are also harmless.
warning: /var/lib/nfs/etab created as /var/lib/nfs/etab.rpmnew
warning: /var/lib/nfs/rmtab created as /var/lib/nfs/rmtab.rpmnew
warning: /var/lib/nfs/state created as /var/lib/nfs/state.rpmnew
warning: /var/lib/nfs/xtab created as /var/lib/nfs/xtab.rpmnew
These mean you've reinstalled some RPMs; specifically nfs-utils As it looks like this is appearing on the client image creation, I'm concerned that the image already existed. I just checked the fc2 rpmlist, and the package isn't duplicated.
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
ls: readlink:: No such file or directory
ls: file: No such file or directory
ls: expected: No such file or directory
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
awk: cmd. line:2: fatal: cannot open file `/etc/fstab' for reading (No such file or directory)
Same stuff as the first item, same command.
ERROR: Tag "mpi" does not exist
ibid
warning: /var/spool/pbs/mom_priv/config saved as /var/spool/pbs/mom_priv/config.rpmorig
duplicate rpm installation, again?
So, just to confirm, the cluster successfully installed. Correct?
------------------------------------------------------- This SF.Net email is sponsored by: Sybase ASE Linux Express Edition - download now for FREE LinuxWorld Reader's Choice Award Winner for best database on Linux. http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click _______________________________________________ Oscar-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/oscar-devel
