search

ARTbio / GalaxyKickStart

Ansible playbooks for Galaxy Server deployment
GNU General Public License v3.0
24 stars 22 forks source link

In PR #129, problem with TASK [artimed_extras : Restart/start supervisor tasks] confirmed #130

Closed drosofff closed 8 years ago

drosofff commented 8 years ago

with PR #129

with a t2.small (1 proc, 2G) or a t2.medium, same error on fresh install

TASK [artimed_extras : Restart/start supervisor tasks] *************************
failed: [52.201.220.207] => (item={u'state': u'restarted', u'name': u'proftpd'}) => {"failed": true, "item": {"name": "proftpd", "state": "restarted"}, "msg": "proftpd: stopped\nproftpd: ERROR (abnormal termination)\n"}
ok: [52.201.220.207] => (item={u'state': u'started', u'name': u'munge'})
ok: [52.201.220.207] => (item={u'state': u'started', u'name': u'nginx'})

RUNNING HANDLER [galaxyprojectdotorg.galaxy : restart galaxy] ******************

RUNNING HANDLER [galaxyprojectdotorg.galaxy : email administrator with changeset id] ***
    to retry, use: --limit @galaxy.retry

PLAY RECAP *********************************************************************
52.201.220.207             : ok=115  changed=70   unreachable=0    failed=1
mvdbeek commented 8 years ago

okay, so this must have something to do with the masquerade setting ...

mvdbeek commented 8 years ago

Okay, I got it, it's a problem in the startup order! Supervisor gets started in the ansible-galaxy-extras role, but the environmental variables only get installed afterwards, so a supervisor restart should be enough. And indeed, this is only a problem when using the nat_masquerade option.