# Migration trouble related to DiscourseJsProcessor?

**URL:** <https://meta.discourse.org/t/migration-trouble-related-to-discoursejsprocessor/276480>\
**Category:** Bug\
**Created:** [August 24, 2023, 4:52pm UTC](https://meta.discourse.org/t/migration-trouble-related-to-discoursejsprocessor/276480 "2023-08-24T16:52:56Z")\
**Posts on this page:** 1\
**Showing post:** 6

<div class="post-metadata">

**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\
**Post date:** [August 24, 2023, 5:27pm UTC](https://meta.discourse.org/t/migration-trouble-related-to-discoursejsprocessor/276480/6 "2023-08-24T17:27:01Z")

</div>

I spoke too soon.

It just failed again, but . .. . oh. But the last time the database had already been migrated?

When it worked I ran a `./launcher bootstrap x` from the command line.

Then I ran it with Ansible, which does

```
      git pull && git checkout main && ./launcher bootstrap {{ discourse_yml }} {{ launcher_args | default("")}}

```

(I guess I need to remove `git checkout main`–not sure why that was there)

Aha. But Ansible is dropping the database first (this is for a site I use for migrations, so starting anew is a frequent occurrence). So that’s consistent with your eggs. Sigh. But then I turned off the `drop_database` and ran it twice from ansible, and it failed, and then bootstrapped again from the command line, and it still failed. There are no clues on the migrations:

```plaintext
Installing mysql2 0.5.5 with native extensions
Bundle complete! 137 Gemfile dependencies, 173 gems now installed.
Gems in the groups 'test' and 'development' were not installed.
Bundled gems are installed into `./vendor/bundle`

I, [2023-08-24T17:24:31.403199 #1] INFO -- : Replacing types { with set_real_ip_from 192.168.1.0/24;
set_real_ip_from 172.19.0.0/24;
set_real_ip_from 172.18.0.0/24;
set_real_ip_from 172.17.0.0/24;
set_real_ip_from 38.242.7.193/28;
real_ip_recursive on;
real_ip_header X-Forwarded-For;
types {
 in /etc/nginx/conf.d/discourse.conf
I, [2023-08-24T17:24:31.403687 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'LOAD_PLUGINS=0 bundle exec rake plugin:pull_compatible_all'
I, [2023-08-24T17:24:33.084210 #1] INFO -- : discourse-microsoft-auth is already at latest compatible version

I, [2023-08-24T17:24:33.084593 #1] INFO -- : > cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate'
rake aborted!
Errno::ENOENT: No such file or directory @ rb_sysopen - tmp/js-processor.js
/var/www/discourse/lib/discourse_js_processor.rb:140:in `read'
/var/www/discourse/lib/discourse_js_processor.rb:140:in `create_new_context'
/var/www/discourse/lib/discourse_js_processor.rb:156:in `block in v8'
/var/www/discourse/lib/discourse_js_processor.rb:154:in `synchronize'
/var/www/discourse/lib/discourse_js_processor.rb:154:in `v8'
/var/www/discourse/lib/discourse_js_processor.rb:169:in `block in v8_call'
/var/www/discourse/lib/discourse_js_processor.rb:168:in `synchronize'
/var/www/discourse/lib/discourse_js_processor.rb:168:in `v8_call'
/var/www/discourse/lib/discourse_js_processor.rb:193:in `perform'
/var/www/discourse/lib/pretty_text.rb:54:in `apply_es6_file'

```

But also could ` 'templates/enable-ruby-yjit.yml'` be the problem? EDIT: That wasn’t it. And then I removed the mysql and import templates. Still no joy.

Has this problem been around for a while? I upgraded another site recently that’s on ECS and it seemed like there was something strange going on with the migration and then the assets were broken. It’s a huge database, though, so I thought I might just be impatient, and also I did some of that process by hand, so I thought I’d just been careless.

---

_[View the full topic](https://meta.discourse.org/t/migration-trouble-related-to-discoursejsprocessor/276480)._