I guess kind of obvious when I say it but I'm going to say it anyway (fixed a nextcloud error message)
I guess kind of obvious when I say it but I'm going to say it anyway (fixed a nextcloud error message)
Anyone who knows me knows that I've been using next cloud forever, and I fully endorse anyone doing any level of self hosting should have their own. It's just a self-hosted Swiss army knife, and I personally find it even easier to use than something like SharePoint.
I had a recurring issue where my logs would show "MYSQL server has gone away". It generally wasn't doing anything, but occasionally would cause large large file uploads to fail or other random failures that would stop quickly after.
The only thing I did is I went in and doubled wait_timeout in my /etc/mysql/mariadb.conf.d/50-server.cnf
After that, my larger file uploads went through properly.
It might not be the best solution but it did work so I figured I'd share.
Just read the other day here that Nextcloud runs much much better with PostgreSQL. Migrating to that (or the all in one installation) is my next big project.
Yes way faster, I switched a long time ago. If you want more extra speed add redis cache via unix sockets ☝🏻
Looks like I’ve got a project for next weekend
Interesting. Do you remember where you read this?
The process seems simple enough. I'm on the nextcloud:stable docker image, so adding a postgres container is really easy, but it's a scary task...
Okay, did the migration just now. Everything seems a little more responsive, but I wouldn't call it way faster.
Either way, it wasn't very scary at all. For anybody coming after me:
- add postgres container to compose file like so. I named mine "postgres", added a "postgres" volume, and added it to depends_on for app and cron
- run migration command from nextcloud app container like any other occ command and check admin settings/system for db state:
./occ db:convert-type --password $POSTGRES_PASSWORD --all-apps pgsql $POSTGRES_USER postgres $POSTGRES_DB - remove old "db" container and volume and all references to it from compose file and run
docker compose up -d --remove-orphans
Well, another guy responded before you, so that would be the last time I heard it.
It was probably on one of the posts in this community.