Re: [Users] Issues after updating to 7.0.14 (136)

top/suspended when rebooting the HWNode they are looking a this potential issue with netflter and latest updates . to be continued ... Thanks . De: "Oleksiy Tkachenko" À: "OpenVZ users" Envoyé: Mercredi 8 Juillet 2020 23:49:51 Objet: Re: [Users] Issues after

Re: [Users] Issues after updating to 7.0.14 (136)

>> ... >> Error in ploop_check (check.c:663): Dirty flag is set >> ... >> # ploop mount /vz/private/144dc737-b4e3-4c03-852c-25a6df06cee4/root.hdd/DiskDescriptor.xml >> Error in ploop_mount_image (ploop.c:2495): Image /vz/private/144dc737-b4e3-4c03-852c-25a6df06cee4/root.hdd/root.hds already used

Re: [Users] Issues after updating to 7.0.14 (136)

    0 Jehan . _ De: "jjs - mainphrame" À: "OpenVZ users" Cc: "Kevin Drysdale" Envoyé: Jeudi 2 Juillet 2020 18:22:33 Objet: Re: [Users] Iss

Re: [Users] Issues after updating to 7.0.14 (136)

Hello If it can help, what I did so far to try to re-enable dead CTs # prlctl stop ldap2 Stopping the CT... Failed to stop the CT: PRL_ERR_VZCTL_OPERATION_FAILED (Details: Cannot lock the Container ) # cat /vz/lock/144dc737-b4e3-4c03-852c-25a6df06cee4.lck 6227 resuming # ps auwx | grep 6227

Re: [Users] Issues after updating to 7.0.14 (136)

Hello, I am back to the initial pb related to that post , since I updated to /OpenVZ release 7.0.14 (136)  | ///Virtuozzo Linux release 7.8.0 (609)// , I am also facing CT corrupted status . I don't see the exact same error as mentioned by Kevin Drysdale below (ploop/fsck) , but I am not

Re: [Users] Issues after updating to 7.0.14 (136)

errors ? Jehan . De: "jjs - mainphrame" À: "OpenVZ users" Envoyé: Jeudi 2 Juillet 2020 19:33:23 Objet: Re: [Users] Issues after updating to 7.0.14 (136) Thanks for that sanity check, the conundrum is resolved. vzlinux-release and virtuozzo-release are indeed dif

Re: [Users] Issues after updating to 7.0.14 (136)

t; Updates 0 >> >> Jehan . >> >> ---------- >> *De: *"jjs - mainphrame" >> *À: *"OpenVZ users" >> *Cc: *"Kevin Drysdale" >> *Envoyé: *Jeudi 2 Juillet 2020 18:22:33 >

Re: [Users] Issues after updating to 7.0.14 (136)

*Cc: *"Kevin Drysdale" mailto:kevin.drysd...@iomart.com>> *Envoyé: *Jeudi 2 Juillet 2020 18:22:33 *Objet: *Re: [Users] Issues after updating to 7.0.14 (136) Jehan, are you running factory? My ovz hosts are up to date, and I see: [root@annie ~]# cat /etc

Re: [Users] Issues after updating to 7.0.14 (136)

À: *"OpenVZ users" > *Cc: *"Kevin Drysdale" > *Envoyé: *Jeudi 2 Juillet 2020 18:22:33 > *Objet: *Re: [Users] Issues after updating to 7.0.14 (136) > > Jehan, are you running factory? > > My ovz hosts are up to date, and I see: > > [root@annie ~]# cat /e

Re: [Users] Issues after updating to 7.0.14 (136)

Envoyé: Jeudi 2 Juillet 2020 18:22:33 Objet: Re: [Users] Issues after updating to 7.0.14 (136) Jehan, are you running factory? My ovz hosts are up to date, and I see: [root@annie ~]# cat /etc/virtuozzo-release OpenVZ release 7.0.15 (222) Jake On Thu, Jul 2, 2020

Re: [Users] Issues after updating to 7.0.14 (136)

Hello Kevin, What was the OpenVz version *before* update to 7.0.14-136? Sparse files for CTs are here for at least two years. Best regards, Konstantin -Original Message- From: users-boun...@openvz.org On Behalf Of Kevin Drysdale Sent: Monday, June 29, 2020 1:30 PM To:

Re: [Users] Issues after updating to 7.0.14 (136)

Jehan, are you running factory? My ovz hosts are up to date, and I see: [root@annie ~]# cat /etc/virtuozzo-release OpenVZ release 7.0.15 (222) Jake On Thu, Jul 2, 2020 at 9:08 AM Jehan Procaccia IMT < jehan.procac...@imtbs-tsp.eu> wrote: > "updating to 7.0.14 (136)" !? > > I did an update

Re: [Users] Issues after updating to 7.0.14 (136)

"updating to 7.0.14 (136)" !? I did an update yesterday , I am far behind that version /# cat /etc/vzlinux-release// / /Virtuozzo Linux release 7.8.0 (609)/ / / /# uname -a // //Linux localhost 3.10.0-1127.8.2.vz7.151.14 #1 SMP Tue Jun 9 12:58:54 MSK 2020 x86_64 x86_64 x86_64 GNU/Linux// /