Apps Stuck Updating - Cleaning up old install - even after stopping/restarting task

[avatar1024]

So I guess it could well have to do with the WP unmanaged package as it seems like a common factor so far across all instances (of everyone in the thread) experiencing the issue and the singularity on my buggy instance instance compared to the others

[humptydumpty]

@girish the server is running fine after upgrading to 22.04. I manually updated one app yesterday and it updated just fine. A bunch of apps auto updated last night without any issues and I manually updated Wekan minutes ago. I hope I’m not jumping the gun here fingers crossed!

[p44]

@girish hello Girish, I'm trying to update a LAMP instance and problem still there, any ideas on how to proceed? Thank's

[girish]

@p44 can you write to support@ . I am afraid to give a suggestion without knowing the current state of the server.

[p44]

@girish Ok I'll do ASAP. thank's a lot

[avatar1024]

@p44 Have you tried to reboot your server and then do the update?

@p44 out of interest, do you have a WP unmanaged app installed on your instance?

[girish]

@avatar1024 this is not unmanaged WP related. We have been investigating this a lot last few days but it appears to happen very often in netcup servers at least.

The main issue is that runc is getting stuck (you can also do ps auxf on the server):

root       84188  0.0  0.0 712448  9880 ?        Sl   11:09   0:01 /usr/bin/containerd-shim-runc-v2 -namespace moby -id afb25df337753f9944749bdba5bcb577ae58630d4529da3293ea3730c3164be4 -address /run/containerd/c
root       84200  0.0  0.0 1230148 10704 ?       Sl   11:09   0:00  \_ runc --root /var/run/docker/runtime-runc/moby --log /run/containerd/io.containerd.runtime.v2.task/moby/afb25df337753f9944749bdba5bcb577ae586
root       84210  0.0  0.0 1083864 10968 ?       Ssl  11:09   0:00      \_ runc init

Those runc init above is just hanging there waiting for something (you can strace and see it's waiting on some futex). It's unclear what the issue is so far.

[robi]

@girish I wonder if sysbox would have the same issue.

[p44]

@avatar1024 Yes I did reboot but nothing. No have any WP unmanaged on instance. Only two LAMP applications.

[subven]

@girish said in Apps Stuck Updating - Cleaning up old install - even after stopping/restarting task:

happen very often in netcup servers

I know you (or @nebulon) have an account at Netcups Forum. Maybe ask them for help?

[p44]

@subven I think is not Netcup related issue.

[nebulon]

So we had an instance which seems to not hit this issue anymore by making sure the kvm version is updated. On netcup this apparently means to shutdown and boot the instance through their control panel. A simple reboot/restart will not solve it. Maybe anyone here facing this and being on netcup could attempt this so we get more info.

[jdaviescoates]

@nebulon said in Apps Stuck Updating - Cleaning up old install - even after stopping/restarting task:

Maybe anyone here facing this and being on netcup could attempt this so we get more info.

I just did that (a power cycle via their scp server control panel), let's see if it resolves the issue for me...

[martinkbs]

The same problem occurs on my Hetzner and Contabo servers.

[avatar1024]

Weird, got three Netcup instances and only ever hit the issue one. Plus other people seem to be hitting it with other providers.

@avatar1024 said in Apps Stuck Updating - Cleaning up old install - even after stopping/restarting task:

PS: the instance I restarted earlier today and that was working now hangs again on updates. Restarted again and now working fine...for some time...

Good news is that ever since the last reboot my instance stopped hanging (it's been 4 days). The only thing I did compared to the other time I rebooted is that I updated all apps manually to their latest version and so had no more update to do (the last app was WP unmanaged). Ever since updates have been working fine.

@nebulon said in Apps Stuck Updating - Cleaning up old install - even after stopping/restarting task:

Maybe anyone here facing this and being on netcup could attempt this so we get more info.

I had actually already done this from Netcup SCP the first time I hit the issue but it hadn't solved for me.

[girish]

Ok, so one thing which I have noticed is common is that the kernel is 5.4.0-132-generic (output of uname -nar and Ubuntu 20.04.5 (lsb_release -a). Can others please confirm what kernel and ubuntu they are on?

[humptydumpty]

@girish is there a way to check what I was running prior to upgrading to22.04?

[avatar1024]

@girish
All three instances are on kernel 5.4.0-132-generic
Two instances (including the one that used to hang) are on Ubuntu 20.04.3
One instance is on 20.04.4

[girish]

@humptydumpty no, I think not. Are you still facing this issue? What's your current kernel and ubuntu release?

[subven]

@girish Netcup RS 4000 G9 Ubuntu 20.04.2 Kernel 5.4.0-131-generic - no issue.