Hi Jacek,
thanks for sharing your experience! I think we will choose an upgrade over just rebooting the filer, as well.
Cheers
Jochen
-----Original Message----- From: Jacek [mailto:janosldx@gazeta.pl] Sent: Wednesday, January 13, 2010 9:52 PM To: Willeke, Jochen Cc: toasters@mathworks.com Subject: Re: Autosupport post - soo_write Failure
Hochen,
From my experience the only solution is an upgrade. We faced this issue for several months and NetApp could not find any resolution for us (yes, we tried to delete some asup filers but with no effect). Reboot can be considered a relief only because the same issue is back quickly. If my memory serves me well, in one case (and we had several ones in our ~100 filers environment) asup was hung again in just a couple of hours after reboot. Our filers were upgraded 0.5 - 1 year ago and we have not registered any single asup issue since then.
Best regards,
Jacek
Willeke, Jochen wrote:
Hi Jacek,
we do have 7.2.4 in place. The bug is known to me, sadly it requires a reboot to solve this situation and this is not an option at the moment.
Cheers and thanks
Jochen
-----Original Message----- From: Jacek [mailto:janosldx@gazeta.pl] Sent: Tuesday, January 12, 2010 9:50 PM To: toasters@mathworks.com Cc: Willeke, Jochen Subject: Re: Autosupport post - soo_write Failure
Jochen,
Which ONTAP version are you running? There is a bug #263066 in some 7.2 releases that causes asup process hanging. You can reboot the filer that will resume asup functionality but you have no warranty that it will not hang again in few weeks or even few hours. The only real solution is to upgrade to bug free release.
Best regards,
Jacek Nogala
Willeke, Jochen wrote:
Hi,
tested myself, the deletion did not solve the problem, sadly....
Searching for other solutions besides rebooting the system.
Regards
Jochen
-----Original Message----- From: Willeke, Jochen Sent: Monday, January 11, 2010 4:16 PM To: toasters@mathworks.com Subject: Autosupport post - soo_write Failure
Hey Toasters,
I do have a question regarding a problem with autosupport from one filer. We use the post-method, due to mail-delivery-restrictions. Since some days we do see error-msg like these:
[filername: asup.log.socket.err.post:error]: soo_write failed in autosupport post due to the error - Resource temporarily unavailable.
Sadly this seems to be related to a bug, which needs a reboot which cannot be done in the next days. I found out that there are two files under /etc/log/autosupport which have the ending .post. Those files are the directly from the point in time when autosupport stopped working and start spaming the messages-file.
My question is, are those files the blocking point, and can the deletion of the files solve this issue?? The files do have size 0kb and now content. Anybody ever come across this?
Cheers and thanks in advance
Jochen