Post Aa9XoBYlPyWF9BNKfg by pasmac@atmasto.com
 (DIR) More posts by pasmac@atmasto.com
 (DIR) Post #Aa8VuQTCV6cE3sf3eC by seb@ioc.exchange
       2023-09-25T20:13:35Z
       
       0 likes, 0 repeats
       
       #mastoadmin Anyone else ran into the issue that the streaming@4000 service didn't want to come up after 4.2 upgrade? (Looking for a solution...)
       
 (DIR) Post #Aa8WPegFiTOR6zeom8 by telsin@sphere.fx4.net
       2023-09-25T20:19:14Z
       
       0 likes, 0 repeats
       
       @seb if you had modified your streaming config for db pool and or streaming cluster before, the old environment variable "STREAMING_CLUSTER_NUMBER=x" breaks the new streamer. Removed that and it started normally. Good luck!
       
 (DIR) Post #Aa8XVwzodGoJblNE5w by pasmac@atmasto.com
       2023-09-25T20:28:48Z
       
       0 likes, 0 repeats
       
       @seb I am doing a clean live install meaning:Delete live folder (always with .env.prod and db backup ) then do the installation from scratch when reach the config I put the previous .env.production. Also copy the the new services and nginx conf (don’t forgetting the “hardening” tls, etc) and voila . Performed also de db migration not sure if needed …Nodejs 18 is working also …
       
 (DIR) Post #Aa8oqyKaYvHj3ChRS4 by seb@ioc.exchange
       2023-09-25T23:45:53Z
       
       0 likes, 0 repeats
       
       @pasmac I must be doing something wrong. This also ended in a Node-Error, although a different one.
       
 (DIR) Post #Aa9XoBYlPyWF9BNKfg by pasmac@atmasto.com
       2023-09-26T08:09:06Z
       
       0 likes, 0 repeats
       
       @seb Sorry for the late response: needed to increase chars limit :PSo my receipt for upgrading from 4.1 to 4.2: pg_dump -W -F t mastodon_production > backup_fi_22_09_2023.tar cp ~mastodon/live/.env.production /opt/bck/ su - mastodon cd ~mastodon rm live -rf #Be aware of bookmarks etc you may loose them with deleting all folder git clone https://github.com/mastodon/mastodon.git live && cd livegit fetch && git checkout v4.2.0 bundle config deployment 'true' bundle config without 'development test' bundle install -j$(getconf _NPROCESSORS_ONLN) yarn install --pure-lockfile cp /opt/bck/.env.production ~mastodon/live/ cd ~mastodon/live bundle install yarn install --frozen-lockfile SKIP_POST_DEPLOYMENT_MIGRATIONS=true RAILS_ENV=production bundle exec rails db:migrate RAILS_ENV=production bundle exec rails assets:precompile RAILS_ENV=production bundle exec rails db:migrate#as root or sudo#backup old confcp /etc/nginx/sites-enabled/mastodon /opt/bck/cp /home/mastodon/live/dist/nginx.conf /etc/nginx/sites-available/mastodon#Re enter your harneded nginx mastodon configcp /home/mastodon/live/dist/mastodon-*.service /etc/systemd/system/systemctl daemon-reloadsystemctl enable --now mastodon-web mastodon-sidekiq mastodon-streaming