Cloudron Forum

Sounds good. Yes, we're happy to help with query optimisation in apps and send feedback upstream. This is the quickest way we can do that. With some luck, we'll all end up with faster apps from this R&D too.

@girish I saw no red indicators on the nav bar. I guess that would have helped me towards the source of the problem. But I will keep an eye if a service gets into trouble again.

Ok, finally sorted after stopping queries that were locking old txnids and then doing a full vacuum. I suppose restarting the postgres container could have done that. This was useful to find blocking queries, in addition to pg_terminate_backend: SELECT pid, datname, usename, state, backend_xmin, query FROM pg_stat_activity WHERE backend_xmin IS NOT NULL ORDER BY age(backend_xmin) DESC; Went from 88% full to 38% full in about 10 minutes.

@nebulon I didn't get any notifications in the dashboard for OOM which is why debugging was fairly unintuitive. @girish If I encounter it again, I'll check dmesg and let you know.

@debossnow Do I have to install a particular ADMIN PosgreSQL tool in my Cloudron application to see & administer this Mastadon database? You can use the Weberminal to get shell like access. On the top there will be button for Database access. And to see all my files & their paths in a UI do I need to install a separate directory or file browser in my Cloudron application? Like the Web Terminal you can use the File Manager to see your files. The path in the File Manager is always /app/data/.

@privsec That worked, thanks!

@girish I use DBeaver with an SSH tunnel. I just found an option that I forgot to toggle on -- "Show all databases". Now it shows all the databases! On a side note, I did first try to configure an SSH tunnel and a post-command to execute "/usr/local/bin/docker exec -ti postgresql bash" and that worked as well. But, only one tunnel is needed to the cloudron server to login as root that allows access to all databases. I'm good to go. Thanks for the help!

@murgero Thank you Before seeing this, I decided to be a 'windows user' and reboot the cloudron server. I guess same effect, but will definitely do your more limited kick next time. And yes it is working again. Many thanks

@girish thanks for the guidance, that's exactly what I was looking for

@Lanhild said in Postgresql multiple databases support: I'm not sure to understand? What I meant is maybe the manifest can use "postgreSQL": { "prefixCount": 10 } and it creates 10 databases or something like that. Also, multiple databases could benefit to the use of the addon as a "standalone" app - that could act as a simple PostgreSQL cluster. I think it will be nice to create PostgreSQL as an app and with a small frontend to add/remove databases and maybe manage roles. Maybe this app can not use existing addon. Of course, this app has to be developed!

@grienauer You can set this thread to "solved" yourself.

I finally managed to get to the bottom of this. There was a bug in the postgresql addon backup logic where connections were not closed properly. This resulted in periodic backups keeping lots of connections open. This is fixed in 6.3.

@amg-web I mean the recovery mode, which you can enable for the app in the "Repair" section on the app configure view in the Cloudron dashboard.

This should be fixed in the latest package.

@girish Dump now works fine. Thank's a lot!

@nebulon said in App Install & Uninstall fails with `Error : Inactive - Error getting IP of postgresql service`: I doubt this is related to your subdomains. Can you verify that unbound on the Cloudron is running and maybe restart the postgres addon? You are 100% right. The postgres service was simply not running. Silly me, could have checked that myself.

Thank you for sharing. There's a lot to unpack there, especially the postgres stuff. I can see how many users wouldn't know what to do there. Can you expand on all those 'postgres' parts and what to look for? The 'manual migration' may not be needed since the app will do that on restart exiting recovery mode.

@jensbee4 you have to wait for next cloudron release. The change is part of cloudron 5.6.2 (see the announcement category).

@girish don't worry I'll survive without this plugin thank you for your consideration

@girish Thanks! I was hoping to get an official feature going - but thanks, I'll check the link out!