task postgresql 7.3 - Re: [stellation-res] Volunteer - Installing the co

[Dave Shields <shields@xxxxxxxxxxxxxx>]

On Fri, Dec 20, 2002 at 12:13:26PM -0500, jhoward@xxxxxxxxxxxxxxx wrote:
> Hello,
> 
> > Yikes. This is bizarre, as I run the tests using 7.2.3 as part of the
> > current build process. Before digging too deeply, you might want to try
> > an older build, say 2002-12-10, to see if problem shows up there as well.
> 
> I tried 2002-12-10 with the same results.  It hangs on test 02 in the
> same place.  
> 
> > You might want to also conduct some simple tests re add/synchronize. For
> > example
> >   tsvc create p
> >   tsvc checkout p
> >   echo "file" > a
> >   tsvc add a
> >   tsvc ci
> >   echo "more" > b
> >   tsvc sync
> > and so forth. If you get a hang, then rerun with -d3 to get log output.
> > For example,
> >   tsvc -d3 ci
> 
> Well, I started in on this process, and I ran into a problem along the
> way.  (Either I'm going to be incredibly helpful in testing, or this
> will all trace back to user error and I'll have to put my keyboard
> down before I hurt myself.  ;)
> 

Don't worry about hurting yourself. Your just hurting my ego - but that's part
of the job.

> In order to conduct these hand tests, I needed to initialize a dabase
> in which to work.  According to the core install instructions, the
> right command is "svcadmin postgres:stellation stellation
> stellation-password".  Because I'm working out of the compiled
> build/bin directory with the t* commands, I translated this to
> "tsvcadmin postgres:stellation stellation stellation-password"
> 

Recent work has included changes to tsvcadmin. I try to keep documents up to
date but sometimes they are out of sync. The download includes the docs, while 
our website has docs corresponding to latest current build. Some of the changes
to tsvcadmin came about as part of Firebird work, which resulted in adding new
options --dbusername and --dbpassword as well as changing argument giving location
to tsvcadmin by use of --location option. There was also a problem in that the database
access code required 'postgres' be used, and didn't allow 'postgresql' or an abbreviation
thereof, which is the usual cli convention. I have fixed these things as I have come across
them, but behavior has changed from 2002-12-10 build to latest, as you have noticed.

> The error message printed was:
> 
> "Error: Invalid command postgres:stellation."
> 
> After hunting around a bit, I saw (unfortunately I don't remember
> where) something that suggested that I should be using the command
> line "svcadmin init postgres:stellation stellation password"
> 
> So, trying "tsvcadmin init postgres:stellation stellation password", I saw:
> 
> Usage:
>   svcadmin init location file
>   svcadmin init location admin-name admin-password
> 
> I noted in the tests that the location used was
> "postgresql:[databasename]" instead of "postgres:[databasename]" as
> the documentation is written.  So I tried that and got a usage message
> again.  Lastly, I tried using the full command line syntax I'd seen in
> the tests:
> 
> tsvcadmin init --location postgresql:stellation --username stellation --password password
> 
> That worked.  The command ran to completion without trouble.
> 
> >   tsvc create p
> >   tsvc checkout p
> >   echo "file" > a
> >   tsvc add a
> >   tsvc ci
> >   echo "more" > b
> >   tsvc sync
> > and so forth. If you get a hang, then rerun with -d3 to get log output.
> > For example,
> >   tsvc -d3 ci
> 
> Just running this sequence of commands without anything more
> complicated, I got up to tsvc sync. That hung, and I ran the command
> again with -d3.  Unfortunately, when I ran it with -d3, everything
> terminated normally.  This was very odd, and it made me wonder if
> perhaps some state from the uncompleted command had allowed the run
> with -d3 to succeed.  I cleaned up from the test, dropped the
> database, and started over, this time running -d3 with every command.
> And much to my satisfaction, I now have a trace with -d3 when the sync
> command froze up.  That trace is...
> 
> ./tsvc -d3 --location=postgresql:stellation --username=jhoward --password=password sync
> 
> 0 [main] INFO org.eclipse.stellation.cli.workspace.Workspace  - start xerces read of workspace doc
> 8 [main] INFO org.eclipse.stellation.cli.workspace.Workspace  - end xerces read of workspace doc
> 16 [main] INFO org.eclipse.stellation.cli.data.LogManager  - start xerces read log
> 35 [main] INFO org.eclipse.stellation.cli.data.LogManager  - end xerces read log
> 107 [main] DEBUG org.eclipse.stellation.cli.workspace.Workspace  - attributes initial size 3
> 188 [main] DEBUG org.eclipse.stellation.cli.workspace.Change - stateNow 0
> 1063 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -1
> 1423 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -2
> 1805 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -3
> 2188 [main] DEBUG org.eclipse.stellation.cli.io.FileInput  - getInputStream -4
> 
> And there the trace stops.  No further progress is reported even after
> a substantial amount of time.
> 
> > Also, which JRE are you using?
> 
> Sun's 1.4.1 JDK.  The full java -version info is:
> 

Hmm. I'm using IBM's JRE 1.3. I don't know if anyone else has tried 1.4.
I'll try to get Sun's JDK. I'd like to get a clean machine to do further testing,
as my machine currently has postgres 7.3.2, postgres 7.3, firebird and db2 all installed,
and is also my development environment, and I may have implicitly added some feature that
is resulting in expected behavior on my machine which you are unable to duplciate on yours.
However, Research is going into "holiday mode" with many people away for a couple of weeks, so 
I don't expect to get a machine to play with until the new year.

> java version "1.4.1"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.1-b21)
> Java HotSpot(TM) Client VM (build 1.4.1-b21, mixed mode)
> 
> 
> 
> Thanks again for all your help,

Thanks for yours -- especially your patience!

> Jeffrey
> _______________________________________________
> stellation-res mailing list
> stellation-res@xxxxxxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/stellation-res

I'd suggest putting your postgres work on the back burner for now, while I try
to sort out some of the issues you have raised. I'm in the midst of an edit related
to support for link files, and would like to get that to stable state before investigating
postgres further. 

In the interim, I suggest you try to install the Eclipse version, via the 
"Installable Eclipse Feature" part of the downloads page. I saw Jim at our 
weekly tea today earler this afternoon, and he said he'd try to put up 
new build soon, as what's there reflects the state of the system before 
the source re-org. Though Jim will be on vacation for a week or so 
and won't be able to respond if you have any questions, others on
the list may be able to help until he gets back.

thanks,
dave

-- 
Dave Shields, IBM Research, shields@xxxxxxxxxxxxxx.