Hi everyone,
I’m encountering a persistent issue with my Mastodon instance running in a Docker container on Unraid. After updating to version 4.3.8, when the container is started, I’ve noticed some scheduled tasks are queuing and completing successfully according to the logs, but goes no further. Mastodon is not able to start.
Here’s a sample of the log output showing the successful execution of scheduler tasks:
2025-06-23T18:16:41.528Z pid=314 tid=5me INFO: Booting Sidekiq 6.5.12 with Sidekiq::RedisConnection::RedisAdapter options {:url=>"redis://192.168.0.133:6379/0", :driver=>:hiredis, :namespace=>nil}
[320] Puma starting in cluster mode...
[320] * Puma version: 6.4.3 (ruby 3.3.8-p144) ("The Eagle of Durango")
[320] * Min threads: 5
[320] * Max threads: 5
[320] * Environment: production
[320] * Master PID: 320
[320] * Workers: 2
[320] * Restarts: (✔) hot (✖) phased
[320] * Preloading application
[320] * Listening on http://0.0.0.0:3000
[320] Use Ctrl-C to stop
[320] - Worker 0 (PID: 404) booted in 0.01s, phase: 0
[320] - Worker 1 (PID: 414) booted in 0.01s, phase: 0
Connection to localhost (127.0.0.1) 3000 port [tcp/*] succeeded!
[ls.io-init] done.
2025-06-23T18:16:46.529Z pid=314 tid=5me INFO: Booted Rails 7.1.5.1 application in production environment
2025-06-23T18:16:46.529Z pid=314 tid=5me INFO: Running in ruby 3.3.8 (2025-04-09 revision b200bad6cd) +YJIT [x86_64-linux-musl]
2025-06-23T18:16:46.529Z pid=314 tid=5me INFO: See LICENSE and the LGPL-3.0 for licensing details.
2025-06-23T18:16:46.529Z pid=314 tid=5me INFO: Upgrade to Sidekiq Pro for more features and support: https://sidekiq.org
2025-06-23T18:16:46.538Z pid=314 tid=5me INFO: Loading Schedule
2025-06-23T18:16:46.538Z pid=314 tid=5me INFO: Scheduling scheduled_statuses_scheduler {"every"=>"5m", "class"=>"Scheduler::ScheduledStatusesScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.547Z pid=314 tid=5me INFO: Scheduling trends_refresh_scheduler {"every"=>"5m", "class"=>"Scheduler::Trends::RefreshScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.547Z pid=314 tid=5me INFO: Scheduling trends_review_notifications_scheduler {"every"=>"6h", "class"=>"Scheduler::Trends::ReviewNotificationsScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.548Z pid=314 tid=5me INFO: Scheduling indexing_scheduler {"interval"=>"1 minute", "class"=>"Scheduler::IndexingScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.558Z pid=314 tid=5me INFO: Scheduling vacuum_scheduler {"cron"=>"54 5 * * *", "class"=>"Scheduler::VacuumScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.638Z pid=314 tid=5me INFO: Scheduling follow_recommendations_scheduler {"cron"=>"27 6 * * *", "class"=>"Scheduler::FollowRecommendationsScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.654Z pid=314 tid=5me INFO: Scheduling user_cleanup_scheduler {"cron"=>"41 4 * * *", "class"=>"Scheduler::UserCleanupScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.680Z pid=314 tid=5me INFO: Scheduling ip_cleanup_scheduler {"cron"=>"54 4 * * *", "class"=>"Scheduler::IpCleanupScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.688Z pid=314 tid=5me INFO: Scheduling pghero_scheduler {"cron"=>"0 0 * * *", "class"=>"Scheduler::PgheroScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.695Z pid=314 tid=5me INFO: Scheduling instance_refresh_scheduler {"cron"=>"0 * * * *", "class"=>"Scheduler::InstanceRefreshScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.702Z pid=314 tid=5me INFO: Scheduling accounts_statuses_cleanup_scheduler {"interval"=>"1 minute", "class"=>"Scheduler::AccountsStatusesCleanupScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.711Z pid=314 tid=5me INFO: Scheduling suspended_user_cleanup_scheduler {"interval"=>"1 minute", "class"=>"Scheduler::SuspendedUserCleanupScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.712Z pid=314 tid=5me INFO: Scheduling software_update_check_scheduler {"interval"=>"30 minutes", "class"=>"Scheduler::SoftwareUpdateCheckScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.712Z pid=314 tid=5me INFO: Scheduling auto_close_registrations_scheduler {"interval"=>"1 hour", "class"=>"Scheduler::AutoCloseRegistrationsScheduler", "queue"=>"scheduler"}
2025-06-23T18:16:46.717Z pid=314 tid=5me INFO: Schedules Loaded
2025-06-23T18:16:46.720Z pid=314 tid=5me uniquejobs=upgrade_locks INFO: Already upgraded to 7.1.33
2025-06-23T18:16:46.721Z pid=314 tid=5me uniquejobs=reaper INFO: Starting Reaper
2025-06-23T18:16:46.744Z pid=314 tid=2p16 uniquejobs=reaper INFO: Nothing to delete; exiting.
2025-06-23T18:16:46.744Z pid=314 tid=2p16 uniquejobs=reaper INFO: Nothing to delete; exiting.
2025-06-23T18:17:46.638Z pid=314 tid=2p0u INFO: queueing Scheduler::IndexingScheduler (indexing_scheduler)
2025-06-23T18:17:46.714Z pid=314 tid=2p02 class=Scheduler::IndexingScheduler jid=dc30ec29ee93d61b44f69ce3 INFO: start
2025-06-23T18:17:46.731Z pid=314 tid=2p02 class=Scheduler::IndexingScheduler jid=dc30ec29ee93d61b44f69ce3 elapsed=0.017 INFO: done
2025-06-23T18:17:46.936Z pid=314 tid=2p0u INFO: queueing Scheduler::AccountsStatusesCleanupScheduler (accounts_statuses_cleanup_scheduler)
2025-06-23T18:17:46.936Z pid=314 tid=2p3i INFO: queueing Scheduler::SuspendedUserCleanupScheduler (suspended_user_cleanup_scheduler)
2025-06-23T18:17:46.942Z pid=314 tid=2p6a class=Scheduler::AccountsStatusesCleanupScheduler jid=a678cbc878787c3cc2ee63bf INFO: start
2025-06-23T18:17:46.942Z pid=314 tid=2p5y class=Scheduler::SuspendedUserCleanupScheduler jid=59c419b3b2930b3f299ee963 INFO: start
2025-06-23T18:17:47.050Z pid=314 tid=2p5y class=Scheduler::SuspendedUserCleanupScheduler jid=59c419b3b2930b3f299ee963 elapsed=0.108 INFO: done
2025-06-23T18:17:47.063Z pid=314 tid=2p6a class=Scheduler::AccountsStatusesCleanupScheduler jid=a678cbc878787c3cc2ee63bf elapsed=0.121 INFO: done
2025-06-23T18:18:47.002Z pid=314 tid=2p0u INFO: queueing Scheduler::IndexingScheduler (indexing_scheduler)
2025-06-23T18:18:47.002Z pid=314 tid=2p3i INFO: queueing Scheduler::AccountsStatusesCleanupScheduler (accounts_statuses_cleanup_scheduler)
2025-06-23T18:18:47.003Z pid=314 tid=2ovu INFO: queueing Scheduler::SuspendedUserCleanupScheduler (suspended_user_cleanup_scheduler)
2025-06-23T18:18:47.012Z pid=314 tid=2p02 class=Scheduler::IndexingScheduler jid=a692155d7885892e57c213b6 INFO: start
2025-06-23T18:18:47.012Z pid=314 tid=2ovi class=Scheduler::AccountsStatusesCleanupScheduler jid=6c6c5873024bb48aa83a14d8 INFO: start
2025-06-23T18:18:47.016Z pid=314 tid=2ouq class=Scheduler::SuspendedUserCleanupScheduler jid=bb7aabc4912ca3da47a0a6f0 INFO: start
2025-06-23T18:18:47.032Z pid=314 tid=2p02 class=Scheduler::IndexingScheduler jid=a692155d7885892e57c213b6 elapsed=0.02 INFO: done
2025-06-23T18:18:47.060Z pid=314 tid=2ouq class=Scheduler::SuspendedUserCleanupScheduler jid=bb7aabc4912ca3da47a0a6f0 elapsed=0.045 INFO: done
2025-06-23T18:18:47.094Z pid=314 tid=2ovi class=Scheduler::AccountsStatusesCleanupScheduler jid=6c6c5873024bb48aa83a14d8 elapsed=0.082 INFO: done
2025-06-23T18:19:47.038Z pid=314 tid=2p0u INFO: queueing Scheduler::IndexingScheduler (indexing_scheduler)
2025-06-23T18:19:47.042Z pid=314 tid=2p3i INFO: queueing Scheduler::AccountsStatusesCleanupScheduler (accounts_statuses_cleanup_scheduler)
2025-06-23T18:19:47.042Z pid=314 tid=2ovu INFO: queueing Scheduler::SuspendedUserCleanupScheduler (suspended_user_cleanup_scheduler)
2025-06-23T18:19:47.058Z pid=314 tid=2p02 class=Scheduler::IndexingScheduler jid=966d64d93659ad76da7503b3 INFO: start
2025-06-23T18:19:47.058Z pid=314 tid=2ouq class=Scheduler::AccountsStatusesCleanupScheduler jid=c9af60784a85a0fffd2ad8c0 INFO: start
2025-06-23T18:19:47.061Z pid=314 tid=2ovi class=Scheduler::SuspendedUserCleanupScheduler jid=8a66b0b0ca1735135d333f3c INFO: start
2025-06-23T18:19:47.065Z pid=314 tid=2p02 class=Scheduler::IndexingScheduler jid=966d64d93659ad76da7503b3 elapsed=0.007 INFO: done
2025-06-23T18:19:47.070Z pid=314 tid=2ovi class=Scheduler::SuspendedUserCleanupScheduler jid=8a66b0b0ca1735135d333f3c elapsed=0.009 INFO: done
2025-06-23T18:19:47.083Z pid=314 tid=2ouq class=Scheduler::AccountsStatusesCleanupScheduler jid=c9af60784a85a0fffd2ad8c0 elapsed=0.025 INFO: done
There are no explicit error messages in this output. I’ve checked other logs and configurations but haven’t pinpointed the cause.
Steps I’ve taken:
Verified resources allocated to the Docker container
Ensured all database migrations are applied
Reviewed environment configuration files for any discrepancies
Rebuilt the Docker container and rolled back to previous working container
Two things to note: I updated Redis and Postgresql14 docker containers as well. They appear to be functioning without issue. I also initially updated Unraid to 7.1.4, from 7.1.2 - but then downgraded back when I ran into this problem hoping that was the solution.
If anyone has insights on what might be causing this persistent issue or has experienced something similar after updating to 4.3.8, your help would be greatly appreciated.
Thank you!