'
I, [2023-02-23T16:57:37.374835 #5267] INFO -- : Refreshing Gem list
```
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [February 23, 2023, 4:58pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/8 "2023-02-23T16:58:54Z")
So:
[https://github.com/discourse/discourse-data-explorer/pull/227](https://github.com/discourse/discourse-data-explorer/pull/227)
?
That change included `requires_plugin DataExplorer.plugin_name` → `requires_plugin DataExplorer::PLUGIN_NAME`
---
### Author:  [@Falco](https://meta.discourse.org/u/Falco)
#### Post date: [February 23, 2023, 5:04pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/9 "2023-02-23T17:04:27Z")
Weird, from a cursory look at the code it appears that this should work. Also Meta should be running this without problems 🤔
Any ideas @nbianca ?
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [February 23, 2023, 5:07pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/10 "2023-02-23T17:07:22Z")
I’ll rebuild without [data explorer](https://meta.discourse.org/t/32566?silent=true) for now.
---
### Author:  [@nbianca](https://meta.discourse.org/u/nbianca)
#### Post date: [February 23, 2023, 5:10pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/11 "2023-02-23T17:10:39Z")
Sorry for the issues I caused @Stephen. I am reverting my commit now and you should be able to rebuild your forum really soon.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [February 23, 2023, 5:11pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/12 "2023-02-23T17:11:53Z")
Not a problem at all, I’m already building without [data explorer](https://meta.discourse.org/t/32566?silent=true) for now. I will re-introduce it tonight assuming this solves the rebuild issues.
I mostly flag this stuff in the hope we can catch it before it impacts others! 🤞
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [February 23, 2023, 5:22pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/13 "2023-02-23T17:22:51Z")
Confirmed, disabling [data explorer](https://meta.discourse.org/t/32566?silent=true) resolves the issue for now. Thanks @falco @nbianca !
Will re-enable after hours to ensure reverting that commit solves it.
---
### Author:  [@pfaffman](https://meta.discourse.org/u/pfaffman)
#### Post date: [February 23, 2023, 6:08pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/14 "2023-02-23T18:08:03Z")
Here are the docker logs (from hours ago when it was broken).
I just did a rebuild and I’m back up.
```plaintext
(147) exiting
supervisor pid: 164 unicorn pid: 166
config/unicorn_launcher: line 71: kill: (166) - No such process
config/unicorn_launcher: line 15: kill: (166) - No such process
(164) exiting
supervisor pid: 181 unicorn pid: 183
config/unicorn_launcher: line 71: kill: (183) - No such process
config/unicorn_launcher: line 15: kill: (183) - No such process
(181) exiting
supervisor pid: 198 unicorn pid:
```
---
### Author:  [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [February 23, 2023, 6:40pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/15 "2023-02-23T18:40:10Z")
> [@nbianca](#):
>
> I am reverting my commit now and you should be able to rebuild your forum really soon.
I see that has been reverted:
[https://github.com/discourse/discourse-data-explorer/commit/0f6b30c2d84d44978be1c845267609446ca9dbf2](https://github.com/discourse/discourse-data-explorer/commit/0f6b30c2d84d44978be1c845267609446ca9dbf2)
I’ve been able to successfully rebuild now - thank you for getting onto that so promptly!
---
### Author:  [@Godmar\_Back](https://meta.discourse.org/u/Godmar_Back)
#### Post date: [February 23, 2023, 8:57pm UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/16 "2023-02-23T20:57:34Z")
I pulled 10 minutes ago but still end with a broken container. Dumb question: what steps are necessary to pull the update? Would `git pull`, `./launcher rebuild app` suffice? My .yml reads:
```plaintext
## Plugins go here
## see https://meta.discourse.org/t/19157 for details
hooks:
after_code:
- exec:
cd: $home/plugins
cmd:
- git clone https://github.com/discourse/docker_manager.git
- git clone https://github.com/tfpk/discourse-reveal-anonymous.git
- git clone https://github.com/discourse/discourse-push-notifications.git
- git clone https://github.com/discourse/discourse-data-explorer.git
- git clone https://github.com/discourse/discourse-solved.git
- git clone https://github.com/discourse/discourse-math.git
```
---
### Author:  [@nathank](https://meta.discourse.org/u/nathank)
#### Post date: [February 24, 2023, 12:09am UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/17 "2023-02-24T00:09:51Z")
> [@Godmar\_Back](#):
>
> Would `git pull`, `./launcher rebuild app` suffice?
That should do it - maybe you have an unrelated problem.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [February 24, 2023, 12:13am UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/18 "2023-02-24T00:13:04Z")
No need to git pull.
If your instance is running tests-passed and you’re affected by the earlier problem then a rebuild alone will do it.
---
### Author:  [@Godmar\_Back](https://meta.discourse.org/u/Godmar_Back)
#### Post date: [February 24, 2023, 1:06am UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/19 "2023-02-24T01:06:00Z")
Confirmed that rebuilding the container corrected it.
---
### Author:  [@Stephen](https://meta.discourse.org/u/Stephen)
#### Post date: [March 26, 2023, 1:06am UTC](https://meta.discourse.org/t/data-explorer-taking-instance-down-on-rebuild/256078/20 "2023-03-26T01:06:31Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.