We had this issue too. I agree with the post below that it could be
message size. However, if it's just past asups that were too large
because of the messages file (or one of the other attachments), you can
set the autosupport.content size to minimal to delete all the queued
asups, then "doit" to generate one without the attachments to see if you
receive it, then put the content back to complete. It cleared the issue
on one of our NearStores....the other one appears to have a "corrupt"
character in the data chunk as viewed from the smtp server logs.
-----Original Message-----
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]
On Behalf Of Sphar, Mike
Sent: Tuesday, February 27, 2007 2:19 PM
To: toasters@mathworks.com
Subject: RE: autosupport stops functioning
I don't think this is the same problem as the one originally posted, but
we once had a similar problem here where autosupport messages stopped
being received by netapp because our mail gateway was rejecting all
messages larger than a certain size. We didn't even know they were
bouncing (we weren't getting the bounces) until one of the mail admins
finally said something about it.
--
Michael W. Sphar - IS&T - Lead Systems Administrator
SMBU Engineering Support Services, BMC Software
-----Original Message-----
From: owner-toasters@mathworks.com [mailto:owner-toasters@mathworks.com]
On Behalf Of Stephen C. Losen
Sent: Tuesday, February 27, 2007 6:55 AM
To: Leeds, Daniel
Cc: toasters@mathworks.com
Subject: Re: autosupport stops functioning
>
> anyone else have this happen?
>
> suddenly one of our filers stops generating autosupport messages.
both autosupport.enable and autosupport.support.enable are on. if
i generate a test email with the autosupport.doit option nothing
happens.
not even a failed message, the console just sits there as if i never
generated one.
>
> needless to say neither netapp or our email server gets anything from
this filer and nothing hits the console about generating any
autosupport
emails.
>
>
One of our filers stopped sending weekly autosupports because
the /etc/messages file was huge (170MB). It gets sent to netapp
as part of the autosupport. I got an automatic email
from Netapp support telling me that they hadn't received an
autosupport for two weeks. Buried in my huge /etc/messages
file was an error indicating that autosupport had failed, but
no reason why.
This particular filer holds our home directories and gets a lot of
CIFS logins, which we want to log. We have enabled CIFS login
tracing, which is very verbose.
I used /etc/syslog.conf to divert the CIFS auth messages to another
file:
*.warning;auth.none /dev/console
*.info;auth.none /etc/messages
auth.info /etc/cifs_auth_log
I rotate the cifs_auth_log with a cron job because I think ONTAP
will only rotate /etc/messages.
Now /etc/messages only grows to about 200K and autosupport is working
again.
Steve Losen scl@virginia.edu phone: 434-924-0640
University of Virginia ITC Unix Support
