Ok… The echo did in fact return nothing even though CSPACE_INSTANCE_ID was set in the .bashrc and had been sourced multiple times. So I exported it to the shell (ran the export from the command line) then echo returned the proper value. This indicated mvn wasn’t properly using the environment, so on a whim I rebooted the VM. And the install ran fine! Argh! Now onward… Thanks everyone! Tim On Jun 2, 2017, at 11:21 AM, James Keeline <james@keeline.com<mailto:james@keeline.com>> wrote: It looks as if the environmental variable is not set. You can check this by running this command a Linux prompt: echo $CSPACE_INSTANCE_ID Notice the dollar sign which is used when you want to get the value of a Bash variable. If it returns nothing, it is not set. Otherwise it will show the path that has been defined for it. _____ Look for the place where it is set (perhaps in ~/.bashrc ?). The .bashrc file is read and processed when you log in. Just altering the file won't set the environmental variable. However, you can force the file to be processed with this command: source ~/.bashrc You can then repeat the above echo command to see if it is different. Inside the .bashrc file you will normally use something like this: export CSPACE_INSTANCE_ID=/some/path/that/shows/where/your/installation/is Notice here that no dollar sign is used on the variable. In Bash you don't use the dollar sign when setting a variable, only when accessing its value. Another source of confusion is that when you are logged in as a non-root user the prompt usually has a dollar sign at the end. This is not the same as a dollar sign that you are asked to use when accessing this variable value as part of a command. These things can be confusing the first time you encounter them. I hope this explanation moves you in the right direction. James D. Keeline ________________________________ From: Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>> To: Richard Millet <richard.millet@lyrasis.org<mailto:richard.millet@lyrasis.org>> Cc: CollectionSpace Talk List <talk@lists.collectionspace.org<mailto:talk@lists.collectionspace.org>> Sent: Friday, June 2, 2017 10:11 AM Subject: Re: [Talk] Login connection error Ah, ok. CSPACE_INSTANCE_ID isn’t below. The db passwords are all specified in the cspace .bashrc yet they are defaulted below so clearly I’m pulling my env from somewhere else. [cspace@collection<mailto:cspace@collection> services]$ env XDG_VTNR=1 SSH_AGENT_PID=4980 XDG_SESSION_ID=19 HOSTNAME=collection IMSETTINGS_INTEGRATE_DESKTOP=yes GPG_AGENT_INFO=/run/user/595/keyring/gpg:0:1 TERM=xterm-256color XDG_MENU_PREFIX=gnome- SHELL=/bin/bash VTE_VERSION=3804 CATALINA_HOME=/usr/local/share/apache-tomcat-7.0.57 HISTSIZE=1000 WINDOWID=41943047 OLDPWD=/home/cspace/collectionspace-source ANT_OPTS=-Xmx768m -XX:MaxPermSize=512m IMSETTINGS_MODULE=none USER=cspace LS_COLORS=rs=0:di=38;5;27:ln=38;5;51:mh=44;38;5;15:pi=40;38;5;11:so=38;5;13:do=38;5;5:bd=48;5;232;38;5;11:cd=48;5;232;38;5;3:or=48;5;232;38;5;9:mi=05;48;5;232;38;5;15:su=48;5;196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;196;38;5;226:tw=48;5;10;38;5;16:ow=48;5;10;38;5;21:st=48;5;21;38;5;15:ex=38;5;34:*.tar=38;5;9:*.tgz=38;5;9:*.arc=38;5;9:*.arj=38;5;9:*.taz=38;5;9:*.lha=38;5;9:*.lz4=38;5;9:*.lzh=38;5;9:*.lzma=38;5;9:*.tlz=38;5;9:*.txz=38;5;9:*.tzo=38;5;9:*.t7z=38;5;9:*.zip=38;5;9:*.z=38;5;9:*.Z=38;5;9:*.dz=38;5;9:*.gz=38;5;9:*.lrz=38;5;9:*.lz=38;5;9:*.lzo=38;5;9:*.xz=38;5;9:*.bz2=38;5;9:*.bz=38;5;9:*.tbz=38;5;9:*.tbz2=38;5;9:*.tz=38;5;9:*.deb=38;5;9:*.rpm=38;5;9:*.jar=38;5;9:*.war=38;5;9:*.ear=38;5;9:*.sar=38;5;9:*.rar=38;5;9:*.alz=38;5;9:*.ace=38;5;9:*.zoo=38;5;9:*.cpio=38;5;9:*.7z=38;5;9:*.rz=38;5;9:*.cab=38;5;9:*.jpg=38;5;13:*.jpeg=38;5;13:*.gif=38;5;13:*.bmp=38;5;13:*.pbm=38;5;13:*.pgm=38;5;13:*.ppm=38;5;13:*.tga=38;5;13:*.xbm=38;5;13:*.xpm=38;5;13:*.tif=38;5;13:*.tiff=38;5;13:*.png=38;5;13:*.svg=38;5;13:*.svgz=38;5;13:*.mng=38;5;13:*.pcx=38;5;13:*.mov=38;5;13:*.mpg=38;5;13:*.mpeg=38;5;13:*.m2v=38;5;13:*.mkv=38;5;13:*.webm=38;5;13:*.ogm=38;5;13:*.mp4=38;5;13:*.m4v=38;5;13:*.mp4v=38;5;13:*.vob=38;5;13:*.qt=38;5;13:*.nuv=38;5;13:*.wmv=38;5;13:*.asf=38;5;13:*.rm=38;5;13:*.rmvb=38;5;13:*.flc=38;5;13:*.avi=38;5;13:*.fli=38;5;13:*.flv=38;5;13:*.gl=38;5;13:*.dl=38;5;13:*.xcf=38;5;13:*.xwd=38;5;13:*.yuv=38;5;13:*.cgm=38;5;13:*.emf=38;5;13:*.axv=38;5;13:*.anx=38;5;13:*.ogv=38;5;13:*.ogx=38;5;13:*.aac=38;5;45:*.au=38;5;45:*.flac=38;5;45:*.mid=38;5;45:*.midi=38;5;45:*.mka=38;5;45:*.mp3=38;5;45:*.mpc=38;5;45:*.ogg=38;5;45:*.ra=38;5;45:*.wav=38;5;45:*.axa=38;5;45:*.oga=38;5;45:*.spx=38;5;45:*.xspf=38;5;45: SSH_AUTH_SOCK=/run/user/595/keyring/ssh SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/4774,unix/unix:/tmp/.ICE-unix/4774 USERNAME=cspace MAVEN_OPTS=-Xmx768m -XX:MaxPermSize=512m GNOME_SHELL_SESSION_MODE=classic PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin:/bin:/sbin:/home/cspace/.local/bin:/home/cspace/bin MAIL=/var/spool/mail/cspace DESKTOP_SESSION=gnome-classic QT_IM_MODULE=ibus DB_READER_PASSWORD=your_reader_database_user_password_here PWD=/home/cspace/collectionspace-source/services XMODIFIERS=@im=ibus DB_NUXEO_PASSWORD=your_nuxeo_database_user_password_here JAVA_HOME=/usr/java/jdk1.8.0_131 LANG=en_US.UTF-8 GDM_LANG=en_US.UTF-8 CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-7.0.57 CATALINA_OPTS=-Xmx1024m -XX:MaxPermSize=384m GDMSESSION=gnome-classic HISTCONTROL=ignoredups HOME=/home/cspace SHLVL=2 XDG_SEAT=seat0 GNOME_DESKTOP_SESSION_ID=this-is-deprecated CATALINA_PID=/usr/local/share/apache-tomcat-7.0.57/bin/tomcat.pid DB_CSPACE_PASSWORD=your_cspace_database_user_password_here XDG_SESSION_DESKTOP=gnome-classic LOGNAME=cspace DB_CSADMIN_PASSWORD=your_csadmin_database_user_password_here DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-2fTV0X2G0X,guid=c35a0214adeb0ab7a2f98d1859304046 LESSOPEN=||/usr/bin/lesspipe.sh %s WINDOWPATH=1 XDG_RUNTIME_DIR=/run/user/595 DISPLAY=:0 XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME JEE_PORT=8180 XAUTHORITY=/run/gdm/auth-for-cspace-iwQMMn/database _=/usr/bin/env > On Jun 2, 2017, at 10:59 AM, Richard Millet <richard.millet@lyrasis.org<mailto:richard.millet@lyrasis.org>> wrote: > > That's ok. > > From the command line, run just this: > > env > > That will (should) show you a list of all the current environment variables. The form "${env.CSPACE_INSTANCE_ID}" is just meant for the Ant task embedded in the Maven pom.xml file -the one in the top level source directory of the services layer. > > If the CSPACE_INSTANCE_ID environment variable is set, it should show up in the output of the "env" command. > ________________________________________ > From: Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>> > Sent: Friday, June 2, 2017 9:53 AM > To: Richard Millet > Cc: CollectionSpace Talk List > Subject: Re: [Talk] Login connection error > > I may be misunderstanding something here… > > > [cspace@collection<mailto:cspace@collection> services]$ env.CSPACE_INSTANCE_ID > bash: env.CSPACE_INSTANCE_ID: command not found… > [cspace@collection<mailto:cspace@collection> services]$ ./env.CSPACE_INSTANCE_ID > bash: ./env.CSPACE_INSTANCE_ID: No such file or directory > [cspace@collection<mailto:cspace@collection> services]$ echo message="The value for CSPACE_INSTANCE_ID is: ${env.CSPACE_INSTANCE_ID}" > bash: The value for CSPACE_INSTANCE_ID is: ${env.CSPACE_INSTANCE_ID}: bad substitution > > >> On Jun 2, 2017, at 10:24 AM, Richard Millet <richard.millet@lyrasis.org<mailto:richard.millet@lyrasis.org>> wrote: >> >> Tim, >> >> So that seems to indicate the environment variable is either not set not available to the Maven command -not sure why or how that could happen. What is the output of running the 'env' command in the same shell from which you're running the Maven command? Just curious to see if "CSPACE_INSTANCE_ID" shows up as an environment variable there. >> >> -Richard >> ________________________________________ >> From: Talk <talk-bounces@lists.collectionspace.org<mailto:talk-bounces@lists.collectionspace.org>> on behalf of Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>> >> Sent: Friday, June 2, 2017 9:14 AM >> To: CollectionSpace Talk List >> Subject: Re: [Talk] Login connection error >> >> Richard, >> >> Echo returns nothing that I could find. >> >> Cheers, >> Tim >> >>> On Jun 1, 2017, at 3:31 PM, Richard Millet <richard.millet@lyrasis.org<mailto:richard.millet@lyrasis.org>> wrote: >>> >>> Tim, >>> >>> You could trying adding the following 'echo' Ant task to the top-level pom.xml file in the services layer to help you debug this. So near line 375 of the top-level pom.xml file add this: >>> >>> <echo message="The value for CSPACE_INSTANCE_ID is: ${env.CSPACE_INSTANCE_ID}" /> >>> >>> Make sure that you add that line somewhere between the <tasks> tags. The echo task should print out the value of the CSPACE_INSTANCE_ID environment variable the next time you run a mvn command from the top-level of the services layer. >>> >>> -Richard >>> ________________________________________ >>> From: Talk <talk-bounces@lists.collectionspace.org<mailto:talk-bounces@lists.collectionspace.org>> on behalf of Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>> >>> Sent: Thursday, June 1, 2017 12:56 PM >>> To: CollectionSpace Talk List >>> Subject: Re: [Talk] Login connection error >>> >>> Ok, on the mvn services install, I’m getting: >>> >>> An Ant BuildException has occured: Required environment variable CSPACE_INSTANCE_ID has not been set. Use '_default' as a default value. >>> >>> But CSPACE_INSTANCE_ID has been set to ‘_default’ in .bashrc. And I sourced it :) >>> >>> >>> On Jun 1, 2017, at 12:58 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> >>> In fact that was key. War-entry succeeded. I’m proceeding… >>> Thanks! >>> >>> On Jun 1, 2017, at 12:48 PM, Jesse Martinez <mjesse@gmail.com<mailto:mjesse@gmail.com><mailto:mjesse@gmail.com<mailto:mjesse@gmail.com>>> wrote: >>> >>> Hi Tim, >>> >>> It looks like the wiki documentation page you are referencing is out of date, unfortunately. >>> >>> Looking over the install instructions for Ubuntu<https://wiki.collectionspace.org/display/DOC/Installing+on+Ubuntu+14.04> shows a few additional environmental variables that should be added, including: >>> >>> export CSPACE_INSTANCE_ID="_default" >>> export DB_HOST="localhost" >>> export DB_PORT="5432" >>> export JEE_PORT="8180" >>> >>> This might be a key to the error messages you are seeing. >>> >>> Jesse >>> >>> On Thu, Jun 1, 2017 at 1:35 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Aron, et. al; >>> >>> After a long distraction, I’ve gotten back to this. I decided to try from ground zero. Following the steps here: https://wiki.collectionspace.org/display/DOC/Installing+on+Yum+Compatible+Linux+Distributions, I get to the mvn clean install -DskipTests step where things fail The fail point is: Failed to set JEE_PORT environment variable. Attached is an .rtf of the command output. >>> >>> Seems like I’m missing something stupidly obvious, but I can’t seem to put my finger on it. >>> >>> Cheers, >>> Tim >>> >>> On May 4, 2017, at 7:11 PM, Aron Roberts <aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu><mailto:aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu>>> wrote: >>> >>>> I did run the ant command. >>> >>> Excellent - thanks, Tim! >>> >>>> I tried to watch for errors, but that was practically pointless :) I'll run the individual pieces in verbose mode on Monday. >>> >>> Sounds good! >>> >>> If this helps, one can use 'tee' to capture the output from those various 'ant' commands in one or more file(s); e.g.: >>> >>> ant -v {ant target name and optional parameters here} 2>&1 | tee -a mylogfile >>> >>> (Remove the '-a' after tee and replace the filename with a unique one if you'd like to capture each command's output in a different file.) >>> >>> Aron >>> >>> On Thu, May 4, 2017 at 5:27 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Aron, >>> I did run the ant command. I tried to watch for errors, but that was practically pointless :) >>> I'll run the individual pieces in verbose mode on Monday. >>> >>> Thanks! >>> Tim >>> >>> Sent from my iPhone >>> >>> On May 4, 2017, at 3:07 PM, Aron Roberts <aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu><mailto:aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu>>> wrote: >>> >>> Cool - thanks, Tim! Am hoping that we're getting a bit closer each time. >>> >>>> The "mvn clean install -DskipTests" command didn’t return any errors that I saw, but the Catalina.out has an error that the CollectionSpace services could not initialize. >>> >>> Have you run the subsequent command in the Yum-based systems' install guide<https://wiki.collectionspace.org/display/DOC/Installing+on+Yum+Compatible+Linux+Distributions>? >>> >>> ant undeploy deploy create_db -Drecreate_db=true import >>> >>> And if so, did that step also complete without errors? >>> >>> If the issue is simply that this step hasn't yet been run, that would be terrific, as that means your install is likely close to success. >>> >>> 'mvn clean install' builds a set of artifacts locally (within the source code tree). The subsequent 'ant ... deploy ...' step copies those artifacts into the relevant places in the Tomcat folder, initializes databases and tables, and then populates the authentication-related tables with users, roles, permissions, etc. Both steps are vital. >>> >>> Or if you *have* run this 'ant...' command before, perhaps it's failing somewhere and the pertinent error message is being buried in a sea of output? If so we can zero in on that. >>> >>> It can be easier to spot errors when running each step individually; e.g.: >>> >>> ant undeploy >>> ant deploy >>> ant create_db -Drecreate_db=true >>> ant import >>> >>> As well, if an error occurs during any of these steps, but if there isn't a lot of detail shown as to its cause, one follow-up might be to run each step with Ant's verbose flag ('-v'), so we can see exactly what's failing; e.g. >>> >>> ant -v undeploy >>> ... >>> >>> Aron >>> >>> >>> >>> On Thu, May 4, 2017 at 1:42 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Ok, did that. The "mvn clean install -DskipTests" command didn’t return any errors that I saw, but the Catalina.out has an error that the CollectionSpace services could not initialize. >>> And, the previous error still exits. >>> I did find and fix a java issue. >>> >>> Thanks, >>> Tim >>> >>> >>> On May 3, 2017, at 3:28 PM, Aron Roberts <aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu><mailto:aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu>>> wrote: >>> >>> Thanks, Tim! >>> >>> In that logfile, there are entries pertaining to the startup of its UI and Application layers, respectively: >>> >>> INFO: Deploying web application archive /usr/local/share/apache-tomcat-7.0.57/webapps/cspace-ui.war >>> and >>> INFO: Deploying web application archive /usr/local/share/apache-tomcat-7.0.57/webapps/collectionspace.war >>> >>> There should also have been a log entry pertaining to the startup of CollectionSpace's Services layer, but I'm not seeing that: >>> >>> INFO: Deploying web application archive /usr/local/share/apache-tomcat-7.0.57/webapps/cspace-services.war >>> >>> As Yousef suggested earlier, "you may need to rebuild and redeploy the Services layer." That is, run the build steps starting at "Initialize database and users and permissions" in Installing on Yum Compatible Linux Distributions<https://wiki.collectionspace.org/display/DOC/Installing+on+Yum+Compatible+Linux+Distributions>. >>> >>> If you encounter any errors during that install - perhaps that might have occurred during an earlier install, as well - please let us know, as we can proceed from there. >>> >>> Thanks and best wishes, >>> Aron >>> >>> >>> On Wed, May 3, 2017 at 2:10 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Aron, >>> >>> Here ’tis: >>> >>> >>> >>> On May 3, 2017, at 3:01 PM, Aron Roberts <aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu><mailto:aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu>>> wrote: >>> >>> Thanks, Tim. >>> >>> My best guess is that the pertinent error might be a bit earlier in catalina.out, and not revealed by 'tail'. Could you attach the entire logfile? >>> >>> On Wed, May 3, 2017 at 1:55 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Aron, >>> >>> A tail of cspace-app.log (I don’t have a cspace-services.log) shows: 2017-05-03 14:31:40,008 ERROR [http-bio-8180-exec-3] [org.collectionspace.chain.csp.webui.misc.WebLogin:129] Login attempt to tenant '1' with username ' admin@core.collectionspace.org<mailto:admin@core.collectionspace.org><mailto:admin@core.collectionspace.org<mailto:admin@core.collectionspace.org>>' failed. >>> >>> A tail of catalina.out shows: >>> May 03, 2017 2:36:34 PM org.apache.catalina.loader.WebappClassLoader checkThreadLocalMapForLeaks >>> SEVERE: The web application [/collectionspace] created a ThreadLocal with key of type [ch.elca.el4j.services.xmlmerge.XmlMergeContext$1] (value [ch.elca.el4j.services.xmlmerge.XmlMergeContext$1@3112db77<mailto:1@3112db77>]) and a value of type [java.util.HashMap] (value [{}]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol stop >>> INFO: Stopping ProtocolHandler ["http-bio-8180"] >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol stop >>> INFO: Stopping ProtocolHandler ["ajp-bio-8009"] >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol destroy >>> INFO: Destroying ProtocolHandler ["http-bio-8180"] >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol destroy >>> INFO: Destroying ProtocolHandler ["ajp-bio-8009"] >>> >>> A tail of localhost_access_log.2017-05-03.txt for the same time stamp shows: >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/citationauthorities/urn:cspace:name(worldcat)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1073 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/workauthorities/urn:cspace:name(work)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1057 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/workauthorities/urn:cspace:name(cona_work)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1067 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/personauthorities/urn:cspace:name(person)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1065 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/personauthorities/urn:cspace:name(ulan_pa)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1067 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/orgauthorities/urn:cspace:name(organization)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1071 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/orgauthorities/urn:cspace:name(ulan_oa)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1061 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/locationauthorities/urn:cspace:name(location)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1073 >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/locationauthorities/urn:cspace:name(offsite_sla)?wf_deleted=false&showRelations=true HTTP/1.1" 404 1079 >>> fe80:0:0:0:e79e:5faf:94de:f881%2 - - [03/May/2017:14:31:41 -0600] "GET /collectionspace/tenant/core/namespaces/uischema HTTP/1.1" 200 3159 >>> >>> The other log files are either empty or have nothing around the 14:31 time stamp. >>> >>> Thanks, >>> tb >>> >>> On May 3, 2017, at 2:26 PM, Aron Roberts <aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu><mailto:aron@socrates.berkeley.edu<mailto:aron@socrates.berkeley.edu>>> wrote: >>> >>> Thanks, Tim, for these additional details. >>> >>> From your earlier conversation with Yousuf: >>>>> Try restarting the server. If that doesn't do it, check the server log. >>>> >>>> Messages log shows nothing. Secure log shows: May 1 08:39:47 collection gdm-password]: gkr-pam: unlocked login keyring >>> >>> Have you had a look at CollectionSpace's own logs, in $CSPACE_JEESERVER_HOME/logs? Am thinking that catalina.out and/or cspace-services.log might potentially offer pertinent error message(s). >>> >>> Aron >>> >>> On Wed, May 3, 2017 at 1:07 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Jesse, >>> >>> Yes, I’m building CS on a RHEL 7.3 workstation VM within VirtualBox. >>> Here’s the output from the curl command: >>> HTTP/1.1 404 Not Found >>> Server: Apache-Coyote/1.1 >>> Content-Type: text/html;charset=utf-8 >>> Content-Language: en >>> Content-Length: 1017 >>> Date: Wed, 03 May 2017 20:05:25 GMT >>> >>> Cheers, >>> Tim >>> >>> On May 3, 2017, at 8:56 AM, Jesse Martinez <mjesse@gmail.com<mailto:mjesse@gmail.com><mailto:mjesse@gmail.com<mailto:mjesse@gmail.com>>> wrote: >>> >>> Hi Tim, >>> >>> It appears you are using a Gnome desktop version for development. Are you developing directly on your machine or using a VM or shelling into an external server? >>> I'm not too familiar with Gnome but could you check that the services layer is running and accessible whenever you receive that error message? I'm curious if the desktop is suspending active terminal sessions at any point. >>> >>> Also sharing a small curl command that can help test if the services layer is accessible. This logs into the default core tenant. >>> curl -I -H "Authorization: Basic YWRtaW5AY29yZS5jb2xsZWN0aW9uc3BhY2Uub3JnOkFkbWluaXN0cmF0b3I=" localhost:8180/cspace-services/collectionobjects >>> >>> Jesse >>> >>> On Mon, May 1, 2017 at 10:50 AM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Sever restarted multiple times. >>> Messages log shows nothing. Secure log shows: May 1 08:39:47 collection gdm-password]: gkr-pam: unlocked login keyring >>> >>> Redeploying the Services layer has no discernible effect. >>> >>> Cheers, >>> Tim >>> >>> On Apr 27, 2017, at 4:59 PM, Yousuf Nejati <yousufnejati@gmail.com<mailto:yousufnejati@gmail.com><mailto:yousufnejati@gmail.com<mailto:yousufnejati@gmail.com>>> wrote: >>> >>> Try restarting the server. If that doesn't do it, check the server log. You may need to rebuild and redeploy the Services layer. >>> >>> Yousuf >>> >>> On Apr 27, 2017 3:15 PM, "Tim Brewer" <Brewer@uwyo.edu<mailto:Brewer@uwyo.edu><mailto:Brewer@uwyo.edu<mailto:Brewer@uwyo.edu>>> wrote: >>> Hello, >>> >>> Still working on my first install. When I go to the site (localhost:8180) in enter the admin or reader credentials, I receive this error: >>> <Screen Shot 2017-04-27 at 4.06.51 PM.png> >>> >>> Anyone have an idea? >>> >>> Thanks, >>> Tim >>> >>> _______________________________________________ >>> Talk mailing list >>> Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org><mailto: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><mailto: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><mailto: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><mailto: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 > _______________________________________________ Talk mailing list Talk@lists.collectionspace.org<mailto:Talk@lists.collectionspace.org> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

Could you send the exact line in your .bashrc that sets CSPACE_INSTANCE_ID? There may be something wrong with it -- for example, there can be no blanks around the equals sign... Good luck, glad things are starting to work! John On Fri, Jun 2, 2017 at 1:30 PM, Tim Brewer <Brewer@uwyo.edu> wrote: > Ok… > > The echo did in fact return nothing even though CSPACE_INSTANCE_ID was set > in the .bashrc and had been sourced multiple times. So I exported it to the > shell (ran the export from the command line) then echo returned the proper > value. This indicated mvn wasn’t properly using the environment, so on a > whim I rebooted the VM. And the install ran fine! Argh! > > Now onward… > > Thanks everyone! > Tim > > > On Jun 2, 2017, at 11:21 AM, James Keeline <james@keeline.com> wrote: > > It looks as if the environmental variable is not set. You can check this > by running this command a Linux prompt: > > *echo $**CSPACE_INSTANCE_ID* > > Notice the dollar sign which is used when you want to get the value of a > Bash variable. > > If it returns nothing, it is not set. Otherwise it will show the path > that has been defined for it. > _____ > > Look for the place where it is set (perhaps in ~/.bashrc ?). The .bashrc > file is read and processed when you log in. Just altering the file won't > set the environmental variable. However, you can force the file to be > processed with this command: > > *source ~/.bashrc* > > You can then repeat the above *echo* command to see if it is different. > > Inside the .bashrc file you will normally use something like this: > > *export > CSPACE_INSTANCE_ID=/some/path/that/shows/where/your/installation/is* > > Notice here that no dollar sign is used on the variable. In Bash you > don't use the dollar sign when setting a variable, only when accessing its > value. > > Another source of confusion is that when you are logged in as a non-root > user the prompt usually has a dollar sign at the end. This is not the same > as a dollar sign that you are asked to use when accessing this variable > value as part of a command. > > These things can be confusing the first time you encounter them. I hope > this explanation moves you in the right direction. > > James D. Keeline > > ------------------------------ > *From:* Tim Brewer <Brewer@uwyo.edu> > *To:* Richard Millet <richard.millet@lyrasis.org> > *Cc:* CollectionSpace Talk List <talk@lists.collectionspace.org> > *Sent:* Friday, June 2, 2017 10:11 AM > *Subject:* Re: [Talk] Login connection error > > Ah, ok. CSPACE_INSTANCE_ID isn’t below. The db passwords are all specified > in the cspace .bashrc yet they are defaulted below so clearly I’m pulling > my env from somewhere else. > > [cspace@collection services]$ env > XDG_VTNR=1 > SSH_AGENT_PID=4980 > XDG_SESSION_ID=19 > HOSTNAME=collection > IMSETTINGS_INTEGRATE_DESKTOP=yes > GPG_AGENT_INFO=/run/user/595/keyring/gpg:0:1 > TERM=xterm-256color > XDG_MENU_PREFIX=gnome- > SHELL=/bin/bash > VTE_VERSION=3804 > CATALINA_HOME=/usr/local/share/apache-tomcat-7.0.57 > HISTSIZE=1000 > WINDOWID=41943047 > OLDPWD=/home/cspace/collectionspace-source > ANT_OPTS=-Xmx768m -XX:MaxPermSize=512m > IMSETTINGS_MODULE=none > USER=cspace > LS_COLORS=rs=0:di=38;5;27:ln=38;5;51:mh=44;38;5;15:pi=40; > 38;5;11:so=38;5;13:do=38;5;5:bd=48;5;232;38;5;11:cd=48;5; > 232;38;5;3:or=48;5;232;38;5;9:mi=05;48;5;232;38;5;15:su=48; > 5;196;38;5;15:sg=48;5;11;38;5;16:ca=48;5;196;38;5;226:tw=48; > 5;10;38;5;16:ow=48;5;10;38;5;21:st=48;5;21;38;5;15:ex=38;5; > 34:*.tar=38;5;9:*.tgz=38;5;9:*.arc=38;5;9:*.arj=38;5;9:*. > taz=38;5;9:*.lha=38;5;9:*.lz4=38;5;9:*.lzh=38;5;9:*.lzma=38; > 5;9:*.tlz=38;5;9:*.txz=38;5;9:*.tzo=38;5;9:*.t7z=38;5;9:*. > zip=38;5;9:*.z=38;5;9:*.Z=38;5;9:*.dz=38;5;9:*.gz=38;5;9:*. > lrz=38;5;9:*.lz=38;5;9:*.lzo=38;5;9:*.xz=38;5;9:*.bz2=38;5; > 9:*.bz=38;5;9:*.tbz=38;5;9:*.tbz2=38;5;9:*.tz=38;5;9:*.deb= > 38;5;9:*.rpm=38;5;9:*.jar=38;5;9:*.war=38;5;9:*.ear=38;5;9: > *.sar=38;5;9:*.rar=38;5;9:*.alz=38;5;9:*.ace=38;5;9:*.zoo= > 38;5;9:*.cpio=38;5;9:*.7z=38;5;9:*.rz=38;5;9:*.cab=38;5;9:* > .jpg=38;5;13:*.jpeg=38;5;13:*.gif=38;5;13:*.bmp=38;5;13:*. > pbm=38;5;13:*.pgm=38;5;13:*.ppm=38;5;13:*.tga=38;5;13:*. > xbm=38;5;13:*.xpm=38;5;13:*.tif=38;5;13:*.tiff=38;5;13:*. > png=38;5;13:*.svg=38;5;13:*.svgz=38;5;13:*.mng=38;5;13:*. > pcx=38;5;13:*.mov=38;5;13:*.mpg=38;5;13:*.mpeg=38;5;13:*. > m2v=38;5;13:*.mkv=38;5;13:*.webm=38;5;13:*.ogm=38;5;13:*. > mp4=38;5;13:*.m4v=38;5;13:*.mp4v=38;5;13:*.vob=38;5;13:*. > qt=38;5;13:*.nuv=38;5;13:*.wmv=38;5;13:*.asf=38;5;13:*. > rm=38;5;13:*.rmvb=38;5;13:*.flc=38;5;13:*.avi=38;5;13:*. > fli=38;5;13:*.flv=38;5;13:*.gl=38;5;13:*.dl=38;5;13:*.xcf= > 38;5;13:*.xwd=38;5;13:*.yuv=38;5;13:*.cgm=38;5;13:*.emf= > 38;5;13:*.axv=38;5;13:*.anx=38;5;13:*.ogv=38;5;13:*.ogx= > 38;5;13:*.aac=38;5;45:*.au=38;5;45:*.flac=38;5;45:*.mid=38; > 5;45:*.midi=38;5;45:*.mka=38;5;45:*.mp3=38;5;45:*.mpc=38;5; > 45:*.ogg=38;5;45:*.ra=38;5;45:*.wav=38;5;45:*.axa=38;5;45:*. > oga=38;5;45:*.spx=38;5;45:*.xspf=38;5;45: > SSH_AUTH_SOCK=/run/user/595/keyring/ssh > SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/4774,unix/unix:/ > tmp/.ICE-unix/4774 > USERNAME=cspace > MAVEN_OPTS=-Xmx768m -XX:MaxPermSize=512m > GNOME_SHELL_SESSION_MODE=classic > PATH=/usr/local/bin:/usr/local/sbin:/usr/bin:/usr/sbin: > /bin:/sbin:/home/cspace/.local/bin:/home/cspace/bin > MAIL=/var/spool/mail/cspace > DESKTOP_SESSION=gnome-classic > QT_IM_MODULE=ibus > DB_READER_PASSWORD=your_reader_database_user_password_here > PWD=/home/cspace/collectionspace-source/services > XMODIFIERS=@im=ibus > DB_NUXEO_PASSWORD=your_nuxeo_database_user_password_here > JAVA_HOME=/usr/java/jdk1.8.0_131 > LANG=en_US.UTF-8 > GDM_LANG=en_US.UTF-8 > CSPACE_JEESERVER_HOME=/usr/local/share/apache-tomcat-7.0.57 > CATALINA_OPTS=-Xmx1024m -XX:MaxPermSize=384m > GDMSESSION=gnome-classic > HISTCONTROL=ignoredups > HOME=/home/cspace > SHLVL=2 > XDG_SEAT=seat0 > GNOME_DESKTOP_SESSION_ID=this-is-deprecated > CATALINA_PID=/usr/local/share/apache-tomcat-7.0.57/bin/tomcat.pid > DB_CSPACE_PASSWORD=your_cspace_database_user_password_here > XDG_SESSION_DESKTOP=gnome-classic > LOGNAME=cspace > DB_CSADMIN_PASSWORD=your_csadmin_database_user_password_here > DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-2fTV0X2G0X,guid= > c35a0214adeb0ab7a2f98d1859304046 > LESSOPEN=||/usr/bin/lesspipe.sh %s > WINDOWPATH=1 > XDG_RUNTIME_DIR=/run/user/595 > DISPLAY=:0 > XDG_CURRENT_DESKTOP=GNOME-Classic:GNOME > JEE_PORT=8180 > XAUTHORITY=/run/gdm/auth-for-cspace-iwQMMn/database > _=/usr/bin/env > > > > On Jun 2, 2017, at 10:59 AM, Richard Millet <richard.millet@lyrasis.org> > wrote: > > > > That's ok. > > > > From the command line, run just this: > > > > env > > > > That will (should) show you a list of all the current environment > variables. The form "${env.CSPACE_INSTANCE_ID}" is just meant for the Ant > task embedded in the Maven pom.xml file -the one in the top level source > directory of the services layer. > > > > If the CSPACE_INSTANCE_ID environment variable is set, it should show up > in the output of the "env" command. > > ________________________________________ > > From: Tim Brewer <Brewer@uwyo.edu> > > Sent: Friday, June 2, 2017 9:53 AM > > To: Richard Millet > > Cc: CollectionSpace Talk List > > Subject: Re: [Talk] Login connection error > > > > I may be misunderstanding something here… > > > > > > [cspace@collection services]$ env.CSPACE_INSTANCE_ID > > bash: env.CSPACE_INSTANCE_ID: command not found… > > [cspace@collection services]$ ./env.CSPACE_INSTANCE_ID > > bash: ./env.CSPACE_INSTANCE_ID: No such file or directory > > [cspace@collection services]$ echo message="The value for > CSPACE_INSTANCE_ID is: ${env.CSPACE_INSTANCE_ID}" > > bash: The value for CSPACE_INSTANCE_ID is: ${env.CSPACE_INSTANCE_ID}: > bad substitution > > > > > >> On Jun 2, 2017, at 10:24 AM, Richard Millet <richard.millet@lyrasis.org> > wrote: > >> > >> Tim, > >> > >> So that seems to indicate the environment variable is either not set > not available to the Maven command -not sure why or how that could happen. > What is the output of running the 'env' command in the same shell from > which you're running the Maven command? Just curious to see if > "CSPACE_INSTANCE_ID" shows up as an environment variable there. > >> > >> -Richard > >> ________________________________________ > >> From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Tim > Brewer <Brewer@uwyo.edu> > >> Sent: Friday, June 2, 2017 9:14 AM > >> To: CollectionSpace Talk List > >> Subject: Re: [Talk] Login connection error > >> > >> Richard, > >> > >> Echo returns nothing that I could find. > >> > >> Cheers, > >> Tim > >> > >>> On Jun 1, 2017, at 3:31 PM, Richard Millet <richard.millet@lyrasis.org> > wrote: > >>> > >>> Tim, > >>> > >>> You could trying adding the following 'echo' Ant task to the top-level > pom.xml file in the services layer to help you debug this. So near line > 375 of the top-level pom.xml file add this: > >>> > >>> <echo message="The value for CSPACE_INSTANCE_ID is: > ${env.CSPACE_INSTANCE_ID}" /> > >>> > >>> Make sure that you add that line somewhere between the <tasks> tags. > The echo task should print out the value of the CSPACE_INSTANCE_ID > environment variable the next time you run a mvn command from the top-level > of the services layer. > >>> > >>> -Richard > >>> ________________________________________ > >>> From: Talk <talk-bounces@lists.collectionspace.org> on behalf of Tim > Brewer <Brewer@uwyo.edu> > >>> Sent: Thursday, June 1, 2017 12:56 PM > >>> To: CollectionSpace Talk List > >>> Subject: Re: [Talk] Login connection error > >>> > >>> Ok, on the mvn services install, I’m getting: > >>> > >>> An Ant BuildException has occured: Required environment variable > CSPACE_INSTANCE_ID has not been set. Use '_default' as a default value. > >>> > >>> But CSPACE_INSTANCE_ID has been set to ‘_default’ in .bashrc. And I > sourced it :) > >>> > >>> > >>> On Jun 1, 2017, at 12:58 PM, Tim Brewer <Brewer@uwyo.edu<mailto:Brewer > @uwyo.edu>> wrote: > >>> > >>> In fact that was key. War-entry succeeded. I’m proceeding… > >>> Thanks! > >>> > >>> On Jun 1, 2017, at 12:48 PM, Jesse Martinez <mjesse@gmail.com<mailto: > mjesse@gmail.com>> wrote: > >>> > >>> Hi Tim, > >>> > >>> It looks like the wiki documentation page you are referencing is out > of date, unfortunately. > >>> > >>> Looking over the install instructions for Ubuntu<https://wiki. > collectionspace.org/display/DOC/Installing+on+Ubuntu+14.04> shows a few > additional environmental variables that should be added, including: > >>> > >>> export CSPACE_INSTANCE_ID="_default" > >>> export DB_HOST="localhost" > >>> export DB_PORT="5432" > >>> export JEE_PORT="8180" > >>> > >>> This might be a key to the error messages you are seeing. > >>> > >>> Jesse > >>> > >>> On Thu, Jun 1, 2017 at 1:35 PM, Tim Brewer <Brewer@uwyo.edu<mailto: > Brewer@uwyo.edu>> wrote: > >>> Aron, et. al; > >>> > >>> After a long distraction, I’ve gotten back to this. I decided to try > from ground zero. Following the steps here: https://wiki.collectionspace. > org/display/DOC/Installing+on+Yum+Compatible+Linux+Distributions, I get > to the mvn clean install -DskipTests step where things fail The fail point > is: Failed to set JEE_PORT environment variable. Attached is an .rtf of > the command output. > >>> > >>> Seems like I’m missing something stupidly obvious, but I can’t seem to > put my finger on it. > >>> > >>> Cheers, > >>> Tim > >>> > >>> On May 4, 2017, at 7:11 PM, Aron Roberts <aron@socrates.berkeley.edu< > mailto:aron@socrates.berkeley.edu>> wrote: > >>> > >>>> I did run the ant command. > >>> > >>> Excellent - thanks, Tim! > >>> > >>>> I tried to watch for errors, but that was practically pointless :) > I'll run the individual pieces in verbose mode on Monday. > >>> > >>> Sounds good! > >>> > >>> If this helps, one can use 'tee' to capture the output from those > various 'ant' commands in one or more file(s); e.g.: > >>> > >>> ant -v {ant target name and optional parameters here} 2>&1 | tee -a > mylogfile > >>> > >>> (Remove the '-a' after tee and replace the filename with a unique one > if you'd like to capture each command's output in a different file.) > >>> > >>> Aron > >>> > >>> On Thu, May 4, 2017 at 5:27 PM, Tim Brewer <Brewer@uwyo.edu<mailto: > Brewer@uwyo.edu>> wrote: > >>> Aron, > >>> I did run the ant command. I tried to watch for errors, but that was > practically pointless :) > >>> I'll run the individual pieces in verbose mode on Monday. > >>> > >>> Thanks! > >>> Tim > >>> > >>> Sent from my iPhone > >>> > >>> On May 4, 2017, at 3:07 PM, Aron Roberts <aron@socrates.berkeley.edu< > mailto:aron@socrates.berkeley.edu>> wrote: > >>> > >>> Cool - thanks, Tim! Am hoping that we're getting a bit closer each > time. > >>> > >>>> The "mvn clean install -DskipTests" command didn’t return any errors > that I saw, but the Catalina.out has an error that the CollectionSpace > services could not initialize. > >>> > >>> Have you run the subsequent command in the Yum-based systems' install > guide<https://wiki.collectionspace.org/display/DOC/Installing+on+Yum+ > Compatible+Linux+Distributions>? > >>> > >>> ant undeploy deploy create_db -Drecreate_db=true import > >>> > >>> And if so, did that step also complete without errors? > >>> > >>> If the issue is simply that this step hasn't yet been run, that would > be terrific, as that means your install is likely close to success. > >>> > >>> 'mvn clean install' builds a set of artifacts locally (within the > source code tree). The subsequent 'ant ... deploy ...' step copies those > artifacts into the relevant places in the Tomcat folder, initializes > databases and tables, and then populates the authentication-related tables > with users, roles, permissions, etc. Both steps are vital. > >>> > >>> Or if you *have* run this 'ant...' command before, perhaps it's > failing somewhere and the pertinent error message is being buried in a sea > of output? If so we can zero in on that. > >>> > >>> It can be easier to spot errors when running each step individually; > e.g.: > >>> > >>> ant undeploy > >>> ant deploy > >>> ant create_db -Drecreate_db=true > >>> ant import > >>> > >>> As well, if an error occurs during any of these steps, but if there > isn't a lot of detail shown as to its cause, one follow-up might be to run > each step with Ant's verbose flag ('-v'), so we can see exactly what's > failing; e.g. > >>> > >>> ant -v undeploy > >>> ... > >>> > >>> Aron > >>> > >>> > >>> > >>> On Thu, May 4, 2017 at 1:42 PM, Tim Brewer <Brewer@uwyo.edu<mailto: > Brewer@uwyo.edu>> wrote: > >>> Ok, did that. The "mvn clean install -DskipTests" command didn’t > return any errors that I saw, but the Catalina.out has an error that the > CollectionSpace services could not initialize. > >>> And, the previous error still exits. > >>> I did find and fix a java issue. > >>> > >>> Thanks, > >>> Tim > >>> > >>> > >>> On May 3, 2017, at 3:28 PM, Aron Roberts <aron@socrates.berkeley.edu< > mailto:aron@socrates.berkeley.edu>> wrote: > >>> > >>> Thanks, Tim! > >>> > >>> In that logfile, there are entries pertaining to the startup of its UI > and Application layers, respectively: > >>> > >>> INFO: Deploying web application archive /usr/local/share/apache- > tomcat-7.0.57/webapps/cspace-ui.war > >>> and > >>> INFO: Deploying web application archive /usr/local/share/apache- > tomcat-7.0.57/webapps/collectionspace.war > >>> > >>> There should also have been a log entry pertaining to the startup of > CollectionSpace's Services layer, but I'm not seeing that: > >>> > >>> INFO: Deploying web application archive /usr/local/share/apache- > tomcat-7.0.57/webapps/cspace-services.war > >>> > >>> As Yousef suggested earlier, "you may need to rebuild and redeploy the > Services layer." That is, run the build steps starting at "Initialize > database and users and permissions" in Installing on Yum Compatible Linux > Distributions<https://wiki.collectionspace.org/display/ > DOC/Installing+on+Yum+Compatible+Linux+Distributions>. > >>> > >>> If you encounter any errors during that install - perhaps that might > have occurred during an earlier install, as well - please let us know, as > we can proceed from there. > >>> > >>> Thanks and best wishes, > >>> Aron > >>> > >>> > >>> On Wed, May 3, 2017 at 2:10 PM, Tim Brewer <Brewer@uwyo.edu<mailto: > Brewer@uwyo.edu>> wrote: > >>> Aron, > >>> > >>> Here ’tis: > >>> > >>> > >>> > >>> On May 3, 2017, at 3:01 PM, Aron Roberts <aron@socrates.berkeley.edu< > mailto:aron@socrates.berkeley.edu>> wrote: > >>> > >>> Thanks, Tim. > >>> > >>> My best guess is that the pertinent error might be a bit earlier in > catalina.out, and not revealed by 'tail'. Could you attach the entire > logfile? > >>> > >>> On Wed, May 3, 2017 at 1:55 PM, Tim Brewer <Brewer@uwyo.edu<mailto: > Brewer@uwyo.edu>> wrote: > >>> Aron, > >>> > >>> A tail of cspace-app.log (I don’t have a cspace-services.log) shows: > 2017-05-03 14:31:40,008 ERROR [http-bio-8180-exec-3] > [org.collectionspace.chain.csp.webui.misc.WebLogin:129] Login attempt to > tenant '1' with username ' admin@core.collectionspace.org<mailto: > admin@core.collectionspace.org>' failed. > >>> > >>> A tail of catalina.out shows: > >>> May 03, 2017 2:36:34 PM org.apache.catalina.loader.WebappClassLoader > checkThreadLocalMapForLeaks > >>> SEVERE: The web application [/collectionspace] created a ThreadLocal > with key of type [ch.elca.el4j.services.xmlmerge.XmlMergeContext$1] > (value [ch.elca.el4j.services.xmlmerge.XmlMergeContext$1@3112db77]) and a > value of type [java.util.HashMap] (value [{}]) but failed to remove it when > the web application was stopped. Threads are going to be renewed over time > to try and avoid a probable memory leak. > >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol stop > >>> INFO: Stopping ProtocolHandler ["http-bio-8180"] > >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol stop > >>> INFO: Stopping ProtocolHandler ["ajp-bio-8009"] > >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol destroy > >>> INFO: Destroying ProtocolHandler ["http-bio-8180"] > >>> May 03, 2017 2:36:34 PM org.apache.coyote.AbstractProtocol destroy > >>> INFO: Destroying ProtocolHandler ["ajp-bio-8009"] > >>> > >>> A tail of localhost_access_log.2017-05-03.txt for the same time stamp > shows: > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > citationauthorities/urn:cspace:name(worldcat)?wf_ > deleted=false&showRelations=true HTTP/1.1" 404 1073 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > workauthorities/urn:cspace:name(work)?wf_deleted=false&showRelations=true > HTTP/1.1" 404 1057 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > workauthorities/urn:cspace:name(cona_work)?wf_deleted=false&showRelations=true > HTTP/1.1" 404 1067 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > personauthorities/urn:cspace:name(person)?wf_deleted=false&showRelations=true > HTTP/1.1" 404 1065 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > personauthorities/urn:cspace:name(ulan_pa)?wf_deleted=false&showRelations=true > HTTP/1.1" 404 1067 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > orgauthorities/urn:cspace:name(organization)?wf_deleted=false&showRelations=true > HTTP/1.1" 404 1071 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > orgauthorities/urn:cspace:name(ulan_oa)?wf_deleted=false&showRelations=true > HTTP/1.1" 404 1061 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > locationauthorities/urn:cspace:name(location)?wf_ > deleted=false&showRelations=true HTTP/1.1" 404 1073 > >>> 127.0.0.1 - - [03/May/2017:14:31:41 -0600] "GET /cspace-services/ > locationauthorities/urn:cspace:name(offsite_sla)?wf_ > deleted=false&showRelations=true HTTP/1.1" 404 1079 > >>> fe80:0:0:0:e79e:5faf:94de:f881%2 - - [03/May/2017:14:31:41 -0600] > "GET /collectionspace/tenant/core/namespaces/uischema HTTP/1.1" 200 3159 > >>> > >>> The other log files are either empty or have nothing around the 14:31 > time stamp. > >>> > >>> Thanks, > >>> tb > >>> > >>> On May 3, 2017, at 2:26 PM, Aron Roberts <aron@socrates.berkeley.edu< > mailto:aron@socrates.berkeley.edu>> wrote: > >>> > >>> Thanks, Tim, for these additional details. > >>> > >>> From your earlier conversation with Yousuf: > >>>>> Try restarting the server. If that doesn't do it, check the server > log. > >>>> > >>>> Messages log shows nothing. Secure log shows: May 1 08:39:47 > collection gdm-password]: gkr-pam: unlocked login keyring > >>> > >>> Have you had a look at CollectionSpace's own logs, in > $CSPACE_JEESERVER_HOME/logs? Am thinking that catalina.out and/or > cspace-services.log might potentially offer pertinent error message(s). > >>> > >>> Aron > >>> > >>> On Wed, May 3, 2017 at 1:07 PM, Tim Brewer <Brewer@uwyo.edu<mailto: > Brewer@uwyo.edu>> wrote: > >>> Jesse, > >>> > >>> Yes, I’m building CS on a RHEL 7.3 workstation VM within VirtualBox. > >>> Here’s the output from the curl command: > >>> HTTP/1.1 404 Not Found > >>> Server: Apache-Coyote/1.1 > >>> Content-Type: text/html;charset=utf-8 > >>> Content-Language: en > >>> Content-Length: 1017 > >>> Date: Wed, 03 May 2017 20:05:25 GMT > >>> > >>> Cheers, > >>> Tim > >>> > >>> On May 3, 2017, at 8:56 AM, Jesse Martinez <mjesse@gmail.com<mailto: > mjesse@gmail.com>> wrote: > >>> > >>> Hi Tim, > >>> > >>> It appears you are using a Gnome desktop version for development. Are > you developing directly on your machine or using a VM or shelling into an > external server? > >>> I'm not too familiar with Gnome but could you check that the services > layer is running and accessible whenever you receive that error message? > I'm curious if the desktop is suspending active terminal sessions at any > point. > >>> > >>> Also sharing a small curl command that can help test if the services > layer is accessible. This logs into the default core tenant. > >>> curl -I -H "Authorization: Basic YWRtaW5AY29yZS5jb2xsZWN0aW9uc3 > BhY2Uub3JnOkFkbWluaXN0cmF0b3I=" localhost:8180/cspace- > services/collectionobjects > >>> > >>> Jesse > >>> > >>> On Mon, May 1, 2017 at 10:50 AM, Tim Brewer <Brewer@uwyo.edu<mailto: > Brewer@uwyo.edu>> wrote: > >>> Sever restarted multiple times. > >>> Messages log shows nothing. Secure log shows: May 1 08:39:47 > collection gdm-password]: gkr-pam: unlocked login keyring > >>> > >>> Redeploying the Services layer has no discernible effect. > >>> > >>> Cheers, > >>> Tim > >>> > >>> On Apr 27, 2017, at 4:59 PM, Yousuf Nejati <yousufnejati@gmail.com< > mailto:yousufnejati@gmail.com>> wrote: > >>> > >>> Try restarting the server. If that doesn't do it, check the server > log. You may need to rebuild and redeploy the Services layer. > >>> > >>> Yousuf > >>> > >>> On Apr 27, 2017 3:15 PM, "Tim Brewer" <Brewer@uwyo.edu<mailto:Brewer > @uwyo.edu>> wrote: > >>> Hello, > >>> > >>> Still working on my first install. When I go to the site > (localhost:8180) in enter the admin or reader credentials, I receive this > error: > >>> <Screen Shot 2017-04-27 at 4.06.51 PM.png> > >>> > >>> Anyone have an idea? > >>> > >>> Thanks, > >>> Tim > >>> > >>> _______________________________________________ > >>> 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 > >>> > >>> > >>> > >>> > >>> _______________________________________________ > >>> 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 > >>> > >>> > >>> > >>> > >> > >> _______________________________________________ > >> 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 > > > > > _______________________________________________ > Talk mailing list > Talk@lists.collectionspace.org > http://lists.collectionspace.org/mailman/listinfo/talk_ > lists.collectionspace.org > >