Build Fails on New Host

I copied and the entire /var/discourse to a new host. Updated the CNAME and SSL all working fine. When I try to do a rebuild, I get an issue with that I can’t figure out.

 sudo ./launcher rebuild app
I, [2022-03-11T16:50:42.832830 #1]  INFO -- :
I, [2022-03-11T16:50:42.833980 #1]  INFO -- : Replacing pid /run/nginx.pid; with daemon off; in /etc/nginx/nginx.conf
I, [2022-03-11T16:50:42.834524 #1]  INFO -- : Replacing (?m-ix:upstream[^\}]+\}) with upstream discourse { server 127.0.0.1:3000; } in /etc/nginx/conf.d/discourse.conf
I, [2022-03-11T16:50:42.834854 #1]  INFO -- : Replacing (?-mix:server_name.+$) with server_name _ ; in /etc/nginx/conf.d/discourse.conf
I, [2022-03-11T16:50:42.835184 #1]  INFO -- : Replacing (?-mix:client_max_body_size.+$) with client_max_body_size $upload_size ; in /etc/nginx/conf.d/discourse.conf
I, [2022-03-11T16:50:42.835501 #1]  INFO -- : Replacing (?-mix:worker_connections.+$) with worker_connections $nginx_worker_connections ; in /etc/nginx/nginx.conf
I, [2022-03-11T16:50:42.835804 #1]  INFO -- : > echo "done configuring web"
I, [2022-03-11T16:50:42.839749 #1]  INFO -- : done configuring web

I, [2022-03-11T16:50:42.840160 #1]  INFO -- : > cd /var/www/discourse && gem install bundler --conservative -v $(awk '/BUNDLED WITH/ { getline; gsub(/ /,""); print $0 }' Gemfile.lock)
ERROR:  Could not find a valid gem 'bundler' (= 2.3.4), here is why:
          Unable to download data from https://rubygems.org/ - Net::OpenTimeout: execution expired (https://rubygems.org/specs.4.8.gz)
I, [2022-03-11T16:55:43.338723 #1]  INFO -- :
I, [2022-03-11T16:55:43.339140 #1]  INFO -- : Terminating async processes
I, [2022-03-11T16:55:43.339338 #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-03-11T16:55:43.339402 #1]  INFO -- : Sending TERM to exec chpst -u redis -U redis /usr/bin/redis-server /etc/redis/redis.conf pid: 103
2022-03-11 16:55:43.339 UTC [42] LOG:  received fast shutdown request
103:signal-handler (1647017743) Received SIGTERM scheduling shutdown...
2022-03-11 16:55:43.340 UTC [42] LOG:  aborting any active transactions
2022-03-11 16:55:43.342 UTC [42] LOG:  background worker "logical replication launcher" (PID 51) exited with exit code 1
2022-03-11 16:55:43.346 UTC [46] LOG:  shutting down
2022-03-11 16:55:43.361 UTC [42] LOG:  database system is shut down
103:M 11 Mar 2022 16:55:43.363 # User requested shutdown...
103:M 11 Mar 2022 16:55:43.363 * Saving the final RDB snapshot before exiting.
103:M 11 Mar 2022 16:55:43.433 * DB saved on disk
103:M 11 Mar 2022 16:55:43.434 # Redis is now ready to exit, bye bye...

A wget the rubygems works fine, internet connectivity is fine. Any suggestions?

1 Like

If internet connectivity is working on the host, you need to debug internet connectivity inside docker containers on that host.

2 Likes

I found my issue. I have IPv6 enabled on docker which seems to confuse things.

I had to turn it off then reload docker.

{
  "ipv6": false,
  "fixed-cidr-v6": "2001:db8:1::/64"
}

Thank you for the help!

2 Likes

More specifically: you had IPv6 enabled and configured to hand out addresses that won’t get back to your containers.

Not all apps are written to fall back to v4 of v6 connectivity is broken.

2 Likes

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.