From w.moghrabi@servicemagic.eu Mon Aug 13 13:50:25 2018 Received: (at submit) by bugs.x2go.org; 13 Aug 2018 11:50:27 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.8 required=3.0 tests=BAYES_50,HTML_MESSAGE, MIME_QP_LONG_LINE autolearn=ham autolearn_force=no version=3.4.1 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 1919A5DAEB for ; Mon, 13 Aug 2018 13:50:25 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id tg_QgA0Osnhz for ; Mon, 13 Aug 2018 13:50:17 +0200 (CEST) Received: from zm-01.servicemagic.eu (zm-01.servicemagic.eu [176.31.236.17]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 19A1F5DAE9 for ; Mon, 13 Aug 2018 13:50:17 +0200 (CEST) Received: from localhost (localhost.localdomain [127.0.0.1]) by zm-01.servicemagic.eu (Postfix) with ESMTP id C65EC81258004 for ; Mon, 13 Aug 2018 13:50:16 +0200 (CEST) X-Amavis-Modified: Mail body modified (using disclaimer) - zm-01.servicemagic.eu X-Virus-Scanned: amavisd-new at servicemagic.eu Received: from zm-01.servicemagic.eu ([127.0.0.1]) by localhost (zm-01.servicemagic.eu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id eW1kkvn3hVkc for ; Mon, 13 Aug 2018 13:50:16 +0200 (CEST) Received: from zm-01.servicemagic.eu (localhost.localdomain [127.0.0.1]) by zm-01.servicemagic.eu (Postfix) with ESMTP id 674C68120B1BC for ; Mon, 13 Aug 2018 13:50:16 +0200 (CEST) Date: Mon, 13 Aug 2018 13:50:16 +0200 (CEST) From: Walid MOGHRABI To: submit@bugs.x2go.org Message-ID: <1674651030.4011736.1534161016401.JavaMail.root@servicemagic.eu> In-Reply-To: <1645395177.4011470.1534160988289.JavaMail.root@servicemagic.eu> Subject: x2gobroker : maintenance mode MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_4011735_56064288.1534161016400" X-Originating-IP: [195.200.167.70] X-Mailer: Zimbra 7.2.0_GA_2669 (ZimbraWebClient - GC68 (Linux)/7.2.0_GA_2669) ------=_Part_4011735_56064288.1534161016400 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit package: x2gobroker version: 0.0.4.0-0~1038~ubuntu16.04.1 priority: enhancement In case of trouble, this is sometimes needed to block any new incoming connection to the broker (the broker itself, not the x2go server). For example, lately I did a stupid thing by mistake, I shut down a whole X2Go servers chassis (16 servers at the same time) so 2/3 of my users were kicked off the platform. Problem is that they tried to reconnect before I could restart those servers and thus, the broker did his job and sent them to the remaining servers except that they are 2 times less so they couldn't handle that much people at the same time. We lost precious time by asking people to throttle their connecions and wait for the platform to be ready. Would be great to have a "maintenance mode" option in the x2gobroker-sessionprfiles.conf (or even globally on the x2gobroker.conf), just a switch with a message you can activate so that, in case of trouble, with this switch enabled, users trying to connect would get a message from the broker saying it is in a maintenance mode and they should try again later. --- DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you ------=_Part_4011735_56064288.1534161016400 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: quoted-printable <= div style=3D'font-family: arial,helvetica,sans-serif; font-size: 10pt; colo= r: #333333'>
package: x2gobroker
version: 0.0= .4.0-0~1038~ubuntu16.04.1
priority: enhancement

In case of trouble, this is sometimes needed to blo= ck any new incoming connection to the broker (the broker itself, not the x2= go server).
For example, lately I did a stupid thing b= y mistake, I shut down a whole X2Go servers chassis (16 servers at the same= time) so 2/3 of my users were kicked off the platform.
Problem is that they tried to reconnect before I could restart those serv= ers and thus, the broker did his job and sent them to the remaining servers= except that they are 2 times less so they couldn't handle that much people= at the same time.
We lost precious time by asking peo= ple to throttle their connecions and wait for the platform to be ready.

Would be great to have a "maint= enance mode" option in the x2gobroker-sessionprfiles.conf (or even globally= on the x2gobroker.conf), just a switch with a message you can activate so = that, in case of trouble, with this switch enabled, users trying to connect= would get a message from the broker saying it is in a maintenance mode and= they should try again later.

=
DISCLAIMER: This e-mail is private and confidential and may contain proprietary or legally privileged information. It is for the intended recipient only. If you have received this email in error, please notify the author by replying to it and then destroy it. If you are not the intended recipient you must not use, disclose, distribute, copy, print or rely on this e-mail or any attachment. Thank you
= ------=_Part_4011735_56064288.1534161016400--