Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Mailcatcher failing install #333

Closed
cmosguy opened this issue May 15, 2014 · 6 comments
Closed

Mailcatcher failing install #333

cmosguy opened this issue May 15, 2014 · 6 comments

Comments

@cmosguy
Copy link

cmosguy commented May 15, 2014

Firstly, I am noticing that when installing ruby I need to > 385MB for the vagrant session.

When going to the point of installing mailcatcher I see:

Installing Mailcatcher
Reading package lists...
Building dependency tree...
Reading state information...
libsqlite3-dev is already the newest version.
0 upgraded, 0 newly installed, 0 to remove and 21 not upgraded.
Building native extensions. This could take a while...
ERROR: Error installing mailcatcher:
ERROR: Failed to build gem native extension.
/usr/bin/ruby1.9.1 extconf.rb
/usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require: cannot load such file -- mkmf (LoadError)
from /usr/lib/ruby/1.9.1/rubygems/custom_require.rb:36:in require
from extconf.rb:2:in `

'
Gem files will remain installed in /var/lib/gems/1.9.1/gems/eventmachine-1.0.3 for inspection.

@fideloper
Copy link
Owner

Thanks! I've added a note about the memory issue in the issue related to this (#312). Keep track of #312 for this!

@cmosguy
Copy link
Author

cmosguy commented May 19, 2014

@fideloper i did a test where I logged into the guest the box and copied over the script using wget for mailcatcher.sh. Then I ran the script in the guest machine and it worked! Do you know why it is failing here during the provisioning? Is this information useful?

@fideloper
Copy link
Owner

It is useful, thank you!

So far I've seen a few cases failing on provisioning but NOT after provisioning:

  1. VM exhausts its allocated memory (I'm not sure if this is a bug in newer Vagrant, related to Ubuntu 14.04 or if something else is going on)
  2. Apt-get repositories fail to install without the --force-yes option, due to some issue with verifying packages via their public keys
  3. Third-party package aren't yet up to date for Ubuntu 14.04 (this would happen regardless of during provisioning or after I think, however)

It sounds like you might be running into 1 and 3?

@cmosguy
Copy link
Author

cmosguy commented May 19, 2014

are you having the same error when you run your provisions?

On Mon, May 19, 2014 at 7:30 AM, Chris Fidao [email protected]:

It is useful, thank you!

So far I've seen a few cases failing on provisioning but NOT after
provisioning:

  1. VM exhausts its allocated memory (I'm not sure if this is a bug in
    newer Vagrant, related to Ubuntu 14.04 or if something else is going on)
  2. Apt-get repositories fail to install without the --force-yesoption, due to some issue with verifying packages via their public keys
  3. Third-party package aren't yet up to date for Ubuntu 14.04

It sounds like you might be running into 1 and 3?


Reply to this email directly or view it on GitHubhttps://github.com//issues/333#issuecomment-43511036
.

@fideloper
Copy link
Owner

I haven't tried mailcatcher, but everyone else is having issues with it as well.

Memory issues are currently happening when installing composer and laravel/symfony using HHVM (but not during normal installations).

I use --force-yes in most installers that also include a new repository (PHP, mysql, mariadb, nginx, apache) so that has been less of an issue.

@allebb
Copy link

allebb commented May 21, 2014

FYI... I'm also having the issue with Mailcatcher, most annoying :( - I love that program! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants