:bc: Attention Beige Party-goers! :bc:
-
:bc: Attention Beige Party-goers! :bc:
Ok! Streaming service appears to be working now! Long story short, I think I misinterpreted some of the upgrade steps for 4.3.0. One of the major changes is that the streaming service got moved over to a separate docker image. Well I updated the yaml file to point to the new image, but I missed a step because the build for the streaming service also has to point to a separate streaming docker file.
Ok, long story even shorter: pretty sure the streaming service was broken since the last update, but due to the nature of docker containers it was continually restarting, so it would work in fits and starts and then die again.
I did hear some reports that feeds seemed to be "stuck" and then would update after several minutes, so that would seem to fit with that theory. Weird thing is that every time I checked myself it seemed to be working, but I didn't go into docker and actually check the status of the streaming service. I have done so now and everything seems to be up and healthy, so I think we are good.
Anyways, welcome to version 4.3.1, and thanks for bearing with me while I figure all this out!
Beige-bless :bb:
PS: If any #MastoAdmins, are having this issue, this is where I found the solution:
nodejs disappears from the container (main branch) · Issue #28828 · mastodon/mastodon
Steps to reproduce the problem docker compose build docker compose up -d [FATAL tini (7)] exec node failed: No such file or directory ... Expected behaviour Start the streaming backend Actual behaviour [FATAL tini (7)] exec node failed: ...
GitHub (github.com)
-
Tyrion 🐧🏴☠️replied to Velocirooster adminensis :bc: last edited by
@thomasp <<< Could this have anything to do with the "delays" we've been seeing in the Vivaldi instance since the 4.3 upgrade?
-
@TyrionTargaryen No, things would be much more broken if the streaming service were offline. I know this because ours also needed fixing in the first 20 minutes on our 4.3 launch day.
-
Gotcha!
