After launching nexctcloud upgrade (by Truenas GUI), it failed and unfortunatly it’s now staying stopped and I’m not able to start it. Here is the app_lifecycle.log :
[2026/03/20 10:29:21] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘nextcloud’ app: Timed out waiting for response
I’m wondering if the best solution would’be to push ‘Roll Back’ button ?
Just seen my lifecycle log following your method through ssh. The last events written are the same I read this morning :
And no more
I tried to roll back but unfortunately it also failed due to app has to be running Here what I’m getting :
Traceback (most recent call last):
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 515, in run
await self.future
File “/usr/lib/python3/dist-packages/middlewared/job.py”, line 562, in __run_body
rv = await self.middleware.run_in_thread(self.method, *args)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 627, in run_in_thread
return await self.run_in_executor(io_thread_pool_executor, method, *args, **kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/main.py”, line 624, in run_in_executor
return await loop.run_in_executor(pool, functools.partial(method, *args, **kwargs))
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.11/concurrent/futures/thread.py”, line 58, in run
result = self.fn(*self.args, **self.kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/api/base/decorator.py”, line 101, in wrapped
result = func(*args)
^^^^^^^^^^^
File “/usr/lib/python3/dist-packages/middlewared/plugins/apps/rollback.py”, line 41, in rollback
verrors.check()
File “/usr/lib/python3/dist-packages/middlewared/service_exception.py”, line 72, in check
raise self
middlewared.service_exception.ValidationErrors: [EINVAL] app_name: App must not be in stopped state to rollback
Finally, for sharing my experience and for those who would get this issue, mine came from an Ethernet connection unsteady, due to the malfunction of a CPL.