njam
commented
10 years ago I have the same behaviour.
It seems the Daemons.run_proc-call hangs when starting and stopping the daemon proc.
It doesn't matter what code the block contains (i.e. if I replace the RubyDNS::run_server with just loop { sleep 1 } I still see the same behaviour).
Within the daemons gem I tracked it down to call_as_daemon inside lib/daemons/daemonize.rb which looks like this:
def call_as_daemon(block, logfile_name = nil, app_name = nil)
rd, wr = IO.pipe
if tmppid = safefork
# parent
wr.close
pid = rd.read.to_i // <-- THIS LINE IS BLOCKING
rd.close
[...]
else
# child
rd.close
[...]
wr.write Process.pid
wr.close
[...]
endso basically the child process sends its PID through a pipe to the parent which reads it.
While debugging I noticed that the PID is sent into the pipe, but never received in the parent. So that rd.read-call hangs.
I can only reproduce this behaviour within the "vagrant ruby", by running bundle exec vagrant up. If I run the same code in my local ruby environment it doesn't hang.
Can anyone confirm this behaviour? I wanted to start using vagrant-dns just now, anyone using it for longer and can confirm this bug?
I noticed that the Gemfile.lock is gitignored. Since the gemspec uses git ls-files to populate gem.files I assume the gem doesn't include a lock-file. Therefore probably the newest version will be installed for all gems when installing the plugin?
fnordfish
I configured vagrant-dns according to instructions, but when bringing my machine up, the boot process hangs (the machine comes up successfully however, and DNS queries to it resolve).
This hang started happening only when I installed vagrant-dns, so I am thinking it is the culprit. Here's the behavior I've seen:
If I have a vagrant-dns server already running, the "vagrant up" process tries to kill it (I see messages from vagrant-dns to that effect). Then, I see in my process list that a new vagrant-dns is up. Then, everything hangs. If I press Ctrl-C, this is what I get: