Errore durante l'esecuzione di 'postInstallation': eliminazione dei file temporanei

Ciao,

Sto cercando di eseguire un’installazione non standard, ma forse qualcuno potrebbe avere qualche intuizione sulla causa dell’errore. Sto utilizzando docker-compose per eseguire postgres, redis, sidekiq e l’app principale da immagini separate di Bitnami 2.3.9, che funzionano perfettamente sul mio computer Windows. Tuttavia, quando vengono distribuiti su AWS ECS, ricevo un errore nell’app principale a metà dell’installazione. Inoltre, le ultime righe relative al bundling delle risorse (l’elenco è più lungo) non compaiono affatto sul mio Windows locale; su Windows, il processo attende a lungo e poi stampa i messaggi di successo.

postgre INFO Found PostgreSQL server listening at postgresql:5432
postgre INFO PostgreSQL server listening and working at postgresql:5432
discour INFO Preparing Discourse environment...
discour INFO Configuring the Discourse database files...
discour INFO Configuring Redis...
discour INFO Setting up SMTP in Discourse...
discour INFO Configuring Discourse database...
discour INFO Enabling PostgreSQL plugins for Discourse...
discour INFO Migrating database...
discour INFO Creating the Discourse admin user...
discour INFO Configuring your Discourse installation...
Error executing 'postInstallation': Purging temp files
Bundling assets
I, [2020-02-10T13:56:52.236240 #1088] INFO -- : Writing /opt/bitnami/discourse/public/assets/vendor-3b2f6dcdff2179eecae36277e07dc69ded2872f619a6a2bd222bbfe69e9f28ae.js
I, [2020-02-10T13:56:58.189628 #1088] INFO -- : Writing /opt/bitnami/discourse/public/assets/admin-e6fbf7cad5fdf706d3f174807bd8e6f8051c81dabdcb8c2c1cfae1ccee125eff.js

Unsupported install are, well, unsupported.

You can run a supported install by following our discourse/docs/INSTALL-cloud.md at main · discourse/discourse · GitHub where it is completely with an external database like our guide Running Discourse with a separate PostgreSQL server.

3 Mi Piace

That sounds good because main reason was to split database from the monolith. I have went through the config and bootstrap process, running Ubuntu linux (WSL) on Windows with a mounted Windows docker (as native docker does not work on WSL), all went nicely, image was bootstrapped, database updated and a load of other things on screen. Finally docker is started (I see it in docker ps, and ports are properly mapped), but when I try to access it on localhost (that’s how I configured it), I get a blank screen as server does not send any response. Same thing was working finely on the bitnami docker containers (application opening) which I could not get to run properly on AWS for some reason. Could I be missing something? I doubt that running through WSL should be an issue, as it is a real linux and bootstrapping went without errors.

E molto simile: installato su AWS EC2, avviato, Docker lanciato e non riesce a funzionare sulla porta 80. Sembra questo:

[*******]# telnet localhost 80
Trying 127.0.0.1...
Connected to localhost.
Escape character is '^]'.
Connection closed by foreign host.

Connesso al Docker all’interno di EC2, nei log di nginx trovo questi errori ogni secondo:
cannot load certificate “/shared/ssl/ec2-x-x-x-x.xx-xx.compute.amazonaws.com.cer”: PEM_read_bio_X509_AUX() failed (SSL: error:0909006C:PEM routines:get_name: no start line: Expecting: TRUSTED CERTIFICATE)

I log di Redis e Postgres sono a posto. Anche i log dell’applicazione in /var/www/discourse/log non mostrano nulla di particolare (anche se sono molto brevi).

Ciao,

Sei riuscito a risolvere il problema? Sto riscontrando lo stesso errore…
Per me sono presenti anche questi log aggiuntivi:

at runProgram (/opt/bitnami/nami/node_modules/nami-utils/lib/os/run-program.js:223:14)
    at Object.runProgram (/opt/bitnami/nami/node_modules/nami-utils/lib/os/index.js:63:12)
    at Object.$app.helpers.execute (/root/.nami/components/com.bitnami.ruby/helpers.js:44:7)
    at Object.$app.helpers.bundleExecute (/root/.nami/components/com.bitnami.ruby/helpers.js:62:8)
    at Object.<anonymous> (/opt/bitnami/nami/node_modules/lodash/index.js:51:276)
    at Service.$app.postInstallation (/root/.nami/components/com.bitnami.discourse/main.js:82:8)
    at Service.runStep (/opt/bitnami/nami/node_modules/nami-core/lib/components/component.js:159:12)
    at _.each.step (/opt/bitnami/nami/node_modules/nami-core/lib/components/component.js:236:32)
    at r (/opt/bitnami/nami/node_modules/lodash/index.js:5:348)
    at Function.sf (/opt/bitnami/nami/node_modules/lodash/index.js:78:256)
Error executing 'postInstallation': Purging temp files

Ciao @George_Guliman, purtroppo le installazioni Bitnami non sono supportate qui. Dovrai cercare assistenza altrove, probabilmente dal supporto Bitnami.

1 Mi Piace

Sì, lo so… Ero solo curioso se il giornalista fosse riuscito a risolverlo.

Grazie,