mastodon 4.4.1

sean

I'll try to have an upgrade procedure for this soon.

mergy

Probably going to go ahead and try this again since we are up to 4.4.2 now. Perhaps local ruby, etc...

sean

Still working on this on our end but it's possible that we've hit the limit on what we can support on CentOS 7.

I think we may be announcing some good news regarding the new operating system soon - it should be much easier to maintain apps like Mastodon on the newer system, if not natively on the filesystem then possibly in a container 😎

mergy

Ah - understood. I can hold I think.

sean

mergy thanks for your patience.

I was finally able to upgrade a working 4.3 install to 4.4.3 on CentOS 7 with the following steps:

First (after backing up your instance!), log into a fresh shell session and install Redis 6 in your home directory with the following commands:

mkdir -p ~/opt/redis/src
cd ~/opt/redis/src
wget https://github.com/redis/redis/archive/refs/tags/6.2.19.tar.gz
tar zxf 6.2.19.tar.gz
cd redis-6.2.19
source scl_source enable devtoolset-11 ruby32 nodejs20
make
find $PWD/src -type f -executable -name "redis*" | xargs -I _ ln -s _ $HOME/bin/
cd ~/apps/self_social
sed -i -e 's/rh-redis5//' start setenv

Next, update your instance to 4.4.0 with the following commands:

cd ~/apps/self_social
source setenv
cd mastodon
git fetch && git checkout v4.4.0
bundle install
yarn install --immutable
# I noticed warnings in yarn output but everything seems to have worked
RAILS_ENV=production bundle exec rails assets:precompile
SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate
../stop
gem install bundler -v '~> 2.6'
pkill -f supervisord
../start
RAILS_ENV=production bundle exec rails db:migrate

Finally, log out of your shell, log back in, then update to the latest 4.4.3 with the following commands:

cd ~/apps/self_social
source setenv
cd mastodon
git fetch && git checkout v4.4.3
bundle install
RAILS_ENV=production bundle exec rails assets:precompile
../restart

Thanks again for being so patient with this! Please let us know if you run into any further problems.

mergy

paring-down the storage now and backing-up first to try this. Thanks again. Will update on status...

mergy

Something is up with the redis I think.
E, [2025-08-10T22:28:02.113297 #202039] ERROR -- : RedisCacheStore: read_entry failed, returned nil: Redis::CannotConnectError: Error connecting to Redis on <path>/mastodon/tmp/sockets/redis.sock (Errno::ECONNREFUSED)
E, [2025-08-10T22:28:02.166689 #202039] ERROR -- : RedisCacheStore: write_entry failed, returned nil: Redis::CannotConnectError: Error connecting to Redis on <path>/mastodon/tmp/sockets/redis.sock (Errno::ECONNREFUSED)
E, [2025-08-10T22:28:02.167192 #202039] ERROR -- : RedisCacheStore: write_entry failed, returned nil: Redis::CannotConnectError: Error connecting to Redis on <path>/mastodon/tmp/sockets/redis.sock (Errno::ECONNREFUSED)

Checked perms on the new /opt and everything and touhced a file for the redis.sock and check mastodon/tmp/socket perms, but meh.

mergy

I think it's very close. So, will stick with this.

mergy

I am running now on 4.4.3.

I manually started redis-server and point it at the ~/apps/<app>/mastdon/redis.conf

and we're up.

nick

mergy I was looking at your setup on server and was just going to mention something like that, glad you got it going 🙂

mergy

yep - had to play

but we're in business. How best should I keep redis-server running? I guess I can just add that somewhere.

nick

mergy That is already handled by supervisor via the Mastodon start script. You can verify the redis block in the supervisord.conffile that starts redis-server. Try a full stop/wait/start to see if it loads automatically or not (it should).

mergy

nick So yeah, it doesn't want to go on that but we'll see. I might give it the full path to redis-server and see.

mergy

yeah - not taking it via the supervisord.conf, but if I go in and manually start redis via the ~/opt/redis/src it seems to hold.

mergy

could also be when I hit my opalstack ram limit, all things die and I have to restart.

nick

mergy Hi there, I pinged your past related support ticket with more details.

« Previous Page