I really doubt this is what fixed it, but in docker-compose.yml I changed:

- RUST_LOG="warn"

to

- RUST_LOG="warn,lemmy_server=debug,lemmy_api=debug,lemmy_api_common=debug,lemmy_api_crud=debug,lemmy_apub=debug,lemmy_db_schema=debug,lemmy_db_views=debug,lemmy_db_views_actor=debug,lemmy_db_views_moderator=debug,lemmy_routes=debug,lemmy_utils=debug,lemmy_websocket=debug"
- RUST_BACKTRACE=full

(got the latter from the sample docker-compose.yml on GitHub).

It had been going for 10h, so think it world have been done by then.

Hmm, seems to have gone away after a few more restarts and after changing some logging options :)

Is anyone else seeing super high CPU usage after updating? The docker container seems to spawn a ton of lemmy_server processes, each eating up 50-100% of a core. I don’t see anything suspicious in the logs though, it just calmly processes posts.

I’m nearly certain Ziply will sell you business fiber to a home address. Price does seem quite low, but then again they are now selling residential gig fiber for $80/$90.

As much as I hate redirecting to Reddit, the ZiplyFiber subreddit is very actively monitored and they’d quickly answer those questions there. I’ve found that to be much more accurate and quick than phone sales / support, although the dedicated business support is probably much better.

Ziply is amazing, I’m sure they can sort you out.

I found this website to be pretty helpful in terms of walking you through a docker- based install:

https://www.bentasker.co.uk/posts/blog/general/running-a-lemmy-social-networking-instance-using-docker-compose.html

The official docs are a little sparse at times.

Super straightforward upgrade via docker compose, thanks for all the hard work ❤️