Date:  Tue, 8 Apr 2008 10:06:46 -0500
From:  "Gerald Waugh" <gwaugh (at mark) frontstreetnetworks.com>
Subject:  [coba-e:12494] Re: Unable to lock - not running.
To:  <coba-e (at mark) bluequartz.org>
Message-Id:  <07a001c8998a$2cff13f0$0101a8c0@systemax>
In-Reply-To:  
X-Mail-Count: 12494

Gerald Waugh wrote;
> Gustavo Silva [mailto:pseudo (at mark) zbronx.com] 
> > 
> > I started receiving the same message after doing the 
> > flat-file password 
> > db upgrade procedure. Or it was a BIG coincidence =)
> > Anyway... Is this your case?
> > 
>  
> > JMG-Support escreveu:
> > > I am getting this email from the server.  Does anyone know 
> > how to correct
> > > this problem.  It started Sunday.
> > >
> > > From: Cron Daemon 
> > > Subject: Cron <root@ns1> /usr/bin/php -q 
> > /usr/local/mailwatch/mailq.php
> > > MSG: Unable to lock - not running.
> > >
> Try 
>   chmod 666 /var/run/mailq.lock
> Might should be 644, but 666 seems to cure the problem
> Not sure if it might get changed on a reboot...
> 
BTW mailq.php is called from;
 /etc/cron.d/mailwatch-mailq
Which reads;
 10 * * * *      root    /usr/bin/php -q /usr/local/mailwatch/mailq.php

Gerald