Problem solved : We just had to kill Java processes !   Thank you for your attention, you can get back to a normal life :)
Hello, As we experienced some troubles to operate administration and maintenance, we planned to restart MCS like we always did. dpnctl stop mcs && dpnctl start mcs,sched   But we are in the same state since 5 hours....nothing more tha, "Shutting down MCS..."   admin[NAME]:~/>: dpnctl stop mcs && dpnctl start mcs,schedIdentity added: /home/admin/.ssh/admin_key (/home/admin/.ssh/admin_key) dpnctl: INFO: Shutting down MCS...   In another CLI session, maintenance operation are still running, we passed from crunchwait to balance recently :   All reported states=(ONLINE), runlevels=(fullaccess), modes=(mhpu+0hpu+0hpu)System-Status: okAccess-Status: full Last checkpoint: cp.20190520114138 finished Mon May 20 13:44:34 2019 after 02m 53s (OK)Last GC: finished Mon May 20 11:31:43 2019 after 31m 28s >> recovered 164.41 GB (OK)Last hfscheck: finished Mon May 20 13:40:35 2019 after 57m 23s >> checked 66642 of 66642 stripes (OK) Maintenance windows scheduler capacity profile is active.The maintenance window is currently running.Currently running task(s): balanceNext backup window start time: Mon May 20 21:00:00 2019 CESTNext maintenance window start time: Tue May 21 11:00:00 2019 CEST   If we try to run a dpnctl stop from another CLI, we get an error about a lock and we donnot want to override the warning fearing to lost consitency and have to force rollback checkpoint :)   Any idea what is going on ? Should we wait more or force restart ?
MCS donnot shut down and btw donnot restart after dpnctl cli command