AIO not working, trying to recover

ā„¹ļø Support šŸ“¦ Appliances (Docker, Snappy, VM, NCP, AIO)
, ,
1

My AIO setup had been working and honestly Iā€™m not sure why/when it stopped because I donā€™t use it every day. Hoping someone can give me some help getting it back up.

MasterContainer logs give this over and over

WARNING: bridge-nf-call-iptables is disabled

981

WARNING: bridge-nf-call-ip6tables is disabled

982

WARNING: bridge-nf-call-iptables is disabled

983

WARNING: bridge-nf-call-ip6tables is disabled

984

Youā€™ve set NEXTCLOUD_MEMORY_LIMIT but not to an allowed value.

985

The string must start with a number and end with ā€˜Mā€™.

986

It is set to ā€˜1GBā€™.

Apache container just keeps saying: ā€œWaiting for Nextcloud to startā€

Nextcloud container log repeats:

nc: getaddrinfo for host ā€œnextcloud-aio-databaseā€ port 5432: Try again

982

Waiting for database to startā€¦

Database container, and I think this is the base problem is log repeats:

chmod: /var/run/postgresql: Operation not permitted

996

997

PostgreSQL Database directory appears to contain a database; Skipping initialization

998

999

2024-10-24 10:26:58.618 CDT [14] FATAL: database files are incompatible with server

1000

2024-10-24 10:26:58.618 CDT [14] DETAIL: The data directory was initialized by PostgreSQL version 15, which is not compatible with this version 16.4.

I canā€™t get into the AIO interface so no idea how I can upgrade the postgresSQL. Any help would be appreciated

2

Sorry for being terse right now, but:

Youā€™ll find a solution in the docs
https://github.com/nextcloud/all-in-one

Seems to me you had a typo in NEXTCLOUD_MEMORY_LIMITS.

You donā€™t have data to lose, because your cloud was never up and running, right?

Restart with the plain command for new install, refrain from extra options for a start.

1 Like
3

Thanks, that got me back into AIO (editing memory), now however Iā€™m getting this in my database container:

2024-10-25T20:23:57.116011009Z DUMP dir is not writeable by postgres user.

no idea what the DUMP dir might be, nor what the permission would be but I assume if I knew that I could chown/chmod it to find the next step in the puzzle.

4

My cloud was up and running, so I do have data to lose, but it was stored on the host, though there were some users set up and such for family so Iā€™d like to avoid losing that if at all possible but if needed I will redo the whole thing.

5

Can You open the admin page?
Are there backups? Just donā€™t know if backups are on by default.

6

Are you talking the https://hostname:8080 as the admin page? If so then yes. If not then not sure what you mean.

Last backup failed

7

If I new what in the DB container contained the actual Database, could I pull it out, delete the container, have AIO recreate the container and then drop the old database in? IF so Iā€™m completely open to doing something like that.

8

See all-in-one/Containers/postgresql/start.sh at a0ce2c1bec82e7807e41716d71c582e65f805462 Ā· nextcloud/all-in-one Ā· GitHub

This problem can only happen if the permissions of the underlying docker volumes were changed outside AIO.

So something happened on your host that changed the permissions of the docker volumes to incorrect values.

9

right hostname:8080 it is.
Myself I would not dare to figgle with AIOs inner organs. Just restore the best backup one has.
Nighty night for now.

1 Like
10

Would you be willing to let me know what the permissions of the container are supposed to be? It looks the same (owner and permission) as other AIO containers but I can always redo them in case something isnā€™t displaying correctly

11

I would also rather recommend to restore a backup

12

This topic was automatically closed after 90 days. New replies are no longer allowed.