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

Hardcoded harvard email server, installation freezes #18

Closed
brainstorm opened this issue Jul 1, 2014 · 5 comments
Closed

Hardcoded harvard email server, installation freezes #18

brainstorm opened this issue Jul 1, 2014 · 5 comments

Comments

@brainstorm
Copy link

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 03:49 min
[INFO] Finished at: 2014-07-01T00:19:54-08:00
[INFO] Final Memory: 25M/124M
[INFO] ------------------------------------------------------------------------
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Use of uninitialized value $user_entry in string ne at ./install line 229.
Could not establish connection to mail.hmdc.harvard.edu,
the address you provided for your Mail server.
Please select a valid mail server, and try again.

The block of text above keeps repeating indefinitely.

@brainstorm brainstorm changed the title Hardcoded harvard email server Hardcoded harvard email server, installation freezes Jul 1, 2014
@pdurbin
Copy link
Member

pdurbin commented Jul 1, 2014

There are a couple ways we could handle this. I'm assuming @brainstorm is using the installer from within vagrant based on #16 and #17. My main interest is in making sure vagrant up completes successfully.

My first thought: How about we provide a flag for the installer to specify the SMTP server like this: ./install --mailserver smtp.example.com. Then we would need a way for the user to specify the mailserver before running vagrant up. Perhaps we could use an environment variable, as in this example: http://stackoverflow.com/questions/13065576/override-vagrant-configuration-settings-locally-per-dev/13287035#13287035

@brainstorm
Copy link
Author

What you propose is totally doable and in fact did it quite recently myself over here:

https://github.com/brainstorm/ansible-neurostars.org/blob/master/Vagrantfile

The alternative is to just leave it unconfigured by default. For development purposes (your objective with this Vagrantbox maybe), it's enough, imho.

When an admin installs, say, postfix, it's not configured by default either (example.com).

@pdurbin
Copy link
Member

pdurbin commented Jul 1, 2014

As of the commit above you should see this:

$ vagrant up
MAIL_SERVER environment variable not specified. Using localhost by default.
To specify it in bash: export MAIL_SERVER=localhost

For the record, the vagrant environment is still a little experimental (though I did recently document it a bit in the dev guide). Mostly I use it to run a few integration tests and to document the setup programmatically. In the future, I'd like to use it to test mod_shib, I think.

I'm going to close this issue but @brainstorm and others should feel free to comment if the fix isn't suitable. At least now vagrant up should work fine from networks other than the one I sit on all day. Thanks for the bug report @brainstorm!

@pdurbin pdurbin closed this as completed Jul 1, 2014
@brainstorm
Copy link
Author

Thanks @pdurbin!

By the way, see you in #BOSC2014 dinner if you are going. I would like to talk with you about DataVerse.

I just pulled your changes, but there are still issues that prevent a clean instantiation of the VM:

==> default: Invalid Glassfish directory !
==> default: Enter the root directory of your Glassfish installation:
==> default: (Or ctrl-C to exit the installer):
==> default: Invalid Glassfish directory !
==> default: Enter the root directory of your
==> default: p at ./install line 751.
==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 751.
==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 746.
==> default: Use of uninitialized value $glassfish_dir in scalar chop at ./install line 751.
==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 751.
==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 746.
==> default: Use of uninitialized value $glassfish_dir in scalar chop at ./install line 751.
==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 751.
==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 746.

(...)

==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 746.
==> default: Use of uninitialized value $glassfish_dir in scalar chop at ./install line 751.
==> default: Use of uninitialized value $glassfish_dir in concatenation (.) or string at ./install line 751.
==> default: Use of
==> default: Forcing shutdown of VM...
==> default: Destroying VM and associated drives...
==> default: Running cleanup tasks for 'shell' provisioner...
==> default: Running cleanup tasks for 'shell' provisioner...
==> default: Running cleanup tasks for 'shell' provisioner...
==> default: Running cleanup tasks for 'shell' provisioner...
/Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/buffered_io.rb:99:in `send': Broken pipe - send(2) (Errno::EPIPE)
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/buffered_io.rb:99:in `send_pending'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:244:in `block in postprocess'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:243:in `each'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:243:in `postprocess'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:211:in `process'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in `block in loop'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in `loop'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/session.rb:169:in `loop'
    from /Applications/Vagrant/embedded/gems/gems/net-ssh-2.9.1/lib/net/ssh/connection/channel.rb:269:in `wait'

@pdurbin
Copy link
Member

pdurbin commented Jul 14, 2014

By the way, see you in #BOSC2014 dinner if you are going. I would like to talk with you about DataVerse.

/me looks at http://www.open-bio.org/wiki/BOSC_2014

Hmm, no plans to go but I'm (almost) always happy to chat about Dataverse. The best way to reach me is the #dataverse IRC channel on freenode: http://webchat.freenode.net/?channels=dataverse http://irclog.iq.harvard.edu/dataverse/today

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

2 participants