# Proceso secundario "logical replication launcher" (PID 51) salió con código de salida 1

**URL:** https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695
**Category:** Self-hosting
**Created:** [11 Septiembre, 2022 13:26 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695 "2022-09-11T13:26:16Z")
**Posts on this page:** 18
**Page:** 1

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [11 Septiembre, 2022 13:26 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/1 "2022-09-11T13:26:16Z")

</div>

La reconstrucción del contenedor de datos en una configuración multisitio está generando el error `background worker \"logical replication launcher\" (PID 51) exited with exit code 1`. Más registros a continuación

```plaintext
218:C 11 Sep 2022 13:22:51.288 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
218:C 11 Sep 2022 13:22:51.289 # Redis version=6.2.6, bits=64, commit=00000000, modified=0, pid=218, just started
218:C 11 Sep 2022 13:22:51.289 # Configuration loaded
218:M 11 Sep 2022 13:22:51.292 * monotonic clock: POSIX clock_gettime
218:M 11 Sep 2022 13:22:51.293 * Running mode=standalone, port=6379.
218:M 11 Sep 2022 13:22:51.293 # Server initialized
218:M 11 Sep 2022 13:22:51.294 * Loading RDB produced by version 6.2.6
218:M 11 Sep 2022 13:22:51.294 * RDB age 53 seconds
218:M 11 Sep 2022 13:22:51.294 * RDB memory usage when created 32.70 Mb
218:M 11 Sep 2022 13:22:51.429 # Done loading RDB, keys loaded: 7811, keys expired: 0.
218:M 11 Sep 2022 13:22:51.429 * DB loaded from disk: 0.135 seconds
218:M 11 Sep 2022 13:22:51.429 * Ready to accept connections
I, [2022-09-11T13:23:01.284321 #1] INFO -- :
I, [2022-09-11T13:23:01.284632 #1] INFO -- : Terminating async processes
I, [2022-09-11T13:23:01.284702 #1] INFO -- : Sending INT to HOME=/var/lib/postgresql USER=postgres exec chpst -u postgres:postgres:ssl-cert -U postgres:postgres:ssl-cert /usr/lib/postgresql/13/bin/postmaster -D /etc/postgresql/13/main pid: 42
I, [2022-09-11T13:23:01.284791 #1] INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 218
218:signal-handler (1662902581) Received SIGTERM scheduling shutdown...
2022-09-11 13:23:01.287 UTC [42] LOG: received fast shutdown request
2022-09-11 13:23:01.306 UTC [42] LOG: aborting any active transactions
2022-09-11 13:23:01.318 UTC [42] LOG: background worker \"logical replication launcher\" (PID 51) exited with exit code 1
218:M 11 Sep 2022 13:23:01.345 # User requested shutdown...
218:M 11 Sep 2022 13:23:01.345 * Saving the final RDB snapshot before exiting.
2022-09-11 13:23:01.356 UTC [46] LOG: shutting down
218:M 11 Sep 2022 13:23:02.113 * DB saved on disk
218:M 11 Sep 2022 13:23:02.114 # Redis is now ready to exit, bye bye...
2022-09-11 13:23:02.169 UTC [42] LOG: database system is shut down
sha256:30b91243b63ec58aa8555df5d1dfac509abe121e5c8d7081dbab2f2278d7d837
11e8bce45c8d0d7020de971c08d49d26287cc513967230530c8ba925a3c058bb
Removing old container

```

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [11 Septiembre, 2022 13:27 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/2 "2022-09-11T13:27:20Z")

</div>

Pero tu compilación parece haberse completado sin errores. ¿Estás experimentando algún error al iniciar el contenedor de datos?

---

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [11 Septiembre, 2022 13:32 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/3 "2022-09-11T13:32:27Z")

</div>

No con el contenedor de datos, sino un error con el contenedor web al reconstruir

```plaintext
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Tasks: TOP => multisite:migrate => db:load_config => environment
(See full trace by running task with --trace)
I, [2022-09-11T13:30:49.381804 #1] INFO -- : gem install iso8601 -v 0.13.0 -i /var/www/discourse/plugins/discourse-automation/gems/2.7.6 --no-document --ignore-dependencies --no-user-install
Successfully installed iso8601-0.13.0
1 gem installed
gem install rrule -v 0.4.4 -i /var/www/discourse/plugins/discourse-automation/gems/2.7.6 --no-document --ignore-dependencies --no-user-install
Successfully installed rrule-0.4.4
1 gem installed

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse &amp;&amp; sudo -E -u discourse bundle exec rake multisite:migrate failed with return #&lt;Process::Status: pid 1095 exit 1&gt;
Location of failure: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec failed with the params "cd /var/www/discourse &amp;&amp; sudo -E -u discourse bundle exec rake multisite:migrate"
bootstrap failed with exit code 1

```

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [11 Septiembre, 2022 13:34 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/4 "2022-09-11T13:34:22Z")

</div>

¿Estás usando algún plugin de terceros?

---

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [11 Septiembre, 2022 13:36 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/5 "2022-09-11T13:36:01Z")

</div>

Usando bastantes complementos oficiales de Discourse. Pero el error sigue ahí con todos los complementos deshabilitados excepto Docker Manager.

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [11 Septiembre, 2022 13:45 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/6 "2022-09-11T13:45:22Z")

</div>

Lo que señalas como error me parece un mensaje normal (para el contenedor de datos)

 ![image](https://global.discourse-cdn.com/meta/original/4X/9/3/0/93050ef1504de8e28804b786ffd7b1c5c9a571ff.png)

Acabo de reconstruir tanto los datos como la web en mi sandbox y se completaron con éxito. ¿Puedes compartir tu `web_only.yml` redactado?

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [11 Septiembre, 2022 14:05 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/8 "2022-09-11T14:05:03Z")

</div>

> [@TechGeek](#):
>
> ` EMBER_CLI_PROD_ASSETS: 1`

¿Puedes comentar esto y tratar de reconstruir? No creo que esto sea necesario ya.

---

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [11 Septiembre, 2022 14:13 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/9 "2022-09-11T14:13:49Z")

</div>

Sigue igual con `EMBER_CLI_PROD_ASSETS: 1` comentado. La reconstrucción del contenedor web sigue arrojando el siguiente error:

```plaintext
FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate failed with return #<Process::Status: pid 983 exit 1>

```

---

<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: [11 Septiembre, 2022 14:24 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/10 "2022-09-11T14:24:32Z")

</div>

Tienes que desplazarte hacia arriba hasta donde se imprimió el mensaje sobre cuál es el problema con la migración.

---

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [11 Septiembre, 2022 14:32 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/11 "2022-09-11T14:32:26Z")

</div>

Más líneas abajo, el error está relacionado con no encontrar la clave esperada al analizar un mapeo de bloques en la línea 2, columna 1, no estoy seguro de qué se trata.

```plaintext
Usando cose 1.2.1
0: cose (1.2.1) de /var/www/discourse/vendor/bundle/ruby/2.7.0/specifications/cose-1.2.1.gemspec
¡Paquete completo! 126 dependencias de Gemfile, 183 gemas instaladas ahora.
Las gemas en los grupos 'test' y 'development' no se instalaron.
Las gemas empaquetadas se instalan en './vendor/bundle'

I, [2022-09-11T14:12:48.956298 #1] INFO -- : > cd /var/www/discourse & sudo -E -u discourse bundle exec rake multisite:migrate
rake aborted!
Psych::SyntaxError: (desconocido): no encontró la clave esperada al analizar un mapeo de bloques en la línea 2, columna 1
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:181:in `load_config!'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:177:in `initialize'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:38:in `new'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.1/lib/rails_multisite/connection_management.rb:38:in `config_filename='
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rails_multisite-4.0.1/lib/rails_multisite/railtie.rb:19:in `block in <class:Railtie>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/initializable.rb:32:in `instance_exec'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/initializable.rb:32:in `run'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/initializable.rb:61:in `block in run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/initializable.rb:60:in `run_initializers'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/application.rb:372:in `initialize!'
/var/www/discourse/config/environment.rb:7:in `<main>'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/bootsnap-1.13.0/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:32:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/zeitwerk-2.6.0/lib/zeitwerk/kernel.rb:35:in `require'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/application.rb:348:in `require_environment!'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/railties-7.0.3.1/lib/rails/application.rb:511:in `block in run_tasks_blocks'
/var/www/discourse/vendor/bundle/ruby/2.7.0/gems/rake-13.0.6/exe/rake:27:in `<top (required)>'
/usr/local/bin/bundle:25:in `load'
/usr/local/bin/bundle:25:in `<main>'
Tasks: TOP => multisite:migrate => db:load_config => environment
(Ver el rastreo completo ejecutando la tarea con --trace)
I, [2022-09-11T14:12:53.236265 #1] INFO -- :

FAILED
--------------------
Pups::ExecError: cd /var/www/discourse & sudo -E -u discourse bundle exec rake multisite:migrate falló con retorno #<Process::Status: pid 983 exit 1>
Ubicación del fallo: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
exec falló con los parámetros "cd /var/www/discourse & sudo -E -u discourse bundle exec rake multisite:migrate"
bootstrap falló con código de salida 1

```

---

<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: [11 Septiembre, 2022 17:39 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/13 "2022-09-11T17:39:59Z")

</div>

> [@TechGeek](#):
>
> `Psych::SyntaxError: (<unknown>): did not find expected key while parsing a block mapping at line 2 column 1`

Eso significa que tu app.yml contiene un error de formato. Parece que proviene de la parte multisitio.

---

<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: [11 Septiembre, 2022 18:35 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/14 "2022-09-11T18:35:11Z")

</div>

El único plugin que veo con `sych::SyntaxError` es `discourse-calendar`. ¿Puedes intentar eliminarlo? Y si eso resuelve tu problema, entonces implica que hay un error con ese plugin.

---

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [12 Septiembre, 2022 03:47 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/15 "2022-09-12T03:47:16Z")

</div>

> [@pfaffman](#):
>
> El único plugin que veo con `sych::SyntaxError` es `discourse-calendar`. ¿Puedes intentar eliminarlo? Y si eso resuelve tu problema, entonces implica que hay un error con ese plugin.

No estoy usando el plugin de calendario.

---

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [12 Septiembre, 2022 04:23 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/16 "2022-09-12T04:23:03Z")

</div>

> [@Falco](#):
>
> Eso significa que tu app.yml contiene un error de formato. Parece que proviene de la parte multisitio.

Lo he comprobado con el validador YML y no hay errores.

Salida de error actualizada a continuación

```plaintext
INFO -- : El migrador multisitio se está ejecutando con 1 hilos

Migrando predeterminado
Migrando site2
Sembrando predeterminado
Sembrando site2

FALLIDO
--------------------
Pups::ExecError: cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate falló con retorno #<Process::Status: pid 983 exit 1>
Ubicación del fallo: /usr/local/lib/ruby/gems/2.7.0/gems/pups-1.1.1/lib/pups/exec_command.rb:117:in `spawn'
ejecución fallida con los parámetros "cd /var/www/discourse && sudo -E -u discourse bundle exec rake multisite:migrate"
el arranque falló con el código de salida 1
**FALLO AL ARRANQUE** por favor, desplázate hacia arriba y busca mensajes de error anteriores, puede haber más de uno.
./discourse-doctor puede ayudar a diagnosticar el problema.

```

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [13 Septiembre, 2022 04:00 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/18 "2022-09-13T04:00:29Z")

</div>

¿Puedes exportar un log completo usando `./discourse-doctor`?

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [13 Septiembre, 2022 04:04 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/20 "2022-09-13T04:04:57Z")

</div>

Durante la compilación habrá una línea que dice `1 Migration Failed` y debajo estará la información sobre qué sitio está fallando. Necesitas averiguar qué está mal con ese sitio para que la compilación ocurra realmente.

---

<div class="post-metadata">

### Author: ![TechGeek](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/techgeek/32/274321_2.png) [@TechGeek](https://meta.discourse.org/u/TechGeek)
#### Post date: [17 Septiembre, 2022 09:47 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/31 "2022-09-17T09:47:20Z")

</div>

Mover a un tema separado ya que es un error confirmado [Multisite build error: #\<MiniRacer::RuntimeError: Error: Parser rule not found: fragments\_join\>](https://meta.discourse.org/t/multisite-build-error-miniracer-error-parser-rule-not-found-fragments-join/239265)

---

<div class="post-metadata">

### Author: ![david](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/david/32/157490_2.png) [@david](https://meta.discourse.org/u/david)
#### Post date: [17 Septiembre, 2022 14:53 UTC](https://meta.discourse.org/t/background-worker-logical-replication-launcher-pid-51-exited-with-exit-code-1/238695/32 "2022-09-17T14:53:55Z")

</div>


