FAILED
--------------------
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrate' failed with return #<Process::Status: pid 449 e
xit 1>
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", "tag"=>"migrate", "hook"=>"db_migrate", "cmd"=>["su discourse -c 'bundle exec rake db:migra
te'"]}
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.
in original post as i mentioned
Pups::ExecError: cd /var/www/discourse && su discourse -c 'bundle exec rake db:migrateâ failed with return #<Process::Status: pid 449 e
xit 1>
oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
Redis version=7.0.15, bits=64, commit=00000000, modified=0, pid=447, just started
Configuration loaded
monotonic clock: POSIX clock_gettime
Warning: Could not create server TCP listening socket *:6379: bind: Address already in use
Failed listening on port 6379 (TCP), aborting.
cd /var/www/discourse && su discourse -c bundle exec rake db:migrate rake aborted!
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 peeraddr=xx.xx.xx.xx:443 state=error: unexpected eof while reading (OpenSSL::S
SL::SSLError)
No .git on plugins github link. The first line for docker has a â.gitâ. plugins are just link addresses.
If you scroll up in the log you should see some kind of error related to the locations plugin line. The error you posted I get that one but it does not affect rebuilding
Okay wasnât aware. Just was comparing my instance app.yml lines and noticed only docker line had extension of â.gitâ and recalled warnings if how sensitive these file layouts are.
then my question is how rest of other plugins with .git in the url are working fine Example : Calendar and news plugins worked well with .git that the way we normally apply git command. can you explain bit .git make difference?
If you saw @supermathie response to mine. I was mistaken. I was based it on my app.yml setup. Apparently either layout is fine.
I wouldnât worry about the earlier port error you posted as I get those and it rebuilds fine. Try removing the locations plugin and rebuild and see if it still fails
Scroll up if it fails capture a fair bit of the output above the final fail message. There should be if it is a plugin install issue or maybe something else an error messages
It is possible maybe when you were editting the app.yml Fike you might have inserted a space or something. A good practice is to before changing the app.yml file capture the contents prior to the change so if it fails you can compare the old with the new. If needed line by line.
I typically watch as it rebuilds each time and have become used to some of the common error/warning messages that donât seem to affect the rebuild.
I had a fail quite sometime ago that was plugin related but was due to in my case at that time missing the update that Chat was merged with core.
Folks here will need to see more of the rebuild log file to help identify where it is failing.
Running discourse-doctor as the failed result suggests might also help. But in my XP usually scrolling up has been my best go to.
You could also copy the bottom section or all of your app yml and paste it here. Just be sure to edit out sensitive things like your mail provider lines, maxmind info. Though you suspect plugin area so ⌠even just copying from the bottom section of $home down might yeild some insights
I can see this line also and i can confirm my 2nd VM having same issue only for location plugins
Caused by:
OpenSSL::SSL::SSLError: SSL_connect returned=1 errno=0 peeraddr=184.104.226.109:443 state=error: unexpected eof while reading (OpenSSL::SSL::SSLError)
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:46:in connect_nonblock' /var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-protocol-0.2.2/lib/net/protocol.rb:46:in ssl_socket_connectâ
/var/www/discourse/vendor/bundle/ruby/3.3.0/gems/net-http-0.6.0/lib/net/http.rb:1742:in `connectâ
I believe Robert will look at the location plugin issues soon. I noticed an error with the latest Discourse version in a PR to fix a deprecation, and he said he would take a look very soon.
Consider a post in Marketplace if you want this looked into with priority and have budget, but it looks like a gem version/compatibility issue somehow.
