From unknown Thu Mar 28 16:34:41 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#1332: Reply-To: Michael =?UTF-8?Q?B=C3=BCchler?= , 1332@bugs.x2go.org Resent-From: Michael =?UTF-8?Q?B=C3=BCchler?= Resent-To: x2go-dev@lists.x2go.org Resent-CC: owner@bugs.x2go.org X-Loop: owner@bugs.x2go.org Resent-Date: Wed, 15 Apr 2020 15:50:01 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1332 X-X2Go-PR-Package: x2go client X-X2Go-PR-Keywords: References: Received: via spool by 1332-submit@bugs.x2go.org id=B1332.158696578228184 (code B ref 1332); Wed, 15 Apr 2020 15:50:01 +0000 Received: (at 1332) by bugs.x2go.org; 15 Apr 2020 15:49:42 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.7 required=3.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,SPF_HELO_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from mail-wm1-x343.google.com (mail-wm1-x343.google.com [IPv6:2a00:1450:4864:20::343]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 23B3A5DA73 for <1332@bugs.x2go.org>; Wed, 15 Apr 2020 17:49:38 +0200 (CEST) Received: by mail-wm1-x343.google.com with SMTP id y24so79533wma.4 for <1332@bugs.x2go.org>; Wed, 15 Apr 2020 08:49:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=message-id:subject:from:to:date:user-agent:mime-version :content-transfer-encoding; bh=VgebP8Z95rVyNNhROGOOPmAyT9eKI7eQvooA9z6D8B4=; b=GFcRh+QJ4lpsxQmF31lJiA9ykrquohm3U2q99BuFvtdoBzx4KfSDevPGHwGKE/7T1+ FeAtbJcKCYfLaRBJQfj04N2wTxNk9uZdwdtfphKmSqWfjGKM+Y/p+8yXiRocXkiC3ebh M9rODlIHuzwWkn6TMgcAW5S7UdQUWioTV7E+TsMzA9bQsszzE7kEcNUn1SIBkcAiYZu6 2S7WpFNnCc3sgSOEmx3T/er6b8d2Bgsr35NfVxHGutnanSjriFtJ0o0wX0EuJ8ZTaPpW cncjBPpIbH2j9bzN7mWMnqSMBkqt8J9tUPCNMM3yIfkpUHh3SEGvbLHDgUuZalAp9M8V skzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:message-id:subject:from:to:date:user-agent :mime-version:content-transfer-encoding; bh=VgebP8Z95rVyNNhROGOOPmAyT9eKI7eQvooA9z6D8B4=; b=d9BWuFvaPUANA3n199zsB8GqoHvXu+MtKAQNJbMXhwG8ixy7CVVXCs+t7P787PO1Ck NJzqbksvMnrFhzyDGqQPxjyDAAMEQuhKg88kf30x5OSoSRXjiDvWCgCZgIE9IEOc/Eia RNu4ynsmAO0SVZXTuL5w8cH9lh1+HWg+APnbBlvxDmRSU2/swWCzXWkiYsbjK2TM9Y+W 74wxYVgPr1YM1+ITQHt1AetLBuX1uy3Wk7Dg61/etFVaTl1NSaJGcyBddiEObKr0C5sp 7+yPx8XYQ8WhcMbDFRHssY+BfVSUpEflvrNcAJl6JNddWWEt869ZBFky6XQ95sMFXq3N YRlQ== X-Gm-Message-State: AGi0Puao/G7JgaARnKq2nImvcp3Ogqu+bW7XlohS4f9NOFcGTCUezo1p 585XmMy8DQ47Ix/0Qrcn2gsTSA52 X-Google-Smtp-Source: APiQypIRihOCDebrKYiv/nU4wqrss3vOX5g/ltI48L8qc5yqwMT3mnkAxLOWcSoxJAGTki8XrmDq3A== X-Received: by 2002:a1c:7d04:: with SMTP id y4mr5828641wmc.10.1586965777368; Wed, 15 Apr 2020 08:49:37 -0700 (PDT) Received: from [192.168.102.11] (55d42d2b.access.ecotel.net. [85.212.45.43]) by smtp.googlemail.com with ESMTPSA id w18sm23502698wrn.55.2020.04.15.08.49.36 for <1332@bugs.x2go.org> (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 15 Apr 2020 08:49:36 -0700 (PDT) Message-ID: <83035f3aae1750e3500d6e4ace11a57ab09f534b.camel@gmail.com> From: Michael =?UTF-8?Q?B=C3=BCchler?= To: 1332@bugs.x2go.org Date: Wed, 15 Apr 2020 17:49:35 +0200 Content-Type: text/plain; charset="UTF-8" User-Agent: Evolution 3.32.5 MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Package: X2Go Server Version: 4.1.0.3-0~1708~ubuntu18.04.1 am64 I had the same issue: this morning I suddenly couldn't connect after a few weeks of usage. Turned out my root filesystem was 100% full. Who did this? X2Go, apparently. This file was 254 GiB in size: /tmp/.x2go-username/C-username-50-blabla/cmdoutput First I removed that file, then I found out that there were still processes with active file descriptors on that (deleted) file. Thus the filesystem didn't release the space. These processes can be found by using # lsof | grep cmdoutput To let the filesystem free the space I tried this and it worked: # ls -l /proc/15644/fd/ # cat /dev/null > /proc/15644/fd/1 where 15644 is the PID of one of these processes and 1 is the fd number that points to the deleted file. And when I say "I tried this" then I mean "I googled for some stackexchange results and applied them", of course. Maybe this helps someone in a similar situation. Or is it even a bug in X2Go? Long solved in recent versions that you get on a decent distro? Regards Michael