{"action":"created","issue":{"url":"https://api.github.com/repos/artefactual/deploy-pub/issues/22","repository_url":"https://api.github.com/repos/artefactual/deploy-pub","labels_url":"https://api.github.com/repos/artefactual/deploy-pub/issues/22/labels{/name}","comments_url":"https://api.github.com/repos/artefactual/deploy-pub/issues/22/comments","events_url":"https://api.github.com/repos/artefactual/deploy-pub/issues/22/events","html_url":"https://github.com/artefactual/deploy-pub/issues/22","id":179626395,"number":22,"title":"Problem: AM services require manual start up in Vagrant environment ","user":{"login":"hakamine","id":10160634,"avatar_url":"https://avatars3.githubusercontent.com/u/10160634?v=4","gravatar_id":"","url":"https://api.github.com/users/hakamine","html_url":"https://github.com/hakamine","followers_url":"https://api.github.com/users/hakamine/followers","following_url":"https://api.github.com/users/hakamine/following{/other_user}","gists_url":"https://api.github.com/users/hakamine/gists{/gist_id}","starred_url":"https://api.github.com/users/hakamine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hakamine/subscriptions","organizations_url":"https://api.github.com/users/hakamine/orgs","repos_url":"https://api.github.com/users/hakamine/repos","events_url":"https://api.github.com/users/hakamine/events{/privacy}","received_events_url":"https://api.github.com/users/hakamine/received_events","type":"User","site_admin":false},"labels":[{"id":604084802,"url":"https://api.github.com/repos/artefactual/deploy-pub/labels/P3","name":"P3","color":"e99695","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-09-27T22:01:17Z","updated_at":"2017-11-29T18:57:45Z","closed_at":null,"author_association":"CONTRIBUTOR","body":"When restarting the vagrant VM (vagrant halt -> vagrant up), archivematica services (archivematica-dashboard, archivematica-mcp-server, archivematica-mcp-client) require manual start up:\n$ sudo start archivematica-storage-service\n$ sudo start archivematica-mcp-server\n$ sudo start archivematica-mcp-client\n$ sudo start archivematica-dashboard\n\nSeeing the following errors in the upstart log files:\n\n> Invalid value for chdir: /usr/lib/archivematica/storage-service\n> Error: can't chdir to '/usr/lib/archivematica/storage-service'\n> \n> Invalid value for chdir: /usr/share/archivematica/dashboard\n> Error: can't chdir to '/usr/share/archivematica/dashboard'\n> \n> /proc/self/fd/9: 4: /proc/self/fd/9: /usr/lib/archivematica/MCPServer/archivematicaMCP.py: not found\n> \n> /proc/self/fd/9: 7: /proc/self/fd/9: /usr/lib/archivematica/MCPClient/archivematicaClient.py: not found\n"},"comment":{"url":"https://api.github.com/repos/artefactual/deploy-pub/issues/comments/347960546","html_url":"https://github.com/artefactual/deploy-pub/issues/22#issuecomment-347960546","issue_url":"https://api.github.com/repos/artefactual/deploy-pub/issues/22","id":347960546,"user":{"login":"hakamine","id":10160634,"avatar_url":"https://avatars3.githubusercontent.com/u/10160634?v=4","gravatar_id":"","url":"https://api.github.com/users/hakamine","html_url":"https://github.com/hakamine","followers_url":"https://api.github.com/users/hakamine/followers","following_url":"https://api.github.com/users/hakamine/following{/other_user}","gists_url":"https://api.github.com/users/hakamine/gists{/gist_id}","starred_url":"https://api.github.com/users/hakamine/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hakamine/subscriptions","organizations_url":"https://api.github.com/users/hakamine/orgs","repos_url":"https://api.github.com/users/hakamine/repos","events_url":"https://api.github.com/users/hakamine/events{/privacy}","received_events_url":"https://api.github.com/users/hakamine/received_events","type":"User","site_admin":false},"created_at":"2017-11-29T18:57:45Z","updated_at":"2017-11-29T18:57:45Z","author_association":"CONTRIBUTOR","body":"I did a quick test on trusty (upstart), and it looks like adding a `vagrant-mounted` condition to the `start on` statement ( as described in http://razius.com/articles/launching-services-after-vagrant-mount/ ) in the archivematica upstart files (/etc/init/archivematica-dashboard.conf, etc) helps with the issue. I am dubious about where could be the best place to fix it, should we fix in the [ansible-archivematica-src](https://github.com/artefactual-labs/ansible-archivematica-src) role or in the playbook (adding a few tasks after the ansible-archivematica-src role is done)? "}}
{"actor":{"display_login":"hakamine"}}