<div dir="ltr"><div><div><div><div><div><div><div><div>Hi Blake,<br><br></div>I was able to get my issues sorted out and I've now got archivesspace 2.2.2 running on Centos 7. I've got it set up in a vagrant box if you want to have a look. If you've got virtualbox and vagrant set up on your local machine then you can get it running like this,<br><b><br></b></div><b> $ git clone git@github.com:NYULibraries/vagrant-archivesspace.git<br></b></div><b> $ cd vagrant-archivesspace<br></b></div><b> $ vagrant up<br></b></div><b> $ vagrant ssh<br></b></div><b> $ sudo systemctl start archivesspace.service</b><br><br></div>It'll install archivesspace in /opt/archviesspace, and the unit file will be at /ets/systemd/system/archivesspace.service. All the config details, usernames, passwords and such, can be found in <br></div><div> <br></div><div><b> </b>/etc/puppetlabs/code/environments/development/data/archivesspace.yaml <br></div><div><br></div><div>Once archivesspace is up and running you'll be able to connect via your browser at localhost:8080. If you've already got something running on your local machine on any of the archivesspace ports you'll need to change the port mappings in the Vagrantfile before you run `vagrant up`.<br><br></div>-f<br><div><div><div><div><div><div><div><br> <br></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Jan 26, 2018 at 1:49 PM, Blake Carver <span dir="ltr"><<a href="mailto:blake.carver@lyrasis.org" target="_blank">blake.carver@lyrasis.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Has anyone had any luck with systemd yet?<br>
<br>
<br>
<br>
______________________________<wbr>__________<br>
From: <a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a> <<a href="mailto:archivesspace_users_group-bounces@lyralists.lyrasis.org">archivesspace_users_group-<wbr>bounces@lyralists.lyrasis.org</a>> on behalf of Flannon Jackson <<a href="mailto:flannon@nyu.edu">flannon@nyu.edu</a>><br>
Sent: Monday, August 7, 2017 2:01:15 PM<br>
To: Archivesspace Users Group<br>
Subject: [Archivesspace_Users_Group] Running archivesspace from systemd<br>
<div><div class="h5"><br>
Hi All,<br>
<br>
I'm trying to run the archivesspace daemon from a systemd unit file but I'm getting an odd delay. If I start archivesspace manually by running "$ sudo archivesspace.sh start" things run normally, but when I start archivesspace from systemctl then any operation on port 8080 delays from 10 to 20 seconds before it returns results.<br>
<br>
If anyone is running archivesspace from systemctl and can offer any advice it would be appreciated.<br>
<br>
The details of my deployment are as follow,<br>
<br>
OS : Centos 7.3.10<br>
Java: OpenJDK 1.8.0_141<br>
archivesspace: 2.0.0 | 2.0.1 | 2.1.0 (i've tried all three with the same results)<br>
<br>
My unit file is as follows,<br>
<br>
[Unit]<br>
Description=Archivesspace Service<br>
After=syslog.target network.target<br>
<br>
[Service]<br>
Type=forking<br>
ExecStart=/opt/archivesspace/<wbr>archivesspace.sh start<br>
PIDFile=/opt/archivesspace/<wbr>data/.archivesspace.pid<br>
User=aspace<br>
Group=aspace<br>
TimeoutStopSec=10<br>
Restart=on-failure<br>
<br>
[Install]<br>
WantedBy=multi-user.target<br>
<br>
Initially I tried running it as user aspace. When that didn't work I also tried as root, but that didn't change anything.<br>
<br>
Currently I'm running archivesspace 1.5.2 on Centos 6 and the archivesspace daemon gets started from a wrapper script in init.d, so I thought that if I replicated that structure and had a wrapper script to run from the unit fil,e and set the type to either simple, or oneshot or idle, that that might do it. So I tried it like this,<br>
<br>
[Unit]<br>
Description=Archivesspace Service<br>
After=syslog.target network.target<br>
<br>
[Service]<br>
Type=simple<br>
ExecStart=/opt/archivesspace/<wbr>aspace-start.sh<br>
PIDFile=/opt/archivesspace/<wbr>data/.archivesspace.pid<br>
User=root<br>
Group=root<br>
<br>
[Install]<br>
WantedBy=multi-user.target<br>
<br>
But basically nothing changed -- archivesspace started fine but I still had the crazy delay. I'm thinking at this point that rather than having a unit file that calls archivesspace.sh that I need to write a unit file that replaces the functionality of archivesspace.sh and calls archivesspace directly. As you've probably noticed, archivesspace.sh is not exactly a trivial shell script, so before I get started I wanted to see if anyone else has had any luck getting archivesspace running on systemd.<br>
<br>
Thanks,<br>
<br>
Flannon<br>
</div></div>______________________________<wbr>_________________<br>
Archivesspace_Users_Group mailing list<br>
<a href="mailto:Archivesspace_Users_Group@lyralists.lyrasis.org">Archivesspace_Users_Group@<wbr>lyralists.lyrasis.org</a><br>
<a href="http://lyralists.lyrasis.org/mailman/listinfo/archivesspace_users_group" rel="noreferrer" target="_blank">http://lyralists.lyrasis.org/<wbr>mailman/listinfo/<wbr>archivesspace_users_group</a><br>
</blockquote></div><br></div>