similar to: environment variables required for startup

Hello ~ I am using the Capistrano recipe outlined in this post to restart my backgroundrb server: http://rubyforge.org/pipermail/backgroundrb-devel/2007-February/000718.html My Version: ~~~~~~~~~~~~ task :before_restart, :roles => :app do restart_backgroundrb end task :start_backgroundrb, :roles => :app do sudo "nohup

Good time! After upgrading samba 4.5.10 to 4.9.13, name resolution in AD hangs. # /etc/init.d/samba status ?* status: crashed But the domain itself works, but hangs when resolving user names. What can be done? [2019/10/13 12:24:52.896473, 10, pid=17379, effective(0, 0), real(0, 0), class=ldb] ../lib/ldb-samba/ldb_wrap.c:77(ldb_wrap_debug) ? ldb: Added timed event

Is there any script guru on the list that can help me. I'm trying to start asterisk with nice -5. Normally the command would be: nice -5 asterisk but asterisk start from the scrip on Gentoo as -U asterisk -G asterisk Here is the script: =============== depend() { need net use zaptel } start() { local OPTS USER GROUP if [[ -n "${ASTERISK_NICE}" ]];

> Message: 2 > Date: Fri, 03 Dec 2004 10:10:35 +1300 > From: Paul <lists@loudas.com> > Subject: [Shorewall-users] another network to add > To: Shorewall List <shorewall-users@lists.shorewall.net> > Message-ID: <41AF84CB.5080304@loudas.com> > Content-Type: text/plain; charset=ISO-8859-1; format=flowed > > Hi Tom (and others) > encase you

I have this configuration: class monit { # Installing packages. package { "monit": ensure => latest; } file { "/etc/default/monit": owner => "root", group => "root", mode => "0644", source => "puppet:///monit/etc/default/monit", } file { "/etc/monit/monitrc": owner => "root", group =>

First off, a big thank you to Zed and the development team for mongrel and mongrel cluster. I''ve deployed it for two apps (through an apache 2.2 proxy) and it''s amazing how much snappier everything is. Previously we were using lighttpd and lighttpd-fastcgi proxying through apache 2.0, which was turning into a hassle for lots of reasons, most notably the ruby fcgi

I started emailing monit mailing list because I started getting this problem where I couldn''t start backgroundrb with monit anymore, thinking it was a monit problem. However, I back tracked a bit since I had added code to my project, and monit was able to start backgroundrb again. I seem to have zeroed in on the problem. I''m not sure where the problem lies - maybe monit or

Alright, I have googles and read through the docs on monit I get this error when adding -v starting monit monit: Cannot connect to the monit daemon. Did you start it with http support? monit: Cannot connect to the monit daemon. Did you start it with http support? Am I missing something here? set daemon 120 set logfile syslog facility log_daemon set mailserver localhost set httpd port 28212

Has anybody here tried the "Monit" utility (http://mmonit.com/monit/)? I need to set up some kind of "watchdog" functionality for a custom service otherwise started via init (i.e. via a script in /etc/init.d + rc*.d links managed by chkconfig) and it seems like this system may give me nearly what I want. However, something that concerns me about it, is that it appears to

Might there be anything CentOS related on why I cannot access the Monit GUI system on http://box-running-monit.com:2812 ? I am using a very basic /etc/monit.conf config, but I cannot get it serve the web page on my box The service start and stops fine (e.g. "/etc/init.d/monit start"), and I have it set to listen to port 2812 in the "/etc/monit.conf file" (so far, kept the

Monit 4.9, Mongrel 1.0.1, Rails 1.2.6, Mac OS X 10.4.11 (PPC) I don''t know whether this is a mongrel issue or a monit issue. I''m trying to poke my way around a system set up by someone else. I have no more experience w/ mongrel that local Rails dev at this point, and a conceptual understanding of how monit is working. I have the Deploying Rails beta book, and I''m

Hi, I try install python-psycopg2 with other packages, when run apt-get -y update returns the errors: err: /Stage[main]/Etc/Package[build-essential]/ensure: change from purged to present failed: Could not set ''present on ensure: Read-only file system - /tmp/puppet20120216-1063-18q7lsz-0 at /tmp/vagrant-puppet/manifests/vagrant.pp:15 err:

While I could figure this out, I''m asking here first to see if anyone has already dealt with/created this. I''m running a mongrel cluster, running 4 mongrels on ports 8001-4. I''m using capistrano to deploy. And I''d like to use monit to check to make sure everything is running nice. I''d like to have monit restart only single mongrels if they fail, and

Hi, was wondering if anyone else had a similar problem and knows why or a solution. basically my mongrels seems to work fine. i am running three clusters all which are monitored by monit. monit has the ability to restart a mongrel if it doesn''t pass a port connection test. so the problem is that after some time. aprox. 6hrs. to 20hrs. after clusters are started, the mongrels get

Hello, I''m trying to do this: service { monit: ensure => running, enable => true, hasrestart => true, if ($operatingsystem == ''centos'') { hasstatus => true, }, require => Package[''monit''], subscribe => File[''monit.conf''], } And it doesn''t work in

I am setting up dovecot 1.0-rc15 as a proxy. When I try to log in, I get errors such as the following: Dec 4 17:39:23 vega dovecot: Dovecot v1.0.rc15 starting up Dec 4 17:39:24 vega dovecot: auth-worker(default): mysql: Connected to localhost (ad_mail) Dec 4 17:39:31 vega dovecot: auth(default): client in: AUTH 1 PLAINservice=POP3 lip=xx.xx.xx.xx rip=xx.xx.xx.xx

With the latest version of Mongrel, will Mongrel reopen log files when sent a HUP signal? I would like to do a log rotate, but would prefer not to restart the mongrel instances as monit is watching after them all. monit is great for restarting the individual instances, but I would prefer not to do a restart all through monit. I would be curious if this is advisable. -- ----- Christopher

On one of my development servers mongrel dies when idle for any length of time. Since I''ve not been able to solve that problem I thought I''d route around it by using monit to kick things when necessary. My monitrc contains the following... -------------------------------------------------------------------------------- check process mongrel_8310 with pidfile

Hi all, I currently use puppet and cacti, and am in need of an alerting system for systems/services that are down. Alerts through cacti are a major pain, so I have begun looking at a small and simple tool called monit. Monit, however, seems to be doing a lot of things that puppet is already doing for me (such as checking if services are running and starting them if they aren''t, etc), so

Greetings - I dug around a bit and I couldn''t find a definitive answer to this question, apologies if it''s been covered before. A box running a apache 2.2 -> mongrel cluster for a rails app got power cycled at my ISP. Unfortunately monit couldn''t start the mongrel processes because the pid files were still there. Here is my monit config (for each mongrel