Page Comparison

Task Description

This task describes how to start the CollectionSpace server.

...

• Login to your system as the collectionspace user that was created when you installed CollectionSpace

• As the collectionspace user on Linux/Unix/Mac OS X, at your command prompt, enter:

  Code Block
  $CSPACE_JEESERVER_HOME/bin/startup.sh

...

If you used the Automated Installer to install CollectionSpace, you can find the password for the collectionspace user in the file initial_password.txt in the home directory of the collectionspace user. To get there you'll need to perform this command:

...

Validate

Check server logs

...

The startup message in the log file may look something like the following:

Jan 15, 2016 3:41:17 PM02-Apr-2024 23:19:40.339 INFO [main] org.apache.coyote.AbstractProtocol.start Starting ProtocolHandler ["http-nio-8180"]
02-Apr-2024 23:19:40.346 INFO [main] org.apache.catalina.startup.Catalina .start
INFO: Server startup in 38052590505 ms

Even though a startup message appears, this message does not absolutely indicate a working CollectionSpace system. Non-fatal but nonetheless serious errors could have occurred during the startup process. As a best practice, at each startup, System Administrators should review server logs for evidence of error conditions that could impede proper behavior of the system.

Try sending an API request

To see if the installation was successful and that the CollectionSpace server started up without problems.  Try the following command:

curl -i -u admin@core.collectionspace.org:Administrator http://localhost:8180/cspace-services/collectionobjects -u admin@core.collectionspace.org:Administrator

Replace Administrator with the password you set for the built-in admin user, if you've already done that step.

If successful, you should see output that looks something like this:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=745CD7316C77FF98D2474C0640009FDD; Path=/cspace-services/; HttpOnly
Cache-Control: no-cache, no-store, max-age=0, must-revalidate
Pragma: no-cache
Expires: 0
X-XSS-Protection: 1; mode=block
X-Frame-Options: DENY
X-Content-Type-Options: nosniff
Content-Type: application/xml
Content-Length: 3831415
Date: Wed, 2003 JulApr 20162024 2203:2403:0021 GMT

If you don't see "HTTP/1.1 200 OK" in the first line of the output, review the installation instructions to see if you missed a step.  If you are not able to get past this error, contact the CollectionSpace community "Talk" list at talk@collectionspace.org.  Please include as much detail as possible so someone in the community can try to help you.

...

You can view these processes using the command line ps command for Linux, Unix and Mac OS X systems, or the command line tasklist or wmic commands for Windows systemsin Linux. Your operating system may also provide graphical tool(s) that you can use to view running processes. Please see your operating system documentation for details.

...

You should see something like this as a in the result:

cspacecollect+   15228    31303 298 1 173 17:07Apr02 pts/04    00:0109:1211 /usr/lib/jvm/java-78-openjdk-amd64arm64//bin/java -Djava.util.logging.config.file=/opt/collectionspace/apache-tomcat-8.5.51/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager -Dnuxeo.home=/opt/collectionspace/apache-tomcat-8.5.51/nuxeo-server -Dnuxeo.home.dir=/opt/collectionspace/apache-tomcat-8.5.51/nuxeo-server -Dnuxeo.log.dir=/opt/collectionspace/apache-tomcat-8.5.51/nuxeo-server/log -Dfile.encoding=UTF-8 -Duser.timezone=UTC -Xms512m -Xmx1024m -Dorg.collectionspace.services.elasticsearch.reset=false -Dorg.collectionspace.services.authorities.reset=false -Dlog4j2.formatMsgNoLookups=true -Djdk.tls.ephemeralDHKeySize=2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -agentlib:jdwp=transport=dt_socket,address=localhost:8000,server=y,suspend=n -Xmx1524m -Dignore.endorsed.dirs=/usr/local/share -classpath /opt/collectionspace/apache-tomcat-8.5.51/bin/bootstrap.jar:/opt/collectionspace/apache-tomcat-8.5.51/bin/tomca-juli.jar -Dcatalina.base=/opt/collectionspace/apache-tomcat-8.5.51 -Dcatalina.home=/opt/collectionspace/apache-tomcat-8.5.51 -Djava.io.tmpdir=/opt/collectionspace/apache-tomcat-7.0.578.5.51/temp org.apache.catalina.startup.Bootstrap start

Some of the words that might appear in this process list entry, that you could use to search for and identify this process, may include catalina collectionspace, nuxeo, java, and tomcat.

Try logging in

You can try connecting to the login page for the demonstration core tenant on your server by pointing your web browser at:

http://{hostname}:8180/collectionspace/uicspace/core/htmllogin

where {hostname} is either localhost (if the server is running on your computer), or the hostname or IP address of the server.

If the login page appears, you can then try logging in by following the instructions on that page.

Testing with the API

To see if the installation was successful and that the CollectionSpace server started up without problems.  Try the following command:

curl -i http://localhost:8180/cspace-services/collectionobjects -u admin@core.collectionspace.org:Administrator

If successful, you should see output that looks something like this:

HTTP/1.1 200 OK
Server: Apache-Coyote/1.1
Set-Cookie: JSESSIONID=745CD7316C77FF98D2474C0640009FDD; Path=/cspace-services/; HttpOnly
Content-Type: application/xml
Content-Length: 383
Date: Wed, 20 Jul 2016 22:24:00 GMT

If you don't see "HTTP/1.1 200 OK" in the first line of the output, review the installation instructions to see if you missed a step.  If you are not able to get passed this error, contact the CollectionSpace community "Talk" list at talk@collectionspace.org.  Please include as much detail as possible so someone in the community can try to help you.

See Also

• Shutting Down the CollectionSpace Server
• Enabling remote debugging in Tomcat