[gpfsug-discuss] Executing Callbacks on other Nodes

[Oesterlin, Robert]

Hi Roland

I ran into that issue as well – if you are running 6.3 you need to update to get to the later levels. RH 6.3 is getting a bit dated, so an upgrade might be a good idea – but I all too well how hard it is to push through those updates!

Bob Oesterlin
Sr Storage Engineer, Nuance HPC Grid

From: <gpfsug-discuss-bounces at spectrumscale.org<mailto:gpfsug-discuss-bounces at spectrumscale.org>> on behalf of Roland Pabel <dr.roland.pabel at gmail.com<mailto:dr.roland.pabel at gmail.com>>
Organization: RRZK Uni Köln
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>>
Date: Tuesday, April 12, 2016 at 8:25 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org<mailto:gpfsug-discuss at spectrumscale.org>>
Subject: Re: [gpfsug-discuss] Executing Callbacks on other Nodes

Hi Bob,

thanks for your remarks. I already understood that deadlocks are more timeouts
than "tangled up balls of code". I was not (yet) planning on changing the
whole routine, I'd just like to get a notice when something unexpected happens
in the cluster. So, first, I just want to write these notices into a file and
email it once it reaches a certain size.

From what you are saying, it sounds like it is worth upgrading to 4.1.1.x . We
are planning a maintenance next month, I'll try to get this into the todo-
list. Upgrading beyond this is going require a longer preparation, unless the
prerequisite of "RHEL 6.4 or later" as stated on the IBM FAQ is irrelevant.
Our clients still run RHEL 6.3.

Best regards,

Roland

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160412/180cbd6d/attachment.htm>