Ruby on Rails, Running Guard, immediately dies with "Killed"

Question

I set the protection and spork according to the Rails Bates RailsCast (under Linux Mint 12), and the protection process shows "Killed" as soon as it starts. Running "exec exec exec --verbose" gives:

bunch of exec exec --verbose DEBUG (12:17:27): Executing the command: which notify-send

Guard uses NotifySend to send notifications.

Now Guard is watching "path_to_project"

DEBUG (12:17:27): Hook: start_begin done for Guard :: Spork

DEBUG (12:17:27): Executing the command: ps aux | awk '/ spork / &! / awk / {print $ 2;}'

DEBUG (12:17:27): Killing Spork servers with PID: 8884

Killed

I tried to fine-tune the values ​​in the Guard Gem documentation "Advanced Linux system setup" (max_queued_events and max_user_instances, max_users_watches). There is no joy there far above the default for all.

Any ideas? Thanks in advance if so. Google-fu has not yet shown anything useful for this particular problem.

Answer 1

I saw how it happened now. What you need to do is find the running spork process and kill it. For instance:

ps aux | grep spork

Note the pid of any active spork processes (first column). If it was 123, enter:

kill 123

And start the guard again.