talk@lists.collectionspace.org

WE HAVE SUNSET THIS LISTSERV - Join us at collectionspace@lyrasislists.org

View all threads

1.7 installation snag

JS
Joe Slag
Thu, Jun 2, 2011 5:07 PM

After verifying that nuxeo wasn't running, I re-ran ant create_db import
from my service checkout, which seems to be the right one:

~/collection-space/svc/v1.7$ svn info
Path: .
URL:
https://source.collectionspace.org/collection-space/src/services/tags/v1.7
Repository Root: https://source.collectionspace.org/collection-space
Repository UUID: 632a04b0-194a-439a-a497-68f405da15a8
Revision: 4898
Node Kind: directory
Schedule: normal
Last Changed Author: aron
Last Changed Rev: 4866
Last Changed Date: 2011-05-25 10:56:14 -0500 (Wed, 25 May 2011)

After that returned successfully, I started up nuxeo and then checked the
table definitions. Still no groups_common, and collectionspace_core is
missing the 'uri' field.

On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz pschmitz@berkeley.eduwrote:

Here's another test:

describe collectionspace_core;

It should look like the following. If not, then the nuxeo instance is still
running a previous data model, and not 1.7.

+-----------+--------------+------+-----+---------+-------+
| Field    | Type        | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| id        | varchar(36)  | NO  | PRI | NULL    |      |
| updatedat | datetime    | YES  |    | NULL    |      |
| uri      | varchar(500) | YES  |    | NULL    |      |
| createdat | datetime    | YES  |    | NULL    |      |
| tenantid  | varchar(500) | YES  |    | NULL    |      |
+-----------+--------------+------+-----+---------+-------+


From: joe.slag@gmail.com [mailto:joe.slag@gmail.com] *On Behalf Of *Joe
Slag
Sent: Thursday, June 02, 2011 9:35 AM
To: Patrick Schmitz
Cc: Chris Martin; talk@lists.collectionspace.org

Subject: Re: [Talk] 1.7 installation snag

Aha.

mysql> describe groups_common;
ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist

Pretty sure that nuxeo was shut down when I ran ant create_db import,
but I'll do it again and be positive.

On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz pschmitz@berkeley.eduwrote:

That's not the right one. You need to look for groups_common. Try:

describe groups_common;


After verifying that nuxeo wasn't running, I re-ran `ant create_db import` from my service checkout, which seems to be the right one: ~/collection-space/svc/v1.7$ svn info Path: . URL: https://source.collectionspace.org/collection-space/src/services/tags/v1.7 Repository Root: https://source.collectionspace.org/collection-space Repository UUID: 632a04b0-194a-439a-a497-68f405da15a8 Revision: 4898 Node Kind: directory Schedule: normal Last Changed Author: aron Last Changed Rev: 4866 Last Changed Date: 2011-05-25 10:56:14 -0500 (Wed, 25 May 2011) After that returned successfully, I started up nuxeo and then checked the table definitions. Still no groups_common, and collectionspace_core is missing the 'uri' field. On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz <pschmitz@berkeley.edu>wrote: > Here's another test: > > describe collectionspace_core; > > It should look like the following. If not, then the nuxeo instance is still > running a previous data model, and not 1.7. > > +-----------+--------------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +-----------+--------------+------+-----+---------+-------+ > | id | varchar(36) | NO | PRI | NULL | | > | updatedat | datetime | YES | | NULL | | > | uri | varchar(500) | YES | | NULL | | > | createdat | datetime | YES | | NULL | | > | tenantid | varchar(500) | YES | | NULL | | > +-----------+--------------+------+-----+---------+-------+ > > > ------------------------------ > *From:* joe.slag@gmail.com [mailto:joe.slag@gmail.com] *On Behalf Of *Joe > Slag > *Sent:* Thursday, June 02, 2011 9:35 AM > *To:* Patrick Schmitz > *Cc:* Chris Martin; talk@lists.collectionspace.org > > *Subject:* Re: [Talk] 1.7 installation snag > > Aha. > > mysql> describe groups_common; > ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist > > Pretty sure that nuxeo was shut down when I ran `ant create_db import`, > but I'll do it again and be positive. > > On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz <pschmitz@berkeley.edu>wrote: > >> That's not the right one. You need to look for groups_common. Try: >> >> describe groups_common; >> >> >> ------------------------------ >> >>
AR
Aron Roberts
Thu, Jun 2, 2011 5:37 PM

In the message "Re: [Talk] 1.7 installation snag", dated 2011-06-02,
Joe Slag wrote:

After verifying that nuxeo wasn't running, I re-ran ant create_db import from my service checkout, which seems to be the right one:
... I started up nuxeo and then checked the table definitions. Still
no groups_common, and collectionspace_core is missing the 'uri'
field.

Two more questions:

  1. Is the groups_common table present after you also start up the
    CSpace server, not just the Nuxeo server?

  2. Is the file
    org.collectionspace.services.group.3rdparty.nuxeo...jar (probably
    org.collectionspace.services.group.3rdparty.nuxeo-1.7-SNAPSHOT.jar)
    present in $JBOSS_HOME/server/default/deploy/nuxeo.ear/plugins?
    AFAIK, this is the document type JAR that Nuxeo references to create
    that table.

If not, does that .jar file get installed there when you type 'ant
deploy' from within services/trunk/services/group?

There's a 'deploy' target down in a sub-directory of group/3rdparty
that copies the built .jar file to that location, at least in current
(1.8) trunk.

Aron

On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz
<mailto:pschmitz@berkeley.edupschmitz@berkeley.edu> wrote:

Here's another test:

describe collectionspace_core;

It should look like the following. If not, then the nuxeo instance
is still running a previous data model, and not 1.7.

+-----------+--------------+------+-----+---------+-------+
| Field    | Type        | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| id        | varchar(36)  | NO  | PRI | NULL    |      |
| updatedat | datetime    | YES  |    | NULL    |      |
| uri      | varchar(500) | YES  |    | NULL    |      |
| createdat | datetime    | YES  |    | NULL    |      |
| tenantid  | varchar(500) | YES  |    | NULL    |      |
+-----------+--------------+------+-----+---------+-------+

From: mailto:joe.slag@gmail.comjoe.slag@gmail.com
[mailto:mailto:joe.slag@gmail.comjoe.slag@gmail.com] On Behalf Of
Joe Slag

Sent: Thursday, June 02, 2011 9:35 AM
To: Patrick Schmitz
Cc: Chris Martin;
mailto:talk@lists.collectionspace.orgtalk@lists.collectionspace.org

Subject: Re: [Talk] 1.7 installation snag

Aha.

mysql> describe groups_common;
ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist

Pretty sure that nuxeo was shut down when I ran ant create_db import, but I'll do it again and be positive.

On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz
<mailto:pschmitz@berkeley.edupschmitz@berkeley.edu> wrote:

That's not the right one. You need to look for groups_common. Try:

describe groups_common;


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

In the message "Re: [Talk] 1.7 installation snag", dated 2011-06-02, Joe Slag wrote: >After verifying that nuxeo wasn't running, I re-ran `ant create_db >import` from my service checkout, which seems to be the right one: >... I started up nuxeo and then checked the table definitions. Still >no groups_common, and collectionspace_core is missing the 'uri' >field. Two more questions: 1. Is the groups_common table present after you also start up the CSpace server, not just the Nuxeo server? 2. Is the file org.collectionspace.services.group.3rdparty.nuxeo...jar (probably org.collectionspace.services.group.3rdparty.nuxeo-1.7-SNAPSHOT.jar) present in $JBOSS_HOME/server/default/deploy/nuxeo.ear/plugins? AFAIK, this is the document type JAR that Nuxeo references to create that table. If not, does that .jar file get installed there when you type 'ant deploy' from within services/trunk/services/group? There's a 'deploy' target down in a sub-directory of group/3rdparty that copies the built .jar file to that location, at least in current (1.8) trunk. Aron > >On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz ><<mailto:pschmitz@berkeley.edu>pschmitz@berkeley.edu> wrote: > >Here's another test: > >describe collectionspace_core; > >It should look like the following. If not, then the nuxeo instance >is still running a previous data model, and not 1.7. > >+-----------+--------------+------+-----+---------+-------+ >| Field | Type | Null | Key | Default | Extra | >+-----------+--------------+------+-----+---------+-------+ >| id | varchar(36) | NO | PRI | NULL | | >| updatedat | datetime | YES | | NULL | | >| uri | varchar(500) | YES | | NULL | | >| createdat | datetime | YES | | NULL | | >| tenantid | varchar(500) | YES | | NULL | | >+-----------+--------------+------+-----+---------+-------+ > > > >From: <mailto:joe.slag@gmail.com>joe.slag@gmail.com >[mailto:<mailto:joe.slag@gmail.com>joe.slag@gmail.com] On Behalf Of >Joe Slag > >Sent: Thursday, June 02, 2011 9:35 AM >To: Patrick Schmitz >Cc: Chris Martin; ><mailto:talk@lists.collectionspace.org>talk@lists.collectionspace.org > >Subject: Re: [Talk] 1.7 installation snag > > >Aha. > >mysql> describe groups_common; >ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist > >Pretty sure that nuxeo was shut down when I ran `ant create_db >import`, but I'll do it again and be positive. > >On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz ><<mailto:pschmitz@berkeley.edu>pschmitz@berkeley.edu> wrote: > >That's not the right one. You need to look for groups_common. Try: > >describe groups_common; > > > > > >_______________________________________________ >Talk mailing list >Talk@lists.collectionspace.org >http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
PS
Patrick Schmitz
Thu, Jun 2, 2011 5:39 PM

Well then there is some confusion about the sources and schemas. Is there a services/group folder in your source tree?

Have you checked out source from the 1.7 tag?

Patrick
Thx - Patrick

-----Original Message-----
From: Joe Slag joe@slagwerks.com
Sender: joe.slag@gmail.com
Date: Thu, 2 Jun 2011 12:07:48
To: Patrick Schmitzpschmitz@berkeley.edu
Cc: Chris Martincsm22@caret.cam.ac.uk; talk@lists.collectionspace.org
Subject: Re: [Talk] 1.7 installation snag

After verifying that nuxeo wasn't running, I re-ran ant create_db import
from my service checkout, which seems to be the right one:

~/collection-space/svc/v1.7$ svn info
Path: .
URL:
https://source.collectionspace.org/collection-space/src/services/tags/v1.7
Repository Root: https://source.collectionspace.org/collection-space
Repository UUID: 632a04b0-194a-439a-a497-68f405da15a8
Revision: 4898
Node Kind: directory
Schedule: normal
Last Changed Author: aron
Last Changed Rev: 4866
Last Changed Date: 2011-05-25 10:56:14 -0500 (Wed, 25 May 2011)

After that returned successfully, I started up nuxeo and then checked the
table definitions. Still no groups_common, and collectionspace_core is
missing the 'uri' field.

On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz pschmitz@berkeley.eduwrote:

Here's another test:

describe collectionspace_core;

It should look like the following. If not, then the nuxeo instance is still
running a previous data model, and not 1.7.

+-----------+--------------+------+-----+---------+-------+
| Field    | Type        | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| id        | varchar(36)  | NO  | PRI | NULL    |      |
| updatedat | datetime    | YES  |    | NULL    |      |
| uri      | varchar(500) | YES  |    | NULL    |      |
| createdat | datetime    | YES  |    | NULL    |      |
| tenantid  | varchar(500) | YES  |    | NULL    |      |
+-----------+--------------+------+-----+---------+-------+


From: joe.slag@gmail.com [mailto:joe.slag@gmail.com] *On Behalf Of *Joe
Slag
Sent: Thursday, June 02, 2011 9:35 AM
To: Patrick Schmitz
Cc: Chris Martin; talk@lists.collectionspace.org

Subject: Re: [Talk] 1.7 installation snag

Aha.

mysql> describe groups_common;
ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist

Pretty sure that nuxeo was shut down when I ran ant create_db import,
but I'll do it again and be positive.

On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz pschmitz@berkeley.eduwrote:

That's not the right one. You need to look for groups_common. Try:

describe groups_common;


Well then there is some confusion about the sources and schemas. Is there a services/group folder in your source tree? Have you checked out source from the 1.7 tag? Patrick Thx - Patrick -----Original Message----- From: Joe Slag <joe@slagwerks.com> Sender: joe.slag@gmail.com Date: Thu, 2 Jun 2011 12:07:48 To: Patrick Schmitz<pschmitz@berkeley.edu> Cc: Chris Martin<csm22@caret.cam.ac.uk>; <talk@lists.collectionspace.org> Subject: Re: [Talk] 1.7 installation snag After verifying that nuxeo wasn't running, I re-ran `ant create_db import` from my service checkout, which seems to be the right one: ~/collection-space/svc/v1.7$ svn info Path: . URL: https://source.collectionspace.org/collection-space/src/services/tags/v1.7 Repository Root: https://source.collectionspace.org/collection-space Repository UUID: 632a04b0-194a-439a-a497-68f405da15a8 Revision: 4898 Node Kind: directory Schedule: normal Last Changed Author: aron Last Changed Rev: 4866 Last Changed Date: 2011-05-25 10:56:14 -0500 (Wed, 25 May 2011) After that returned successfully, I started up nuxeo and then checked the table definitions. Still no groups_common, and collectionspace_core is missing the 'uri' field. On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz <pschmitz@berkeley.edu>wrote: > Here's another test: > > describe collectionspace_core; > > It should look like the following. If not, then the nuxeo instance is still > running a previous data model, and not 1.7. > > +-----------+--------------+------+-----+---------+-------+ > | Field | Type | Null | Key | Default | Extra | > +-----------+--------------+------+-----+---------+-------+ > | id | varchar(36) | NO | PRI | NULL | | > | updatedat | datetime | YES | | NULL | | > | uri | varchar(500) | YES | | NULL | | > | createdat | datetime | YES | | NULL | | > | tenantid | varchar(500) | YES | | NULL | | > +-----------+--------------+------+-----+---------+-------+ > > > ------------------------------ > *From:* joe.slag@gmail.com [mailto:joe.slag@gmail.com] *On Behalf Of *Joe > Slag > *Sent:* Thursday, June 02, 2011 9:35 AM > *To:* Patrick Schmitz > *Cc:* Chris Martin; talk@lists.collectionspace.org > > *Subject:* Re: [Talk] 1.7 installation snag > > Aha. > > mysql> describe groups_common; > ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist > > Pretty sure that nuxeo was shut down when I ran `ant create_db import`, > but I'll do it again and be positive. > > On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz <pschmitz@berkeley.edu>wrote: > >> That's not the right one. You need to look for groups_common. Try: >> >> describe groups_common; >> >> >> ------------------------------ >> >>
MJ
Martinez, Jesse
Thu, Jun 2, 2011 5:47 PM

Thought I'd throw this out there:

I ran into something a bit similar a while back where my JBOSS_HOME
environmental var was pointing to an old deployment of cspace.
(JBOSS_HOME was set to /usr/local/share/1.5/jboss-4.3.2.GA rather than
.../1.6/jboss-4.3.2.GA) This caused a headache upon deployment where I
couldn't get the services layer to communicate properly.

My 2c.

  • Jesse

From: talk-bounces@lists.collectionspace.org
[mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Patrick
Schmitz
Sent: Thursday, June 02, 2011 1:40 PM
To: Joe Slag; joe.slag@gmail.com
Cc: talk@lists.collectionspace.org
Subject: Re: [Talk] 1.7 installation snag

Well then there is some confusion about the sources and schemas. Is
there a services/group folder in your source tree?

Have you checked out source from the 1.7 tag?

Patrick

Thx - Patrick


From: Joe Slag joe@slagwerks.com

Sender: joe.slag@gmail.com

Date: Thu, 2 Jun 2011 12:07:48 -0500

To: Patrick Schmitzpschmitz@berkeley.edu

Cc: Chris Martincsm22@caret.cam.ac.uk;
talk@lists.collectionspace.org

Subject: Re: [Talk] 1.7 installation snag

After verifying that nuxeo wasn't running, I re-ran ant create_db import from my service checkout, which seems to be the right one:

~/collection-space/svc/v1.7$ svn info

Path: .

URL:
https://source.collectionspace.org/collection-space/src/services/tags/v1
.7

Repository Root: https://source.collectionspace.org/collection-space

Repository UUID: 632a04b0-194a-439a-a497-68f405da15a8

Revision: 4898

Node Kind: directory

Schedule: normal

Last Changed Author: aron

Last Changed Rev: 4866

Last Changed Date: 2011-05-25 10:56:14 -0500 (Wed, 25 May 2011)

After that returned successfully, I started up nuxeo and then checked
the table definitions. Still no groups_common, and collectionspace_core
is missing the 'uri' field.

On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz pschmitz@berkeley.edu
wrote:

Here's another test:

describe collectionspace_core;

It should look like the following. If not, then the nuxeo instance is
still running a previous data model, and not 1.7.

+-----------+--------------+------+-----+---------+-------+
| Field    | Type        | Null | Key | Default | Extra |
+-----------+--------------+------+-----+---------+-------+
| id        | varchar(36)  | NO  | PRI | NULL    |      |
| updatedat | datetime    | YES  |    | NULL    |      |
| uri      | varchar(500) | YES  |    | NULL    |      |
| createdat | datetime    | YES  |    | NULL    |      |
| tenantid  | varchar(500) | YES  |    | NULL    |      |
+-----------+--------------+------+-----+---------+-------+


From: joe.slag@gmail.com [mailto:joe.slag@gmail.com] On Behalf

Of Joe Slag

Sent: Thursday, June 02, 2011 9:35 AM
To: Patrick Schmitz
Cc: Chris Martin; talk@lists.collectionspace.org


Subject: Re: [Talk] 1.7 installation snag

 

Aha. 

 

mysql> describe groups_common;

ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist

 

Pretty sure that nuxeo was shut down when I ran `ant create_db

import`, but I'll do it again and be positive.

On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz

pschmitz@berkeley.edu wrote:

That's not the right one. You need to look for groups_common.

Try:

describe groups_common;

 

	

Thought I'd throw this out there: I ran into something a bit similar a while back where my JBOSS_HOME environmental var was pointing to an old deployment of cspace. (JBOSS_HOME was set to /usr/local/share/1.5/jboss-4.3.2.GA rather than .../1.6/jboss-4.3.2.GA) This caused a headache upon deployment where I couldn't get the services layer to communicate properly. My 2c. - Jesse ________________________________ From: talk-bounces@lists.collectionspace.org [mailto:talk-bounces@lists.collectionspace.org] On Behalf Of Patrick Schmitz Sent: Thursday, June 02, 2011 1:40 PM To: Joe Slag; joe.slag@gmail.com Cc: talk@lists.collectionspace.org Subject: Re: [Talk] 1.7 installation snag Well then there is some confusion about the sources and schemas. Is there a services/group folder in your source tree? Have you checked out source from the 1.7 tag? Patrick Thx - Patrick ________________________________ From: Joe Slag <joe@slagwerks.com> Sender: joe.slag@gmail.com Date: Thu, 2 Jun 2011 12:07:48 -0500 To: Patrick Schmitz<pschmitz@berkeley.edu> Cc: Chris Martin<csm22@caret.cam.ac.uk>; <talk@lists.collectionspace.org> Subject: Re: [Talk] 1.7 installation snag After verifying that nuxeo wasn't running, I re-ran `ant create_db import` from my service checkout, which seems to be the right one: ~/collection-space/svc/v1.7$ svn info Path: . URL: https://source.collectionspace.org/collection-space/src/services/tags/v1 .7 Repository Root: https://source.collectionspace.org/collection-space Repository UUID: 632a04b0-194a-439a-a497-68f405da15a8 Revision: 4898 Node Kind: directory Schedule: normal Last Changed Author: aron Last Changed Rev: 4866 Last Changed Date: 2011-05-25 10:56:14 -0500 (Wed, 25 May 2011) After that returned successfully, I started up nuxeo and then checked the table definitions. Still no groups_common, and collectionspace_core is missing the 'uri' field. On Thu, Jun 2, 2011 at 11:43 AM, Patrick Schmitz <pschmitz@berkeley.edu> wrote: Here's another test: describe collectionspace_core; It should look like the following. If not, then the nuxeo instance is still running a previous data model, and not 1.7. +-----------+--------------+------+-----+---------+-------+ | Field | Type | Null | Key | Default | Extra | +-----------+--------------+------+-----+---------+-------+ | id | varchar(36) | NO | PRI | NULL | | | updatedat | datetime | YES | | NULL | | | uri | varchar(500) | YES | | NULL | | | createdat | datetime | YES | | NULL | | | tenantid | varchar(500) | YES | | NULL | | +-----------+--------------+------+-----+---------+-------+ ________________________________ From: joe.slag@gmail.com [mailto:joe.slag@gmail.com] On Behalf Of Joe Slag Sent: Thursday, June 02, 2011 9:35 AM To: Patrick Schmitz Cc: Chris Martin; talk@lists.collectionspace.org Subject: Re: [Talk] 1.7 installation snag Aha. mysql> describe groups_common; ERROR 1146 (42S02): Table 'nuxeo.groups_common' doesn't exist Pretty sure that nuxeo was shut down when I ran `ant create_db import`, but I'll do it again and be positive. On Thu, Jun 2, 2011 at 11:30 AM, Patrick Schmitz <pschmitz@berkeley.edu> wrote: That's not the right one. You need to look for groups_common. Try: describe groups_common; ________________________________
JS
Joe Slag
Thu, Jun 2, 2011 7:29 PM

I think I've stumbled on the source of my problems.

Since I started upgrading CollectionSpace back around release 1.2, I'd
unconsciously come to the conclusion that
the jboss-4.2.3.GA-default-5.3.2.tar.gz files were the same between
releases, and that all changes resided in either
the jboss-4.2.3.GA-cspace-1.*.tar.gz files or in the subversion check-outs.
So I'd been skipping the step of re-downloading what I thought was a file I
already had.

Kasper's question made me aware of this assumption, which I just realized is
false. Currently in the process of grabbing the default tarball from the 1.7
directory and reinstalling using it.

I'm probably the only person to make this particular mistake so far, but
going forwards I wonder if it would be possible to name these files such
that they wouldn't be easily confused?

thanks for all the help debugging, folks.

  • Joe

On Wed, Jun 1, 2011 at 6:37 PM, Joe Slag joe@slagwerks.com wrote:

Hello CSpacers,

I downloaded the 1.7 tarball today and went about setting it up, but
have run into a snag.

I'm following the steps in

http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions
including the ant create_db import, so my assumption is that nothing
lying around from previous installations on the server should be
interfering. Correct?

The first sign of something possibly being off is this error in
server.log, which shows up when logging in to the web UI.

https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log

Perhaps this has to do with not having initialized the authorities?

Moving on, I tried to initialize the authorities, and got the error

"Create request failed:  detail:
org.collectionspace.services.common.document.DocumentException:
org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not
found: uri".

More details:

https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js

I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set
to localhost, but just to be sure I changed it to the server's IP,
restarted, and tried again -- same results. That segment looks like:

<persistence> <service> <url>http://our ip:8180/cspace-services</url> <config-tenant></config-tenant> <config-bindings></config-bindings> <ims-url>http://our ip:8180/collectionspace/chain/</ims-url> <!-- XXX should be in separate IMS section --> </service> </persistence>

Since that fails, of course the controlled list dropdowns are all
unpopulated.

I assume I'm missing something obvious, but sadly it isn't obvious to
me. Any ideas?

thanks,
Joe

I think I've stumbled on the source of my problems. Since I started upgrading CollectionSpace back around release 1.2, I'd unconsciously come to the conclusion that the jboss-4.2.3.GA-default-5.3.2.tar.gz files were the same between releases, and that all changes resided in either the jboss-4.2.3.GA-cspace-1.*.tar.gz files or in the subversion check-outs. So I'd been skipping the step of re-downloading what I thought was a file I already had. Kasper's question made me aware of this assumption, which I just realized is false. Currently in the process of grabbing the default tarball from the 1.7 directory and reinstalling using it. I'm probably the only person to make this particular mistake so far, but going forwards I wonder if it would be possible to name these files such that they wouldn't be easily confused? thanks for all the help debugging, folks. - Joe On Wed, Jun 1, 2011 at 6:37 PM, Joe Slag <joe@slagwerks.com> wrote: > Hello CSpacers, > > I downloaded the 1.7 tarball today and went about setting it up, but > have run into a snag. > > I'm following the steps in > > http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions > including the `ant create_db import`, so my assumption is that nothing > lying around from previous installations on the server should be > interfering. Correct? > > The first sign of something possibly being off is this error in > server.log, which shows up when logging in to the web UI. > > > https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log > > Perhaps this has to do with not having initialized the authorities? > > Moving on, I tried to initialize the authorities, and got the error > > "Create request failed: detail: > org.collectionspace.services.common.document.DocumentException: > org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not > found: uri". > > More details: > > > https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js > > I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set > to localhost, but just to be sure I changed it to the server's IP, > restarted, and tried again -- same results. That segment looks like: > > <persistence> > <service> > <url>http://our ip:8180/cspace-services</url> > <config-tenant></config-tenant> > <config-bindings></config-bindings> > <ims-url>http://our ip:8180/collectionspace/chain/</ims-url> > <!-- XXX should be in separate IMS section --> > </service> > </persistence> > > Since that fails, of course the controlled list dropdowns are all > unpopulated. > > I assume I'm missing something obvious, but sadly it isn't obvious to > me. Any ideas? > > thanks, > Joe >
KG
Kasper Galschiot Markus
Thu, Jun 2, 2011 8:12 PM

+1 to that idea.

I have myself not been 100% sure how much (and whether at all) the
default tarballs varied between releases - I've downloaded and exploded
the latest default tarball every time just to be sure (and to enjoy the
inter-slice speed) - but naming the jboss default tarball with the
cspace version should make it clearer that both tarballs are indeed
needed to be the latest (even if this is only true on some upgrades).

~Kasper

On 06/02/2011 02:29 PM, Joe Slag wrote:

I think I've stumbled on the source of my problems.

Since I started upgrading CollectionSpace back around release 1.2, I'd
unconsciously come to the conclusion that
the jboss-4.2.3.GA-default-5.3.2.tar.gz files were the same between
releases, and that all changes resided in either
the jboss-4.2.3.GA-cspace-1.*.tar.gz files or in the subversion
check-outs. So I'd been skipping the step of re-downloading what I
thought was a file I already had.

Kasper's question made me aware of this assumption, which I just
realized is false. Currently in the process of grabbing the default
tarball from the 1.7 directory and reinstalling using it.

I'm probably the only person to make this particular mistake so far,
but going forwards I wonder if it would be possible to name these
files such that they wouldn't be easily confused?

thanks for all the help debugging, folks.

  • Joe

On Wed, Jun 1, 2011 at 6:37 PM, Joe Slag <joe@slagwerks.com
mailto:joe@slagwerks.com> wrote:

 Hello CSpacers,

 I downloaded the 1.7 tarball today and went about setting it up, but
 have run into a snag.

 I'm following the steps in
 http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions
 including the `ant create_db import`, so my assumption is that nothing
 lying around from previous installations on the server should be
 interfering. Correct?

 The first sign of something possibly being off is this error in
 server.log, which shows up when logging in to the web UI.

 https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log

 Perhaps this has to do with not having initialized the authorities?

 Moving on, I tried to initialize the authorities, and got the error

  "Create request failed:  detail:
 org.collectionspace.services.common.document.DocumentException:
 org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not
 found: uri".

 More details:

 https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js

 I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set
 to localhost, but just to be sure I changed it to the server's IP,
 restarted, and tried again -- same results. That segment looks like:

 <persistence>
 <service>
 <url>http://our ip:8180/cspace-services</url>
 <config-tenant></config-tenant>
 <config-bindings></config-bindings>
 <ims-url>http://our ip:8180/collectionspace/chain/</ims-url>
 <!-- XXX should be in separate IMS section -->
 </service>
 </persistence>

 Since that fails, of course the controlled list dropdowns are all
 unpopulated.

 I assume I'm missing something obvious, but sadly it isn't obvious to
 me. Any ideas?

 thanks,
 Joe

Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

+1 to that idea. I have myself not been 100% sure how much (and whether at all) the default tarballs varied between releases - I've downloaded and exploded the latest default tarball every time just to be sure (and to enjoy the inter-slice speed) - but naming the jboss default tarball with the cspace version should make it clearer that both tarballs are indeed needed to be the latest (even if this is only true on some upgrades). ~Kasper On 06/02/2011 02:29 PM, Joe Slag wrote: > I think I've stumbled on the source of my problems. > > Since I started upgrading CollectionSpace back around release 1.2, I'd > unconsciously come to the conclusion that > the jboss-4.2.3.GA-default-5.3.2.tar.gz files were the same between > releases, and that all changes resided in either > the jboss-4.2.3.GA-cspace-1.*.tar.gz files or in the subversion > check-outs. So I'd been skipping the step of re-downloading what I > thought was a file I already had. > > Kasper's question made me aware of this assumption, which I just > realized is false. Currently in the process of grabbing the default > tarball from the 1.7 directory and reinstalling using it. > > I'm probably the only person to make this particular mistake so far, > but going forwards I wonder if it would be possible to name these > files such that they wouldn't be easily confused? > > thanks for all the help debugging, folks. > > - Joe > > On Wed, Jun 1, 2011 at 6:37 PM, Joe Slag <joe@slagwerks.com > <mailto:joe@slagwerks.com>> wrote: > > Hello CSpacers, > > I downloaded the 1.7 tarball today and went about setting it up, but > have run into a snag. > > I'm following the steps in > http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions > including the `ant create_db import`, so my assumption is that nothing > lying around from previous installations on the server should be > interfering. Correct? > > The first sign of something possibly being off is this error in > server.log, which shows up when logging in to the web UI. > > https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log > > Perhaps this has to do with not having initialized the authorities? > > Moving on, I tried to initialize the authorities, and got the error > > "Create request failed: detail: > org.collectionspace.services.common.document.DocumentException: > org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not > found: uri". > > More details: > > https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js > > I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set > to localhost, but just to be sure I changed it to the server's IP, > restarted, and tried again -- same results. That segment looks like: > > <persistence> > <service> > <url>http://our ip:8180/cspace-services</url> > <config-tenant></config-tenant> > <config-bindings></config-bindings> > <ims-url>http://our ip:8180/collectionspace/chain/</ims-url> > <!-- XXX should be in separate IMS section --> > </service> > </persistence> > > Since that fails, of course the controlled list dropdowns are all > unpopulated. > > I assume I'm missing something obvious, but sadly it isn't obvious to > me. Any ideas? > > thanks, > Joe > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
AR
Aron Roberts
Thu, Jun 2, 2011 8:26 PM

Ahh ... makes lots of sense, Joe!  Hoping that your install works
after reinstalling with the 1.7 release's copy of
jboss-4.2.3.GA-default-5.3.2.tar.gz!

Have added a JIRA for your suggestion:
http://issues.collectionspace.org/browse/CSPACE-4058

Aron

In the message "Re: [Talk] 1.7 installation snag", dated 2011-06-02,
Joe Slag wrote:

I think I've stumbled on the source of my problems.

Since I started upgrading CollectionSpace back around release 1.2,
I'd unconsciously come to the conclusion that
the jboss-4.2.3.GA-default-5.3.2.tar.gz files were the same between
releases, and that all changes resided in either
the jboss-4.2.3.GA-cspace-1.*.tar.gz files or in the subversion
check-outs. So I'd been skipping the step of re-downloading what I
thought was a file I already had.

Kasper's question made me aware of this assumption, which I just
realized is false. Currently in the process of grabbing the default
tarball from the 1.7 directory and reinstalling using it.

I'm probably the only person to make this particular mistake so far,
but going forwards I wonder if it would be possible to name these
files such that they wouldn't be easily confused?

thanks for all the help debugging, folks.

  • Joe

On Wed, Jun 1, 2011 at 6:37 PM, Joe Slag
<mailto:joe@slagwerks.comjoe@slagwerks.com> wrote:

Hello CSpacers,

I downloaded the 1.7 tarball today and went about setting it up, but
have run into a snag.

I'm following the steps in
http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributionshttp://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions
including the ant create_db import, so my assumption is that nothing
lying around from previous installations on the server should be
interfering. Correct?

The first sign of something possibly being off is this error in
server.log, which shows up when logging in to the web UI.

https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.loghttps://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log

Perhaps this has to do with not having initialized the authorities?

Moving on, I tried to initialize the authorities, and got the error

"Create request failed:  detail:
org.collectionspace.services.common.document.DocumentException:
org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not
found: uri".

More details:

https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.jshttps://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js

I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set
to localhost, but just to be sure I changed it to the server's IP,
restarted, and tried again -- same results. That segment looks like:

<persistence> <service> <url><http://our>http://our ip:8180/cspace-services</url> <config-tenant></config-tenant> <config-bindings></config-bindings> <ims-url><http://our>http://our ip:8180/collectionspace/chain/</ims-url> <!-- XXX should be in separate IMS section --> </service> </persistence>

Since that fails, of course the controlled list dropdowns are all unpopulated.

I assume I'm missing something obvious, but sadly it isn't obvious to
me. Any ideas?

thanks,
Joe


Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Ahh ... makes lots of sense, Joe! Hoping that your install works after reinstalling with the 1.7 release's copy of jboss-4.2.3.GA-default-5.3.2.tar.gz! Have added a JIRA for your suggestion: http://issues.collectionspace.org/browse/CSPACE-4058 Aron In the message "Re: [Talk] 1.7 installation snag", dated 2011-06-02, Joe Slag wrote: >I think I've stumbled on the source of my problems. > >Since I started upgrading CollectionSpace back around release 1.2, >I'd unconsciously come to the conclusion that >the jboss-4.2.3.GA-default-5.3.2.tar.gz files were the same between >releases, and that all changes resided in either >the jboss-4.2.3.GA-cspace-1.*.tar.gz files or in the subversion >check-outs. So I'd been skipping the step of re-downloading what I >thought was a file I already had. > >Kasper's question made me aware of this assumption, which I just >realized is false. Currently in the process of grabbing the default >tarball from the 1.7 directory and reinstalling using it. > >I'm probably the only person to make this particular mistake so far, >but going forwards I wonder if it would be possible to name these >files such that they wouldn't be easily confused? > >thanks for all the help debugging, folks. > >- Joe > >On Wed, Jun 1, 2011 at 6:37 PM, Joe Slag ><<mailto:joe@slagwerks.com>joe@slagwerks.com> wrote: > >Hello CSpacers, > >I downloaded the 1.7 tarball today and went about setting it up, but >have run into a snag. > >I'm following the steps in ><http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions>http://wiki.collectionspace.org/display/DOC/Installing+1.7+on+Aptitude+Compatible+Linux+Distributions >including the `ant create_db import`, so my assumption is that nothing >lying around from previous installations on the server should be >interfering. Correct? > >The first sign of something possibly being off is this error in >server.log, which shows up when logging in to the web UI. > > ><https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log>https://gist.github.com/raw/8015e91fd7606af3a1d6/7486dcc4e2a9a9afdb2a998345c501cefd9dd157/server.log > >Perhaps this has to do with not having initialized the authorities? > >Moving on, I tried to initialize the authorities, and got the error > > "Create request failed: detail: >org.collectionspace.services.common.document.DocumentException: >org.nuxeo.ecm.core.api.model.PropertyNotFoundException: Property not >found: uri". > >More details: > > ><https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js>https://gist.github.com/raw/56ebe61d1a1e5e683af5/4d7fafce4564b2b6f1b1b25e91e08f6c0217b96a/error.js > >I'd left the $JBOSS_HOME/server/cspace/conf/settings.xml url field set >to localhost, but just to be sure I changed it to the server's IP, >restarted, and tried again -- same results. That segment looks like: > > <persistence> > <service> > <url><http://our>http://our ip:8180/cspace-services</url> > <config-tenant></config-tenant> > <config-bindings></config-bindings> > <ims-url><http://our>http://our ip:8180/collectionspace/chain/</ims-url> ><!-- XXX should be in separate IMS section --> > </service> > </persistence> > >Since that fails, of course the controlled list dropdowns are all unpopulated. > >I assume I'm missing something obvious, but sadly it isn't obvious to >me. Any ideas? > >thanks, >Joe > > > >_______________________________________________ >Talk mailing list >Talk@lists.collectionspace.org >http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org