Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2020-07-25 Thread Cron Daemon 
/usr/local/bin/runRuleQArefresh.sh: line 64: syntax error near unexpected token 
`then'
/usr/local/bin/runRuleQArefresh.sh: line 64: ` -ne 0 ]]; then'

Re: Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-02 Thread Paul Stead 
On Sun, 2 Jun 2019 at 18:04, Kevin A. McGrail  wrote:

> with just the cron log output :-)
>

I don't know to commend you or commit you ;-)

Re: Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-02 Thread Kevin A. McGrail 
I appreciate the noise.

For the record, when the system catastrophically failed, I rebuilt it
from the ground up on a new server with just the cron log output :-)

On 6/2/2019 3:41 AM, Paul Stead wrote:
> Looks good now - I've made the lock fail error a bit quieter but the lock
> fails since my last email are valid - just the hourly is running for long
> time -
>
> ---8<---
> automc   20493  5.3  0.1  43140 21496 ?SN   04:05  11:34
> /usr/bin/perl -w
> /usr/local/spamassassin/automc/svn/masses/rule-qa/corpus-hourly
> --dir=/usr/local/spamassassin/automc/rsync/corpus
> pds@sa-vm1:~$ date
> Sun Jun  2 07:41:23 UTC 2019
> ---8<---
>
> Paul
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-02 Thread Cron Daemon 
/usr/local/bin/runRuleQArefresh.sh: line 71: 0: command not found

Re: Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-02 Thread Paul Stead 
Looks good now - I've made the lock fail error a bit quieter but the lock
fails since my last email are valid - just the hourly is running for long
time -

---8<---
automc   20493  5.3  0.1  43140 21496 ?SN   04:05  11:34
/usr/bin/perl -w
/usr/local/spamassassin/automc/svn/masses/rule-qa/corpus-hourly
--dir=/usr/local/spamassassin/automc/rsync/corpus
pds@sa-vm1:~$ date
Sun Jun  2 07:41:23 UTC 2019
---8<---

Paul

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
Exit: ENO_LOCKFAIL(2)

Re: Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Paul Stead 
This should be sorted now - thankfully due to the changes, a missed
mass-check or two isn't a problem (unless it lasts more than 3 days :) )



Paul

On Sat, 1 Jun 2019 at 14:08, Kevin A. McGrail  wrote:

> Good signs that something is working because things are breaking, Paul.
> :-)
>
> Thanks for working on this and I just wanted to +1 to break some eggs to
> make some omelets.  David and I concur that this scripts are one of the
> more complicated things we've worked on in our lives so don't be afraid
> to get dirty!
>
> On 6/1/2019 9:05 AM, Cron Daemon wrote:
> > lock failed, PID 30743 is active
> > Exit: ENO_LOCKFAIL(2)
>
>
> --
> Kevin A. McGrail
> Member, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
/usr/local/bin/runRuleQArefresh.sh: exit trap: line 4: syntax error near 
unexpected token `fi'
/usr/local/bin/runRuleQArefresh.sh: exit trap: line 4: `  fi'

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 13048 is active
Exit: ENO_LOCKFAIL(2)

Re: Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Kevin A. McGrail 
Good signs that something is working because things are breaking, Paul.  :-)

Thanks for working on this and I just wanted to +1 to break some eggs to
make some omelets.  David and I concur that this scripts are one of the
more complicated things we've worked on in our lives so don't be afraid
to get dirty!

On 6/1/2019 9:05 AM, Cron Daemon wrote:
> lock failed, PID 30743 is active
> Exit: ENO_LOCKFAIL(2)


-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
/usr/local/bin/runRuleQArefresh.sh: line 80: RC = 0: command not found

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
lock failed, PID 30743 is active
Exit: ENO_LOCKFAIL(2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
Removing lock. Exit: ENO_SUCCESS(0)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-06-01 Thread Cron Daemon 
Removing lock. Exit: ENO_SUCCESS(0)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-05-31 Thread Cron Daemon 
/usr/local/bin/runRuleQArefresh.sh: line 29: nal: command not found
/usr/local/bin/runRuleQArefresh.sh: line 34: : No such file or directory
/usr/local/bin/runRuleQArefresh.sh: line 41: syntax error near unexpected token 
`else'
/usr/local/bin/runRuleQArefresh.sh: line 41: `else'
Removing lock. Exit: (2)

Cron . /etc/profile; /usr/local/bin/runRuleQArefresh.sh > /dev/null

2019-05-25 Thread Cron Daemon 
/usr/local/bin/runRuleQArefresh.sh: line 28:  7749 Killed  
$HOME/svn/masses/rule-qa/corpus-hourly --dir=$HOME/rsync/corpus > ${LOG}.tmp 
2>&1