Monit program manual#
Monit program code#
Monit program series#

It’s a good idea to create Capistrano recipes for setting up the server, like we did in episode 337. We could set up this configuration directly on the server by adding files to the /etc/monit/conf.d directory but it’s generally better not to do extensive configuration on the server but instead to put configuration files within our Rails application under source control. Monit will then check this process and we can tell it what to do if the process fails. This tells us that we can run the check process command to do this, passing in a unique name and a pidfile.

Monit program manual#

The manual is a good resource when editing the configuration and there’s a Configuration Examples page that is useful. That’s all we need to do to this configuration file and next we’ll instruct Monit to monitor our Rails application. We don’t have any files in this directory but if we want to configure Monit for various processes such as Nginx or Unicorn this is a good place to put them. The last line tells Monit to include any configuration files that appear in the conf.d directory. The next few lines configure various file paths and then we have an eventqueue setting that tells Monit to remember any alert messages that it can’t send over email. We’ll change this to 30 seconds so that the application is checked more frequently. The first line above tells Monit to run in the background and to perform a check every two minutes. Slots 100 # optionally limit the queue size If you still face any problems, drop a comment below, I’d be happy to help.Set daemon 120 # check services at 2-minute intervalsīasedir /var/lib/monit/events # set the base directory where events will be stored Monit should restart the process in 30 seconds. Now, reload monit and try killing the sidekiq process. $rvm_path/scripts/rvm cd /home/ubuntu/rails_project/ bundle exec sidekiqctl stop /home/ubuntu/rails_project/tmp/pids/sidekiq.pid 10'' as uid ubuntu as gid ubuntu Stop program = '/bin/bash -c 'export rvm_path=/home/ubuntu/.rvm. $rvm_path/scripts/rvm cd /home/ubuntu/rails_project bundle exec sidekiq -e production -L /home/ubuntu/rails_project/log/sidekiq.log -C /home/ubuntu/rails_project/config/sidekiq.yml -P /home/ubuntu/rails_project/tmp/pids/sidekiq.pid'' as uid ubuntu as gid ubuntu Start program = '/bin/bash -c 'export rvm_path=/home/ubuntu/.rvm. You may have to export your rvm_path variable and run the commands above as the user. error : 'sidekiq' process is not running If the process does not restart, and you see errors like these in log file – You can view the monit logfile at /var/log/monit.log Now, when you kill the sidekiq process on your server, it should restart automatically. To restart the monit daemon with updated configuration, run Next, you should check the syntax of your monit file using If multiple processes are being created, you should check whether the path to sidekiq pidfile is correct and the file is being updated properly. You can test out the start and stop commands in your terminal to see that they start and stop the correct sidekiq process, without creating multiple processes. Stop program = '/bin/bash -c ' cd /home/ubuntu/rails_project/ bundle exec sidekiqctl stop /home/ubuntu/rails_project/tmp/pids/sidekiq.pid 10'' Start program = '/bin/bash -c ' cd /home/ubuntu/rails_project bundle exec sidekiq -e production -L /home/ubuntu/rails_project/log/sidekiq.log -C /home/ubuntu/rails_project/config/sidekiq.yml -P /home/ubuntu/rails_project/tmp/pids/sidekiq.pid'' With pidfile /home/ubuntu/rails_project/tmp/pids/sidekiq.pid

Monit program code#

The timeout option lets you define the amount of time Monit will wait for the start/stop action to finish before giving up and reporting an error. The default is 30 seconds.Īssuming your home folder is /home/ubuntu and the path to your rails project is /home/ubuntu/rails_project, our code now looks like:

Monit program series#

The start_command and stop_command are series of commands to navigate to project folder and run sidekiq from bundler. The path_to_sidekiq_pid is usually found in rails_project/tmp/pids/sidekiq.pid Stop program = stop_command with timeout y Start program = start_command with timeout x You can set up Gmail to send notifications (A comprehensive list of examples can be found here) We’ll be editing this file to configure monit for Sidekiq monitoring. Monit’s behaviour is defined in a control file called monitrc which can be usually found in Monit can be installed with a simple command: It can send mail alerts or automatically restart processes as per configuration. Monit is a handy utility that can be used to monitor memory, processes or services on your Unix machine or server.