Não consigo instalar o plugin de reação

Suporte Instalação
1

Tentei instalar meu primeiro plugin, o plugin de reações, seguindo este guia.

Meu arquivo .yml se parece com isto:

## Plugins vão aqui
## veja https://meta.discourse.org/t/19157 para detalhes
hooks:
  after_code:
    - exec:
        cd: $home/plugins
        cmd:
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-reactions.git

## Quaisquer comandos personalizados para executar após a compilação

Salvei corretamente e executei ./launcher rebuild app

Não consigo encontrar o plugin em lugar nenhum na administração. Reiniciei o servidor e tentei uma segunda reconstrução, mas ele ainda não é encontrado em lugar nenhum. Verifiquei novamente o arquivo .yml e a URL do git clone ainda está lá corretamente.

Estou executando um servidor Ubuntu 22.04 que está atualizado.

Alguma ideia?

2

Hmm. Isso é bastante incomum. E a reconstrução foi bem-sucedida? (E no servidor certo. Parece bobo, mas já aconteceu antes :slight_smile:)

E definitivamente não está na sua página /admin/plugins?

3

Não vi nenhum erro na primeira reconstrução após a instalação do plugin, mas tentei reconstruir novamente para ver se funcionava e ele mostrou erros:

error Error: https://registry.yarnpkg.com/rxjs/-/rxjs-6.6.7.tgz: ESOCKETTIMEDOUT
    at ClientRequest.<anonymous> (/usr/share/yarn/lib/cli.js:142037:19)
    at Object.onceWrapper (node:events:631:28)
    at ClientRequest.emit (node:events:517:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:847:9)
    at Object.onceWrapper (node:events:631:28)
    at TLSSocket.emit (node:events:529:35)
    at Socket._onTimeout (node:net:598:8)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
I, [2024-06-09T15:50:06.758203 #1]  INFO -- : yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info There appears to be trouble with your network connection. Retrying...
info Visit https://yarnpkg.com/en/docs/cli/install for documentation about this command.

I, [2024-06-09T15:50:06.760651 #1]  INFO -- : Terminating async processes
I, [2024-06-09T15:50:06.760756 #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: 36
I, [2024-06-09T15:50:06.760884 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 98
2024-06-09 15:50:06.820 UTC [36] LOG:  received fast shutdown request
98:signal-handler (1717948206) Received SIGTERM scheduling shutdown...
98:M 09 Jun 2024 15:50:06.821 # User requested shutdown...
98:M 09 Jun 2024 15:50:06.821 * Saving the final RDB snapshot before exiting.
2024-06-09 15:50:06.843 UTC [36] LOG:  aborting any active transactions
2024-06-09 15:50:06.853 UTC [36] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
2024-06-09 15:50:06.854 UTC [46] LOG:  shutting down
2024-06-09 15:50:06.994 UTC [36] LOG:  database system is shut down
98:M 09 Jun 2024 15:50:07.069 * DB saved on disk
98:M 09 Jun 2024 15:50:07.069 # Redis is now ready to exit, bye bye...


FAILED
--------------------
Pups::ExecError: cd /var/www/discourse &amp;&amp; su discourse -c 'yarn install --frozen-lockfile &amp;&amp; yarn cache clean' failed with return #&lt;Process::Status: pid 274 exit 1&gt;
Location of failure: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec failed with the params {"cd"=>"$home", "hook"=>"yarn", "cmd"=>["if [ \"$version\" != \"tests-passed\" ]; then\n  rm -rf app/assets/javascripts/node_modules\nfi", "su discourse -c 'yarn install --frozen-lockfile &amp;&amp; yarn cache clean'"]}
bootstrap failed with exit code 1
** FAILED TO BOOTSTRAP ** please scroll up and look for earlier error messages, there may be more than one.
./discourse-doctor may help diagnose the problem.
369d797bef305a3d8e265ae1c7a22c3fa0c773883a73f928eeff5ce9d2f9eb02

O fórum está inativo desde a reconstrução.

5

Tente este link.

Em seu app.yml, execute ./discourse-doctor

6

Na verdade, acabei de executar o discourse doctor e ele está perguntando se quero criar uma versão publicamente disponível do arquivo. Não quero que minhas informações sejam públicas, então há alguma maneira de fazer isso sem disponibilidade pública, mas ainda assim compartilhá-lo?

7

Sempre selecionei N (Não) sem problemas. Não consigo dizer especificamente o backend disso, mas sei que isso pode potencialmente ajudá-lo com este problema.

8

Ok, aqui está a saída do discourse doctor:

DISCOURSE DOCTOR Sun Jun 9 16:11:34 UTC 2024
OS: Linux hv-client-35215-device-38240 5.15.0-112-generic #122-Ubuntu SMP Thu May 23 07:48:21 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux


Found containers/app.yml

==================== YML SETTINGS ====================
DISCOURSE_HOSTNAME=
SMTP_ADDRESS=
DEVELOPER_EMAILS=REDACTED 
SMTP_PASSWORD=REDACTED 
SMTP_PORT=587
SMTP_USER_NAME=
LETSENCRYPT_ACCOUNT_EMAIL=REDACTED 

==================== DOCKER INFO ====================
DOCKER VERSION: Docker version 24.0.5, build 24.0.5-0ubuntu1~22.04.1

DOCKER PROCESSES (docker ps -a)

CONTAINER ID   IMAGE                 COMMAND        CREATED       STATUS                      PORTS     NAMES
88f5e9f2ae3b   local_discourse/app   "/sbin/boot"   3 weeks ago   Exited (5) 29 minutes ago             app

==================== SERIOUS PROBLEM!!!! ====================
app not running!
Attempting to rebuild
==================== REBUILD LOG ====================
x86_64 arch detected.
Ensuring launcher is up to date
Fetching origin
Launcher is up-to-date
Stopping old container
+ /usr/bin/docker stop -t 600 app
app
2.0.20240602-0023: Pulling from discourse/base
Digest: sha256:5e0c30da851a00e824a58b033d59b8f3dd840b513a7694a7a5d0674285c0ee3c
Status: Image is up to date for discourse/base:2.0.20240602-0023
docker.io/discourse/base:2.0.20240602-0023
/usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups.rb
/usr/local/bin/pups --stdin
I, [2024-06-09T16:12:00.126218 #1]  INFO -- : Reading from stdin
I, [2024-06-09T16:12:00.147839 #1]  INFO -- : File > /etc/service/postgres/run  chmod: +x  chown: 
I, [2024-06-09T16:12:00.155377 #1]  INFO -- : File > /etc/service/postgres/log/run  chmod: +x  chown: 
I, [2024-06-09T16:12:00.162120 #1]  INFO -- : File > /etc/runit/3.d/99-postgres  chmod: +x  chown: 
I, [2024-06-09T16:12:00.168391 #1]  INFO -- : File > /root/install_postgres  chmod: +x  chown: 
I, [2024-06-09T16:12:00.174232 #1]  INFO -- : File > /root/upgrade_postgres  chmod: +x  chown: 
I, [2024-06-09T16:12:00.174569 #1]  INFO -- : Replacing data_directory = '/var/lib/postgresql/13/main' with data_directory = '/shared/postgres_data' in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.176474 #1]  INFO -- : Replacing (?-mix:#?listen_addresses *=.*) with listen_addresses = '*' in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.181474 #1]  INFO -- : Replacing (?-mix:#?synchronous_commit *=.*) with synchronous_commit = $db_synchronous_commit in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.197097 #1]  INFO -- : Replacing (?-mix:#?shared_buffers *=.*) with shared_buffers = $db_shared_buffers in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.204913 #1]  INFO -- : Replacing (?-mix:#?work_mem *=.*) with work_mem = $db_work_mem in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.207341 #1]  INFO -- : Replacing (?-mix:#?default_text_search_config *=.*) with default_text_search_config = '$db_default_text_search_config' in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.209062 #1]  INFO -- : Replacing (?-mix:#?checkpoint_segments *=.*) with checkpoint_segments = $db_checkpoint_segments in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.211320 #1]  INFO -- : Replacing (?-mix:#?logging_collector *=.*) with logging_collector = $db_logging_collector in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.213228 #1]  INFO -- : Replacing (?-mix:#?log_min_duration_statement *=.*) with log_min_duration_statement = $db_log_min_duration_statement in /etc/postgresql/13/main/postgresql.conf
I, [2024-06-09T16:12:00.215253 #1]  INFO -- : Replacing (?-mix:^#local +replication +postgres +peer$) with local replication postgres  peer in /etc/postgresql/13/main/pg_hba.conf
I, [2024-06-09T16:12:00.216273 #1]  INFO -- : Replacing (?-mix:^host.*all.*all.*127.*$) with host all all 0.0.0.0/0 md5 in /etc/postgresql/13/main/pg_hba.conf
I, [2024-06-09T16:12:00.224544 #1]  INFO -- : Replacing (?-mix:^host.*all.*all.*::1\/128.*$) with host all all ::/0 md5 in /etc/postgresql/13/main/pg_hba.conf
I, [2024-06-09T16:12:00.240561 #1]  INFO -- : > [ -f /root/install_postgres ] && /root/install_postgres && rm -f /root/install_postgres
I, [2024-06-09T16:12:04.764680 #1]  INFO -- : Generating locales (this might take a while)...
Generation complete.

I, [2024-06-09T16:12:04.765009 #1]  INFO -- : > 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
I, [2024-06-09T16:12:04.782630 #1]  INFO -- : File > /usr/local/bin/create_db  chmod: +x  chown: 
I, [2024-06-09T16:12:04.792990 #1]  INFO -- : File > /var/lib/postgresql/take-database-backup  chmod: +x  chown: postgres:postgres
I, [2024-06-09T16:12:04.797112 #1]  INFO -- : File > /var/spool/cron/crontabs/postgres  chmod:   chown: 
I, [2024-06-09T16:12:04.797535 #1]  INFO -- : > sleep 5
2024-06-09 16:12:05.036 UTC [36] LOG:  starting PostgreSQL 13.15 (Debian 13.15-1.pgdg110+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 10.2.1-6) 10.2.1 20210110, 64-bit
2024-06-09 16:12:05.042 UTC [36] LOG:  listening on IPv4 address "0.0.0.0", port 5432
2024-06-09 16:12:05.043 UTC [36] LOG:  listening on IPv6 address "::", port 5432
2024-06-09 16:12:05.115 UTC [36] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-06-09 16:12:05.141 UTC [45] LOG:  database system was shut down at 2024-06-09 15:50:06 UTC
2024-06-09 16:12:05.172 UTC [36] LOG:  database system is ready to accept connections
I, [2024-06-09T16:12:09.802209 #1]  INFO -- : 
I, [2024-06-09T16:12:09.802472 #1]  INFO -- : > /usr/local/bin/create_db
2024-06-09 16:12:09.924 UTC [55] postgres@postgres ERROR:  database "discourse" already exists
2024-06-09 16:12:09.924 UTC [55] postgres@postgres STATEMENT:  CREATE DATABASE discourse;
createdb: error: database creation failed: ERROR:  database "discourse" already exists
2024-06-09 16:12:10.236 UTC [58] postgres@discourse ERROR:  role "discourse" already exists
2024-06-09 16:12:10.236 UTC [58] postgres@discourse STATEMENT:  create user discourse;
ERROR:  role "discourse" already exists
NOTICE:  extension "hstore" already exists, skipping
NOTICE:  extension "pg_trgm" already exists, skipping
NOTICE:  extension "vector" already exists, skipping
NOTICE:  extension "hstore" already exists, skipping
NOTICE:  extension "pg_trgm" already exists, skipping
NOTICE:  extension "vector" already exists, skipping
I, [2024-06-09T16:12:11.611371 #1]  INFO -- : GRANT
ALTER SCHEMA
CREATE EXTENSION
CREATE EXTENSION
CREATE EXTENSION
CREATE EXTENSION
CREATE EXTENSION
CREATE EXTENSION
UPDATE 0

I, [2024-06-09T16:12:11.612138 #1]  INFO -- : > echo postgres installed!
I, [2024-06-09T16:12:11.615822 #1]  INFO -- : postgres installed!

I, [2024-06-09T16:12:11.625092 #1]  INFO -- : File > /etc/service/redis/run  chmod: +x  chown: 
I, [2024-06-09T16:12:11.633574 #1]  INFO -- : File > /etc/service/redis/log/run  chmod: +x  chown: 
I, [2024-06-09T16:12:11.642438 #1]  INFO -- : File > /etc/runit/3.d/10-redis  chmod: +x  chown: 
I, [2024-06-09T16:12:11.643464 #1]  INFO -- : Replacing daemonize yes with  in /etc/redis/redis.conf
I, [2024-06-09T16:12:11.645641 #1]  INFO -- : Replacing (?-mix:^pidfile.*$) with  in /etc/redis/redis.conf
I, [2024-06-09T16:12:11.729106 #1]  INFO -- : > install -d -m 0755 -o redis -g redis /shared/redis_data
I, [2024-06-09T16:12:11.737439 #1]  INFO -- : 
I, [2024-06-09T16:12:11.738307 #1]  INFO -- : Replacing (?-mix:^logfile.*$) with logfile "" in /etc/redis/redis.conf
I, [2024-06-09T16:12:11.767277 #1]  INFO -- : Replacing (?-mix:^bind .*$) with  in /etc/redis/redis.conf
I, [2024-06-09T16:12:11.770596 #1]  INFO -- : Replacing (?-mix:^dir .*$) with dir /shared/redis_data in /etc/redis/redis.conf
I, [2024-06-09T16:12:11.775175 #1]  INFO -- : Replacing (?-mix:^protected-mode yes) with protected-mode no in /etc/redis/redis.conf
I, [2024-06-09T16:12:11.787974 #1]  INFO -- : Replacing # io-threads 4 with io-threads $redis_io_threads in /etc/redis/redis.conf
I, [2024-06-09T16:12:11.791757 #1]  INFO -- : > echo redis installed
I, [2024-06-09T16:12:11.800447 #1]  INFO -- : redis installed

I, [2024-06-09T16:12:11.801001 #1]  INFO -- : > cat /etc/redis/redis.conf | grep logfile
I, [2024-06-09T16:12:11.817020 #1]  INFO -- : logfile ""

I, [2024-06-09T16:12:11.817748 #1]  INFO -- : > exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf
I, [2024-06-09T16:12:11.822066 #1]  INFO -- : > sleep 10
98:C 09 Jun 2024 16:12:11.856 # oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
98:C 09 Jun 2024 16:12:11.862 # Redis version=7.0.7, bits=64, commit=00000000, modified=0, pid=98, just started
98:C 09 Jun 2024 16:12:11.862 # Configuration loaded
98:M 09 Jun 2024 16:12:11.874 * monotonic clock: POSIX clock_gettime
98:M 09 Jun 2024 16:12:11.876 * Running mode=standalone, port=6379.
98:M 09 Jun 2024 16:12:11.876 # Server initialized
98:M 09 Jun 2024 16:12:11.876 # WARNING Memory overcommit must be enabled! Without it, a background save or replication may fail under low memory condition. Being disabled, it can can also cause failures without low memory condition, see https://github.com/jemalloc/jemalloc/issues/1328. To fix this issue add 'vm.overcommit_memory = 1' to /etc/sysctl.conf and then reboot or run the command 'sysctl vm.overcommit_memory=1' for this to take effect.
98:M 09 Jun 2024 16:12:11.876 * Loading RDB produced by version 7.0.7
98:M 09 Jun 2024 16:12:11.876 * RDB age 1325 seconds
98:M 09 Jun 2024 16:12:11.876 * RDB memory usage when created 12.09 Mb
98:M 09 Jun 2024 16:12:12.044 * Done loading RDB, keys loaded: 735, keys expired: 5.
98:M 09 Jun 2024 16:12:12.044 * DB loaded from disk: 0.168 seconds
98:M 09 Jun 2024 16:12:12.044 * Ready to accept connections
I, [2024-06-09T16:12:21.839461 #1]  INFO -- : 
I, [2024-06-09T16:12:21.840480 #1]  INFO -- : > thpoff echo "thpoff is installed!"
I, [2024-06-09T16:12:21.845540 #1]  INFO -- : thpoff is installed!

I, [2024-06-09T16:12:21.846306 #1]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_SMTP_ADDRESS"] == "smtp.example.com"; puts "Aborting! Mail is not configured!"; exit 1; end'
I, [2024-06-09T16:12:22.119797 #1]  INFO -- : 
I, [2024-06-09T16:12:22.121728 #1]  INFO -- : > /usr/local/bin/ruby -e 'if ENV["DISCOURSE_HOSTNAME"] == "discourse.example.com"; puts "Aborting! Domain is not configured!"; exit 1; end'
I, [2024-06-09T16:12:22.284181 #1]  INFO -- : 
I, [2024-06-09T16:12:22.285101 #1]  INFO -- : > /usr/local/bin/ruby -e 'if (ENV["DISCOURSE_CDN_URL"] || "")[0..1] == "//"; puts "Aborting! CDN must have a protocol specified. Once fixed you should rebake your posts now to correct all posts."; exit 1; end'
I, [2024-06-09T16:12:22.445414 #1]  INFO -- : 
I, [2024-06-09T16:12:22.446452 #1]  INFO -- : > rm -f /etc/cron.d/anacron
I, [2024-06-09T16:12:22.450926 #1]  INFO -- : 
I, [2024-06-09T16:12:22.455762 #1]  INFO -- : File > /etc/cron.d/anacron  chmod:   chown: 
I, [2024-06-09T16:12:22.463698 #1]  INFO -- : File > /etc/runit/1.d/copy-env  chmod: +x  chown: 
I, [2024-06-09T16:12:22.471280 #1]  INFO -- : File > /etc/service/unicorn/run  chmod: +x  chown: 
I, [2024-06-09T16:12:22.478939 #1]  INFO -- : File > /etc/service/nginx/run  chmod: +x  chown: 
I, [2024-06-09T16:12:22.486584 #1]  INFO -- : File > /etc/runit/3.d/01-nginx  chmod: +x  chown: 
I, [2024-06-09T16:12:22.494456 #1]  INFO -- : File > /etc/runit/3.d/02-unicorn  chmod: +x  chown: 
I, [2024-06-09T16:12:22.495122 #1]  INFO -- : Replacing # postgres with if [ -f /root/install_postgres ]; then
  /root/install_postgres
  rm /root/install_postgres
fi
sv start postgres || exit 1
 in /etc/service/unicorn/run
I, [2024-06-09T16:12:22.498080 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git reset --hard
Updating files:  14% (4891/34508)
Updating files:  15% (5177/34508)
Updating files:  16% (5522/34508)
Updating files:  17% (5867/34508)
Updating files:  18% (6212/34508)
Updating files:  19% (6557/34508)
Updating files:  20% (6902/34508)
Updating files:  20% (6928/34508)
Updating files:  21% (7247/34508)
Updating files:  22% (7592/34508)
Updating files:  23% (7937/34508)
Updating files:  24% (8282/34508)
Updating files:  25% (8627/34508)
Updating files:  26% (8973/34508)
Updating files:  26% (9238/34508)
Updating files:  27% (9318/34508)
Updating files:  28% (9663/34508)
Updating files:  29% (10008/34508)
Updating files:  30% (10353/34508)
Updating files:  31% (10698/34508)
Updating files:  32% (11043/34508)
Updating files:  33% (11388/34508)
Updating files:  34% (11733/34508)
Updating files:  34% (11972/34508)
Updating files:  35% (12078/34508)
Updating files:  36% (12423/34508)
Updating files:  37% (12768/34508)
Updating files:  38% (13114/34508)
Updating files:  39% (13459/34508)
Updating files:  40% (13804/34508)
Updating files:  40% (14132/34508)
Updating files:  41% (14149/34508)
Updating files:  42% (14494/34508)
Updating files:  43% (14839/34508)
Updating files:  44% (15184/34508)
Updating files:  45% (15529/34508)
Updating files:  46% (15874/34508)
Updating files:  47% (16219/34508)
Updating files:  48% (16564/34508)
Updating files:  49% (16909/34508)
Updating files:  49% (16929/34508)
Updating files:  50% (17254/34508)
Updating files:  51% (17600/34508)
Updating files:  52% (17945/34508)
Updating files:  53% (18290/34508)
Updating files:  54% (18635/34508)
Updating files:  54% (18896/34508)
Updating files:  55% (18980/34508)
Updating files:  56% (19325/34508)
Updating files:  57% (19670/34508)
Updating files:  58% (20015/34508)
Updating files:  59% (20360/34508)
Updating files:  60% (20705/34508)
Updating files:  60% (20776/34508)
Updating files:  61% (21050/34508)
Updating files:  62% (21395/34508)
Updating files:  63% (21741/34508)
Updating files:  64% (22086/34508)
Updating files:  65% (22431/34508)
Updating files:  66% (22776/34508)
Updating files:  66% (22839/34508)
Updating files:  67% (23121/34508)
Updating files:  68% (23466/34508)
Updating files:  69% (23811/34508)
Updating files:  70% (24156/34508)
Updating files:  71% (24501/34508)
Updating files:  72% (24846/34508)
Updating files:  73% (25191/34508)
Updating files:  74% (25536/34508)
Updating files:  75% (25881/34508)
Updating files:  76% (26227/34508)
Updating files:  77% (26572/34508)
Updating files:  77% (26670/34508)
Updating files:  78% (26917/34508)
Updating files:  79% (27262/34508)
Updating files:  80% (27607/34508)
Updating files:  81% (27952/34508)
Updating files:  82% (28297/34508)
Updating files:  83% (28642/34508)
Updating files:  84% (28987/34508)
Updating files:  85% (29332/34508)
Updating files:  86% (29677/34508)
Updating files:  87% (30022/34508)
Updating files:  87% (30250/34508)
Updating files:  88% (30368/34508)
Updating files:  89% (30713/34508)
Updating files:  90% (31058/34508)
Updating files:  91% (31403/34508)
Updating files:  92% (31748/34508)
Updating files:  93% (32093/34508)
Updating files:  94% (32438/34508)
Updating files:  95% (32783/34508)
Updating files:  95% (32902/34508)
Updating files:  96% (33128/34508)
Updating files:  97% (33473/34508)
Updating files:  98% (33818/34508)
Updating files:  98% (34027/34508)
Updating files:  99% (34163/34508)
Updating files: 100% (34508/34508)
Updating files: 100% (34508/34508), done.
I, [2024-06-09T16:12:36.697834 #1]  INFO -- : HEAD is now at 62b1b69e8 UX: constrain width of chat transcripts in posts (#27288)

I, [2024-06-09T16:12:36.698263 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git clean -f
I, [2024-06-09T16:12:37.144203 #1]  INFO -- : 
I, [2024-06-09T16:12:37.145189 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c '
  set -o errexit
  if [ $(git rev-parse --is-shallow-repository) == "true" ]; then
      git remote set-branches --add origin main
      git remote set-branches origin tests-passed
      git fetch --depth 1 origin tests-passed
  else
      git fetch --tags --prune-tags --prune --force origin
  fi
'
From https://github.com/discourse/discourse
 - [deleted]             (none)     -> origin/add_filter_webhook_events_by_status
 - [deleted]             (none)     -> origin/add_lifecycle_rule_for_inventories
 - [deleted]             (none)     -> origin/application-route-actions
 - [deleted]             (none)     -> origin/avoid_unformatted_logs
 - [deleted]             (none)     -> origin/dependabot/bundler/rails_failover-2.1.0
 - [deleted]             (none)     -> origin/dev/ember-58-upgrade-playground
 - [deleted]             (none)     -> origin/discourse-route-actions
 - [deleted]             (none)     -> origin/discourse-url-native-class
 - [deleted]             (none)     -> origin/fix-group-chat-member-count
 - [deleted]             (none)     -> origin/ghost-button
 - [deleted]             (none)     -> origin/issue/bulk-action-pm-fixes
 - [deleted]             (none)     -> origin/migrations-tooling/converter
 - [deleted]             (none)     -> origin/permalinks
 - [deleted]             (none)     -> origin/route-native-class
 - [deleted]             (none)     -> origin/search-result-consistency
 - [deleted]             (none)     -> origin/support_alternate_bucket_s3_inventory
 - [deleted]             (none)     -> origin/user-posts-stream-native-class
 - [deleted]             (none)     -> origin/ux-account-disclaimer
   62b1b69e8..1fbc1cd32  main                    -> origin/main
 * [new branch]          0-a-fix-perf-watched-words -> origin/0-a-fix-perf-watched-words
 * [new branch]          0-a-skf-gjs             -> origin/0-a-skf-gjs
 * [new branch]          add_mechanism_to_redeliver_all_webhook_events -> origin/add_mechanism_to_redeliver_all_webhook_events
   1dcc6d608..da719ba7e  categories-modal-fix    -> origin/categories-modal-fix
 * [new branch]          chat-drawer-settings-styling -> origin/chat-drawer-settings-styling
 * [new branch]          dependabot/bundler/libv8-node-21.7.2.0 -> origin/dependabot/bundler/libv8-node-21.7.2.0
 * [new branch]          dependabot/bundler/oauth2-2.0.9 -> origin/dependabot/bundler/oauth2-2.0.9
 * [new branch]          dependabot/bundler/omniauth-2.1.2 -> origin/dependabot/bundler/omniauth-2.1.2
 * [new branch]          dependabot/bundler/omniauth-google-oauth2-1.1.2 -> origin/dependabot/bundler/omniauth-google-oauth2-1.1.2
 + 01982d4eb...58a828d0b dependabot/bundler/sqlite3-2.0.2 -> origin/dependabot/bundler/sqlite3-2.0.2  (forced update)
 * [new branch]          dev/ember-source-5.9.0-upgrade -> origin/dev/ember-source-5.9.0-upgrade
 + 07c56ec24...bbc178d8a dev/rfc-value-modifier-plugin-api -> origin/dev/rfc-value-modifier-plugin-api  (forced update)
 * [new branch]          feature/requires-confirmation-site-settings -> origin/feature/requires-confirmation-site-settings
 + fc63df2f0...077576634 feature/user-fields-required-for-existing-users-2 -> origin/feature/user-fields-required-for-existing-users-2  (forced update)
 * [new branch]          fix-password-reset-security-key -> origin/fix-password-reset-security-key
   b3d6801e8..a5d017f39  formtoolkit             -> origin/formtoolkit
 * [new branch]          grant-admin-fetch-user  -> origin/grant-admin-fetch-user
 * [new branch]          html_to_markdown        -> origin/html_to_markdown
 * [new branch]          jjaffeux-otp-validation -> origin/jjaffeux-otp-validation
 + b2b6b4468...07d2cfab5 loic-update-to-rails-7.1 -> origin/loic-update-to-rails-7.1  (forced update)
 * [new branch]          modify-class-native-syntax -> origin/modify-class-native-syntax
 * [new branch]          mt/converter            -> origin/mt/converter
 * [new branch]          optimize-chat-email-notification -> origin/optimize-chat-email-notification
 * [new branch]          remove-summarization    -> origin/remove-summarization
   5558028f8..a721e8fa4  stable                  -> origin/stable
 * [new branch]          support_s3_inventory_bucket -> origin/support_s3_inventory_bucket
   62b1b69e8..1fbc1cd32  tests-passed            -> origin/tests-passed
I, [2024-06-09T16:12:38.531554 #1]  INFO -- : 
I, [2024-06-09T16:12:38.532260 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse bash -c '
  set -o errexit
  if [[ $(git symbolic-ref --short HEAD) == tests-passed ]] ; then
      git pull
  else
      git -c advice.detachedHead=false checkout tests-passed
  fi
'
Switched to a new branch 'tests-passed'
I, [2024-06-09T16:12:45.262813 #1]  INFO -- : Branch 'tests-passed' set up to track remote branch 'tests-passed' from 'origin'.

I, [2024-06-09T16:12:45.263776 #1]  INFO -- : > cd /var/www/discourse && sudo -H -E -u discourse git config user.discourse-version tests-passed
I, [2024-06-09T16:12:45.288928 #1]  INFO -- : 
I, [2024-06-09T16:12:45.289152 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp
I, [2024-06-09T16:12:45.295445 #1]  INFO -- : 
I, [2024-06-09T16:12:45.295633 #1]  INFO -- : > cd /var/www/discourse && chown discourse:www-data tmp
I, [2024-06-09T16:12:45.303349 #1]  INFO -- : 
I, [2024-06-09T16:12:45.303522 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/pids
I, [2024-06-09T16:12:45.307132 #1]  INFO -- : 
I, [2024-06-09T16:12:45.307269 #1]  INFO -- : > cd /var/www/discourse && mkdir -p tmp/sockets
I, [2024-06-09T16:12:45.310989 #1]  INFO -- : 
I, [2024-06-09T16:12:45.311127 #1]  INFO -- : > cd /var/www/discourse && touch tmp/.gitkeep
I, [2024-06-09T16:12:45.318838 #1]  INFO -- : 
I, [2024-06-09T16:12:45.319063 #1]  INFO -- : > cd /var/www/discourse && mkdir -p                    /shared/log/rails
I, [2024-06-09T16:12:45.322752 #1]  INFO -- : 
I, [2024-06-09T16:12:45.322916 #1]  INFO -- : > cd /var/www/discourse && bash -c "touch -a           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log"
I, [2024-06-09T16:12:45.399482 #1]  INFO -- : 
I, [2024-06-09T16:12:45.399725 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/log/rails/{production,production_errors,unicorn.stdout,unicorn.stderr,sidekiq}.log /var/www/discourse/log"
I, [2024-06-09T16:12:45.406081 #1]  INFO -- : 
I, [2024-06-09T16:12:45.406284 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/{uploads,backups}"
I, [2024-06-09T16:12:45.444609 #1]  INFO -- : 
I, [2024-06-09T16:12:45.444839 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/{uploads,backups} /var/www/discourse/public"
I, [2024-06-09T16:12:45.450581 #1]  INFO -- : 
I, [2024-06-09T16:12:45.450759 #1]  INFO -- : > cd /var/www/discourse && bash -c "mkdir -p           /shared/tmp/{backups,restores}"
I, [2024-06-09T16:12:45.464585 #1]  INFO -- : 
I, [2024-06-09T16:12:45.464759 #1]  INFO -- : > cd /var/www/discourse && bash -c "ln    -s           /shared/tmp/{backups,restores} /var/www/discourse/tmp"
I, [2024-06-09T16:12:45.470374 #1]  INFO -- : 
I, [2024-06-09T16:12:45.470550 #1]  INFO -- : > cd /var/www/discourse && chown -R discourse:www-data /shared/log/rails /shared/uploads /shared/backups /shared/tmp
I, [2024-06-09T16:12:45.481346 #1]  INFO -- : 
I, [2024-06-09T16:12:45.481527 #1]  INFO -- : > cd /var/www/discourse && [ ! -d public/plugins ] || find public/plugins/ -maxdepth 1 -xtype l -delete
I, [2024-06-09T16:12:45.483755 #1]  INFO -- : 
I, [2024-06-09T16:12:45.484310 #1]  INFO -- : Replacing # redis with sv start redis || exit 1 in /etc/service/unicorn/run
I, [2024-06-09T16:12:45.494687 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/docker_manager.git
Cloning into 'docker_manager'...
I, [2024-06-09T16:12:48.008281 #1]  INFO -- : 
I, [2024-06-09T16:12:48.008631 #1]  INFO -- : > cd /var/www/discourse/plugins && git clone https://github.com/discourse/discourse-reactions.git
Cloning into 'discourse-reactions'...
I, [2024-06-09T16:12:49.185007 #1]  INFO -- : 
I, [2024-06-09T16:12:49.185644 #1]  INFO -- : > cp /var/www/discourse/config/nginx.sample.conf /etc/nginx/conf.d/discourse.conf
I, [2024-06-09T16:12:49.191273 #1]  INFO -- : 
I, [2024-06-09T16:12:49.191729 #1]  INFO -- : > rm /etc/nginx/sites-enabled/default
I, [2024-06-09T16:12:49.196547 #1]  INFO -- : 
I, [2024-06-09T16:12:49.198005 #1]  INFO -- : > mkdir -p /var/nginx/cache
I, [2024-06-09T16:12:49.209868 #1]  INFO -- : 
I, [2024-06-09T16:12:49.210779 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2024-06-09T16:12:49.213114 #1]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2024-06-09T16:12:49.220203 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2024-06-09T16:12:49.221042 #1]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2024-06-09T16:12:49.223101 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2024-06-09T16:12:49.223941 #1]  INFO -- : > echo "done configuring web"
I, [2024-06-09T16:12:49.227370 #1]  INFO -- : done configuring web

I, [2024-06-09T16:12:49.229187 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
I, [2024-06-09T16:12:50.788388 #1]  INFO -- : 
I, [2024-06-09T16:12:50.789223 #1]  INFO -- : > cd /var/www/discourse && find /var/www/discourse ! -user discourse -exec chown discourse {} \+
I, [2024-06-09T16:12:55.377356 #1]  INFO -- : 
I, [2024-06-09T16:12:55.378662 #1]  INFO -- : > cd /var/www/discourse && if [ "tests-passed" != "tests-passed" ]; then
  rm -rf app/assets/javascripts/node_modules
fi
I, [2024-06-09T16:12:55.381620 #1]  INFO -- : 
I, [2024-06-09T16:12:55.381822 #1]  INFO -- : > cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'
warning Resolution field "unset-value@2.0.1" is incompatible with requested version "unset-value@^1.0.0"
error Error: https://registry.yarnpkg.com/rxjs/-/rxjs-7.8.1.tgz: ESOCKETTIMEDOUT
    at ClientRequest.<anonymous> (/usr/share/yarn/lib/cli.js:142037:19)
    at Object.onceWrapper (node:events:631:28)
    at ClientRequest.emit (node:events:517:28)
    at TLSSocket.emitRequestTimeout (node:_http_client:847:9)
    at Object.onceWrapper (node:events:631:28)
    at TLSSocket.emit (node:events:529:35)
    at Socket._onTimeout (node:net:598:8)
    at listOnTimeout (node:internal/timers:569:17)
    at process.processTimers (node:internal/timers:512:7)
I, [2024-06-09T16:19:28.375991 #1]  INFO -- : yarn install v1.22.22
[1/5] Validating package.json...
[2/5] Resolvendo pacotes...
[3/5] Baixando pacotes...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Parece haver problemas com sua conexão de rede. Tentando novamente...
info Visite https://yarnpkg.com/en/docs/cli/install para documentação sobre este comando.
info Parece haver problemas com sua conexão de rede. Tentando novamente...

I, [2024-06-09T16:19:28.385028 #1]  INFO -- : Encerrando processos assíncronos
I, [2024-06-09T16:19:28.385197 #1]  INFO -- : Enviando INT para 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: 36
I, [2024-06-09T16:19:28.386733 #1]  INFO -- : Enviando TERM para exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 98
2024-06-09 16:19:28.387 UTC [36] LOG:  recebido pedido de desligamento rápido
98:signal-handler (1717949968) Recebido SIGTERM agendando desligamento...
2024-06-09 16:19:28.398 UTC [36] LOG:  abortando transações ativas
2024-06-09 16:19:28.407 UTC [36] LOG:  trabalhador em segundo plano "logical replication launcher" (PID 51) saiu com código de saída 1
98:M 09 Jun 2024 16:19:28.419 # Desligamento solicitado pelo usuário...
98:M 09 Jun 2024 16:19:28.419 * Salvando o snapshot RDB final antes de sair.
2024-06-09 16:19:28.434 UTC [46] LOG:  desligando
2024-06-09 16:19:28.598 UTC [36] LOG:  sistema de banco de dados desligado
98:M 09 Jun 2024 16:19:28.638 * Banco de dados salvo no disco
98:M 09 Jun 2024 16:19:28.638 # Redis está pronto para sair, tchau...


FALHOU
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'yarn install --frozen-lockfile && yarn cache clean' falhou com retorno #<Process::Status: pid 274 exit 1>
Local da falha: /usr/local/lib/ruby/gems/3.3.0/gems/pups-1.2.1/lib/pups/exec_command.rb:132:in `spawn'
exec falhou com os parâmetros {"cd"=>"$home", "hook"=>"yarn", "cmd"=>["if [ \"$version\" != \"tests-passed\" ]; then\n  rm -rf app/assets/javascripts/node_modules\nfi", "su discourse -c 'yarn install --frozen-lockfile && yarn cache clean'"]}
bootstrap falhou com código de saída 1
** FALHA AO INICIAR BOOTSTRAP ** por favor, role para cima e procure por mensagens de erro anteriores, pode haver mais de uma.
./discourse-doctor pode ajudar a diagnosticar o problema.
511fc8465aa7cf3613e267d1c6eafeaf53580f04c9b6625e7bc02ea35bb5b6a8
==================== FIM DO LOG DE RECONSTRUÇÃO ====================
Falha ao reconstruir o aplicativo.

Verificando seu nome de domínio . . .

Conexão com o fórum bem-sucedida.
Você provavelmente deve remover qualquer plugin não padrão e reconstruir.
Tentando reiniciar o contêiner existente. . . 
Arquitetura x86_64 detectada.

iniciando contêiner existente
+ /usr/bin/docker start app
app
Contêiner reiniciado.


==================== PLUGINS ====================
          - git clone https://github.com/discourse/docker_manager.git
          - git clone https://github.com/discourse/discourse-reactions.git

Nenhum plugin não oficial detectado.

Veja https://github.com/discourse/discourse/blob/main/lib/plugin/metadata.rb para a lista oficial.

========================================
Versão do Discourse em: NÃO ENCONTRADA
Versão do Discourse em localhost: NÃO ENCONTRADA


==================== INFORMAÇÕES DE MEMÓRIA ====================
SO: Linux
RAM (MB): 4101

               total        usado       livre     compartilhado buff/cache   disponível
Mem:            3911         276        1889           1        1746        3339
Swap:              0           0           0

==================== VERIFICAÇÃO DE ESPAÇO EM DISCO ====================
---------- Espaço em Disco do SO ----------
Sistema de arquivos      Tamanho  Usado Disp. Uso% Montado em
/dev/vda1        78G   15G   63G  19% /

==================== INFORMAÇÕES DE DISCO ====================
Disco /dev/loop0: 63.95 MiB, 67051520 bytes, 130960 setores
Unidades: setores de 1 * 512 = 512 bytes
Tamanho do setor (lógico/físico): 512 bytes / 512 bytes
Tamanho de E/S (mínimo/ideal): 512 bytes / 512 bytes


Disco /dev/loop1: 63.95 MiB, 67051520 bytes, 130960 setores
Unidades: setores de 1 * 512 = 512 bytes
Tamanho do setor (lógico/físico): 512 bytes / 512 bytes
Tamanho de E/S (mínimo/ideal): 512 bytes / 512 bytes


Disco /dev/loop2: 87 MiB, 91230208 bytes, 178184 setores
Unidades: setores de 1 * 512 = 512 bytes
Tamanho do setor (lógico/físico): 512 bytes / 512 bytes
Tamanho de E/S (mínimo/ideal): 512 bytes / 512 bytes


Disco /dev/loop3: 87.03 MiB, 91258880 bytes, 178240 setores
Unidades: setores de 1 * 512 = 512 bytes
Tamanho do setor (lógico/físico): 512 bytes / 512 bytes
Tamanho de E/S (mínimo/ideal): 512 bytes / 512 bytes


Disco /dev/loop4: 38.73 MiB, 40615936 bytes, 79328 setores
Unidades: setores de 1 * 512 = 512 bytes
Tamanho do setor (lógico/físico): 512 bytes / 512 bytes
Tamanho de E/S (mínimo/ideal): 512 bytes / 512 bytes


Disco /dev/loop5: 38.83 MiB, 40714240 bytes, 79520 setores
Unidades: setores de 1 * 512 = 512 bytes
Tamanho do setor (lógico/físico): 512 bytes / 512 bytes
Tamanho de E/S (mínimo/ideal): 512 bytes / 512 bytes


Disco /dev/vda: 80 GiB, 85899345920 bytes, 167772160 setores
Unidades: setores de 1 * 512 = 512 bytes
Tamanho do setor (lógico/físico): 512 bytes / 512 bytes
Tamanho de E/S (mínimo/ideal): 512 bytes / 512 bytes
Tipo de tabela de partição: gpt
Identificador do disco: 92CE6D7D-ACB9-4BD1-B74B-296DC5901CB3

Dispositivo      Início       Fim   Setores  Tamanho Tipo
/dev/vda1  227328 167772126 167544799 79.9G Sistema de arquivos Linux
/dev/vda14   2048     10239      8192    4M Boot BIOS
/dev/vda15  10240    227327    217088  106M Sistema EFI

As entradas da tabela de partição não estão na ordem do disco.

==================== FIM DAS INFORMAÇÕES DE DISCO ====================

==================== TESTE DE E-MAIL ====================
Para um teste robusto, obtenha um endereço em http://www.mail-tester.com/
Teste de e-mail ignorado.

==================== CONCLUÍDO! ====================
`
9

Acredito que este seja o seu erro fatal, sua máquina consegue acessar https://registry.yarnpkg.com com sucesso?

10 
curl -I -L https://registry.yarnpkg.com
HTTP/2 200
date: Sun, 09 Jun 2024 16:38:58 GMT
content-type: application/json
cf-ray: 89128e1899ab8b47-TPA
cf-cache-status: DYNAMIC
npm-notice: This endpoint is deprecated. Use https://replicate.npmjs.com instead.
server: cloudflare
11

Estranho. A velocidade do disco dessa máquina é razoavelmente rápida? Já houve problemas antes com discos lentos:

12

O fórum voltou a funcionar após executar o discourse doctor, mas o plugin ainda não está instalado.

Verifiquei as atualizações no painel de administração e ele diz que uma nova versão do docker manager e do discourse está disponível.

Devo atualizar ou tentar resolver isso primeiro como está?

13

Deveria ser, estou usando um provedor de VPS de ponta com 2 CPUs e 4 GB de RAM e um SSD de 80 GB.

14

O Discourse-doctor reiniciaria o aplicativo (ou seja, a versão anterior à falha de reconstrução que não incluía Reações).

Para instalar o plugin, você precisaria ser capaz de reconstruir com sucesso. A atualização pela interface do usuário primeiro não deveria importar, pois uma reconstrução pela linha de comando também atualizaria seu site de forma semelhante.

15

O que é recomendado neste momento? Postei o erro acima do discourse doctor.

16

Esta é a pergunta eterna. :slight_smile: Reconstruções podem falhar por uma série de razões, dependendo da configuração/instalação do site, e alguns erros são mais reconhecíveis para mais pessoas do que outros.

Este eu não tenho certeza. Só para verificar, a sua é uma instalação padrão?

17

Sim, segui a instalação padrão e o fórum tem funcionado bem nos últimos dias desde a instalação. Não tentei instalar nenhum outro plugin além do plugin de reações.

18

Parece que não há uma solução para este problema.

Acabei de instalar o Discourse há alguns dias, seguindo a instalação padrão, e tudo funcionou bem, mas aparentemente não consigo fazer um rebuild ou instalar plugins.

Quando não há uma solução, qual é a melhor prática? Fazer um backup da minha instância do Discourse e reinstalar o Discourse do zero novamente?

E outra pergunta um tanto relacionada. Fiz a instalação padrão e ela instalou uma versão beta do Discourse. Não seria melhor ter a instalação padrão instalando uma versão estável em vez de beta, ou estou perdendo alguma coisa?

19

Qual Beta? A maioria, acredito, executa “Tests-passed”, pois é mais atualizada e geralmente bastante estável.

20

O meu está mostrando 3.3.0.beta3-dev

Eu não sei o que isso significa. Você pode esclarecer?

Eu não quero que meu problema principal seja ofuscado pela segunda parte da minha pergunta. Eu ainda não consigo instalar plugins ou reconstruir o aplicativo.

21

Existem 3 branches. A versão que você postou é “Tests-passed”. Não tenho certeza do que pode estar causando o problema, XP. Estou executando a mesma versão.