Pseudo-terminal will not be allocated because stdin is not a terminal.
********************************************************************************
*                        ⊹                        ✧          _____             *
*   Welcome to   ✧              ✧        ⊹             _____/..../___     ⊹    *
*        __ __  __ ____   ____ ______ ______ ____     /    /..../    \         *
*       / // / / // __ \ /  _//_  __// ____// __ \   /    /..../___   \  .     *
*  __  / // / / // /_/ / / /   / /  / __/  / /_/ /  /    /......../    \    ⊹  *
* / /_/ // /_/ // ____/_/ /   / /  / /___ / _, _/  /    /......../      \      *
* \____/ \____//_/    /___/  /_/  /_____//_/ |_|  /     ‾‾‾‾/.../        \     *
*                                            .    \        /.../__       /  *  *
*            JU  Pioneer for                       \      /....../      /      *
*                                       ⊹           \    /....../      /  ✧    *
* ✧     Innovative and Transformative       *        \   ‾‾‾/../      /        *
*    *                                                \_____/./______/  .      *
*           Exascale Research           *      ⊹            //             ⊹   *
*   ⊹                      .         ✧                      /       ⊹          *
********************************************************************************
                                                      2025-10-07T17:30:00+02:00
 ## JUPITER state ##

 JUPITER is in a bring up state. That implies instabilities and unexpected node
 states.

 Update (CW44):

 Regarding Storage: ExaSTORE (SCRATCH/DATA) is in production. Your projects
 will automatically receive corresponding folders. Given that demands are hard
 to predict, we will start with the initial JUST6 quotas and then fine-tune the
 settings as a second step. DATA is only available via reviewed and technically
 as well as scientifically justified data projects which are handled
 independently of compute projects.

 Regarding Availability: Due to the focus on hardware repairs of the nodes in
 the current phase, the system was blocked completely starting on 2025-10-28.
 We will inform you once we have increased availability again.

********************************************************************************

                                                      2025-11-03T11:30:00+01:00
 ## JUPITER expected downtime ##

 JUPITER has been operating for multiple months in a preproduction environment,
 including the datacenter. To proceed with the acceptance for the new
 datacenter, and JUPITER's acceptance itself, a datacenter-wide shutdown is
 planned for 10.11.2025. Due to the work necessary on the datacenter side, the
 system will become available again in phases, not all at once. While access to
 first nodes of JUPITER should be available in the 3 weeks following the
 shutdown, full system availability may take as long as 6 weeks.

 The priority during the first weeks would be on the socalled "datahall", which
 implies that login nodes and storage will be the first part of the system that
 will be available for access again. Unfortunately that is also the most
 convoluted part of the work, so a more accurate estimation is at the moment
 not possible. If you need access to the data currently stored in ExaSTORE
 during that period, please remember to copy it outside of the system in time.

********************************************************************************
+------------------------------------------------------------------------------+
| This node is in maintenance. Overall system state visible on the status page |
+------------------------------------------------------------------------------+
Connection closed by 134.94.0.135 port 22