From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <jjk.saji@gmail.com> Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 9A5C699E58 for <pve-user@lists.proxmox.com>; Thu, 4 May 2023 09:55:05 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 779631AF73 for <pve-user@lists.proxmox.com>; Thu, 4 May 2023 09:55:05 +0200 (CEST) Received: from mail-ed1-x52d.google.com (mail-ed1-x52d.google.com [IPv6:2a00:1450:4864:20::52d]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for <pve-user@lists.proxmox.com>; Thu, 4 May 2023 09:55:04 +0200 (CEST) Received: by mail-ed1-x52d.google.com with SMTP id 4fb4d7f45d1cf-50bc25f0c7dso214748a12.3 for <pve-user@lists.proxmox.com>; Thu, 04 May 2023 00:55:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1683186898; x=1685778898; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :from:to:cc:subject:date:message-id:reply-to; bh=3gtSi4KjBjeFf5/pqUYJPgd7avAZu42liblufSg0XHs=; b=ZhEgf+1TmEtLhikKomTFPUy9Hq6CSGsvBL+DGcm40njxRHJsOTTun4nRBszN3ugnnf 8J4QS07QyKDhSgMZYP5P8XbMFH7isDl3lu7RYTBhCgcGQg2L9IDMfAWQ07mQIyn1+kvJ tRWT5NosEYBIekHOg6SsUCoujwvhJFEfS0CIT4d2PDcE6G50v9Pyol9SO1w5o9J2TzPJ ovYcEUz/VhMDDFMjGA4N4mBdrWXL263IQmXEGP5BOE5bNUgb+UaJbKijjMTw7Veatghn D5C6CIcsLJg1Msz8ao60G1HhXVKP/v5gVB7iDgh45Lv/wYgSYgbuaKCjg/F8FI1WwoG6 ZcLA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683186898; x=1685778898; h=to:subject:message-id:date:from:in-reply-to:references:mime-version :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=3gtSi4KjBjeFf5/pqUYJPgd7avAZu42liblufSg0XHs=; b=l1XBbxcHOP3t34fcCp+4phZKgQJWxbi+eeKMrmljQYvMtJM0Ag1kD3aXJoRWHNnd+b LwFk0IhidXlSQj7B0/qa5IxXOuJTuUn9qusgDrgW3KXwzi8jNi6G1XJ/lZK53RqRLDd1 xAh7gcILycI4owCvtCEOUTcPU1xk6s/qMlwz+DLQ07kLOSNJza4qAWSZ4dwzH37SgQBH C93G82FMSCV8ft9meU2tNC+Fdno1J7dRvGV3VBgG1VB0GZqBtbNs5bA5T2XMoro7zECy JWvJ0gHd2AC8PVSApDolDwEhHz+Domu0q0folVpbo8bDW9lC0vwZX95PGbdaLBVpagTH er5g== X-Gm-Message-State: AC+VfDyaWfONeVEncAb6h7pKEubhrAuWKqbHsVU7QdgElYerm/igpTDc QLVEQcYNN+mrbJ8kmRMJg4GfaCnhn9CBd9lImDt41UEtPpE= X-Google-Smtp-Source: ACHHUZ7QeqQQDq5tyZ7jF+OltaCddUIlLTy+OMjJRu7b4xDbkYktfkEhJ1E0ejif21VBlKnQEWmt7HWzE6tB8hi6XwM= X-Received: by 2002:a17:907:3f1d:b0:94f:3b29:e0a5 with SMTP id hq29-20020a1709073f1d00b0094f3b29e0a5mr6279371ejc.20.1683186897963; Thu, 04 May 2023 00:54:57 -0700 (PDT) MIME-Version: 1.0 References: <CAKeuxjA2MbdxsdDEN+=zFrvkVxAcC2c3fo1z2Grey0VUemkTzw@mail.gmail.com> <mailman.136.1683184866.359.pve-user@lists.proxmox.com> In-Reply-To: <mailman.136.1683184866.359.pve-user@lists.proxmox.com> From: Joseph John <jjk.saji@gmail.com> Date: Thu, 4 May 2023 11:54:46 +0400 Message-ID: <CAKeuxjCEXrVjey2UtJfpXjrpJxrZ9KPJON9ObWUQSvtKRircJg@mail.gmail.com> To: Proxmox VE user list <pve-user@lists.proxmox.com> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.269 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain DMARC_PASS -0.1 DMARC pass policy FREEMAIL_FROM 0.001 Sender email is commonly abused enduser mail provider HTML_MESSAGE 0.001 HTML included in message POISEN_SPAM_PILL_4 0.1 random spam to be learned in bayes RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [binovo.es, proxmox.com] Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 Subject: Re: [PVE-User] HEALTH_ERR , showing x 1 Full osd(s) , guidance requested X-BeenThere: pve-user@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE user list <pve-user.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-user/> List-Post: <mailto:pve-user@lists.proxmox.com> List-Help: <mailto:pve-user-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user>, <mailto:pve-user-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Thu, 04 May 2023 07:55:05 -0000 Dear All THANKS a lot Like to update I managed to add some space, by removing some virtual instances which I was not using at all. Then we restarted the 4th node which was showing HEALTH_ERR and now it is working THANKS A LOT to all who gave advice and support thanks On Thu, May 4, 2023 at 11:21=E2=80=AFAM Eneko Lacunza via pve-user < pve-user@lists.proxmox.com> wrote: > > > > ---------- Forwarded message ---------- > From: Eneko Lacunza <elacunza@binovo.es> > To: pve-user@lists.proxmox.com > Cc: > Bcc: > Date: Thu, 4 May 2023 09:20:25 +0200 > Subject: Re: [PVE-User] HEALTH_ERR , showing x 1 Full osd(s) , guidance > requested > Hi Joseph, > > You must resolve that 1 full osd(s) issue. If other OSDs aren't as full, > you can try to reweight the full OSD so that some info is removed from it= . > > Another option would be to add additional OSDs. > > Cheers > > El 4/5/23 a las 8:39, Joseph John escribi=C3=B3: > > Dear All, > > Good morning > > We have a proxmox setup, with 4 nodes, with 6.3-3 > > We have Node 1 and Node 2 running with 6.3-3 > > and Node 3 and Node 4 running with 6.4-15 > > > > today we noticed that , we were not able to ssh to the virtual instance= , > > or not able to login using the console based option > > when I checked the summary, we could see that in "HEALTH_ERR" we are > > getting message that 1 full osd(s) > > > > > > > > Thanks > > Joseph John > > 00971-50-7451809 > > _______________________________________________ > > pve-user mailing list > > pve-user@lists.proxmox.com > > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > > > > Eneko Lacunza > Zuzendari teknikoa | Director t=C3=A9cnico > Binovo IT Human Project > > Tel. +34 943 569 206 | https://www.binovo.es > Astigarragako Bidea, 2 - 2=C2=BA izda. Oficina 10-11, 20180 Oiartzun > > https://www.youtube.com/user/CANALBINOVO > https://www.linkedin.com/company/37269706/ > > > > > > ---------- Forwarded message ---------- > From: Eneko Lacunza via pve-user <pve-user@lists.proxmox.com> > To: pve-user@lists.proxmox.com > Cc: Eneko Lacunza <elacunza@binovo.es> > Bcc: > Date: Thu, 4 May 2023 09:20:25 +0200 > Subject: Re: [PVE-User] HEALTH_ERR , showing x 1 Full osd(s) , guidance > requested > _______________________________________________ > pve-user mailing list > pve-user@lists.proxmox.com > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user >