talk@lists.collectionspace.org

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

View all threads

Re: [Talk] Fw: Failure with automated script

CR
Christopher R. HOFFMAN
Thu, Mar 12, 2015 6:33 PM

Hi John and Ryan,
It's great to hear from another university looking at CollectionSpace!
Could you say a little bit about what you're trying to accomplish with your
installation?  I'm happy to talk off-list but I suspect others would be
interested in hearing more.

Thanks,
Chris

On Mar 12, 2015, at 10:41 AM, John Torgersen jtorg@umich.edu wrote:

Hi Aron,

Ryan let me know that he made the same change as Brian Franzone to get the
manual install to work.

Thanks again,
John

On 3/10/2015 11:35 AM, Aron Roberts wrote:

That's great to hear, John! Thanks much for passing along this report from
Ryan, as well.

We had a report on February 17, from Brian Franzone of the Harvard
University Herbaria, that they needed to make the following change to
complete an installation of v4.1. (I don't know whether they were doing a
manual or automated install.) Was this the change - or among the changes -
that Ryan made? (He mentioned "some files".)

Change info in application/pom.xml file

<!-- remove <repository> <id>libs-snapshot-local</id> <name>libs-snapshot-local</name> <url> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local </url> <snapshots> <enabled>true</enabled> </snapshots> </repository> --> <!--add --> <repository> <id>libs-snapshot-local</id> <name>libs-snapshot-local</name> <url> http://nightly.collectionspace.org:8081/artifactory/libs-release-local</url> <snapshots> <enabled>false</enabled> </snapshots> </repository>

I haven't seen this issue crop up, in my own tests of the automated
installer on a fresh Ubuntu 14.04.01 VM, but haven't looked into it ...

Aron

P.S. Within that application/pom.xml file, in the v4.1.1 tagged release,
there was only a reference to the 'libs-snapshot-local' repo, but not to
'libs-releases-local'. I've observed that the 'lib-releases-local' repo was
added, alongisde 'libs-snapshot-local', in this commit in (v4.2) master
after v.4.1.1's release.

https://github.com/collectionspace/application/commit/7e97d939e8d3ad7ed72762f71eb0b97a57158dd8

On Tue, Mar 10, 2015 at 7:15 AM, John Torgersen jtorg@umich.edu wrote:

Hi Aron,

Thank you for the suggestion. We will definitely try that the next time.

As it turns out, Ryan continued on the manual installation route and sent
me the following:

"[...] updated some XML files where it was trying to to access
http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
and I made it access libs-release instead of lib-snapshot [...]."

which allowed him to finish the install, and we now have it working on our
development server.

Thank you again for your help,
John

On 3/5/2015 1:52 PM, Aron Roberts wrote:

Thanks for this problem report, Ryan and John!

The first thing I'm seeing in the output is this:

Error assembling WAR: /tmp/collectionspace.war is read-only

Could this be a filesystem permissions issue? I've run into that once or
twice when that file was created by root (or some other system user running
as root via 'sudo'), and I was building CollectionSpace's Application layer
as a different (non-privileged) system user.

For starters, you might a) try deleting that file and b) making sure
that the Puppet-based install is run via 'sudo'. Let us know how that goes?

Aron

On Thu, Mar 5, 2015 at 10:42 AM, Megan Forbes megan.forbes@lyrasis.org
wrote:

Talk listers,

Please see the below query from John Torgersen and Ryan Bankston at U
Michigan, who are having a few issues with the automated installer.

Thanks,
Megan

Megan Forbes
CollectionSpace Community Outreach and Support Manager
megan.forbes@lyrasis.org megan.forbes@lyrasis.org
800.999.8558 x 2917 <800.999.8558%20x%202917> Main
917.267.9676 Cell
meganbforbes Skype


From: John Torgersen jtorg@umich.edu
Sent: Tuesday, March 3, 2015 5:04 PM
To: info@collectionspace.org
Subject: Fwd: Failure with automated script

Hello,

We're trying to install a demo version of CollectionSpace, and the sys
admin doing the install has reported the below issues with trying to
install via the script and manually.

Any advice would be much appreciated.

Thank you,
John Torgersen
Database Administrator
University of Michigan
College of Literature, Science & Arts IT Infrastructure

-------- Forwarded Message --------  Subject: Failure with automated
script  Date: Tue, 3 Mar 2015 14:26:27 -0500  From: Ryan Bankston
rbanksto@umich.edu rbanksto@umich.edu  To: John Torgersen
jtorg@umich.edu jtorg@umich.edu

The idea of writing a puppet script to automatically install/configure
the system is actually pretty awesome (
http://wiki.collectionspace.org/display/UNRELEASED/Automated+installer+for+CollectionSpace+4.1).
It can do all of the postgres setup and everything the system needs.
Unfortunately it keeps failing at the same spot, and I don't know enough
puppet to try to fix it:

Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from
Application layer source]/returns: [INFO] Root
.............................................. SUCCESS [1.240s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] CSP: General Utils
................................ SUCCESS [5.898s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] Collection-Space CSP API
.......................... SUCCESS [1.335s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] CSP: Impl
......................................... SUCCESS [3.148s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] Collection-Space CSP Helper
....................... SUCCESS [1.224s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] CSP: Schema
....................................... SUCCESS [3.372s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] JXUtils
........................................... SUCCESS [1.046s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] CSP: Web UI
....................................... SUCCESS [6.411s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] CSP: File
......................................... SUCCESS [0.652s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] CSP: Services
..................................... SUCCESS [3.727s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] CSP: Installation
................................. SUCCESS [1.231s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] tomcat-main
....................................... SUCCESS [6.717s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] war-entry
......................................... FAILURE [3.553s]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO]

Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] BUILD FAILURE
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO]

Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] Total time: 40.285s
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] Finished at: Tue Mar 03 13:24:14 EST 2015
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO] Final Memory: 29M/81M
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [INFO]

Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR] Failed to execute goal
org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on
project war-entry: Error assembling WAR: /tmp/collectionspace.war is
read-only. -> [Help 1]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR] To see the full stack trace of the errors,
re-run Maven with the -e switch.
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR] Re-run Maven using the -X switch to enable
full debug logging.
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR] For more information about the errors and
possible solutions, please read the following articles:
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR]
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR] After correcting the problems, you can
resume the build with the command
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: [ERROR]  mvn <goals> -rf :war-entry
Error: mvn clean install -DskipTests returned 1 instead of one of [0]
Error: /Stage[main]/Cspace_source/Exec[Build and deploy from Application
layer source]/returns: change from notrun to 0 failed: mvn clean install
-DskipTests returned 1 instead of one of [0]
Notice: /Stage[main]/Cspace_source/Notify[Building UI layer]: Dependency
Exec[Build and deploy from Application layer source] has failures: true
Warning: /Stage[main]/Cspace_source/Notify[Building UI layer]: Skipping
because of failed dependencies
Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from UI layer
source]: Dependency Exec[Build and deploy from Application layer source]
has failures: true
Warning: /Stage[main]/Cspace_source/Exec[Build and deploy from UI layer
source]: Skipping because of failed dependencies
Notice: /Stage[main]/Cspace_source/Notify[Deploying Services layer]:
Dependency Exec[Build and deploy from Application layer source] has
failures: true
Warning: /Stage[main]/Cspace_source/Notify[Deploying Services layer]:
Skipping because of failed dependencies
Notice: /Stage[main]/Cspace_source/Exec[Deploy from Services layer
source]: Dependency Exec[Build and deploy from Application layer source]
has failures: true
Warning: /Stage[main]/Cspace_source/Exec[Deploy from Services layer
source]: Skipping because of failed dependencies
Notice: /Stage[main]/Cspace_source/Notify[Creating databases]: Dependency
Exec[Build and deploy from Application layer source] has failures: true
Warning: /Stage[main]/Cspace_source/Notify[Creating databases]: Skipping
because of failed dependencies
Notice: /Stage[main]/Cspace_source/Exec[Create databases from Services
layer source]: Dependency Exec[Build and deploy from Application layer
source] has failures: true
Warning: /Stage[main]/Cspace_source/Exec[Create databases from Services
layer source]: Skipping because of failed dependencies
Notice: /Stage[main]/Cspace_source/Notify[Initializing default user
accounts]: Dependency Exec[Build and deploy from Application layer source]
has failures: true
Warning: /Stage[main]/Cspace_source/Notify[Initializing default user
accounts]: Skipping because of failed dependencies
Notice: /Stage[main]/Cspace_source/Exec[Initialize default user accounts
from Services layer source]: Dependency Exec[Build and deploy from
Application layer source] has failures: true
Warning: /Stage[main]/Cspace_source/Exec[Initialize default user accounts
from Services layer source]: Skipping because of failed dependencies
Notice: Finished catalog run in 740.24 seconds

Running through the manually install always fails here:
[INFO]

[INFO] Reactor Summary:
[INFO]
[INFO] Root .............................................. SUCCESS
[0.821s]
[INFO] CSP: General Utils ................................ SUCCESS
[3.952s]
[INFO] Collection-Space CSP API .......................... SUCCESS
[0.884s]
[INFO] CSP: Impl ......................................... SUCCESS
[2.403s]
[INFO] Collection-Space CSP Helper ....................... SUCCESS
[0.905s]
[INFO] CSP: Schema ....................................... SUCCESS
[2.321s]
[INFO] JXUtils ........................................... SUCCESS
[0.721s]
[INFO] CSP: Web UI ....................................... FAILURE
[0.107s]
[INFO] CSP: File ......................................... SKIPPED
[INFO] CSP: Services ..................................... SKIPPED
[INFO] CSP: Installation ................................. SKIPPED
[INFO] tomcat-main ....................................... SKIPPED
[INFO] war-entry ......................................... SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 12.627s
[INFO] Finished at: Tue Mar 03 10:14:23 EST 2015
[INFO] Final Memory: 21M/57M
[INFO]

[ERROR] Failed to execute goal on project cspi-webui: Could not resolve
dependencies for project org.collectionspace:cspi-webui:jar:4.1.1: Failure
to find
org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1
in
http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
was cached in the local repository, resolution will not be reattempted
until the update interval of libs-snapshot-local has elapsed or updates are
forced -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal on project cspi-webui: Could not resolve dependencies for project
org.collectionspace:cspi-webui:jar:4.1.1: Failure to find
org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1
in
http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
was cached in the local repository, resolution will not be reattempted
until the update interval of libs-snapshot-local has elapsed or updates are
forced

I think the relevant error is:
Failure to find
org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1
in
http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
was cached in the local repository, resolution will not be reattempted
until the update interval of libs-snapshot-local has elapsed or updates are
forced

But i'm not sure how to fix it.

Ryan Bankston
Sr. Systems Administrator
University of Michigan
LSA IT Infrastructure
rbanksto@umich.edu


Talk mailing list
Talk@lists.collectionspace.org

http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Hi John and Ryan, It's great to hear from another university looking at CollectionSpace! Could you say a little bit about what you're trying to accomplish with your installation? I'm happy to talk off-list but I suspect others would be interested in hearing more. Thanks, Chris On Mar 12, 2015, at 10:41 AM, John Torgersen <jtorg@umich.edu> wrote: Hi Aron, Ryan let me know that he made the same change as Brian Franzone to get the manual install to work. Thanks again, John On 3/10/2015 11:35 AM, Aron Roberts wrote: That's great to hear, John! Thanks much for passing along this report from Ryan, as well. We had a report on February 17, from Brian Franzone of the Harvard University Herbaria, that they needed to make the following change to complete an installation of v4.1. (I don't know whether they were doing a manual or automated install.) Was this the change - or among the changes - that Ryan made? (He mentioned "some files".) Change info in application/pom.xml file <!-- remove <repository> <id>libs-snapshot-local</id> <name>libs-snapshot-local</name> <url> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local </url> <snapshots> <enabled>true</enabled> </snapshots> </repository> --> <!--add --> <repository> <id>libs-snapshot-local</id> <name>libs-snapshot-local</name> <url> http://nightly.collectionspace.org:8081/artifactory/libs-release-local</url> <snapshots> <enabled>false</enabled> </snapshots> </repository> I haven't seen this issue crop up, in my own tests of the automated installer on a fresh Ubuntu 14.04.01 VM, but haven't looked into it ... Aron P.S. Within that application/pom.xml file, in the v4.1.1 tagged release, there was only a reference to the 'libs-snapshot-local' repo, but not to 'libs-releases-local'. I've observed that the 'lib-releases-local' repo was added, alongisde 'libs-snapshot-local', in this commit in (v4.2) master after v.4.1.1's release. https://github.com/collectionspace/application/commit/7e97d939e8d3ad7ed72762f71eb0b97a57158dd8 On Tue, Mar 10, 2015 at 7:15 AM, John Torgersen <jtorg@umich.edu> wrote: > Hi Aron, > > Thank you for the suggestion. We will definitely try that the next time. > > As it turns out, Ryan continued on the manual installation route and sent > me the following: > > "[...] updated some XML files where it was trying to to access > http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local > and I made it access libs-release instead of lib-snapshot [...]." > > which allowed him to finish the install, and we now have it working on our > development server. > > Thank you again for your help, > John > > > On 3/5/2015 1:52 PM, Aron Roberts wrote: > > Thanks for this problem report, Ryan and John! > > The first thing I'm seeing in the output is this: > > > Error assembling WAR: /tmp/collectionspace.war is read-only > > Could this be a filesystem permissions issue? I've run into that once or > twice when that file was created by root (or some other system user running > as root via 'sudo'), and I was building CollectionSpace's Application layer > as a different (non-privileged) system user. > > For starters, you might a) try deleting that file and b) making sure > that the Puppet-based install is run via 'sudo'. Let us know how that goes? > > Aron > > On Thu, Mar 5, 2015 at 10:42 AM, Megan Forbes <megan.forbes@lyrasis.org> > wrote: > >> Talk listers, >> >> >> Please see the below query from John Torgersen and Ryan Bankston at U >> Michigan, who are having a few issues with the automated installer. >> >> >> Thanks, >> Megan >> >> >> Megan Forbes >> CollectionSpace Community Outreach and Support Manager >> *megan.forbes@lyrasis.org <megan.forbes@lyrasis.org>* >> 800.999.8558 x 2917 <800.999.8558%20x%202917> Main >> 917.267.9676 Cell >> meganbforbes Skype >> >> >> ------------------------------ >> *From:* John Torgersen <jtorg@umich.edu> >> *Sent:* Tuesday, March 3, 2015 5:04 PM >> *To:* info@collectionspace.org >> *Subject:* Fwd: Failure with automated script >> >> Hello, >> >> We're trying to install a demo version of CollectionSpace, and the sys >> admin doing the install has reported the below issues with trying to >> install via the script and manually. >> >> Any advice would be much appreciated. >> >> Thank you, >> John Torgersen >> Database Administrator >> University of Michigan >> College of Literature, Science & Arts IT Infrastructure >> >> >> -------- Forwarded Message -------- Subject: Failure with automated >> script Date: Tue, 3 Mar 2015 14:26:27 -0500 From: Ryan Bankston >> <rbanksto@umich.edu> <rbanksto@umich.edu> To: John Torgersen >> <jtorg@umich.edu> <jtorg@umich.edu> >> >> The idea of writing a puppet script to automatically install/configure >> the system is actually pretty awesome ( >> http://wiki.collectionspace.org/display/UNRELEASED/Automated+installer+for+CollectionSpace+4.1). >> It can do all of the postgres setup and everything the system needs. >> Unfortunately it keeps failing at the same spot, and I don't know enough >> puppet to try to fix it: >> >> >> >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from >> Application layer source]/returns: [INFO] Root >> .............................................. SUCCESS [1.240s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] CSP: General Utils >> ................................ SUCCESS [5.898s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] Collection-Space CSP API >> .......................... SUCCESS [1.335s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] CSP: Impl >> ......................................... SUCCESS [3.148s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] Collection-Space CSP Helper >> ....................... SUCCESS [1.224s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] CSP: Schema >> ....................................... SUCCESS [3.372s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] JXUtils >> ........................................... SUCCESS [1.046s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] CSP: Web UI >> ....................................... SUCCESS [6.411s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] CSP: File >> ......................................... SUCCESS [0.652s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] CSP: Services >> ..................................... SUCCESS [3.727s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] CSP: Installation >> ................................. SUCCESS [1.231s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] tomcat-main >> ....................................... SUCCESS [6.717s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] war-entry >> ......................................... FAILURE [3.553s] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] >> ------------------------------------------------------------------------ >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] BUILD FAILURE >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] >> ------------------------------------------------------------------------ >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] Total time: 40.285s >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] Finished at: Tue Mar 03 13:24:14 EST 2015 >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] Final Memory: 29M/81M >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [INFO] >> ------------------------------------------------------------------------ >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] Failed to execute goal >> org.apache.maven.plugins:maven-war-plugin:2.1.1:war (default-war) on >> project war-entry: Error assembling WAR: /tmp/collectionspace.war is >> read-only. -> [Help 1] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] To see the full stack trace of the errors, >> re-run Maven with the -e switch. >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] Re-run Maven using the -X switch to enable >> full debug logging. >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] For more information about the errors and >> possible solutions, please read the following articles: >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] [Help 1] >> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] After correcting the problems, you can >> resume the build with the command >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: [ERROR] mvn <goals> -rf :war-entry >> Error: mvn clean install -DskipTests returned 1 instead of one of [0] >> Error: /Stage[main]/Cspace_source/Exec[Build and deploy from Application >> layer source]/returns: change from notrun to 0 failed: mvn clean install >> -DskipTests returned 1 instead of one of [0] >> Notice: /Stage[main]/Cspace_source/Notify[Building UI layer]: Dependency >> Exec[Build and deploy from Application layer source] has failures: true >> Warning: /Stage[main]/Cspace_source/Notify[Building UI layer]: Skipping >> because of failed dependencies >> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy from UI layer >> source]: Dependency Exec[Build and deploy from Application layer source] >> has failures: true >> Warning: /Stage[main]/Cspace_source/Exec[Build and deploy from UI layer >> source]: Skipping because of failed dependencies >> Notice: /Stage[main]/Cspace_source/Notify[Deploying Services layer]: >> Dependency Exec[Build and deploy from Application layer source] has >> failures: true >> Warning: /Stage[main]/Cspace_source/Notify[Deploying Services layer]: >> Skipping because of failed dependencies >> Notice: /Stage[main]/Cspace_source/Exec[Deploy from Services layer >> source]: Dependency Exec[Build and deploy from Application layer source] >> has failures: true >> Warning: /Stage[main]/Cspace_source/Exec[Deploy from Services layer >> source]: Skipping because of failed dependencies >> Notice: /Stage[main]/Cspace_source/Notify[Creating databases]: Dependency >> Exec[Build and deploy from Application layer source] has failures: true >> Warning: /Stage[main]/Cspace_source/Notify[Creating databases]: Skipping >> because of failed dependencies >> Notice: /Stage[main]/Cspace_source/Exec[Create databases from Services >> layer source]: Dependency Exec[Build and deploy from Application layer >> source] has failures: true >> Warning: /Stage[main]/Cspace_source/Exec[Create databases from Services >> layer source]: Skipping because of failed dependencies >> Notice: /Stage[main]/Cspace_source/Notify[Initializing default user >> accounts]: Dependency Exec[Build and deploy from Application layer source] >> has failures: true >> Warning: /Stage[main]/Cspace_source/Notify[Initializing default user >> accounts]: Skipping because of failed dependencies >> Notice: /Stage[main]/Cspace_source/Exec[Initialize default user accounts >> from Services layer source]: Dependency Exec[Build and deploy from >> Application layer source] has failures: true >> Warning: /Stage[main]/Cspace_source/Exec[Initialize default user accounts >> from Services layer source]: Skipping because of failed dependencies >> Notice: Finished catalog run in 740.24 seconds >> >> >> >> Running through the manually install always fails here: >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Reactor Summary: >> [INFO] >> [INFO] Root .............................................. SUCCESS >> [0.821s] >> [INFO] CSP: General Utils ................................ SUCCESS >> [3.952s] >> [INFO] Collection-Space CSP API .......................... SUCCESS >> [0.884s] >> [INFO] CSP: Impl ......................................... SUCCESS >> [2.403s] >> [INFO] Collection-Space CSP Helper ....................... SUCCESS >> [0.905s] >> [INFO] CSP: Schema ....................................... SUCCESS >> [2.321s] >> [INFO] JXUtils ........................................... SUCCESS >> [0.721s] >> [INFO] CSP: Web UI ....................................... FAILURE >> [0.107s] >> [INFO] CSP: File ......................................... SKIPPED >> [INFO] CSP: Services ..................................... SKIPPED >> [INFO] CSP: Installation ................................. SKIPPED >> [INFO] tomcat-main ....................................... SKIPPED >> [INFO] war-entry ......................................... SKIPPED >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] BUILD FAILURE >> [INFO] >> ------------------------------------------------------------------------ >> [INFO] Total time: 12.627s >> [INFO] Finished at: Tue Mar 03 10:14:23 EST 2015 >> [INFO] Final Memory: 21M/57M >> [INFO] >> ------------------------------------------------------------------------ >> [ERROR] Failed to execute goal on project cspi-webui: Could not resolve >> dependencies for project org.collectionspace:cspi-webui:jar:4.1.1: Failure >> to find >> org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1 >> in >> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local >> was cached in the local repository, resolution will not be reattempted >> until the update interval of libs-snapshot-local has elapsed or updates are >> forced -> [Help 1] >> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> goal on project cspi-webui: Could not resolve dependencies for project >> org.collectionspace:cspi-webui:jar:4.1.1: Failure to find >> org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1 >> in >> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local >> was cached in the local repository, resolution will not be reattempted >> until the update interval of libs-snapshot-local has elapsed or updates are >> forced >> >> I think the relevant error is: >> Failure to find >> org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1 >> in >> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local >> was cached in the local repository, resolution will not be reattempted >> until the update interval of libs-snapshot-local has elapsed or updates are >> forced >> >> But i'm not sure how to fix it. >> >> Ryan Bankston >> Sr. Systems Administrator >> University of Michigan >> LSA IT Infrastructure >> rbanksto@umich.edu >> >> >> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org >> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >> >> > > _______________________________________________ Talk mailing list Talk@lists.collectionspace.org http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
JT
John Torgersen
Thu, Mar 12, 2015 6:37 PM

Hi Chris,

We're setting up a test version in our environment, so that it can be
evaluated by a couple of our archaeologically-based museums.

  • John

On 3/12/2015 2:33 PM, Christopher R. HOFFMAN wrote:

Hi John and Ryan,
It's great to hear from another university looking at
CollectionSpace!  Could you say a little bit about what you're trying
to accomplish with your installation?  I'm happy to talk off-list but
I suspect others would be interested in hearing more.

Thanks,
Chris

On Mar 12, 2015, at 10:41 AM, John Torgersen <jtorg@umich.edu
mailto:jtorg@umich.edu> wrote:

Hi Aron,

Ryan let me know that he made the same change as Brian Franzone to
get the manual install to work.

Thanks again,
John

On 3/10/2015 11:35 AM, Aron Roberts wrote:

That's great to hear, John! Thanks much for passing along this
report from Ryan, as well.

We had a report on February 17, from Brian Franzone of the Harvard
University Herbaria, that they needed to make the following change
to complete an installation of v4.1. (I don't know whether they were
doing a manual or automated install.) Was this the change - or among
the changes - that Ryan made? (He mentioned "some files".)

Change info in application/pom.xml file

<!-- remove <repository> <id>libs-snapshot-local</id> <name>libs-snapshot-local</name> <url> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local</url> <snapshots> <enabled>true</enabled> </snapshots> </repository> --> <!--add --> <repository> <id>libs-snapshot-local</id> <name>libs-snapshot-local</name> <url> http://nightly.collectionspace.org:8081/artifactory/libs-release-local</url> <snapshots> <enabled>false</enabled> </snapshots> </repository>

I haven't seen this issue crop up, in my own tests of the automated
installer on a fresh Ubuntu 14.04.01 VM, but haven't looked into it ...

Aron

P.S. Within that application/pom.xml file, in the v4.1.1 tagged
release, there was only a reference to the 'libs-snapshot-local'
repo, but not to 'libs-releases-local'. I've observed that the
'lib-releases-local' repo was added, alongisde
'libs-snapshot-local', in this commit in (v4.2) master after
v.4.1.1's release.

https://github.com/collectionspace/application/commit/7e97d939e8d3ad7ed72762f71eb0b97a57158dd8

On Tue, Mar 10, 2015 at 7:15 AM, John Torgersen <jtorg@umich.edu
mailto:jtorg@umich.edu> wrote:

 Hi Aron,

 Thank you for the suggestion. We will definitely try that the
 next time.

 As it turns out, Ryan continued on the manual installation route
 and sent me the following:

 "[...] updated some XML files where it was trying to to access
 http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
 and I made it access libs-release instead of lib-snapshot [...]."

 which allowed him to finish the install, and we now have it
 working on our development server.

 Thank you again for your help,
 John


 On 3/5/2015 1:52 PM, Aron Roberts wrote:
 Thanks for this problem report, Ryan and John!

 The first thing I'm seeing in the output is this:

Error assembling WAR: /tmp/collectionspace.war is read-only

 Could this be a filesystem permissions issue? I've run into
 that once or twice when that file was created by root (or some
 other system user running as root via 'sudo'), and I was
 building CollectionSpace's Application layer as a different
 (non-privileged) system user.

 For starters, you might a) try deleting that file and b) making
 sure that the Puppet-based install is run via 'sudo'. Let us
 know how that goes?

 Aron

 On Thu, Mar 5, 2015 at 10:42 AM, Megan Forbes
 <megan.forbes@lyrasis.org <mailto:megan.forbes@lyrasis.org>> wrote:

     Talk listers,


     Please see the below query from John Torgersen and Ryan
     Bankston at U Michigan, who are having a few issues with
     the automated installer.


     Thanks,
     Megan


     Megan Forbes
     CollectionSpace Community Outreach and Support Manager
     _megan.forbes@lyrasis.org <mailto:megan.forbes@lyrasis.org>_
     800.999.8558 x 2917 <tel:800.999.8558%20x%202917> Main
     917.267.9676 <tel:917.267.9676> Cell
     meganbforbes Skype

     ------------------------------------------------------------------------
     *From:* John Torgersen <jtorg@umich.edu
     <mailto:jtorg@umich.edu>>
     *Sent:* Tuesday, March 3, 2015 5:04 PM
     *To:* info@collectionspace.org
     <mailto:info@collectionspace.org>
     *Subject:* Fwd: Failure with automated script
     Hello,

     We're trying to install a demo version of CollectionSpace,
     and the sys admin doing the install has reported the below
     issues with trying to install via the script and manually.

     Any advice would be much appreciated.

     Thank you,
     John Torgersen
     Database Administrator
     University of Michigan
     College of Literature, Science & Arts IT Infrastructure


     -------- Forwarded Message --------
     Subject: 	Failure with automated script
     Date: 	Tue, 3 Mar 2015 14:26:27 -0500
     From: 	Ryan Bankston <rbanksto@umich.edu>
     <mailto:rbanksto@umich.edu>
     To: 	John Torgersen <jtorg@umich.edu> <mailto:jtorg@umich.edu>



     The idea of writing a puppet script to automatically
     install/configure the system is actually pretty awesome
     (http://wiki.collectionspace.org/display/UNRELEASED/Automated+installer+for+CollectionSpace+4.1).
     It can do all of the postgres setup and everything the
     system needs.  Unfortunately it keeps failing at the same
     spot, and I don't know enough puppet to try to fix it:



     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] Root
     .............................................. SUCCESS [1.240s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] CSP: General
     Utils ................................ SUCCESS [5.898s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO]
     Collection-Space CSP API .......................... SUCCESS
     [1.335s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] CSP: Impl
     ......................................... SUCCESS [3.148s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO]
     Collection-Space CSP Helper ....................... SUCCESS
     [1.224s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] CSP: Schema
     ....................................... SUCCESS [3.372s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] JXUtils
     ........................................... SUCCESS [1.046s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] CSP: Web UI
     ....................................... SUCCESS [6.411s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] CSP: File
     ......................................... SUCCESS [0.652s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] CSP:
     Services ..................................... SUCCESS [3.727s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] CSP:
     Installation ................................. SUCCESS [1.231s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] tomcat-main
     ....................................... SUCCESS [6.717s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] war-entry
     ......................................... FAILURE [3.553s]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO]
     ------------------------------------------------------------------------
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] BUILD FAILURE
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO]
     ------------------------------------------------------------------------
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] Total time:
     40.285s
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] Finished at:
     Tue Mar 03 13:24:14 EST 2015
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO] Final
     Memory: 29M/81M
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [INFO]
     ------------------------------------------------------------------------
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR] Failed to
     execute goal
     org.apache.maven.plugins:maven-war-plugin:2.1.1:war
     (default-war) on project war-entry: Error assembling WAR:
     /tmp/collectionspace.war is read-only. -> [Help 1]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR] To see the
     full stack trace of the errors, re-run Maven with the -e
     switch.
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR] Re-run
     Maven using the -X switch to enable full debug logging.
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR] For more
     information about the errors and possible solutions, please
     read the following articles:
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR] [Help 1]
     http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR]
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR] After
     correcting the problems, you can resume the build with the
     command
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: [ERROR]   mvn
     <goals> -rf :war-entry
     Error: mvn clean install -DskipTests returned 1 instead of
     one of [0]
     Error: /Stage[main]/Cspace_source/Exec[Build and deploy
     from Application layer source]/returns: change from notrun
     to 0 failed: mvn clean install -DskipTests returned 1
     instead of one of [0]
     Notice: /Stage[main]/Cspace_source/Notify[Building UI
     layer]: Dependency Exec[Build and deploy from Application
     layer source] has failures: true
     Warning: /Stage[main]/Cspace_source/Notify[Building UI
     layer]: Skipping because of failed dependencies
     Notice: /Stage[main]/Cspace_source/Exec[Build and deploy
     from UI layer source]: Dependency Exec[Build and deploy
     from Application layer source] has failures: true
     Warning: /Stage[main]/Cspace_source/Exec[Build and deploy
     from UI layer source]: Skipping because of failed dependencies
     Notice: /Stage[main]/Cspace_source/Notify[Deploying
     Services layer]: Dependency Exec[Build and deploy from
     Application layer source] has failures: true
     Warning: /Stage[main]/Cspace_source/Notify[Deploying
     Services layer]: Skipping because of failed dependencies
     Notice: /Stage[main]/Cspace_source/Exec[Deploy from
     Services layer source]: Dependency Exec[Build and deploy
     from Application layer source] has failures: true
     Warning: /Stage[main]/Cspace_source/Exec[Deploy from
     Services layer source]: Skipping because of failed dependencies
     Notice: /Stage[main]/Cspace_source/Notify[Creating
     databases]: Dependency Exec[Build and deploy from
     Application layer source] has failures: true
     Warning: /Stage[main]/Cspace_source/Notify[Creating
     databases]: Skipping because of failed dependencies
     Notice: /Stage[main]/Cspace_source/Exec[Create databases
     from Services layer source]: Dependency Exec[Build and
     deploy from Application layer source] has failures: true
     Warning: /Stage[main]/Cspace_source/Exec[Create databases
     from Services layer source]: Skipping because of failed
     dependencies
     Notice: /Stage[main]/Cspace_source/Notify[Initializing
     default user accounts]: Dependency Exec[Build and deploy
     from Application layer source] has failures: true
     Warning: /Stage[main]/Cspace_source/Notify[Initializing
     default user accounts]: Skipping because of failed dependencies
     Notice: /Stage[main]/Cspace_source/Exec[Initialize default
     user accounts from Services layer source]: Dependency
     Exec[Build and deploy from Application layer source] has
     failures: true
     Warning: /Stage[main]/Cspace_source/Exec[Initialize default
     user accounts from Services layer source]: Skipping because
     of failed dependencies
     Notice: Finished catalog run in 740.24 seconds



     Running through the manually install always fails here:
     [INFO]
     ------------------------------------------------------------------------
     [INFO] Reactor Summary:
     [INFO]
     [INFO] Root ..............................................
     SUCCESS [0.821s]
     [INFO] CSP: General Utils ................................
     SUCCESS [3.952s]
     [INFO] Collection-Space CSP API ..........................
     SUCCESS [0.884s]
     [INFO] CSP: Impl .........................................
     SUCCESS [2.403s]
     [INFO] Collection-Space CSP Helper .......................
     SUCCESS [0.905s]
     [INFO] CSP: Schema .......................................
     SUCCESS [2.321s]
     [INFO] JXUtils ...........................................
     SUCCESS [0.721s]
     [INFO] CSP: Web UI .......................................
     FAILURE [0.107s]
     [INFO] CSP: File .........................................
     SKIPPED
     [INFO] CSP: Services .....................................
     SKIPPED
     [INFO] CSP: Installation .................................
     SKIPPED
     [INFO] tomcat-main .......................................
     SKIPPED
     [INFO] war-entry .........................................
     SKIPPED
     [INFO]
     ------------------------------------------------------------------------
     [INFO] BUILD FAILURE
     [INFO]
     ------------------------------------------------------------------------
     [INFO] Total time: 12.627s
     [INFO] Finished at: Tue Mar 03 10:14:23 EST 2015
     [INFO] Final Memory: 21M/57M
     [INFO]
     ------------------------------------------------------------------------
     [ERROR] Failed to execute goal on project cspi-webui: Could
     not resolve dependencies for project
     org.collectionspace:cspi-webui:jar:4.1.1: Failure to find
     org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1
     in
     http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
     was cached in the local repository, resolution will not be
     reattempted until the update interval of
     libs-snapshot-local has elapsed or updates are forced ->
     [Help 1]
     org.apache.maven.lifecycle.LifecycleExecutionException:
     Failed to execute goal on project cspi-webui: Could not
     resolve dependencies for project
     org.collectionspace:cspi-webui:jar:4.1.1: Failure to find
     org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1
     in
     http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
     was cached in the local repository, resolution will not be
     reattempted until the update interval of
     libs-snapshot-local has elapsed or updates are forced

     I think the relevant error is:
     Failure to find
     org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1
     in
     http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local
     was cached in the local repository, resolution will not be
     reattempted until the update interval of
     libs-snapshot-local has elapsed or updates are forced

     But i'm not sure how to fix it.

     Ryan Bankston
     Sr. Systems Administrator
     University of Michigan
     LSA IT Infrastructure
     rbanksto@umich.edu <mailto:rbanksto@umich.edu>




     _______________________________________________
     Talk mailing list
     Talk@lists.collectionspace.org
     <mailto:Talk@lists.collectionspace.org>
     http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Chris, We're setting up a test version in our environment, so that it can be evaluated by a couple of our archaeologically-based museums. - John On 3/12/2015 2:33 PM, Christopher R. HOFFMAN wrote: > Hi John and Ryan, > It's great to hear from another university looking at > CollectionSpace! Could you say a little bit about what you're trying > to accomplish with your installation? I'm happy to talk off-list but > I suspect others would be interested in hearing more. > > Thanks, > Chris > > On Mar 12, 2015, at 10:41 AM, John Torgersen <jtorg@umich.edu > <mailto:jtorg@umich.edu>> wrote: > >> Hi Aron, >> >> Ryan let me know that he made the same change as Brian Franzone to >> get the manual install to work. >> >> Thanks again, >> John >> >> On 3/10/2015 11:35 AM, Aron Roberts wrote: >>> That's great to hear, John! Thanks much for passing along this >>> report from Ryan, as well. >>> >>> We had a report on February 17, from Brian Franzone of the Harvard >>> University Herbaria, that they needed to make the following change >>> to complete an installation of v4.1. (I don't know whether they were >>> doing a manual or automated install.) Was this the change - or among >>> the changes - that Ryan made? (He mentioned "some files".) >>> >>> Change info in application/pom.xml file >>> >>> <!-- remove >>> <repository> >>> <id>libs-snapshot-local</id> >>> <name>libs-snapshot-local</name> >>> <url> >>> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local</url> >>> <snapshots> >>> <enabled>true</enabled> >>> </snapshots> >>> </repository> --> >>> >>> <!--add --> >>> <repository> >>> <id>libs-snapshot-local</id> >>> <name>libs-snapshot-local</name> >>> <url> >>> http://nightly.collectionspace.org:8081/artifactory/libs-release-local</url> >>> <snapshots> >>> <enabled>false</enabled> >>> </snapshots> >>> </repository> >>> >>> I haven't seen this issue crop up, in my own tests of the automated >>> installer on a fresh Ubuntu 14.04.01 VM, but haven't looked into it ... >>> >>> Aron >>> >>> P.S. Within that application/pom.xml file, in the v4.1.1 tagged >>> release, there was only a reference to the 'libs-snapshot-local' >>> repo, but not to 'libs-releases-local'. I've observed that the >>> 'lib-releases-local' repo was added, alongisde >>> 'libs-snapshot-local', in this commit in (v4.2) master after >>> v.4.1.1's release. >>> >>> https://github.com/collectionspace/application/commit/7e97d939e8d3ad7ed72762f71eb0b97a57158dd8 >>> >>> On Tue, Mar 10, 2015 at 7:15 AM, John Torgersen <jtorg@umich.edu >>> <mailto:jtorg@umich.edu>> wrote: >>> >>> Hi Aron, >>> >>> Thank you for the suggestion. We will definitely try that the >>> next time. >>> >>> As it turns out, Ryan continued on the manual installation route >>> and sent me the following: >>> >>> "[...] updated some XML files where it was trying to to access >>> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local >>> and I made it access libs-release instead of lib-snapshot [...]." >>> >>> which allowed him to finish the install, and we now have it >>> working on our development server. >>> >>> Thank you again for your help, >>> John >>> >>> >>> On 3/5/2015 1:52 PM, Aron Roberts wrote: >>>> Thanks for this problem report, Ryan and John! >>>> >>>> The first thing I'm seeing in the output is this: >>>> >>>> > Error assembling WAR: /tmp/collectionspace.war is read-only >>>> >>>> Could this be a filesystem permissions issue? I've run into >>>> that once or twice when that file was created by root (or some >>>> other system user running as root via 'sudo'), and I was >>>> building CollectionSpace's Application layer as a different >>>> (non-privileged) system user. >>>> >>>> For starters, you might a) try deleting that file and b) making >>>> sure that the Puppet-based install is run via 'sudo'. Let us >>>> know how that goes? >>>> >>>> Aron >>>> >>>> On Thu, Mar 5, 2015 at 10:42 AM, Megan Forbes >>>> <megan.forbes@lyrasis.org <mailto:megan.forbes@lyrasis.org>> wrote: >>>> >>>> Talk listers, >>>> >>>> >>>> Please see the below query from John Torgersen and Ryan >>>> Bankston at U Michigan, who are having a few issues with >>>> the automated installer. >>>> >>>> >>>> Thanks, >>>> Megan >>>> >>>> >>>> Megan Forbes >>>> CollectionSpace Community Outreach and Support Manager >>>> _megan.forbes@lyrasis.org <mailto:megan.forbes@lyrasis.org>_ >>>> 800.999.8558 x 2917 <tel:800.999.8558%20x%202917> Main >>>> 917.267.9676 <tel:917.267.9676> Cell >>>> meganbforbes Skype >>>> >>>> ------------------------------------------------------------------------ >>>> *From:* John Torgersen <jtorg@umich.edu >>>> <mailto:jtorg@umich.edu>> >>>> *Sent:* Tuesday, March 3, 2015 5:04 PM >>>> *To:* info@collectionspace.org >>>> <mailto:info@collectionspace.org> >>>> *Subject:* Fwd: Failure with automated script >>>> Hello, >>>> >>>> We're trying to install a demo version of CollectionSpace, >>>> and the sys admin doing the install has reported the below >>>> issues with trying to install via the script and manually. >>>> >>>> Any advice would be much appreciated. >>>> >>>> Thank you, >>>> John Torgersen >>>> Database Administrator >>>> University of Michigan >>>> College of Literature, Science & Arts IT Infrastructure >>>> >>>> >>>> -------- Forwarded Message -------- >>>> Subject: Failure with automated script >>>> Date: Tue, 3 Mar 2015 14:26:27 -0500 >>>> From: Ryan Bankston <rbanksto@umich.edu> >>>> <mailto:rbanksto@umich.edu> >>>> To: John Torgersen <jtorg@umich.edu> <mailto:jtorg@umich.edu> >>>> >>>> >>>> >>>> The idea of writing a puppet script to automatically >>>> install/configure the system is actually pretty awesome >>>> (http://wiki.collectionspace.org/display/UNRELEASED/Automated+installer+for+CollectionSpace+4.1). >>>> It can do all of the postgres setup and everything the >>>> system needs. Unfortunately it keeps failing at the same >>>> spot, and I don't know enough puppet to try to fix it: >>>> >>>> >>>> >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] Root >>>> .............................................. SUCCESS [1.240s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] CSP: General >>>> Utils ................................ SUCCESS [5.898s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] >>>> Collection-Space CSP API .......................... SUCCESS >>>> [1.335s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] CSP: Impl >>>> ......................................... SUCCESS [3.148s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] >>>> Collection-Space CSP Helper ....................... SUCCESS >>>> [1.224s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] CSP: Schema >>>> ....................................... SUCCESS [3.372s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] JXUtils >>>> ........................................... SUCCESS [1.046s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] CSP: Web UI >>>> ....................................... SUCCESS [6.411s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] CSP: File >>>> ......................................... SUCCESS [0.652s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] CSP: >>>> Services ..................................... SUCCESS [3.727s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] CSP: >>>> Installation ................................. SUCCESS [1.231s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] tomcat-main >>>> ....................................... SUCCESS [6.717s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] war-entry >>>> ......................................... FAILURE [3.553s] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] >>>> ------------------------------------------------------------------------ >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] BUILD FAILURE >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] >>>> ------------------------------------------------------------------------ >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] Total time: >>>> 40.285s >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] Finished at: >>>> Tue Mar 03 13:24:14 EST 2015 >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] Final >>>> Memory: 29M/81M >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [INFO] >>>> ------------------------------------------------------------------------ >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] Failed to >>>> execute goal >>>> org.apache.maven.plugins:maven-war-plugin:2.1.1:war >>>> (default-war) on project war-entry: Error assembling WAR: >>>> /tmp/collectionspace.war is read-only. -> [Help 1] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] To see the >>>> full stack trace of the errors, re-run Maven with the -e >>>> switch. >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] Re-run >>>> Maven using the -X switch to enable full debug logging. >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] For more >>>> information about the errors and possible solutions, please >>>> read the following articles: >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] [Help 1] >>>> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] After >>>> correcting the problems, you can resume the build with the >>>> command >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: [ERROR] mvn >>>> <goals> -rf :war-entry >>>> Error: mvn clean install -DskipTests returned 1 instead of >>>> one of [0] >>>> Error: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from Application layer source]/returns: change from notrun >>>> to 0 failed: mvn clean install -DskipTests returned 1 >>>> instead of one of [0] >>>> Notice: /Stage[main]/Cspace_source/Notify[Building UI >>>> layer]: Dependency Exec[Build and deploy from Application >>>> layer source] has failures: true >>>> Warning: /Stage[main]/Cspace_source/Notify[Building UI >>>> layer]: Skipping because of failed dependencies >>>> Notice: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from UI layer source]: Dependency Exec[Build and deploy >>>> from Application layer source] has failures: true >>>> Warning: /Stage[main]/Cspace_source/Exec[Build and deploy >>>> from UI layer source]: Skipping because of failed dependencies >>>> Notice: /Stage[main]/Cspace_source/Notify[Deploying >>>> Services layer]: Dependency Exec[Build and deploy from >>>> Application layer source] has failures: true >>>> Warning: /Stage[main]/Cspace_source/Notify[Deploying >>>> Services layer]: Skipping because of failed dependencies >>>> Notice: /Stage[main]/Cspace_source/Exec[Deploy from >>>> Services layer source]: Dependency Exec[Build and deploy >>>> from Application layer source] has failures: true >>>> Warning: /Stage[main]/Cspace_source/Exec[Deploy from >>>> Services layer source]: Skipping because of failed dependencies >>>> Notice: /Stage[main]/Cspace_source/Notify[Creating >>>> databases]: Dependency Exec[Build and deploy from >>>> Application layer source] has failures: true >>>> Warning: /Stage[main]/Cspace_source/Notify[Creating >>>> databases]: Skipping because of failed dependencies >>>> Notice: /Stage[main]/Cspace_source/Exec[Create databases >>>> from Services layer source]: Dependency Exec[Build and >>>> deploy from Application layer source] has failures: true >>>> Warning: /Stage[main]/Cspace_source/Exec[Create databases >>>> from Services layer source]: Skipping because of failed >>>> dependencies >>>> Notice: /Stage[main]/Cspace_source/Notify[Initializing >>>> default user accounts]: Dependency Exec[Build and deploy >>>> from Application layer source] has failures: true >>>> Warning: /Stage[main]/Cspace_source/Notify[Initializing >>>> default user accounts]: Skipping because of failed dependencies >>>> Notice: /Stage[main]/Cspace_source/Exec[Initialize default >>>> user accounts from Services layer source]: Dependency >>>> Exec[Build and deploy from Application layer source] has >>>> failures: true >>>> Warning: /Stage[main]/Cspace_source/Exec[Initialize default >>>> user accounts from Services layer source]: Skipping because >>>> of failed dependencies >>>> Notice: Finished catalog run in 740.24 seconds >>>> >>>> >>>> >>>> Running through the manually install always fails here: >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Reactor Summary: >>>> [INFO] >>>> [INFO] Root .............................................. >>>> SUCCESS [0.821s] >>>> [INFO] CSP: General Utils ................................ >>>> SUCCESS [3.952s] >>>> [INFO] Collection-Space CSP API .......................... >>>> SUCCESS [0.884s] >>>> [INFO] CSP: Impl ......................................... >>>> SUCCESS [2.403s] >>>> [INFO] Collection-Space CSP Helper ....................... >>>> SUCCESS [0.905s] >>>> [INFO] CSP: Schema ....................................... >>>> SUCCESS [2.321s] >>>> [INFO] JXUtils ........................................... >>>> SUCCESS [0.721s] >>>> [INFO] CSP: Web UI ....................................... >>>> FAILURE [0.107s] >>>> [INFO] CSP: File ......................................... >>>> SKIPPED >>>> [INFO] CSP: Services ..................................... >>>> SKIPPED >>>> [INFO] CSP: Installation ................................. >>>> SKIPPED >>>> [INFO] tomcat-main ....................................... >>>> SKIPPED >>>> [INFO] war-entry ......................................... >>>> SKIPPED >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] BUILD FAILURE >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [INFO] Total time: 12.627s >>>> [INFO] Finished at: Tue Mar 03 10:14:23 EST 2015 >>>> [INFO] Final Memory: 21M/57M >>>> [INFO] >>>> ------------------------------------------------------------------------ >>>> [ERROR] Failed to execute goal on project cspi-webui: Could >>>> not resolve dependencies for project >>>> org.collectionspace:cspi-webui:jar:4.1.1: Failure to find >>>> org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1 >>>> in >>>> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local >>>> was cached in the local repository, resolution will not be >>>> reattempted until the update interval of >>>> libs-snapshot-local has elapsed or updates are forced -> >>>> [Help 1] >>>> org.apache.maven.lifecycle.LifecycleExecutionException: >>>> Failed to execute goal on project cspi-webui: Could not >>>> resolve dependencies for project >>>> org.collectionspace:cspi-webui:jar:4.1.1: Failure to find >>>> org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1 >>>> in >>>> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local >>>> was cached in the local repository, resolution will not be >>>> reattempted until the update interval of >>>> libs-snapshot-local has elapsed or updates are forced >>>> >>>> I think the relevant error is: >>>> Failure to find >>>> org.collectionspace.services:org.collectionspace.services.common-api:jar:4.1.1 >>>> in >>>> http://nightly.collectionspace.org:8081/artifactory/libs-snapshot-local >>>> was cached in the local repository, resolution will not be >>>> reattempted until the update interval of >>>> libs-snapshot-local has elapsed or updates are forced >>>> >>>> But i'm not sure how to fix it. >>>> >>>> Ryan Bankston >>>> Sr. Systems Administrator >>>> University of Michigan >>>> LSA IT Infrastructure >>>> rbanksto@umich.edu <mailto:rbanksto@umich.edu> >>>> >>>> >>>> >>>> >>>> _______________________________________________ >>>> Talk mailing list >>>> Talk@lists.collectionspace.org >>>> <mailto:Talk@lists.collectionspace.org> >>>> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org >>>> >>>> >>> >>> >> >> _______________________________________________ >> Talk mailing list >> Talk@lists.collectionspace.org <mailto:Talk@lists.collectionspace.org> >> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org