From: Roland <devzero@web.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Joseph John <jjk.saji@gmail.com>
Subject: Re: [PVE-User] IS able to login through web interface, but the status of the VM is marked as ??
Date: Thu, 17 Aug 2023 08:58:13 +0200 [thread overview]
Message-ID: <4fcabac5-83f8-497c-b219-b4a0c9729b99@web.de> (raw)
In-Reply-To: <CAKeuxjDVc=Y55z60riwLZbGL5+me0pHVLV1KW_1NANroAsxyCg@mail.gmail.com>
https://bugzilla.proxmox.com/show_bug.cgi?id=1410
https://bugzilla.proxmox.com/show_bug.cgi?id=4519
Am 17.08.23 um 06:57 schrieb Joseph John:
> Dear Mark
> THANKS
> Like to give the feedback,
> Most probably the issue might have been occured because of the loal disk
> getting over , reason is that I was moving some images from my old
> instance to the new instance, this may be the reason why this behaviour
> happened
> thanks
>
> On Mon, Aug 14, 2023 at 12:31 PM Wolf Noble <wolf@wolfspyre.com> wrote:
>
>> that tracks… the ‘why’ still could use a bit more digging, but I concur
>> that tracks error-condition-chain wise…
>>
>> oom feels unlikely coz other lower priority stuff’d break first…
>> network loss?
>>
>> time issues?
>>
>> stupid high latency/context switching?
>>
>> could be a lot of things
>>
>>
>> [= The contents of this message have been written, read, processed,
>> erased, sorted, sniffed, compressed, rewritten, misspelled,
>> overcompensated, lost, found, and most importantly delivered entirely with
>> recycled electrons =]
>>
>>> On Aug 14, 2023, at 02:15, Mark Schouten <mark@tuxis.nl> wrote:
>>>
>>> Hi,
>>>
>>> The message ’Transport endport is not connected’ points to a
>> fuse-mountpoint. Given that pvestatd can also not write its statusses (you
>> see question-marks, that points to pvestatd not working), I would assume
>> that the pve-cluster was broken. You should probably see messages in logs
>> from pmxcfs and corosync (on all nodes, I suspect).
>>> —
>>> Mark Schouten
>>> CTO, Tuxis B.V.
>>> +31 318 200208 / mark@tuxis.nl
>>>
>>>
>>> ------ Original Message ------
>>> From "Joseph John" <jjk.saji@gmail.com>
>>> To pve-user@pve.proxmox.com
>>> Date 11/08/2023, 07:03:48
>>> Subject [PVE-User] IS able to login through web interface, but the
>> status of the VM is marked as ??
>>>> 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
>>
> _______________________________________________
> 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-17 6:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
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
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=4fcabac5-83f8-497c-b219-b4a0c9729b99@web.de \
--to=devzero@web.de \
--cc=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