AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20080208115529.57e87eed@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<john.keiffer@onstor.com>,<rendell.fong@onstor.com>,<vikas.saini@onstor.com>,<sandrine.boulanger@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E08350F9D@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 8 Feb 2008 11:56:28 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "John Keiffer" <john.keiffer@onstor.com>
Cc: "Rendell Fong" <rendell.fong@onstor.com>, "Vikas Saini"
 <vikas.saini@onstor.com>, "Sandrine Boulanger"
 <sandrine.boulanger@onstor.com>
Subject: Re: 2 autosupport emails again, this time on Cougar system with Sub
 7
Message-ID: <20080208115628.2a9d08a1@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E08350F9D@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E08350F38@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E03B1C047@onstor-exch02.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E08350F9D@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

On Fri, 8 Feb 2008 11:05:37 -0800 "John Keiffer"
<john.keiffer@onstor.com> wrote:

> Well... after editing the autosupport schedule in the nfx shell, I got
> only 1 message as expected. So clearly something is going on... 
> 
>  
> 
> FOUND IT!
> 
>  
> 
> The first crontab below is from earlier today, the second one is from
> just now after editing the autosupport schedule. So the problem is
> that this one entry needs to be deleted from the crontab in future
> builds or whatever. All references to /usr/local/agile should be
> gone. Right? If I change the schedule back to 8am, then tomorrow I
> will wonder why I'm getting 2 emails again...

This almost certainly an artifact of the fact that we have been
"refreshing" NFS root systems with each submittal, instead of starting
over from scratch, which is what we should have been doing until now.

The old crontab entry was probably mis-modified by the code which is
not expecting the old path.

Modify the "two emails" bug, and make it against upgrade.  Upgrade
process needs to wipe out the old crontab file and let emrscron create
a new one.


> What should we do about the defect I closed yesterday? Should I open a
> new one or get it re-opened?
> 
>  
> 
> #minute hour    mday    month   wday    command
> 
>  
> 
> 0       8       *       *       *       /usr/local/agile/bin/ascron
> <-- this appears to be the defect right???
> 
> */30    *       *       *       *       /etc/cron.hourly/email 
> 
>  
> 
> # gather config every day (at 23:05)
> 
> 5       23      *       *       *       /onstor/bin/emrscron -g config
> 
>  
> 
> # gather stats every hour (on the half hour)
> 
> 30      *       *       *       *       /onstor/bin/emrscron -g stats
> 
>  
> 
> # gather h_res_stats data every 3 min
> 
> */3     *       *       *       *       /onstor/bin/emrscron -g
> h_res_stats
> 
>  
> 
> # keep the last 7 days of config and stats files (removing excess
> daily at 00:53)
> 
> 53      0       *       *       *       /onstor/bin/emrscron -t
> config; /onstor/bin/emrscron -t stats
> 
>  
> 
> # roll the log files for h_res_stats and keep only 7 log files around;
> send files to onstor
> 
> 59      23      *       *       *       /onstor/bin/emrscron -t
> h_res_stats; /onstor/bin/emrscron -s all
> 
>  
> 
> # send the kpi file every hour (the actual minute of this cron job is
> random; seeded by the mac address, so not all field machines send at
> the same time)
> 
> 29      *       *       *       *       /onstor/bin/emrscron -s
> kpi_stats
> 
> 0       8       *       *       *       /onstor/bin/ascron
> 
> 15      *       *       *       *       /onstor/bin/sanmcron local-nis
> 
> 45      *       *       *       *       /onstor/bin/sanmcron local-win
> 
> 30      *       *       *       *       /onstor/bin/sanmcron m1
> 
> 0       *       *       *       *       /onstor/bin/sanmcron jk-dmip1
> 
> 30      *       *       *       *       /onstor/bin/sanmcron jk-dmip2
> 
>  
> 
> #minute hour    mday    month   wday    command
> 
> 0       8       *       *       *       /usr/local/agile/bin/ascron
> 
> */30    *       *       *       *       /etc/cron.hourly/email
> 
>  
> 
> # gather config every day (at 23:05)
> 
> 5       23      *       *       *       /onstor/bin/emrscron -g config
> 
>  
> 
> # gather stats every hour (on the half hour)
> 
> 30      *       *       *       *       /onstor/bin/emrscron -g stats
> 
>  
> 
> # gather h_res_stats data every 3 min
> 
> */3     *       *       *       *       /onstor/bin/emrscron -g
> h_res_stats
> 
>  
> 
> # keep the last 7 days of config and stats files (removing excess
> daily at 00:53)
> 
> 53      0       *       *       *       /onstor/bin/emrscron -t
> config; /onstor/bin/emrscron -t stats
> 
>  
> 
> # roll the log files for h_res_stats and keep only 7 log files around;
> send files to onstor
> 
> 59      23      *       *       *       /onstor/bin/emrscron -t
> h_res_stats; /onstor/bin/emrscron -s all
> 
>  
> 
> # send the kpi file every hour (the actual minute of this cron job is
> random; seeded by the mac address, so not all field machines send at
> the same time)
> 
> 29      *       *       *       *       /onstor/bin/emrscron -s
> kpi_stats
> 
> 15      *       *       *       *       /onstor/bin/sanmcron local-nis
> 
> 45      *       *       *       *       /onstor/bin/sanmcron local-win
> 
> 30      *       *       *       *       /onstor/bin/sanmcron m1
> 
> 0       *       *       *       *       /onstor/bin/sanmcron jk-dmip1
> 
> 30      *       *       *       *       /onstor/bin/sanmcron jk-dmip2
> 
> 50      10      *       *       *       /onstor/bin/ascron
> 
>  
> 
> ________________________________
> 
> From: Rendell Fong 
> Sent: Friday, February 08, 2008 10:37 AM
> To: John Keiffer
> Subject: RE: 2 autosupport emails again, this time on Cougar system
> with Sub 7
> 
>  
> 
> Yes you can try.  The only difference is (should be) that cron invokes
> the ascron cmd based on the schedule rather than you doing it from the
> cmd line.
> 
>  
> 
> ________________________________
> 
> From: John Keiffer 
> Sent: Friday, February 08, 2008 10:33 AM
> To: Rendell Fong
> Subject: RE: 2 autosupport emails again, this time on Cougar system
> with Sub 7
> 
>  
> 
> Ascron gave me only 1 email.
> 
>  
> 
> Should I try moving the schedule again, to see if I can get 2 again at
> say 10:40am?
> 
>  
> 
> ________________________________
> 
> From: Rendell Fong 
> Sent: Friday, February 08, 2008 10:30 AM
> To: John Keiffer
> Subject: RE: 2 autosupport emails again, this time on Cougar system
> with Sub 7
> 
>  
> 
> I don't seem to have this problem.
> 
> Can you try running "ascron" from the root shell?
> 
> Does that give you 2 emails as well?
> 
>  
> 
> ________________________________
> 
> From: John Keiffer 
> Sent: Friday, February 08, 2008 8:38 AM
> To: Rendell Fong; Andy Sharp
> Cc: dl-QA
> Subject: 2 autosupport emails again, this time on Cougar system with
> Sub 7
> 
>  
> 
> I got two emails from my Cougar system now that we have Sub 7. So
> Autosupport is working, but I still don't see why we are getting 2
> emails when only 1 should show up.
> 
>  
> 
> I swear that this is going to drive me crazy (I closed the defect
> yesterday as not reproducible)... Doesn't anyone else have this
> problem? Would everyone please enable autosupport and emrs on all
> your systems and set up a basic schedule?
> 
>  
> 
>  
> 
>  
> 
> 02/08/08 08:34:40 g6r10 diag> autosupport show config
> 
> Auto Support configuration
> 
> --------------------------
> 
> Auto Support State: Enabled
> 
> Auto Support TO address: jkeiffer@onstor.com
> 
> Auto Support NOTETO address: --Not-Set--
> 
> Auto Support FROM address: g6r10@onstor.com
> 
> Auto Support MAIL SERVER: 0.0.0.0
> 
> Auto Support Schedule:
> 
>                min  : 0
> 
>                hour : 8
> 
>                mday : *
> 
>                month: *
> 
>                wday : *
> 
>  
> 
> I am still getting these messages, and I thought this was supposed to
> stop happening with Sub7?
> 
>  
> 
> g6r10:~# l /var/spool/exim4/msglog/
> 
> total 80
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 14:17 1JNF3H-0005rb-8Q
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 15:17 1JNFzM-00023b-0U
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 16:17 1JNGvP-0003k4-Pf
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 17:17 1JNHrU-0005GG-0i
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 18:17 1JNInX-0006lo-FY
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 19:17 1JNJjc-0008GI-GB
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 20:17 1JNKff-0001XG-7T
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 21:17 1JNLbk-00030R-1G
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 22:17 1JNMXn-0004ST-IA
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  7 23:17 1JNNTr-0000ME-Ec
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 00:17 1JNOPw-0001oL-2F
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 01:17 1JNPLz-0003Kg-Az
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 02:17 1JNQI3-0004jo-Rl
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 03:17 1JNRE8-0006H6-66
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 04:17 1JNSAB-0007mn-Kz
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 05:17 1JNT6F-0000v1-72
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 06:17 1JNU2J-0002H3-Rl
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 06:25 1JNUAY-0002WH-FE
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 07:17 1JNUyN-0003eW-9L
> 
> -rw-r----- 1 Debian-exim Debian-exim 192 Feb  8 08:17 1JNVuR-0004ys-Gv
> 
>  
> 
> Thanks,
> 
> John
> 
