[EFAULT] Failed ‘up’ action for ‘nextcloud’ app. Please check /var/log/app_lifecycle.log

My system has Collabora, Pi-Hole and Tailscale runniing properly and up to date as of today.

The current (latest) instrruction DO NOT WORK for me on Electric Eel 24.10.2 (Nextcloud | TrueNAS Documentation Hub)

COULD SOMEONE READ THRU THE STEPS I AM TAKING BELOW AND TELL ME WHAT I AM DING WRONG… Please!!!

[EFAULT] Failed ‘up’ action for ‘nextcloud’ app. Please check /var/log/app_lifecycle.log for more details

TrueNAS Version: ElectricEel-24.10.2

Nextcloud App Version: 30.0.6 Version: 1.6.4 (This was several days ago - it keeps changing)
by TODAY it was Nextcloud App Version: 31.0.0 Version: 1.6.9 when I tried the install again.

BEST Practice Tip: Make your own datasets before the install

Create - Generic dataset Nextcloun with custom ACL owner & group = admin then add a User = netdata with Full Control

Create - Two generic child datasets (I named these datasets app-html & app-data) with custon ACLs owner & group = webdata check apply and save.

Create - A third APT dataset (I named mine portgres_data) then select advanced, go to bottom and select ACL type = POSIX then save and select custom ACL and apply owner = netdata & group = docker .

The dataset names can be your choice, but the way they are created is MANTATORY.

IMPORTANT!!! If you do not use IX created datasets and choose to make your make datasets IGNORE the instructions comment about NOT choosing “Enable ACL” for the portgres_data dataset and checking the Automatic Permissions box. This ONLY works for the IX created datasets per a TrueNAS comment in another post. HOST PATH datasets ALL need Enable ACL box checked when you choose them.

Now goto Install:

When choosing Nexcloud Admin User name I used “admin”
(But if you choose something else I have seen comments saying this name needs administrator rights on your TrueNAS system)

Add ALL three APT Packages (Clink the ADD box three times)

ADD eng in Tesseract Language Codes

Check the Imagery box

Add you systems IP address as the HOST (no port number)

Leave the Data Directory Path as the recommended default value. (/var/www/html/data)

Default settings work for the next four choices.

Check the Cron box (Leave */5 * * * * schedule as is)

WebUI Port = 30027 (can be changed if needed even after the install completes)

DNS Options box - What goes here a DNS IP address causes it to fail earlier and the suggestion shows the weird example of : attempts:3

Choose ‘truenas_default’ Certificate as your Certificate ID

In the storage section: Do NOT choose DEPRECATED: Old Storage Structure 9Unless it applies to your UGRADE needs)

In the next three storage sections choose HOST Path and the Enable ACL box before choosing your new datasets. (You can use the force flag if you think the datasets may already contain data).

With the datasets selected go to bottom and click INSTALL.

This is not true. I’m not sure what other post you’re referring to but it’s either wrong or outdated. The option was specifically added to allow you to mount a host path dataset and let the system automatically assign permissions, since so many users were struggling to get those right.

What might cause it to fail is if you tried to manually set the permissions when you created the dataset and then tried to use Automatic Permissions on top of that.

Regardless that’s probably not the main issue here, assuming you did manually set the permissions correctly.

Let’s start by checking the lifecycle log as suggested. Connect to ssh or use the Shell and enter sudo cat /var/log/app_lifecycle.log.

Here is my latest lifecycle log after I tried your suggestion of letting it auto set the permissions on the poetgress data set.

GNU nano 7.2 /var/log/app_lifecycle.log
[2025/03/03 09:32:54] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘nextcloud’ app: Network ix-nextcloud_default Creating
Network ix-nextcloud_default Created
Container ix-nextcloud-permissions-1 Creating
ime=“2025-03-03T09:32:49-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T09:32:49-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-permissions-1 Created
Container ix-nextcloud-redis-1 Creating
Container ix-nextcloud-postgres_upgrade-1 Creating
Container ix-nextcloud-redis-1 Created
Container ix-nextcloud-postgres_upgrade-1 Created
Container ix-nextcloud-postgres-1 Creating
Container ix-nextcloud-postgres-1 Created
Container ix-nextcloud-nextcloud-1 Creating
time=“2025-03-03T09:32:49-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T09:32:49-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T09:32:49-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T09:32:49-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-nextcloud-1 Created
Container ix-nextcloud-imaginary-1 Creating
Container ix-nextcloud-cron-1 Creating
time=“2025-03-03T09:32:50-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-imaginary-1 Created
Container ix-nextcloud-cron-1 Created
Container ix-nextcloud-permissions-1 Starting
Container ix-nextcloud-permissions-1 Started
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-redis-1 Starting
Container ix-nextcloud-postgres_upgrade-1 Starting
Container ix-nextcloud-redis-1 Started
Container ix-nextcloud-postgres_upgrade-1 Started
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-postgres_upgrade-1 Waiting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-postgres_upgrade-1 service “postgres_upgrade” didn’t complete successfully: exit 1
service “postgres_upgrade” didn’t complete successfully: exit 1

Hmm, I haven’t seen that one before.

Do you have Postgres Image 13 or 17 selected? Some users have said recently that switching to 17 allowed them to deploy successfully.

I’ve seen that comment too. I’ve tried both, but this was tried with it set to 17.

Two things I can think of to try in that case are

  1. (If needed) select Enable ACL for your Postgres dataset and reenter your Host Path. Then use ADD to add full permissions ACL entries for 999:999, and also select Force Flag.

  2. Delete your existing postgres dataset and create a new one using the Generic preset, make no further configuration changes. Then select Automatic Permissions in the app.

The only other thing I can think of is that I’m not entirely clear on how you have your storage set up, but if you have a parent Nextcloud dataset with the others underneath it, there could be a permissions issue there preventing the postgres update from access to the child dataset?

Data set structure looks like screenshot below:


Should the parent Nexcloud dataset be setup as Generic or App? Should its owner & group be left as “root”? What about its type being POSIX??? What does giving user & group 999 full control cause to happen?

The tutorial says “Creating the parent dataset with the preset set to Generic causes permissions issues when you try to create the datasets the app requires with the preset set to Apps.”
So I’d say Apps.

I think this is fine. You may have to also give 568 (apps) access? I’m not sure because I haven’t set Nextcloud up in a little while.

This is expected by postgres, which is one of the reasons the Automatic Permissions checkbox was added.

Gives permissions to 999(netdata):999(docker)

OK, will delete ALL four datasets once again and be sure I know how they are created. Likely the tenth time in the last week.

When you say, “You may have to also give 568 (apps) access?” Access where (In which dataset)?

Nextcloud NOW setup as APP - screenshot below:


The app user poped into the permissions, must be because of be setup as an apps dataset. I also set type to POSIX. . .

post_gres dataset NOW setup as APP with type POSIX with ACL below:

After deleting datasets and recreating them as suggested above Nextcloud failed to install. Tried with permissions set to Automatic first error log below.

Then second try with what I believe is properlly set ACL settings and FORCE set on.

Both error log appear to be identical. . . NOT sure what that tellls me other than maybe my issue is not the way the post_gres dataet is configured.

ERROR log with Host path “port_gres data”" setup with NO ACL and permmisions box checked to AUTOMATIC…

[2025/03/03 14:04:28] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘nextcloud’ app: Network ix-nextcloud_default Creating
Network ix-nextcloud_default Created
Container ix-nextcloud-permissions-1 Creating
time=“2025-03-03T14:04:12-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T14:04:12-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-permissions-1 Created
Container ix-nextcloud-redis-1 Creating
Container ix-nextcloud-postgres_upgrade-1 Creating
Container ix-nextcloud-redis-1 Created
Container ix-nextcloud-postgres_upgrade-1 Created
Container ix-nextcloud-postgres-1 Creating
Container ix-nextcloud-postgres-1 Created
Container ix-nextcloud-nextcloud-1 Creating
time=“2025-03-03T14:04:12-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T14:04:12-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T14:04:12-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T14:04:12-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-nextcloud-1 Created
Container ix-nextcloud-nginx-1 Creating
Container ix-nextcloud-cron-1 Creating
Container ix-nextcloud-imaginary-1 Creating
time=“2025-03-03T14:04:13-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T14:04:13-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-imaginary-1 Created
Container ix-nextcloud-nginx-1 Created
Container ix-nextcloud-cron-1 Created
Container ix-nextcloud-permissions-1 Starting
Container ix-nextcloud-permissions-1 Started
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-redis-1 Starting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-postgres_upgrade-1 Starting
Container ix-nextcloud-redis-1 Started
Container ix-nextcloud-postgres_upgrade-1 Started
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-postgres_upgrade-1 Waiting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-postgres_upgrade-1 Exited
Container ix-nextcloud-postgres-1 Starting
Container ix-nextcloud-postgres-1 Started
Container ix-nextcloud-redis-1 Waiting
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-postgres-1 Waiting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-redis-1 Healthy
Container ix-nextcloud-postgres-1 Healthy
Container ix-nextcloud-nextcloud-1 Starting
Container ix-nextcloud-nextcloud-1 Started
Container ix-nextcloud-nextcloud-1 Waiting
Container ix-nextcloud-nextcloud-1 Waiting
Container ix-nextcloud-nextcloud-1 Waiting
Container ix-nextcloud-nextcloud-1 Error
Container ix-nextcloud-nextcloud-1 Error
Container ix-nextcloud-nextcloud-1 Error
dependency failed to start: container ix-nextcloud-nextcloud-1 is unhealthy

ERROR log with Host path “port_gres data”" setup with ACL checked and permmisions setup in dataset…

[2025/03/03 13:48:45] (ERROR) app_lifecycle.compose_action():56 - Failed ‘up’ action for ‘nextcloud’ app: Network ix-nextcloud_default Creating
Network ix-nextcloud_default Created
Container ix-nextcloud-permissions-1 Creating
time=“2025-03-03T13:45:47-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T13:45:47-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-permissions-1 Created
Container ix-nextcloud-redis-1 Creating
Container ix-nextcloud-postgres_upgrade-1 Creating
Container ix-nextcloud-redis-1 Created
Container ix-nextcloud-postgres_upgrade-1 Created
Container ix-nextcloud-postgres-1 Creating
Container ix-nextcloud-postgres-1 Created
Container ix-nextcloud-nextcloud-1 Creating
time=“2025-03-03T13:45:47-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T13:45:47-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T13:45:47-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T13:45:47-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-nextcloud-1 Created
Container ix-nextcloud-imaginary-1 Creating
Container ix-nextcloud-cron-1 Creating
Container ix-nextcloud-nginx-1 Creating
time=“2025-03-03T13:45:48-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
time=“2025-03-03T13:45:48-06:00” level=warning msg=“config uid, gid and mode are not supported, they will be ignored”
Container ix-nextcloud-imaginary-1 Created
Container ix-nextcloud-nginx-1 Created
Container ix-nextcloud-cron-1 Created
Container ix-nextcloud-permissions-1 Starting
Container ix-nextcloud-permissions-1 Started
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-postgres_upgrade-1 Starting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-redis-1 Starting
Container ix-nextcloud-postgres_upgrade-1 Started
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-postgres_upgrade-1 Waiting
Container ix-nextcloud-redis-1 Started
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-postgres_upgrade-1 Exited
Container ix-nextcloud-postgres-1 Starting
Container ix-nextcloud-postgres-1 Started
Container ix-nextcloud-redis-1 Waiting
Container ix-nextcloud-permissions-1 Waiting
Container ix-nextcloud-postgres-1 Waiting
Container ix-nextcloud-permissions-1 Exited
Container ix-nextcloud-redis-1 Healthy
Container ix-nextcloud-postgres-1 Healthy
Container ix-nextcloud-nextcloud-1 Starting
Container ix-nextcloud-nextcloud-1 Started
Container ix-nextcloud-nextcloud-1 Waiting
Container ix-nextcloud-nextcloud-1 Waiting
Container ix-nextcloud-nextcloud-1 Waiting
Container ix-nextcloud-nextcloud-1 Error
Container ix-nextcloud-nextcloud-1 Error
Container ix-nextcloud-nextcloud-1 Error
dependency failed to start: container ix-nextcloud-nextcloud-1 is unhealthy

Agreed. It looks like it successfully started postgres this time, the question is what else made it fail after that point. I don’t have any other ideas based on what I’ve seen so far unfortunately.

Thank you! I certainly appreciate your help with this, you have confirmed some of my thoughts as how this needs to be setup. Maybe someone will spot an issue I am overlooking.