Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[Mathias Dietz]

Hi Renar, 

the tsctl problem is described in APAR IV93896
https://www-01.ibm.com/support/docview.wss?uid=isg1IV93896

You can easily find out if your system has the problem: Run "tsctl 
shownodes up" and check if the hostnames are valid, if the hostnames are 
wrong/mixed up then you are affected.

This APAR has been fixed with 5.0.2 


Mit freundlichen Grüßen / Kind regards

Mathias Dietz

Spectrum Scale Development - Release Lead Architect (4.2.x)
Spectrum Scale RAS Architect
---
IBM Deutschland
Am Weiher 24
65451 Kelsterbach
Phone: +49 70342744105
Mobile: +49-15152801035
E-Mail: mdi...@de.ibm.com
-
IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Martina Koederitz, Geschäftsführung: Dirk 
WittkoppSitz der Gesellschaft: Böblingen / Registergericht: Amtsgericht 
Stuttgart, HRB 243294



From:   "Olaf Weiser" 
To: "Grunenberg, Renar" 
Cc: gpfsug main discussion list 
Date:   29/11/2018 09:39
Subject:Re: [gpfsug-discuss] Status for Alert: remotely mounted 
filesystem panic on accessing cluster after upgrading the owning cluster 
first
Sent by:gpfsug-discuss-boun...@spectrumscale.org



HI Tomer, 
send my work around wrapper to Renar.. I've seen to less data to be sure, 
that's the same (tsctl shownodes ...) issue 
but he'll try and let us know .. 






From:"Grunenberg, Renar" 
To:gpfsug main discussion list , 
"Olaf Weiser" 
Date:11/29/2018 09:04 AM
Subject:AW: [gpfsug-discuss] Status for Alert: remotely mounted 
filesystem panic on accessing cluster after upgrading the owning cluster 
first



Hallo Tomer,
thanks for this Info, but can you explain in witch release all these 
points fixed now?
 
Renar Grunenberg
Abteilung Informatik ? Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:
09561 96-44110
Telefax:
09561 96-44104
E-Mail:
renar.grunenb...@huk-coburg.de
Internet:
www.huk.de
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter 
Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese 
Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht 
ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information 
in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in 
this information is strictly forbidden.

Von: gpfsug-discuss-boun...@spectrumscale.org [
mailto:gpfsug-discuss-boun...@spectrumscale.org] Im Auftrag von Tomer 
Perry
Gesendet: Donnerstag, 29. November 2018 08:45
An: gpfsug main discussion list ; Olaf 
Weiser 
Betreff: Re: [gpfsug-discuss] Status for Alert: remotely mounted 
filesystem panic on accessing cluster after upgrading the owning cluster 
first
 
Hi,

I remember there was some defect around tsctl and mixed domains - bot sure 
if it was fixed and in what version.
A workaround in the past was to "wrap" tsctl with a script that would 
strip those.

Olaf might be able to provide more info ( I believe he had some sample 
script).


Regards,

Tomer Perry
Scalable I/O Development (Spectrum Scale)
email: t...@il.ibm.com
1 Azrieli Center, Tel Aviv 67021, Israel
Global Tel:+1 720 3422758
Israel Tel:  +972 3 9188625
Mobile: +972 52 2554625




From:"Grunenberg, Renar" 
To:'gpfsug main discussion list' 
Date:29/11/2018 09:29
Subject:Re: [gpfsug-discuss] Status for Alert: remotely mounted 
filesystem panic on accessing cluster after upgrading the owning cluster 
first
Sent by:gpfsug-discuss-boun...@spectrumscale.org





Hallo All,
in this relation to the Alert, i had some question about experiences to 
establish remote cluster with different FQDN?s.
What we see here that the owning (5.0.1.1) and the local Cluster (5.0.2.1) 
has different Domain-Names and both are connected to a firewall. Icmp,1191 
and ephemeral Ports ports are open.
If we dump the tscomm component of both daemons, we see connections to 
nodes that are named [hostname+ FGDN localCluster+
FGDN remote Cluster]. We analyzed nscd, DNS and make some tcp-dumps and so 
on and come to the conclusion that tsctl generate this wrong nodename and 
then if a Cluster Manager takeover are happening, because of a 

Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[Olaf Weiser]

HI Tomer, send my work around wrapper to Renar..
I've seen to less data to be sure, that's the same (tsctl shownodes ...)
issue but he'll try and let us know .. From:      
 "Grunenberg, Renar"
To:      
 gpfsug main discussion
list , "Olaf Weiser"
Date:      
 11/29/2018 09:04 AMSubject:    
   AW: [gpfsug-discuss]
Status for Alert: remotely mounted filesystem panic on accessing cluster
after upgrading the owning cluster firstHallo Tomer,thanks for this Info, but can you explain
in witch release all these points fixed now? Renar GrunenbergAbteilung Informatik – BetriebHUK-COBURGBahnhofsplatz96444 CoburgTelefon:09561
96-44110Telefax:09561
96-44104E-Mail:renar.grunenb...@huk-coburg.deInternet:www.huk.deHUK-COBURG Haftpflicht-Unterstützungs-Kasse
kraftfahrender Beamter Deutschlands a. G. in CoburgReg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021Sitz der Gesellschaft: Bahnhofsplatz, 96444 CoburgVorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.Diese Nachricht enthält vertrauliche und/oder
rechtlich geschützte Informationen.Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich
erhalten haben,informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht
ist nicht gestattet.This information may contain confidential and/or privileged information.If you are not the intended recipient (or have received this information
in error) please notify thesender immediately and destroy this information.Any unauthorized copying, disclosure or distribution of the material in
this information is strictly forbidden.Von: gpfsug-discuss-boun...@spectrumscale.org
[mailto:gpfsug-discuss-boun...@spectrumscale.org]
Im Auftrag von Tomer PerryGesendet: Donnerstag, 29. November 2018 08:45An: gpfsug main discussion list ;
Olaf Weiser Betreff: Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem
panic on accessing cluster after upgrading the owning cluster first Hi,I remember there was some defect around tsctl and mixed domains - bot sure
if it was fixed and in what version.A workaround in the past was to "wrap" tsctl with a script that
would strip those.Olaf might be able to provide more info ( I believe he had some sample
script).Regards,Tomer PerryScalable I/O Development (Spectrum Scale)email: t...@il.ibm.com1 Azrieli Center, Tel Aviv 67021, IsraelGlobal Tel:    +1 720 3422758Israel Tel:      +972 3 9188625Mobile:         +972 52 2554625From:        "Grunenberg,
Renar" To:        'gpfsug
main discussion list' Date:        29/11/2018
09:29Subject:        Re:
[gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on
accessing cluster after upgrading the owning cluster firstSent by:        gpfsug-discuss-boun...@spectrumscale.orgHallo All,in this relation to the Alert, i had some question about experiences to
establish remote cluster with different FQDN’s.What we see here that the owning (5.0.1.1) and the local Cluster (5.0.2.1)
has different Domain-Names and both are connected to a firewall. Icmp,1191
and ephemeral Ports ports are open.If we dump the tscomm component of both daemons, we see connections to
nodes that are named [hostname+ FGDN localCluster+FGDN remote Cluster]. We analyzed nscd, DNS and make some tcp-dumps and
so on and come to the conclusion that tsctl generate this wrong nodename
and then if a Cluster Manager takeover are happening, because of a shutdown
of these daemon (at Owning Cluster side), the join protocol rejected these
connection. Are there any comparable experiences in the field. And if yes what are
the solution of that?Thanks RenarRenar GrunenbergAbteilung Informatik – BetriebHUK-COBURGBahnhofsplatz96444 CoburgTelefon:09561
96-44110Telefax:09561
96-44104E-Mail:renar.grunenb...@huk-coburg.deInternet:www.huk.deHUK-COBURG Haftpflicht-Unterstützungs-Kasse
kraftfahrender Beamter Deutschlands a. G. in CoburgReg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021Sitz der Gesellschaft: Bahnhofsplatz, 96444 CoburgVorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.Diese Nachricht enthält vertrauliche und/oder
rechtlich geschützte Informationen.Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich
erhalten haben,informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht
ist nicht gestattet.This information may contain confidential and/or privileged information.If you are not the intended recipient (or have received this information
in error) please notify thesender immediately and destroy this information.Any 

Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[Grunenberg, Renar]

Hallo Tomer,
thanks for this Info, but can you explain in witch release all these points 
fixed now?


Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:09561 96-44110
Telefax:09561 96-44104
E-Mail: renar.grunenb...@huk-coburg.de
Internet:   www.huk.de

HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands 
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.

Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist 
nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in 
error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this 
information is strictly forbidden.

Von: gpfsug-discuss-boun...@spectrumscale.org 
[mailto:gpfsug-discuss-boun...@spectrumscale.org] Im Auftrag von Tomer Perry
Gesendet: Donnerstag, 29. November 2018 08:45
An: gpfsug main discussion list ; Olaf Weiser 

Betreff: Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem 
panic on accessing cluster after upgrading the owning cluster first

Hi,

I remember there was some defect around tsctl and mixed domains - bot sure if 
it was fixed and in what version.
A workaround in the past was to "wrap" tsctl with a script that would strip 
those.

Olaf might be able to provide more info ( I believe he had some sample script).


Regards,

Tomer Perry
Scalable I/O Development (Spectrum Scale)
email: t...@il.ibm.com
1 Azrieli Center, Tel Aviv 67021, Israel
Global Tel:+1 720 3422758
Israel Tel:  +972 3 9188625
Mobile: +972 52 2554625




From:"Grunenberg, Renar" 
mailto:renar.grunenb...@huk-coburg.de>>
To:'gpfsug main discussion list' 
mailto:gpfsug-discuss@spectrumscale.org>>
Date:29/11/2018 09:29
Subject:Re: [gpfsug-discuss] Status for Alert: remotely mounted 
filesystem panic on accessing cluster after upgrading the owning cluster first
Sent by:
gpfsug-discuss-boun...@spectrumscale.org




Hallo All,
in this relation to the Alert, i had some question about experiences to 
establish remote cluster with different FQDN’s.
What we see here that the owning (5.0.1.1) and the local Cluster (5.0.2.1) has 
different Domain-Names and both are connected to a firewall. Icmp,1191 and 
ephemeral Ports ports are open.
If we dump the tscomm component of both daemons, we see connections to nodes 
that are named [hostname+ FGDN localCluster+
FGDN remote Cluster]. We analyzed nscd, DNS and make some tcp-dumps and so on 
and come to the conclusion that tsctl generate this wrong nodename and then if 
a Cluster Manager takeover are happening, because of a shutdown of these daemon 
(at Owning Cluster side), the join protocol rejected these connection.
Are there any comparable experiences in the field. And if yes what are the 
solution of that?
Thanks Renar

Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:

09561 96-44110

Telefax:

09561 96-44104

E-Mail:

renar.grunenb...@huk-coburg.de

Internet:

www.huk.de


HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands 
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.

Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist 
nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in 
error) please notify the
sender 

Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[Tomer Perry]

Hi,

I remember there was some defect around tsctl and mixed domains - bot sure 
if it was fixed and in what version.
A workaround in the past was to "wrap" tsctl with a script that would 
strip those.

Olaf might be able to provide more info ( I believe he had some sample 
script).


Regards,

Tomer Perry
Scalable I/O Development (Spectrum Scale)
email: t...@il.ibm.com
1 Azrieli Center, Tel Aviv 67021, Israel
Global Tel:+1 720 3422758
Israel Tel:  +972 3 9188625
Mobile: +972 52 2554625




From:   "Grunenberg, Renar" 
To: 'gpfsug main discussion list' 
Date:   29/11/2018 09:29
Subject:Re: [gpfsug-discuss] Status for Alert: remotely mounted 
filesystem panic on accessing cluster after upgrading the owning cluster 
first
Sent by:gpfsug-discuss-boun...@spectrumscale.org



Hallo All,
in this relation to the Alert, i had some question about experiences to 
establish remote cluster with different FQDN?s.
What we see here that the owning (5.0.1.1) and the local Cluster (5.0.2.1) 
has different Domain-Names and both are connected to a firewall. Icmp,1191 
and ephemeral Ports ports are open.
If we dump the tscomm component of both daemons, we see connections to 
nodes that are named [hostname+ FGDN localCluster+
FGDN remote Cluster]. We analyzed nscd, DNS and make some tcp-dumps and so 
on and come to the conclusion that tsctl generate this wrong nodename and 
then if a Cluster Manager takeover are happening, because of a shutdown of 
these daemon (at Owning Cluster side), the join protocol rejected these 
connection. 
Are there any comparable experiences in the field. And if yes what are the 
solution of that?
Thanks Renar
Renar Grunenberg
Abteilung Informatik ? Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:
09561 96-44110
Telefax:
09561 96-44104
E-Mail:
renar.grunenb...@huk-coburg.de
Internet:
www.huk.de
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter 
Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese 
Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht 
ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information 
in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in 
this information is strictly forbidden.

Von: gpfsug-discuss-boun...@spectrumscale.org [
mailto:gpfsug-discuss-boun...@spectrumscale.org] Im Auftrag von John T 
Olson
Gesendet: Montag, 26. November 2018 15:31
An: gpfsug main discussion list 
Betreff: Re: [gpfsug-discuss] Status for Alert: remotely mounted 
filesystem panic on accessing cluster after upgrading the owning cluster 
first
 
This sounds like a different issue because the alert was only for clusters 
with file audit logging enabled due to an incompatibility with the policy 
rules that are used in file audit logging. I would suggest opening a 
problem ticket.


Thanks,

John

John T. Olson, Ph.D., MI.C., K.EY.
Master Inventor, Software Defined Storage
957/9032-1 Tucson, AZ, 85744
(520) 799-5185, tie 321-5185 (FAX: 520-799-4237)
Email: jtol...@us.ibm.com
"Do or do not. There is no try." - Yoda

Olson's Razor:
Any situation that we, as humans, can encounter in life
can be modeled by either an episode of The Simpsons
or Seinfeld.

"Grunenberg, Renar" ---11/23/2018 01:22:05 AM---Hallo All, are there any 
news about these Alert in witch Version will it be fixed. We had yesterday

From: "Grunenberg, Renar" 
To: "gpfsug-discuss@spectrumscale.org" 
Date: 11/23/2018 01:22 AM
Subject: [gpfsug-discuss] Status for Alert: remotely mounted filesystem 
panic on accessing cluster after upgrading the owning cluster first
Sent by: gpfsug-discuss-boun...@spectrumscale.org




Hallo All,
are there any news about these Alert in witch Version will it be fixed. We 
had yesterday this problem but with a reziproke szenario.
The owning Cluster are on 5.0.1.1 an the mounting Cluster has 5.0.2.1. On 
the Owning Cluster(3Node 3 Site Cluster) we do a shutdown of the deamon. 
But the Remote mount was paniced because of: A node join was rejected. 
This could be due to incompatible daemon versions, failure to find the 
node in the configuration database, or no configuration manager found. We 
had no FAL active, what the Alert says, and the owning Cluster are not on 
the affected Version.
Any Hint, please.

Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[Grunenberg, Renar]

Hallo All,
in this relation to the Alert, i had some question about experiences to 
establish remote cluster with different FQDN’s.
What we see here that the owning (5.0.1.1) and the local Cluster (5.0.2.1) has 
different Domain-Names and both are connected to a firewall. Icmp,1191 and 
ephemeral Ports ports are open.
If we dump the tscomm component of both daemons, we see connections to nodes 
that are named [hostname+ FGDN localCluster+
FGDN remote Cluster]. We analyzed nscd, DNS and make some tcp-dumps and so on 
and come to the conclusion that tsctl generate this wrong nodename and then if 
a Cluster Manager takeover are happening, because of a shutdown of these daemon 
(at Owning Cluster side), the join protocol rejected these connection.
Are there any comparable experiences in the field. And if yes what are the 
solution of that?
Thanks Renar

Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:09561 96-44110
Telefax:09561 96-44104
E-Mail: renar.grunenb...@huk-coburg.de
Internet:   www.huk.de

HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands 
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.

Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist 
nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in 
error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this 
information is strictly forbidden.

Von: gpfsug-discuss-boun...@spectrumscale.org 
[mailto:gpfsug-discuss-boun...@spectrumscale.org] Im Auftrag von John T Olson
Gesendet: Montag, 26. November 2018 15:31
An: gpfsug main discussion list 
Betreff: Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem 
panic on accessing cluster after upgrading the owning cluster first


This sounds like a different issue because the alert was only for clusters with 
file audit logging enabled due to an incompatibility with the policy rules that 
are used in file audit logging. I would suggest opening a problem ticket.


Thanks,

John

John T. Olson, Ph.D., MI.C., K.EY.
Master Inventor, Software Defined Storage
957/9032-1 Tucson, AZ, 85744
(520) 799-5185, tie 321-5185 (FAX: 520-799-4237)
Email: jtol...@us.ibm.com
"Do or do not. There is no try." - Yoda

Olson's Razor:
Any situation that we, as humans, can encounter in life
can be modeled by either an episode of The Simpsons
or Seinfeld.

[Inactive hide details for "Grunenberg, Renar" ---11/23/2018 01:22:05 
AM---Hallo All, are there any news about these Alert in wi]"Grunenberg, Renar" 
---11/23/2018 01:22:05 AM---Hallo All, are there any news about these Alert in 
witch Version will it be fixed. We had yesterday

From: "Grunenberg, Renar" 
mailto:renar.grunenb...@huk-coburg.de>>
To: "gpfsug-discuss@spectrumscale.org" 
mailto:gpfsug-discuss@spectrumscale.org>>
Date: 11/23/2018 01:22 AM
Subject: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic 
on accessing cluster after upgrading the owning cluster first
Sent by: 
gpfsug-discuss-boun...@spectrumscale.org





Hallo All,
are there any news about these Alert in witch Version will it be fixed. We had 
yesterday this problem but with a reziproke szenario.
The owning Cluster are on 5.0.1.1 an the mounting Cluster has 5.0.2.1. On the 
Owning Cluster(3Node 3 Site Cluster) we do a shutdown of the deamon. But the 
Remote mount was paniced because of: A node join was rejected. This could be 
due to incompatible daemon versions, failure to find the node in the 
configuration database, or no configuration manager found. We had no FAL 
active, what the Alert says, and the owning Cluster are not on the affected 
Version.
Any Hint, please.
Regards Renar


Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:  09561 96-44110
Telefax:  09561 96-44104
E-Mail:   renar.grunenb...@huk-coburg.de
Internet: www.huk.de

Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[Grunenberg, Renar]

Hallo John,

record is open, TS001631590.



Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:09561 96-44110
Telefax:09561 96-44104
E-Mail: renar.grunenb...@huk-coburg.de
Internet:   www.huk.de

HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands 
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.

Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist 
nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in 
error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this 
information is strictly forbidden.

Von: gpfsug-discuss-boun...@spectrumscale.org 
[mailto:gpfsug-discuss-boun...@spectrumscale.org] Im Auftrag von John T Olson
Gesendet: Montag, 26. November 2018 15:31
An: gpfsug main discussion list 
Betreff: Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem 
panic on accessing cluster after upgrading the owning cluster first


This sounds like a different issue because the alert was only for clusters with 
file audit logging enabled due to an incompatibility with the policy rules that 
are used in file audit logging. I would suggest opening a problem ticket.


Thanks,

John

John T. Olson, Ph.D., MI.C., K.EY.
Master Inventor, Software Defined Storage
957/9032-1 Tucson, AZ, 85744
(520) 799-5185, tie 321-5185 (FAX: 520-799-4237)
Email: jtol...@us.ibm.com
"Do or do not. There is no try." - Yoda

Olson's Razor:
Any situation that we, as humans, can encounter in life
can be modeled by either an episode of The Simpsons
or Seinfeld.

[Inactive hide details for "Grunenberg, Renar" ---11/23/2018 01:22:05 
AM---Hallo All, are there any news about these Alert in wi]"Grunenberg, Renar" 
---11/23/2018 01:22:05 AM---Hallo All, are there any news about these Alert in 
witch Version will it be fixed. We had yesterday

From: "Grunenberg, Renar" 
mailto:renar.grunenb...@huk-coburg.de>>
To: "gpfsug-discuss@spectrumscale.org" 
mailto:gpfsug-discuss@spectrumscale.org>>
Date: 11/23/2018 01:22 AM
Subject: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic 
on accessing cluster after upgrading the owning cluster first
Sent by: 
gpfsug-discuss-boun...@spectrumscale.org





Hallo All,
are there any news about these Alert in witch Version will it be fixed. We had 
yesterday this problem but with a reziproke szenario.
The owning Cluster are on 5.0.1.1 an the mounting Cluster has 5.0.2.1. On the 
Owning Cluster(3Node 3 Site Cluster) we do a shutdown of the deamon. But the 
Remote mount was paniced because of: A node join was rejected. This could be 
due to incompatible daemon versions, failure to find the node in the 
configuration database, or no configuration manager found. We had no FAL 
active, what the Alert says, and the owning Cluster are not on the affected 
Version.
Any Hint, please.
Regards Renar


Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:  09561 96-44110
Telefax:  09561 96-44104
E-Mail:   renar.grunenb...@huk-coburg.de
Internet: www.huk.de
===
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands 
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
===
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist 
nicht 

Re: [gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[John T Olson]

This sounds like a different issue because the alert was only for clusters
with file audit logging enabled due to an incompatibility with the policy
rules that are used in file audit logging.  I would suggest opening a
problem ticket.


Thanks,

John

John T. Olson, Ph.D., MI.C., K.EY.
Master Inventor, Software Defined Storage
957/9032-1 Tucson, AZ, 85744
(520) 799-5185, tie 321-5185 (FAX: 520-799-4237)
Email: jtol...@us.ibm.com
"Do or do not.  There is no try." - Yoda

Olson's Razor:
Any situation that we, as humans, can encounter in life
can be modeled by either an episode of The Simpsons
or Seinfeld.



From:   "Grunenberg, Renar" 
To: "gpfsug-discuss@spectrumscale.org"

Date:   11/23/2018 01:22 AM
Subject:[gpfsug-discuss] Status for Alert: remotely mounted filesystem
panic on accessing cluster after upgrading the owning cluster
first
Sent by:gpfsug-discuss-boun...@spectrumscale.org



Hallo All,
are there any news about these Alert in witch Version will it be fixed. We
had yesterday this problem but with a reziproke szenario.
The owning Cluster are on 5.0.1.1 an the mounting Cluster has 5.0.2.1. On
the Owning Cluster(3Node 3 Site Cluster) we do a shutdown of the deamon.
But the Remote mount was paniced because of: A node join was rejected. This
could be due to incompatible daemon versions, failure to find the node in
the configuration database, or no configuration manager found. We had no
FAL active, what the Alert says, and the owning Cluster are not on the
affected Version.
Any Hint, please.
Regards Renar


Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:  09561 96-44110
Telefax:  09561 96-44104
E-Mail:   renar.grunenb...@huk-coburg.de
Internet: www.huk.de
===
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter
Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
===
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese
Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist
nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in
error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in
this information is strictly forbidden.
===

___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss




___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss

[gpfsug-discuss] Status for Alert: remotely mounted filesystem panic on accessing cluster after upgrading the owning cluster first

[Grunenberg, Renar]

Hallo All,
are there any news about these Alert in witch Version will it be fixed. We had 
yesterday this problem but with a reziproke szenario.
The owning Cluster are on 5.0.1.1 an the mounting Cluster has 5.0.2.1. On the 
Owning Cluster(3Node 3 Site Cluster) we do a shutdown of the deamon. But the 
Remote mount was paniced because of: A node join was rejected. This could be 
due to incompatible daemon versions, failure to find the node in the 
configuration database, or no configuration manager found. We had no FAL 
active, what the Alert says, and the owning Cluster are not on the affected 
Version.
Any Hint, please.
Regards Renar


Renar Grunenberg
Abteilung Informatik – Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:  09561 96-44110
Telefax:  09561 96-44104
E-Mail:   renar.grunenb...@huk-coburg.de
Internet: www.huk.de
===
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands 
a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav 
Herøy, Dr. Jörg Rheinländer (stv.), Sarah Rössler, Daniel Thomas.
===
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte 
Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich 
erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist 
nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in 
error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this 
information is strictly forbidden.
===

___
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss