NyalomaSzemed
Postgress DB connection issue
The db was always operational, the main issue with the connection. In the logs we can see all of the rejected connections, also, if we are trying to attempt any connection from a fake account. I have to say, we still have the priginal user and password, so that's could cause the issue. Now we are able to attach the volume to a volume file browser container and access the db data via file manager. Is there any way to modify the db with a new connection credentials?
19 replies
Postgress DB connection issue
I don't think so, before the connection lost I did not modified the environmental settings. Also, on the same project I added a brand new postgress db with the same settings, and I can connect it to pgadmin without any issue. I think the main problem is related to the private networking... Is there any option or troubleshoot step to check if the db user/password are match?!
19 replies
Postgress DB connection issue
Recreated a similar environment on my colleges user, and double check the settings. While I tried to reconnect umami to the db I also tried different environment settings. The thing what I’m trying to say whit this, the the env settings are fine, the issue is not related to this. It seems that the db cannot be reached with the correct credentials.
19 replies
umami stoped working
Yes, confirmation, sorry. I started this service while in trial, after I upgraded to hobby it doesn't changed. I think because of the service interruption. It would be nice if Railway send any notification about volume size increases.
16 replies
umami stoped working
Ohh god, that was it. You're awwsome @Brody ! 🙏
For the record:
Postgres service, Settings, Go to Volume. Normally, the default size of a volume is limited at 500 MB, which can be resized to 5 GB with a ridiculously long command, which is quite funny. 😂
After doing these I just need to restart all of the services and everything is up and running again!
Again, thanks for the quick help, great community! 
16 replies
umami stoped working
Yes, there is a lot of message, but i'm not sure that these are errors. Regarding some research these messages could be normal:
"2024-01-01 21:17:23.143 UTC [7] LOG: checkpointer process (PID 20614) was terminated by signal 6: Aborted
2024-01-01 21:17:23.143 UTC [7] LOG: terminating any other active server processes
2024-01-01 21:17:23.146 UTC [7] LOG: all server processes terminated; reinitializing
2024-01-01 21:17:23.161 UTC [20616] LOG: database system shutdown was interrupted; last known up at 2024-01-01 21:17:23 UTC
2024-01-01 21:17:23.213 UTC [20616] LOG: database system was not properly shut down; automatic recovery in progress
2024-01-01 21:17:23.215 UTC [20616] LOG: redo starts at 1/728C74F8
2024-01-01 21:17:23.215 UTC [20616] LOG: invalid record length at 1/728C79F0: wanted 24, got 0
2024-01-01 21:17:23.215 UTC [20616] LOG: redo done at 1/728C79C8 system usage: CPU: user: 0.00 s, system: 0.00 s, elapsed: 0.00 s
2024-01-01 21:17:23.218 UTC [20617] LOG: checkpoint starting: end-of-recovery immediate wait
2024-01-01 21:17:23.218 UTC [20617] PANIC: could not write to file "pg_logical/replorigin_checkpoint.tmp": No space left on device"
16 replies