Changes between Version 27 and Version 28 of Public/User_Guide/PaS

Timestamp:

Sep 23, 2020, 9:22:54 AM (4 years ago)

Author:

Jochen Kreutz

Comment:

HW issues updated

Public/User_Guide/PaS

@@ -3 +3 @@
 This page is intended to give a short overview on known issues and to provide potential solutions and workarounds to the issues seen.
 
-''Last update: 2020-09-22''
+''Last update: 2020-09-23''
 {{{#!comment highlighted red text
 [[span(style=color: #FF0000, System maintenance from Monday, 2020-09-07 to Friday, 2020-09-11, no user access !)]]
 }}}
-[[span(style=color: #FF0000, GPFS issues occured, user login currently not possible !)]]
 
 To stay informed, please refer to the [wiki:Public/User_Guide/News News page]. Also, please pay attention to the information contained in the "Message of the day" displayed when logging onto the system. 
@@ -16 +15 @@
 === CM nodes ===
 
-* dp-cn[09,10]: nodes currently reserved for special use case during working hours 
-* dp-cn11: node was not responding (#2426)
-* dp-cn24: thermal trip asserted (#2443, #2306)
-* dp-cn41: node not responding (#2477)
+* dp-cn[01,09,10]: nodes currently reserved for special use case during working hours 
+* dp-cn33: memory issues (#2464)
+* dp-cn49: configuration change required (#2291)
+* dp-cn50: node not reachable (#2488)
 
 === DAM nodes ===
@@ -36 +35 @@
 }}}
 
-* dp-esb02: energy meter reading issues
-* dp-esb03: energy meter reading issues (#2466) 
+* dp-esb05: node hangs in state "Idle+Completing"
 * dp-esb11: wrong GPU Link Speed detected (#2358)
-* dp-esb23: MCE problems (#2350)
 * dp-esb24: CentOS8 Testbed (#2396)
-* dp-esb28: no access to bmc (#2430)
-* dp-esb33: no access to bmc (#2429)
-* dp-esb38: no access to bmc 
 * dp-esb39: energy meter reading issues (#2432)
 * dp-esb52: energy meter reading issues (#2433)
+* dp-esb61: node not reachable (#2469)
 * dp-esb71: energy meter reading issues (#2432)
 * dp-esb73: energy meter reading issues (#2433)
@@ -55 +50 @@
 * nfgw[01,02]: node reachable via nework, but marked as down in SLURM
 * knl01: NVMe issues (#2011)
+* ml-gpu02: memory issues reported with MCE (#2489)
 
 
@@ -66 +62 @@
 
 
-{{{#!comment JK: status to be clarified on Thursday, 2020-09-03
-=== LDAP error message during login ===
-
-- seeing frequent failovers between the master nodes that are being investigated
-- currntly, a failover might lead to seeing the following or a similar error message during login:
-
-{{{
-Error: ldap_search: failed to open connection to LDAP server(s) and search. Exception: socket connection error while opening: [Errno 111] Connection refused 
-}}}
-
-- the message usually can be ignored 
-- in addition, some of the environment variables, e.g. `$PROJECT` are not set (properly)
-- if you see further issues or cannot login at all, please write an email to the support list: `sup(at)deep-est.eu`
-
 === SLURM jobs ===
 
@@ -86 +68 @@
 - this might lead to (temporary) failing job starts for certain users
 - if you cannot start jobs via SLURM, please write an email to the support list: `sup(at)deep-est.eu`
+
 
 === GPU direct usage with IB on ESB ===
@@ -116 +99 @@
 
 - expect performance and stability issues
-
-
-=== Horovod === 
-
-- currently only working with the developer stage 
-
-
-}}}