Re: [stellation-res] Volunteer - Installing the core

[jhoward@xxxxxxxxxxxxxxx]

Hello,

On Thu, Dec 19, 2002 at 10:51:12AM -0500, Dave Shields wrote:
>
> Since we hope to put out an alpha-release soon, I would suggest
> becoming a trial user now. For example, though I have tried to bring
> the core documentation files up to date, I'm sure there are errors
> and omissions, and it's hard as an author to see what's missing and
> wrong. I'd suggest picking a part of the system that interests you,
> then try to get it up and running, and note any problems you run
> across. Whether to use command-line, Eclipse, Windows, Linux,
> PostgreSQL, Firebird, just pick the combination that interests you.

Sounds like a good way for me to get started.  Do you have a
preference for how I bring up anything that I find?  Should I email
this list, open bugs in bugzilla, or something else entirely?

Here's where I am so far.  I downloaded the
stellation-core-2002-12-19-bin.tar.gz build.  I'm running Redhat Linux
7.3, and I haven't done anything wildly bizarre with the system
configuration.  The database I'm working with is PostgreSQL version
7.2.1.

I followed the instructions at the web site in the "Core Install" link
in the User Documentation section.  I had no trouble in the early part
of the manual.  I already have ant set up here for development, and
setting up PostgreSQL and the ~/opt/stellation directory was quite
simple.


I did come across one ambiguity in the core install manual in the
section entitled "Configuring the library stellation-lib.  The first
line reads:

"[...], a collection of required external jar files that must be
downloaded an installed in $HOME/stellation/lib:"

In the third paragraph under the table, the sentence ends, "it is
suggested you use the default definition (from stellation.properties)
of $HOME/opt/stellation-lib."

In practice, I ended up putting the library jars in both places.  It's
not really a big deal, but I might as well be thorough.


I ran into a slightly larger problem with the jar path in the section
titled "Testing".  I ran the command "ant -f install.xml test"
(quotations excluded, of course), and the command failed at the
initdb: target with the following:

initdb:
    [exec] Exception in thread "main" java.lang.NoClassDefFoundError:
org/apache/log4j/Category

I haven't exhaustively checked on this, but my best guess is that the
build.xml file with the initdb target is getting its classpath from
the install.xml invocation.  The install.xml file has a property
defined called "install.class.path" which includes entries such as
"${install.dir}/jakarta-oro.jar" and so on.  Since install.dir is ".",
the script is looking in the wrong directory for all the jar
libraries.  (At least... that's my theory so far.)

Certainly, copying the jar files from ~/opt/stellation-lib to
~/opt/stellation solved the problem, and I began to run the tests...


Running the tests went fine for tests 00 and 01, but I ran into
trouble in test 02.  The test stops progressing after the output of
these lines:

02:

init:
    [mkdir] Created dir: /home/jhoward/opt/stellation/test/build/02

main:
    [exec] test2
    [copy] Copying 11 files to /home/jhoward/opt/stellation/test/build/02/v1.1/dir1
    [copy] Copying 7 files to /home/jhoward/opt/stellation/test/build/02/v1.1/dir2
    [copy] Copying 7 files to /home/jhoward/opt/stellation/test/build/02/v1.1


At that point, the test does not progress any farther.  I killed it,
took a brief look at the test scripts, and decided to run it with
verbose output (-v to Ant) to get a better idea of what's going on.
Here's the last part of the output...

     [copy] Copying 7 files to /home/jhoward/opt/stellation/test/build/02/v1.1
     [copy] Copying /home/jhoward/opt/stellation/test/build/02/base/file8 to /home/jhoward/opt/stellation/test/build/02/v1.1/file8
     [copy] Copying /home/jhoward/opt/stellation/test/build/02/base/file7 to /home/jhoward/opt/stellation/test/build/02/v1.1/file7
     [copy] Copying /home/jhoward/opt/stellation/test/build/02/base/file6 to /home/jhoward/opt/stellation/test/build/02/v1.1/file6
     [copy] Copying /home/jhoward/opt/stellation/test/build/02/base/file5 to /home/jhoward/opt/stellation/test/build/02/v1.1/file5
     [copy] Copying /home/jhoward/opt/stellation/test/build/02/base/file4 to /home/jhoward/opt/stellation/test/build/02/v1.1/file4
     [copy] Copying /home/jhoward/opt/stellation/test/build/02/base/file3 to /home/jhoward/opt/stellation/test/build/02/v1.1/file3
     [copy] Copying /home/jhoward/opt/stellation/test/build/02/base/file9 to /home/jhoward/opt/stellation/test/build/02/v1.1/file9
     [exec] Current OS is Linux
     [exec] Executing '/home/jhoward/opt/stellation/bin/svc' with arguments:
     [exec] '--location=postgresql:tsvctest'
     [exec] '--password=password'
     [exec] '--comment=/dev/null'
     [exec] '--workspace=build/02/v1.1'
     [exec] 'add'
     [exec] 'dir1'
     [exec] 'dir2'
     [exec] 'file3'
     [exec] 'file4'
     [exec] 'file5'
     [exec] 'file6'
     [exec] 'file7'
     [exec] 'file8'
     [exec] 'file9'
     [exec] 
     [exec] The ' characters around the executable and arguments are
     [exec] not part of the command.

I was running the test on a 1GHz processor with 1GB of RAM and
moderate to little load.  I ran out and grabbed dinner and left it
running and it was still here, so I believe it was genuinely hung up.
Last I remember reading on this list, the tests all ran fine, so there
must be something in my system configuration that's causing it to
die.  I'm not yet familiar enough with Stellation's code to hazard a
guess as to what, though.

I apologize for the exhaustive detail to wade through.  As I get a
better feel for the source code, documentation, build, and test system
for Stellation I'll probably be able to be a bit more selective about
what details are important.

If there's any more information I can provide about what I've seen so
far or other variations I should try, do let me know.  Otherwise I'll
start poring over test 02 and the code it exercises in Stellation to
try to find out what about my system is causing it trouble.

Thanks,
Jeffrey

Home: jhoward@xxxxxxxxxxxxxxx
Work: jeffrey2@xxxxxxxxxxxxxxxx