From: Joseph John <jjk.saji@gmail.com>
To: Proxmox VE user list <pve-user@lists.proxmox.com>
Subject: Re: [PVE-User] IS able to login through web interface, but the status of the VM is marked as ??
Date: Sun, 13 Aug 2023 10:27:22 +0400 [thread overview]
Message-ID: <CAKeuxjDnfZU8uxP0P2G8E8nNKcDR0aTgamJfLM3r0E-USsbSDQ@mail.gmail.com> (raw)
In-Reply-To: <63d3de3b-6b9f-a597-839d-2d2700e695dc@web.de>
Thanks Roland,
We will setup a network monitoring tool ( zabbix ) and keep it monitored
for studying such occurrences
Thanks
Joseph John
On Fri, Aug 11, 2023 at 6:15 PM Roland <devzero@web.de> wrote:
> there is a known problem when storage hang as pvestatd may get stuck in
> a syscall and never returns :
>
>
> https://forum.proxmox.com/threads/unavailable-storage-will-make-the-webui-unusable.119107/
>
> https://bugzilla.proxmox.com/show_bug.cgi?id=3714
>
> if you have even ssh login problems, i guess it was some issue/hang with
> the root filesystem/disks/raid
>
> furthermore, it could have been some out of memory condition. to get
> into the details of such, it's useful
> to have external system monitoring, as it will tell you when ram did
> fill up slowly...
>
> roland
>
> Am 11.08.23 um 07:03 schrieb Joseph John:
> > Dear All ,
> > We are using PVE 8.X EE , we have 8 node cluster
> > today one of the cluster , we were able to login through the web
> > interface, but the status of the VM machines were marked as ?
> > We tried to login in using SSH, were able not able to init 6 , it was
> > showing the message
> >
> > root@pve-4:~# init 6
> >
> > *Failed to set wall message, ignoring: Transport endpoint is not
> > connectedCall to Reboot failed: Transport endpoint is not connected*
> >
> > Later on we did hard reset and the system was back
> > How could we know what was the problem?, which log files should we use?
> to
> > understand the issue
> >
> > Advice requested
> >
> >
> > Thanks
> > Joseph John
> > _______________________________________________
> > pve-user mailing list
> > pve-user@lists.proxmox.com
> > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
> >
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
>
next prev parent reply other threads:[~2023-08-13 6:28 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-11 5:03 Joseph John
2023-08-11 5:53 ` proxmox
2023-08-11 14:09 ` Roland
2023-08-13 6:27 ` Joseph John [this message]
[not found] <emdfa69ec7-a6a0-4079-b684-bf1626ba8772@79bf2994.com>
[not found] ` <F027BD13-FCE0-454F-ABCF-001C1479AB07@wolfspyre.com>
2023-08-17 4:57 ` Joseph John
2023-08-17 6:58 ` Roland
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAKeuxjDnfZU8uxP0P2G8E8nNKcDR0aTgamJfLM3r0E-USsbSDQ@mail.gmail.com \
--to=jjk.saji@gmail.com \
--cc=pve-user@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox