Reproduce: Enable the site setting daily performance report (“Analyze NGINX logs daily and post a Staff Only topic with details”). Update the Docker image: cd /var/discourse ./launcher rebuild app Expected Results: A report appears in the “Staff” category periodically. Actual Results: An error message appears in the “Website performance reports” topic in the “Staff” category: Report is only available in latest image, please run: cd /var/discourse ./launcher rebuild app

[image] downey: 2 Update the Docker image: cd /var/discourse ./launcher rebuild app You need a git pull before the rebuild as seen here: [image] Manually update Discourse and Docker image to latest Self-Hosting bookmark This guide provides step-by-step instructions for manually updating Discourse, the Docker container, and the Ubuntu operating system on a self-hosted setup. person_raising_hand Required user level: System Administrator warning SSH access to the server. If you self-host Discourse, you occasionally need to run a manual update via the command line to get the latest security releases and newest libraries. These updates are not picked up in admin/upgrade, which is why you’ll occa…

Not necessarily I thought the launcher command did an implicit git pull @sam?

That change was only made in the last year, very possible @downey has an older git repo.

Don’t know exactly when the change happened but I thought I’d updated fairly recently. After doing the first rebuild I could have sworn I saw a git pull but I didn’t watch carefully enough. As soon as I can take a little more downtime (probably tonight) will try again.

I definitely did a full git pull and then ./launcher rebuild app last night … but still getting the same bug every day instead of a performance report. Can anyone reproduce? Is anyone able to successfully get the performance report?

I’m having the same issue. My guess is that because ./launcher rebuild says “Your version of Discourse Docker is ahead of origin” when git tries to get the latest version, so the latest version is never pulled?

Likely, can you just check out discourse-docker from scratch?

Actually what I did was git reset --hard origin/master to have the repository in sync again and then another ./launcher rebuild (that didn’t trigger the “ahead of origin” message). Now I’l wait to see if I get the reports. Is there any way to trigger those reports manually so that I don’t have to wait?

Visit /sidekiq/scheduler and trigger Jobs::DailyPerformanceReport AFAIK?

That worked, thanks! Now I get the report and that’s really nice!

Daily performance reports keep asking to rebuild container

Product Support Self-hosting

Falco (Falco) January 21, 2016, 6:54pm 2

You need a git pull before the rebuild as seen here:

Topic		Replies	Views
Daily perf reports asking to rebuild container on new install Product Support	5	1475	November 21, 2016
Daily performance report not posted/generated Product Support	9	971	November 18, 2019
Discourse upgrade via Web UI Fails & SSH Upgrade Brings Down Discourse Instance Self-hosting	16	2487	November 26, 2021
Error upgrading Self-hosting	12	1804	October 20, 2016
I got an error after updating my forked install Self-hosting unsupported-install	35	2343	November 13, 2018

Daily performance reports keep asking to rebuild container

Related topics