Rank 2: Process
what container do you need logs of?
Votes
0
Replies
24
Participants
Unknown
Messages
25
Rank 2: Process
what container do you need logs of?
Rank 2: Process
Rank 2: Process
I did get The _APP_CONNECTIONS_MAX variable is not set. Defaulting to a blank string when I run the command the first try.
Admin
how did you upgrade?
Rank 2: Process
I upgraded to 1.4.0 using this command
docker run -it --rm --volume /var/run/docker.sock:/var/run/docker.sock --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw --entrypoint="install" appwrite/appwrite:1.4.0 then I cd into appwrite directory, to run the migration command it failed. So I noticed that 1.4.1 was released so I backed out of appwrite directory and I ran docker run -it --rm --volume /var/run/docker.sock:/var/run/docker.sock --volume "$(pwd)"/appwrite:/usr/src/code/appwrite:rw --entrypoint="install" appwrite/appwrite:1.4.1 then I cd back into the appwrite directory to run the migration command, for it to fail also
Admin
what's in your appwrite folder right now? and what's the output of pwd?
Rank 2: Process
Admin
what's the output of docker compose logs redis?
Rank 2: Process
Rank 2: Process
Do you need more before that It looks normal before that.
Admin
seems like it's online... but the logs from the other containers are still saying they can't connect?
Rank 2: Process
Yeah, so strange
Rank 2: Process
Didn't have this issue before 1.4.0 though
Rank 2: Process
Should I try to go back?
Admin
no. try to restart everything with docker compose down && docker compose up -d
Rank 2: Process
Lol everything is working now? Should I try running the migration command again?
Rank 2: Process
Also added _APP_CONNECTIONS_MAX=20 to .env before restarting everything. (said in the GitHub page)
Rank 2: Process
Ok running the migration command everything is working.
Rank 2: Process
So either the fix is
A. 1. Add `_APP_CONNECTIONS_MAX=20` to `.env` file. 2. then run `docker compose down && docker compose up -d` 3. then run the migration command as usual.
(Maybe?)B. 1. run `docker compose down && docker compose up -d` 2. then run the migration command as usual.```Admin
you shouldn't need that anymore
Rank 2: Process
Ok for testing I removed _APP_CONNECTIONS_MAX=20 from .env and I ran docker compose down && docker compose up -d and still everything works lol. So yeah I guess just restarting everything fixes it.
Rank 2: Process
Idk anyways, thank you!
Admin
[SOLVED] Failed to create connection: php_network_getaddresses: getaddrinfo failed
I want to just mention that I had the same issue today after 1.4.0 upgrade - the "fix" above works, but maybe a PSA could be added if it's the same for everyone upgrading.
Admin
you should be upgrading to the latest patch version (1.4.1 right now) which doesn't have the problem