6 months ago
Application failed to respond
This error appears to be caused by the application.
If this is your project, check out your deploy logs to see what went wrong. Refer to our docs on Fixing Common Errors for help, or reach out over our Help Station.
If you are a visitor, please contact the application owner or try again later.
Request ID:
advwm21IR-q1wQxPrJsmnA
9 Replies
6 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
6 months ago
Your Redis instance saw some big spikes in memory usage that caused it to run out of memory and crash. I've restarted them for you and you should be good to go. You can restart them yourself from the project dashboard in the future.
If you expect spikes like this going forward, you can try to set a Variable to spec the maximum memory Redis can use:
REDIS_MAXMEMORY= 8gb for example.
Read about variables here: https://docs.railway.com/guides/variables
Status changed to Awaiting User Response Railway • 6 months ago
Status changed to Awaiting Railway Response Railway • 6 months ago
5 months ago
This thread has been marked as public for community involvement, as it does not contain any sensitive or personal information. Any further activity in this thread will be visible to everyone.
Status changed to Open brody • 6 months ago
5 months ago
do you have any logs to share? how are the metrics of your services?
5 months ago
Logs:
Lost Redis connection. Trying to reconnect in 1s... (0s/10s)
Lost Redis connection. Trying to reconnect in 1s... (1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (2s/10s)
Lost Redis connection. Trying to reconnect in 1s... (3s/10s)
Lost Redis connection. Trying to reconnect in 1s... (4.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (5.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (6.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (7.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (8.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (9.1s/10s)
Unable to connect to Redis after trying to connect for 10s
Exiting process due to Redis connection error
Last session crashed
Initializing n8n process
n8n ready on ::, port 5678
n8n Task Broker ready on 127.0.0.1, port 5679
Lost Redis connection. Trying to reconnect in 1s... (0s/10s)
Lost Redis connection. Trying to reconnect in 1s... (1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (2s/10s)
Lost Redis connection. Trying to reconnect in 1s... (3s/10s)
Lost Redis connection. Trying to reconnect in 1s... (4.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (5.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (7.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (8.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (9.1s/10s)
Unable to connect to Redis after trying to connect for 10s
Exiting process due to Redis connection error
Last session crashed
n8n Task Broker ready on 127.0.0.1, port 5679
Lost Redis connection. Trying to reconnect in 1s... (0s/10s)
Lost Redis connection. Trying to reconnect in 1s... (1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (2s/10s)
Lost Redis connection. Trying to reconnect in 1s... (3s/10s)
Lost Redis connection. Trying to reconnect in 1s... (4.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (5.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (6.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (7.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (8.1s/10s)
Lost Redis connection. Trying to reconnect in 1s... (9.1s/10s)
Unable to connect to Redis after trying to connect for 10s
Exiting process due to Redis connection error
Last session crashed
Initializing n8n process
n8n ready on ::, port 5678
n8n Task Broker ready on 127.0.0.1, port 5679
Lost Redis connection. Trying to reconnect in 1s... (0s/10s)
Lost Redis connection. Trying to reconnect in 1s... (1s/10s)
[Redis client] connect ETIMEDOUT
[Redis client] connect ETIMEDOUT
Unable to connect to Redis after trying to connect for 10s
Exiting process due to Redis connection error
5 months ago
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/9df3b577-dac4-4c74-976f-6c57ad84db5a/vol_i68jhvkbqer3n9yf
Starting Container
redis 18:33:31.90 INFO ==>
redis 18:33:31.90 INFO ==> Welcome to the Bitnami redis container
redis 18:33:31.90 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
redis 18:33:31.91 INFO ==> NOTICE: Starting August 28th, 2025, only a limited subset of images/charts will remain available for free. Backup will be available for some time at the 'Bitnami Legacy' repository. More info at https://github.com/bitnami/containers/issues/83267
redis 18:33:31.91 INFO ==>
redis 18:33:31.91 INFO ==> Starting Redis setup
redis 18:33:31.99 INFO ==> Initializing Redis
redis 18:33:32.02 INFO ==> Setting Redis config file
redis 18:33:32.04 INFO ==> Redis setup finished!
redis 18:33:32.06 INFO ==> Starting Redis
1:C 27 Aug 2025 18:33:32.086 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
1:C 27 Aug 2025 18:33:32.086 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
1:C 27 Aug 2025 18:33:32.086 * Redis version=8.2.1, bits=64, commit=00000000, modified=1, pid=1, just started
1:C 27 Aug 2025 18:33:32.086 * Configuration loaded
1:M 27 Aug 2025 18:33:32.087 * monotonic clock: POSIX clock_gettime
1:M 27 Aug 2025 18:33:32.088 * Running mode=standalone, port=6379.
1:M 27 Aug 2025 18:33:32.089 * Server initialized
1:M 27 Aug 2025 18:33:32.093 * Reading RDB base file on AOF loading...
1:M 27 Aug 2025 18:33:32.093 * Loading RDB produced by version 8.2.0
1:M 27 Aug 2025 18:33:32.093 * RDB age 1236378 seconds
1:M 27 Aug 2025 18:33:32.093 * RDB memory usage when created 0.62 Mb
1:M 27 Aug 2025 18:33:32.093 * RDB is base AOF
1:M 27 Aug 2025 18:33:32.093 * Done loading RDB, keys loaded: 0, keys expired: 0.
1:M 27 Aug 2025 18:33:32.093 * DB loaded from base file appendonly.aof.1.base.rdb: 0.002 seconds
1:M 27 Aug 2025 18:33:33.006 # Bad file format reading the append only file appendonly.aof.1.incr.aof: make a backup of your AOF file, then use ./redis-check-aof --fix <filename.manifest>
Mounting volume on: /var/lib/containers/railwayapp/bind-mounts/9df3b577-dac4-4c74-976f-6c57ad84db5a/vol_i68jhvkbqer3n9yf
5 months ago
Did you try doing what is written in these logs? Do you have data in this redis instance? If not and if you don't have a lot of experience with redis it might be quicker to delete & recreate...