# Daily perf reports asking to rebuild container on new install

**URL:** <https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970>\
**Category:** Support\
**Created:** [2016年十一月16日 15:31 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970 "2016-11-16T15:31:46Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lee\_Ars](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lee_ars/32/1597_2.png) [@Lee\_Ars](https://meta.discourse.org/u/Lee_Ars)\
**Post date:** [2016年十一月16日 15:31 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/1 "2016-11-16T15:31:46Z")

</div>

After migrating Discourse to a new phy host and restoring the site from backup, I’m still getting [the same error message](https://meta.discourse.org/t/daily-performance-reports-keep-asking-to-rebuild-container/38311) in the staff category with the performance report option enabled—

```plaintext
Report is only available in latest image, please run:

cd /var/discourse
./launcher rebuild app

```

I went back and tried to re-do some of the troubleshooting @sam suggested in [this eariler thread](https://meta.discourse.org/t/analyzing-discourse-performance-using-nginx-logs/30117/13), but there doesn’t appear to be a `/var/www/discourse/script/nginx_analyze.rb` anymore, so I’m not sure exactly where to start.

I can trigger `Jobs::DailyPerformanceReport` from the sidekiq scheduler and it runs without errors, though it completes in 3ms and creates no topics. Triggering the report from the rails console also results in no output:

```plaintext
# rails c
[1] pry(main)> Jobs:: DailyPerformanceReport.new.execute(nil)
=> nil

```

No errors are logged in logster for either.

@downey or anyone else on the team, do you have any suggestions? Happy to do whatever it takes to get this resolved. Can also try to arrange a time to grant login access to the web host if you’d like to poke further.

---

<div class="post-metadata">

**Author:** ![Falco](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/falco/32/179432_2.png) [@Falco](https://meta.discourse.org/u/Falco)\
**Post date:** [2016年十一月16日 15:40 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/2 "2016-11-16T15:40:17Z")

</div>

From the host run:

```plaintext
./launcher enter app
cat /VERSION

```

So we are sure you are on `1.3.7`.

---

<div class="post-metadata">

**Author:** ![Lee\_Ars](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lee_ars/32/1597_2.png) [@Lee\_Ars](https://meta.discourse.org/u/Lee_Ars)\
**Post date:** [2016年十一月16日 15:51 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/3 "2016-11-16T15:51:37Z")

</div>

That’s affirmative—cat /VERSION shows:

```plaintext
root@dockmaster-app:~# cat /VERSION
1.3.7

```

---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2016年十一月16日 21:00 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/4 "2016-11-16T21:00:36Z")

</div>

@tgxworld can give you a hand debugging, he moved it to a plugin so the instructions for debugging need to be updated.

My best guess is that there is some funky security going on.

---

<div class="post-metadata">

**Author:** ![tgxworld](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/tgxworld/32/106117_2.png) [@tgxworld](https://meta.discourse.org/u/tgxworld)\
**Post date:** [2016年十一月21日 03:30 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/5 "2016-11-21T03:30:51Z")

</div>

@Lee_Ars

Try to trigger the script manually and see if there are any errors 🙂

```
./launcher enter app
cd /var/www/discourse
ruby plugins/discourse-nginx-performance-report/script/nginx_analyze.rb --limit 1440

```

---

<div class="post-metadata">

**Author:** ![Lee\_Ars](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lee_ars/32/1597_2.png) [@Lee\_Ars](https://meta.discourse.org/u/Lee_Ars)\
**Post date:** [2016年十一月21日 14:22 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/6 "2016-11-21T14:22:44Z")

</div>

> [@tgxworld](#):
>
> Try to trigger the script manually and see if there are any errors

Thanks, @tgxworld. Triggering manually results in the report running without issue in the terminal window.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/system/32/443519_2.png) [@system](https://meta.discourse.org/u/system)\
**Post date:** [2019年三月31日 15:29 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/7 "2019-03-31T15:29:27Z")

</div>



---

<div class="post-metadata">

**Author:** ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)\
**Post date:** [2019年三月31日 23:28 UTC](https://meta.discourse.org/t/daily-perf-reports-asking-to-rebuild-container-on-new-install/52970/8 "2019-03-31T23:28:09Z")

</div>