1.5 install issues

[Alan Darnell]

I'm following the instructions for a fresh install of 1.5 but am running into issues at step 6 as follows:

vagrant@vagrant-ubuntu-trusty-64:~$ sudo ln -s /etc/nginx/sites-available/storage /etc/nginx/sites-enabled/storage

ln: failed to create symbolic link ‘/etc/nginx/sites-enabled/storage’: No such file or directory

vagrant@vagrant-ubuntu-trusty-64:~$ sudo ln -s /etc/uwsgi/apps-available/storage.ini /etc/uwsgi/apps-enabled/storage.ini

ln: failed to create symbolic link ‘/etc/uwsgi/apps-enabled/storage.ini’: No such file or directory

vagrant@vagrant-ubuntu-trusty-64:~$ sudo service uwsgi restart

uwsgi: unrecognized service

vagrant@vagrant-ubuntu-trusty-64:~$ sudo service nginx restart

nginx: unrecognized service

Any ideas on why the sys link is failing?  Do I need to create the linked to directory manually?

[craig....@arkivum.com]

It looks like nginx and uwsgi haven't installed.  I would suggest running steps 4 and 5 again to see if this solves this issue.

sudo apt-get update
sudo apt-get upgrade

sudo apt-get install -y archivematica-storage-service

If it does not, then I think there may have been a mistake in the commands used in steps 1-3.  Make sure that you enter each command one line at a time - copying and pasting the whole command block for each step may result in errors (it did for me, at least).

HTH

[Alan Darnell]

I started from scratch with

vagrant init ubuntu/trusty64

vagrant up

vagrant ssh

and at the following command in Part 2 of the 1.5 new install instructions:

sudo wget -O - https://packages.archivematica.org/1.5.x/key.asc | apt-key add -

I get this response:

--2016-06-13 15:50:54--  https://packages.archivematica.org/1.5.x/key.asc

Resolving packages.archivematica.org (packages.archivematica.org)... 167.114.216.99

Connecting to packages.archivematica.org (packages.archivematica.org)|167.114.216.99|:443... ERROR: This command can only be used by root.

connected.

HTTP request sent, awaiting response... 200 OK

Length: 3152 (3.1K) [application/octet-stream]

Saving to: ‘STDOUT’

 0% [                                       ] 0           --.-K/s   in 0s      

Cannot write to ‘-’ (Success).

So it seems like there is an Error (not sure with what command) but the final line suggests Success.  Guessing my problems start here.

It would be great if the install instructions included examples of successful execution outputs.  

Alan

[Alan Darnell]

Figured it out -- error in the install instructions:

replaced 

sudo wget -O - https://packages.archivematica.org/1.5.x/key.asc | apt-key add -

with

sudo wget -O - https://packages.archivematica.org/1.5.x/key.asc | sudo apt-key add -

Alan

[craig....@arkivum.com]

Well done!

Where are the vagrant install instructions for 1.5?  Could you post a link?

[Alan Darnell]

Just followed the information here:

https://www.vagrantup.com/docs/getting-started/

after installing Vagrant and VirtualBox.  

The command "vagrant init ubuntu/trusty64" gets Ubuntu up and running, but I'm not sure if that is enough to start the Archivematica install because I run into the following issues:

ClamAV doesn't seem to get installed and then won't load the database definitions file after I install it with "sudo apt-get install clamav" and run "sudo freshclam"

$ sudo freshclam

ClamAV update process started at Mon Jun 13 16:58:54 2016

WARNING: Your ClamAV installation is OUTDATED!

WARNING: Local version: 0.98.7 Recommended version: 0.99.2

DON'T PANIC! Read http://www.clamav.net/support/faq

Empty script main-56.cdiff, need to download entire database

Downloading main.cvd [100%]

ERROR: Database load killed by signal 9

ERROR: Failed to load new database

So tried to run 

$ sudo apt-get install clamav-daemon

which returned this:

Reading package lists... Done

Building dependency tree       

Reading state information... Done

Suggested packages:

  daemon clamav-docs

The following NEW packages will be installed:

  clamav-daemon

0 upgraded, 1 newly installed, 0 to remove and 4 not upgraded.

Need to get 141 kB of archives.

After this operation, 964 kB of additional disk space will be used.

Get:1 http://archive.ubuntu.com/ubuntu/ trusty-updates/main clamav-daemon amd64 0.98.7+dfsg-0ubuntu0.14.04.1 [141 kB]

Fetched 141 kB in 0s (297 kB/s)   

Selecting previously unselected package clamav-daemon.

(Reading database ... 80615 files and directories currently installed.)

Preparing to unpack .../clamav-daemon_0.98.7+dfsg-0ubuntu0.14.04.1_amd64.deb ...

Unpacking clamav-daemon (0.98.7+dfsg-0ubuntu0.14.04.1) ...

Processing triggers for man-db (2.6.7.1-1ubuntu1) ...

Processing triggers for ureadahead (0.100.0-16) ...

Setting up clamav-daemon (0.98.7+dfsg-0ubuntu0.14.04.1) ...

 * Starting ClamAV daemon clamd                                                 LibClamAV Warning: **************************************************

LibClamAV Warning: ***  The virus database is older than 7 days!  ***

LibClamAV Warning: ***   Please update it as soon as possible.    ***

LibClamAV Warning: **************************************************

Killed

                                                                         [fail]

Processing triggers for ureadahead (0.100.0-16) ...

Not surprisingly, the next command doesn't work:

$ sudo /etc/init.d/clamav-daemon start

returns

sudo: /etc/init.d/clamav-daemon: command not found

And then 

$ sudo /etc/init.d/elasticsearch restart

returns

Could not find any executable java binary. Please install java in your PATH or set JAVA_HOME (don't see anything in the install instructions about configuring JAVA_HOME as a prerequisite so maybe something failed in the install)

And then

$ sudo start archivematica-mcp-client

returns

start: Unknown job: archivematica-mcp-client

And then finally:

$ sudo start fits

returns 

start: Unknown job: fits

Alan

[scol...@artefactual.com]

Hi Alan

Those messages make me think that archivematica-mcp-client wasn't installed. 

Can you try to run the command "sudo apt-get install archivematica-mcp-client" ?. That should bring all the needed dependencies (fits, clamav, and much more) and also provide the init script for the mcp-client.

/santi

[Alan Darnell]

Thanks Santi,

That cleared things up.

I'm just struggling with the VirtualBox network setting now.  I've got Adapter 1 set to NAT and Adapter 2 set to Host-only pointing to vboxnet0 which has the IPv4 address of 192.168.168.1 and Network Mask of 255.255.255.0.  DHCP is turned off.

This replicates I think the setup when I use the  ansible playbook but I can't get anything back from 192.168.168.192, which is what I was using to connect to the Dashboard for the instance I installed with ansible.  http://localhost doesn't work either.

Are there any guidelines for setting up Vagrant network settings for Archivematica?

Alan

[scol...@artefactual.com]

Hi Alan

You can also configure one interface as bridged ( config.vm.network "public_network" in Vagrantfile ). This way, the virtual server will have a local ip from your LAN, and anyone in the local network will be able to see the archivematica instance.

/santi

[Alan Darnell]

Thanks.  Will try.  

Not knowing anything about vagrant or virtual box, this is probably the most mysterious part (to me) of setting up Archivematica on a VM.  After running the ansible scripts, I see in VirtualBox that I have a configuration with two network adapters -- one configured as NAT and the other as Host-adapter only, associated with vboxnet0 which indicates an IP address of 192.168.168.1 and net mask of 255.255.255.0.  Archivematica comes up and is somehow assigned IP address 192.168.168.192.  

When I destroyed the VM created by ansible and started from an ubuntu/trusty64 image and installed Archivematica manually, the same network settings wouldn't work.  I got rid of everything and went back to ansible and have a working instance again.  No more time to work on this, but thought I would let others know what I ran into in case they are having similar difficulties.

Alan

[Mathieu Deschaine]

Hi Alan,

I use VBox, with Ubuntu 14.04 and install Archivematica manually (more for the practice than anything else).  I can share with you the network settings I use.

I set up the adapters in VBox like so:

and I edit /etc/network/interfaces so it looks like this:

save and reboot.  When you ifconfig after rebooting it should work properly.  This setup works for me and I can handshake from other applications on other VM's.  Hope if helps you.

-Matt

[Alan Darnell]

Thanks -- will try this out.