[Archivesspace_Users_Group] Stopping ASpace: "Couldn't find a running instance to stop"

[Holland, Andrew S]

Is AS owned by root?

I had an issue with a phantom instance of AS running when I did my start/stop as a root user instead of the web user (wwwrun) who owned the files.

I suggest attempting to stop again. Then running:
> ps –ef | egrep archivesspace

Then kill all running instances before starting again.

-Andrew

From: archivesspace_users_group-bounces at lyralists.lyrasis.org <archivesspace_users_group-bounces at lyralists.lyrasis.org> On Behalf Of Rachel Trent
Sent: Monday, October 29, 2018 8:38 AM
To: archivesspace_users_group at lyralists.lyrasis.org
Subject: [Archivesspace_Users_Group] Stopping ASpace: "Couldn't find a running instance to stop"

Hi folks,

I have just installed a new test instance of ASpace on a server that's never run ASpace before. It's only got this one instance of ASpace. It's pointing to a copy of our production database.

It's running beautifully. The admin UI is running at port 8080, public UI at port 8081. All the data is there.

Weird thing, I can't seem to shut ASpace down.

Here's what an attempt looks like:

# cd /path/to/archivesspace
# sudo ./archivesspace.sh stop

ArchivesSpace base directory: /path/to/archivesspace
Couldn't find a running instance to stop

This is definitely where ArchivesSpace is running, because I just installed it there yesterday.

Our production instance stops and starts perfectly, a mirror of that server stops and starts perfectly, but the fresh install fails to stop.

Any thoughts on what I'm missing?

Thanks!
Rachel

Rachel Trent
Digital Services Manager
Special Collections Research Center
Gelman Library,  George Washington University
2130 H Street NW
Washington DC 20052
202.994.4824
racheltrent at gwu.edu<mailto:racheltrent at gwu.edu>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lyralists.lyrasis.org/pipermail/archivesspace_users_group/attachments/20181029/34ff81b8/attachment.html>