Mailhog related issue when 'vagrant up'

trellis
1

Keep failing when ‘vagrant up’. rest of the process has passed but keep getting below message and xxxx.dev won’t work yet. :frowning:

TASK [mailhog : Download MailHog and mhsendmail binaries.] *********************
System info:
Ansible 2.2.1.0; Vagrant 1.9.2; Darwin
Trellis at “Allow for per-project packagist.com authentication”

failed to create temporary content file: (‘The read operation timed out’,)
failed: [default] (item={u’url’: u’https://github.com/mailhog/MailHog/releases/download/v0.2.0/MailHog_linux_amd64’, u’dest’: u’/opt/mailhog/mailhog’}) => {“failed”: true, “item”: {“dest”: “/opt/mailhog/mailhog”, “url”: “https://github.com/mailhog/MailHog/releases/download/v0.2.0/MailHog_linux_amd64”}}

1 Like
2

Related issue? https://github.com/ansible/ansible/issues/18894

1 Like
3

As a first step, I’d just try vagrant provision again. It’s almost always a temporary issue with connectivity, or GitHub, something like that. – ref

2 Likes
4

Worked!!! Thanks! It was ansible issue!

1 Like
5

FYI also having the same issue today. Ran sudo vagrant provision 4 times with no difference. Previously it worked so hoping this is about connectivity but not sure.

failed to create temporary content file: ('The read operation timed out',)
failed: [default] (item={u'url': u'https://github.com/mailhog/mhsendmail/releases/download/v0.2.0/mhsendmail_linux_amd64', u'dest': u'/opt/mailhog/mhsendmail'}) => {"failed": true, "item": {"dest": "/opt/mailhog/mhsendmail", "url": "https://github.com/mailhog/mhsendmail/releases/download/v0.2.0/mhsendmail_linux_amd64"}}
	to retry, use: --limit @/Volumes/EKA2017/eka/eka-client/trellis/dev.retry

PLAY RECAP *********************************************************************
default                    : ok=36   changed=0    unreachable=0    failed=1   

Ansible failed to complete successfully. Any error output should be
visible above. Please fix these errors and try again.

EDIT: And 10 minutes later + deleting and updating dependencies it’s working again.

6

@krishaamer Just a guess, but it looks like your issue may have been that you were having trouble connecting to GitHub. It looks like it was trying to read from a remote URL and that read timed out.

1 Like