Hi

I am trying to get my first collectionspace server up, but is having some issue. Started with 3.2.1 since this is what the customer is using, but seem to end up with a setup that is somewhat incomplete.

I am using java 7.

the mvn clean deploy succeeds. The ant [undeploy] deploy create_db import also completes with BUILD SUCCESSFUL but there is a lot of warning underway.

According to the troubleshooting there should both be a cspace and nuxeo database now. I only see the cspace.

Attempting to start the tomcat leads to a number of WARN/errors in the log and it ends with the cspace-service not being started. Attached the log file.

It seems to have trouble creating/starting with the lifesci tenant, but that is prob. due to null pointer in

at com.mysql.jdbc.jdbc2.optional.MysqlDataSource.getConnection(MysqlDataSource.java:427)

Can I remove the lifesci if this is creating problems?

In order to make 3.2.2 deploy I had to change the release number from 3.2 to 3.2.2 in the service build.properties, but ends with the same problem.

Tried the 4.0, but this has some dependencies to a csmake.jar in the application. Checked out from git now and trying to build all from source.

My next attempt would be to go the postgres route since this is the default and it seems to be related to MySQL.

cheers,
:-Dennis Schafroth

Hi Dennis and all,

Dennis is working with the SMK on the development of our website's search engine.

I hadn't seen your message, Dennis.
You can ask us before doing so on the forum - even if, as you can see, people here are responsive, helpful and super-skilled.

Cheers,
Sébastien

Fra: Talk [mailto:talk-bounces@lists.collectionspace.org] På vegne af Dennis Schafroth
Sendt: 9. oktober 2013 10:47
Til: Aron Roberts
Cc: talk@lists.collectionspace.org
Emne: Re: [Talk] Problem installing on Mac OS X using MySQL

On Oct 8, 2013, at 19:41 , Aron Roberts <aronroberts@gmail.commailto:aronroberts@gmail.com> wrote:

Thanks, Dennis!  Appreciate the context.

What harvester product are you extending to connect to CollectionSpace?

I am working for a small company Index Data that is specialised in search and indexing technologies mostly within the library domain . We have some open source products such as Pazpar2 (http://www.indexdata.com/pazpar2) and Metaproxy (http://www.indexdata.com/metaproxy).

In our enterprise solution, Masterkey Platform, we also have a Local Unified Index based on Solr/Lucene, which is populated by our harvester: http://www.indexdata.com/masterkey/

Finally, you may have already seen these, but just in case, the
complete Services layer APIs can be found at:

http://wiki.collectionspace.org/display/DOC/Common+Services+REST+API+documentation
and
http://wiki.collectionspace.org/display/DOC/Services+Layer+REST+API

I have read the API documentation, but I feel like I am missing something to understand it fully. I will most like ask some question here later when I gotten around formulate them.

cheers,
:-Dennis

Aron

On Tue, Oct 8, 2013 at 10:29 AM, Dennis Schafroth <dennis@indexdata.commailto:dennis@indexdata.com> wrote:

Thanks for the warning, but I am not going to run this in production. I am just investigating the API and having test server, since we are extending our harvester product to handle CollectionSpace.

cheers,
:-Dennis

On Oct 8, 2013, at 19:20 , Aron Roberts <aronroberts@gmail.commailto:aronroberts@gmail.com> wrote:

As a quick followup, I do want to encourage you to consider using
PostgreSQL for your client in any production uses, given the project's
ongoing commitment to that database system, the fact that MySQL is no
longer routinely tested, and the concern that there are already known
issues with using MySQL.  You'll also find that the rest of the
community, including project staff and members of implementing
institutions, are much more likely to be able to offer support here
for PostgreSQL.

As a relevant aside, a number of us were unfamiliar with PostgreSQL,
since we'd routinely used MySQL for CollectionSpace's early releases
and with other, past systems as well.  The transition wasn't too
painful, and as you might imagine, there is a great deal of
'crosswalk' documentation on the web on "how to perform action x in
PostgreSQL that you might have performed using command y in MySQL," in
the cases where those differ.  PostgreSQL's online documentation is
particularly thorough and well-written, as well.

On Tue, Oct 8, 2013 at 10:14 AM, Aron Roberts <aronroberts@gmail.commailto:aronroberts@gmail.com> wrote:

Great, Dennis!  Feel free to let us know of your experiences with
MySQL, both good and bad, here on the Talk list.

On Tue, Oct 8, 2013 at 10:13 AM, Dennis Schafroth <dennis@indexdata.commailto:dennis@indexdata.com> wrote:

Hi Aron

Yeah, I actually manage to get it up with MySQL by following the "missing" stuff.

Some configuration pointed to postgres for lifesci. The added some missing databases (lifesci, nuxeo), but you are right. I should get it up and running with PostgreSQL. I am just not that familiar with it.

And yes I should be able to find a linux box as well

But thanks for heads up on the MySQL issues.

cheers,
:-Dennis

On Oct 8, 2013, at 19:04 , Aron Roberts <aronroberts@gmail.commailto:aronroberts@gmail.com> wrote:

Hi Dennis,

Although the current documentation may not always make this clear,
the CollectionSpace system currently is only being built and tested
with PostgreSQL.  You'll likely have much better results using
PostgreSQL.

If you don't have any strong commitment to using, say, a Linux
package manager like yum or aptitude, or if you're installing on a
non-Linux system, the Enterprise DB installers for PostgreSQL make the
installation process quite fast and easy.  There are then some - at
present manual - configuration steps you'll need to take to get
PostgreSQL set up for use with CollectionSpace:

http://wiki.collectionspace.org/display/DOC/PostgreSQL+Installation+under+Linux
or
http://wiki.collectionspace.org/display/DOC/PostgreSQL+Installation+-+Windows%2C+Mac+OS+X%2C+Generic+Linux

Aron

P.S. Your note is a reminder that we should - and a commitment that we
will - make this clearer in product documentation. Currently, you can
find the preference for PostgreSQL over MySQL stated in a) the warning
at the top of http://wiki.collectionspace.org/display/DOC/Installing+and+configuring+MySQL
and b) the fact that installation documentation only mentions
PostgreSQL.

On Tue, Oct 8, 2013 at 5:54 AM, Dennis Schafroth <dennis@indexdata.commailto:dennis@indexdata.com> wrote:

Hi

I am trying to get my first collectionspace server up, but is having some issue. Started with 3.2.1 since this is what the customer is using, but seem to end up with a setup that is somewhat incomplete.

I am using java 7.

the mvn clean deploy succeeds. The ant [undeploy] deploy create_db import also completes with BUILD SUCCESSFUL but there is a lot of warning underway.

According to the troubleshooting there should both be a cspace and nuxeo database now. I only see the cspace.

Attempting to start the tomcat leads to a number of WARN/errors in the log and it ends with the cspace-service not being started. Attached the log file.

It seems to have trouble creating/starting with the lifesci tenant, but that is prob. due to null pointer in

at com.mysql.jdbc.jdbc2.optional.MysqlDataSource.getConnection(MysqlDataSource.java:427)

Can I remove the lifesci if this is creating problems?

In order to make 3.2.2 deploy I had to change the release number from 3.2 to 3.2.2 in the service build.properties, but ends with the same problem.

Tried the 4.0, but this has some dependencies to a csmake.jar in the application. Checked out from git now and trying to build all from source.

My next attempt would be to go the postgres route since this is the default and it seems to be related to MySQL.

cheers,
:-Dennis Schafroth

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