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 <[email protected]> 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 <[email protected]> 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 / [email protected] > > > > > > ------ Original Message ------ > > From "Joseph John" <[email protected]> > > To [email protected] > > 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 > >> [email protected] > >> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > _______________________________________________ > pve-user mailing list > [email protected] > https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user > _______________________________________________ pve-user mailing list [email protected] https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
