[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [stellation-res] Running the Stellation Tests Question
|
Jim, all:
I'm happy to report that the fix [bugzilla: 33339] worked. The only
glitch I encountered was that the properties that define the locations of
svc, svcadmin, etc weren't in sync with my directory structure. The svc
property, for example, is specified so:
<property
location="../build/bin/tsvc"
name="svc"/>
and I had no build directory (just bin) i.e.:
/opt/stellation
bin/
lib/
test/
Anyway, this was a quick fix and then I was off and running. Some
minutes later (just over 10) I got the reassuring BUILD SUCCESSFUL
message. Cool!
After I poke a hole in the firewall, I can try to connect with a
client. Am I right in thinking I only need to do this for tsvcserver
(eg 6060) -- that is, *not* postgres as well? (I ask because I need to
make the request to an admin so I'd like to get it right the first
time!)
Again, thanks.
-phil
On Wed, 26 Feb 2003, Jim Wright - IBM Research wrote:
> Hi Philip,
>
> Thanks for reporting the problem!
>
> There were a couple of problems:
>
> 1) In most cases, you should also specify 'dbusername' and 'dbpassword'
> explicitly when running tests in remote mode. (You were only specifying
> 'username' and 'password')
>
> 2) It turns out that the test script is broken: it doesn't handle command-line
> redefinitions of dbusername and dbpassword (and slams username to
> the current user name per ${user.name}, as shown in your original post).
>
> It's not clear why the script was written that way: the original author of that
> script is not currently working actively on Stellation. In any case, I've
> fixed
> the script.
>
> The problem is posted as a new bug (Bugzilla #33339); the fix is attached
> to the
> Bugzilla item as a zip containing both a patch against the current file
> (org.eclipse.stellation.core/test/build.xml, version 1.11) and a complete
> version of the updated Ant script. Please get them from Bugzilla and let
> me know if it fixes your problem.
>
> Here is an example Ant command line for the updated script:
>
> $ Ant -Drdbm=postgresql -Dmode=remote -Dusername=jabber -Dpassword=wocky
> -Ddbusername=stella -Ddbpassword=stellar
>
> In this example, the Stellation command-line client under test is told to
> use <jabber,wocky> for accessing the Stellation repository, using remote mode.
> The Stellation repository is told to use <stella,stellar> for accessing the
> underlying PostgreSQL database.
>
> (I have configured my PostgreSQL installation to include user 'stella',
> password 'stellar' for test purposes.)
>
> Note that I am running this test while logged in as 'jwright', and that's
> the value of ${user.name} when the script is executed. However, because the
> relevant Ant properties are overridden from the Ant command line, ${user.name}
> and various other defaults are ignored.
>
> The test script assumes the following:
>
> A) You have configured the Stellation repository using the desired client
> username and password (__not__ the dbusername and dbpassword, unless they
> happen to be the same):
>
> $ tsvcadmin --location postgresql:tsvctest --username stelUsername
> --password stelPassword init
>
> B) You have configured the underlying SQL database to accept user
> 'dbusername' with password 'dbpassword'.
>
> BTW - you may find it more convenient to put the property definitions in a
> separate
> file, to save typing and typos. For example, I use:
>
> $ Ant -propertyfile testprops
>
> where the file testprops contains:
> rdbm=postgresql
> mode=remote
> username=jabber
> password=wocky
> dbusername=stellad
> dbpassword=stellar
>
> One more point: the file dev-install.html (in
> org.eclipse.stellation.core/doc) is now out of date.
> I haven't had time to fix it yet; I hope to get to it shortly after the
> patch has been verified.
>
> Regards,
> Jim
>
> At 02:59 PM 2/25/2003, Philip Quitslund wrote:
> >Hey there. I'm stalled on running the tests... When I run ant like so:
> >
> >ant -Drdbm=postgresql -Dmode=remote -Dusername=foo -Dpassword=bar
> >
> >I get the following error:
> >
> >main:
> > [exec] comment=/dev/null
> > [exec] dbcreate=true
> > [exec] dbpassword=password
> > [exec] dbusername=postgres
> > [exec] location=remote:localhost.localdomain::tsvctest
> > [exec] password=bar
> > [exec] username=postgres
> >1124386 [Thread-5] INFO org.eclipse.stellation.remote.engine.Engine -
> >engine accepting connections
> >1124401 [Thread-0] INFO org.eclipse.stellation.remote.engine.Engine -
> >Handling auth.request for tsvctest
> >1124401 [Thread-0] INFO org.eclipse.stellation.remote.engine.Engine -
> >Generating challenge for tsvctest
> >1124868 [Thread-0] INFO org.eclipse.stellation.remote.engine.Engine -
> >Handling auth.response for tsvctest
> >User authentication failed: User not found
> > [exec] Remote authentication rejected
> >
> >BUILD FAILED
> >file:/opt/stellation/test/00.xml:33: exec returned: 2
> >
> >
> >The rub seems to be that the username I set as a parameter is getting
> >disregarded?
> >
> >I'm sure I'm missing something silly. Nevertheless, any advice
> >would be greatly appreciated!
> >
> >Thanks!
> >
> >
> >-phil
> >
> >
> >
> >ps: I'm using: stelcore-dev-bin-2003-01-27 (on Redhat.)
> >
> >
> >
> >
> >_______________________________________________
> >stellation-res mailing list
> >stellation-res@xxxxxxxxxxxxxxx
> >http://dev.eclipse.org/mailman/listinfo/stellation-res
>
> --
> Jim Wright, IBM T.J. Watson Research Center
> *** The Stellation project: Advanced SCM for Collaboration
> *** http://www.eclipse.org/stellation
> *** Work Email: jwright@xxxxxxxxxxxxxx ------- Personal Email:
> jim.wright@xxxxxxx
>
> _______________________________________________
> stellation-res mailing list
> stellation-res@xxxxxxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/stellation-res
>
