Hello,

I’m attempting my first install on Red Hat 7.3 workstation. I’ve done it using the automated tool and manually. When I get to this step:

“Starting the server

Start the server:

$CSPACE_JEESERVER_HOME/bin/startup.sh

Wait for it to fully start up. (For more information on verifying server startup, see [Starting Up CollectionSpace Servers].)"

I get command not found. Running a locate on startup.sh from / only returns the startup.sh for Tomcat (which runs fine).

What did I miss?

Thanks,
Tim

Thanks Ray, but still not found. Here’s a snip out of the cspace user’s .bashrc:

Start of environment variable declarations inserted by Puppet code

And here’s my output:

[cspace@localhost ~]$ CSPACE_JEESERVER_HOME/bin/startup.sh
bash: CSPACE_JEESERVER_HOME/bin/startup.sh: No such file or directory

Same result if I put ./ in front…

Cheers,
Tim

On Apr 20, 2017, at 2:23 PM, Ray Lee <rhlee@berkeley.edumailto:rhlee@berkeley.edu> wrote:

Actually, you don't need the curly braces. Just make sure you've got that environment variable set.

Ray

On Thu, Apr 20, 2017 at 1:06 PM, Ray Lee <rhlee@berkeley.edumailto:rhlee@berkeley.edu> wrote:
Hi Tim,
That line should actually read

${CSPACE_JEESERVER_HOME}/bin/startup.sh

(Note curly braces). You should have the CSPACE_JEESERVER_HOME environment variable set to your tomcat directory, so really all this is doing is running the startup.sh that you located.

Ray

On Thu, Apr 20, 2017 at 7:17 AM, Tim Brewer <Brewer@uwyo.edumailto:Brewer@uwyo.edu> wrote:
Hello,

I’m attempting my first install on Red Hat 7.3 workstation. I’ve done it using the automated tool and manually. When I get to this step:

“Starting the server

Start the server:

$CSPACE_JEESERVER_HOME/bin/startup.sh

Wait for it to fully start up. (For more information on verifying server startup, see [Starting Up CollectionSpace Servers].)"

I get command not found. Running a locate on startup.sh from / only returns the startup.sh for Tomcat (which runs fine).

What did I miss?

Thanks,
Tim

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

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:
[cid:B659A007-88AC-47EC-8320-CF2ADF55A3F4@uwyo.edu]

Anyone have an idea?

Thanks,
Tim

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.commailto: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.edumailto: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.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

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.commailto: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.edumailto: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.commailto: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.edumailto: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.orgmailto:Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org

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