#Latest Update
1 messages · Page 1 of 1 (latest)
The appsmith-server container is returning unhealthy, the editor is returning okay - we are running on the Multi Container set-up as we haven't migrated. I'll get you the logs from the appsmith-server, once I remember the docker exec command
Hi! I’m sorry you are experiencing this error.
Please send us the server logs to help us investigate it. You can grab the logs
by running docker logs -f appsmith.
Or you could follow the steps from this guide on how to get the logs:
https://github.com/felix-appsmith/guide-how-to-get-logs-appsmith
Log attached - looks like a Mongo Error.
Thank you. Our team will investigate this and get back to you.
Hey @limber lintel! Can you please let us know which MongoDB version you
are using?
One sec will check - it was on the Multi Container Set-up we haven't changed
Looks like 4.4.6
db version v4.4.6
Build Info: {
"version": "4.4.6",
"gitVersion": "72e66213c2c3eab37d9358d5e78ad7f5c1d0d0d7",
"openSSLVersion": "OpenSSL 1.1.1 11 Sep 2018",
"modules": [],
"allocator": "tcmalloc",
"environment": {
"distmod": "ubuntu1804",
"distarch": "x86_64",
"target_arch": "x86_64"
}
}
Hey! Could you please upgrade MongoDB to 5.0.14 and try again?
Does the Multicontainer set-up store the data on the main drive?
yeah okay I've found it - let me run a back-up
I have 2 instances, both are down now 😦
It happened after last update
Mongo is down
On both instances
The same reason
thanks the upgrade to 5.0.14 fixed the issue,.
@tropic elm are you also unable to get your instance working?
If yes, I'd like to see the logs first. Can you please share the logs?
Container in unhealthy
Mongodb connections are rejected
And Mongo is down
I can do this in 20 minutes
As i am out of Office already
Run docker logs -f [instance]
hello, should I provide any additional info?
i even did docker-compose down, pull and then up
right now I got:
Same thing has happened to my instance.
Sorry for the troubles you are facing. Please update your instance to version
v1.9.1 that we just released and let us know if this fixes the problem.
This did not fix the problem.
@plain dagger Was the update successful?
Could you please send us the server logs? You can grab the logs by running
docker logs -f appsmith.
Or you could follow the steps from this guide on how to get the
logs
Here’s also another solution for the 503 error:
https://docs.appsmith.com/help-and-support/troubleshooting-guide/action-errors/mongodb-errors#503---service-unavailable
[https://docs.appsmith.com/help-and-support/troubleshooting-guide/action-errors/mongodb-errors#503---service-unavailable]
Contribute to felix-appsmith/guide-how-to-get-logs-appsmith development by creating an account on GitHub.
Troubleshooting guide that provides solutions to common MongoDB errors that may occur while using Appsmith. Follow these steps to resolve any issues you may be experiencing with your MongoDB setup.
I am running 1.9.1 and still getting the 503 error. I tried to upgrade Mongo but it turns out my CPU is too old.
@plain dagger Got it. Please check if this command returns any value
for you: docker exec $(docker container ps | grep appsmith | awk '{print $1}') mongod --version
Got permission denied while trying to connect to the Docker daemon socket at uni x:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/v1.24/container s/json": dial unix /var/run/docker.sock: connect: permission denied
"docker exec" requires at least 2 arguments.
See 'docker exec --help'.
Usage: docker exec [OPTIONS] CONTAINER COMMAND [ARG...]
Run a command in a running container
db version v4.4.11
Build Info: {
"version": "4.4.11",
"gitVersion": "b7530cacde8432d2f22ed506f258ff9c3b45c5e9",
"openSSLVersion": "OpenSSL 1.1.1f 31 Mar 2020",
"modules": [],
"allocator": "tcmalloc",
"environment": {
"distmod": "ubuntu2004",
"distarch": "x86_64",
"target_arch": "x86_64"
}
}
How do I manually downgrade my AppSmith container?
Should I downgrade to 1.8.5? Can this fix a problem?
Checking with the team
Change index.docker.io/appsmith/appsmith-ce to
index.docker.io/appsmith/appsmith-ce:v1.8.15, and then do a docker-compose up
-d.
in your docker-compose file
1.9.1 still wasn't working for me, but the manual downgrade to 1.8.15 restored the functionality of my instance.
@plain dagger Thank you for confirming.
@tropic elm did you manage to downgrade to v1.8.15? Please let us know
if it works after that.
Yes, it worked. Thank you.