Upgrade to "version": "4.16.2" end in "Not Responding" state

[benborges]

I spent a few hours trying to make the upgrade work

• disabled all apps
• even in recovery mode I could not access the web terminal
• enabled debug to True, but nothing came up
• even with all apps disabled by renaming the apps/ folder, it would not boot core nextcloud beyond the /healtcheck point

I had to restore to 4.15.0 to have it back online

• Nextcloud 25.0.1

context Cloudron v7.3.4 (Ubuntu 22.04.1 LTS)

[benborges]

curiously, other Nextcloud app on the same cloudron are upgrading in automated mode just fine, so that should be a hint that it's maybe a particular nextcloud app provoking this in this particular nextcloud.

i'll debug some more and try to update again with debug true at the get go and see if I can catch something

[girish]

@benborges Can you check the app logs? it's most likely a plugin bombing.

[benborges]

@girish that's the thing, even with debug, I can see nothing

[girish]

@benborges do you atleast see logs that are printed because the cloudron app health check is done every 10 seconds? Is that a 200 or some 500 ?

[benborges]

@girish 200 but again, right now I'm not on that version, i'm on the version that works just fine.

[benborges]

The more I dig about this the more I think it may be unrelated to Nextcloud?

I have right now, NocoDB, N8N and Metabase apps in "not responding" mode after the their respective last package upgrade.

this for one cloudron v7.3.4 (Ubuntu 22.04.1 LTS)
Nocodb log are strange, crash just after the app start and nginx config done

it's like the logging stop but still display the last "running" log when the app was online? the timing match the time it has been down and the two package upgrade that occured.

N8N logs also stopped the 29 this is just when the app started its upgrade, then rebooted and stopped logging ??

Same for Metabase :

I can restart the app or go in recovery mode and see the log working for these steps, but the moment the apps should actually boot, logs stop and that's it

But curiously, 2 N8N instance on v7.3.5 (Ubuntu 22.04.1 LTS) do not seem to be suffering the same issue.

These apps in "not responding" mode seem to be crashing without any log beyond the restarting progress in the terminal, nothing happens after that.

Should I bring this over to email support ?

[girish]

@benborges something is indeed stuck somewhere. We can look into it further if you drop us a mail on support@ .

[benborges]

@girish email sent, but not sure you received it?

[nebulon]

@benborges actually I have already answered few hours back. Did you not receive it?

[benborges]

@nebulon nope, nothing, that's odd

[nebulon]

@benborges I also answered to your recent ticket now, if you don't receive those, maybe send a mail with your mail client to support@

[benborges]

@nebulon This was a strange episode, still unclear what happened, but everything "came back" to normal for some reason.