Forums

Articles
Create
cancel
Showing results for 
Search instead for 
Did you mean: 

bitbucket 4.14 upgrade problems

joel Cruz April 8, 2019

trying to do a bitbucket 4.14 on linux upgrade. I'm trying to build a new instance and copy the data over or upgrade a clone, whatever is easier.

the zero downtime diy backup worked (the name is a lie btw, builds where breaking entire time during the backup), but the restore doesn't work, kept complaining about a missing postgres port which is weird, the entire var config is copied over, there's nothing missing. 

So i tried to clone the environment instead and just go from there. The problem with this route is bitbucket is sitting behind a reverse proxy with SSL, If i change all the configs with the new server IP's and hostname it breaks beacause suddenly the cert doesn't work, If i change just the IP the proxy just forwards to the live environment.

How do i change the config to go back to the simple tomcat server instead of using the reverse apache server?

Or, how do i get the zero restore script to work?

1 answer

0 votes
John Lawlor
Rising Star
Rising Star
Rising Stars are recognized for providing high-quality answers to other users. Rising Stars receive a certificate of achievement and are on the path to becoming Community Leaders.
April 8, 2019

What exactly was your postgres error? The restore script is a bit tricky. Can you the error you are getting from the restore script?

joel Cruz April 8, 2019

the error reads:

[database-postgresql.sh:41 -> prepare_restore_db][bitbucket] ERROR: The configuration var 'POSTGRES_PORT' is required, please update './bitbucket.diy-backup.vars.sh'.

and in the vars folder it's already defined:

POSTGRES_PORT=5432

the vars is exactly the same as the backup. only thing i changed was the postgres IP and credentials so it can restore to the new db server. 

joel Cruz April 9, 2019

went down the reverse proxy rabbit hole. changed all my configs and added a dns entry for my new environment, but i'm getting the following errors now:

[Tue Apr 09 11:12:29.297195 2019] [proxy:error] [pid 18610] (111)Connection refused: AH00957: HTTP: attempt to connect to 10.50.1.92:7990 (bitbucket2) failed
[Tue Apr 09 11:12:29.297364 2019] [proxy:error] [pid 18610] AH00959: ap_proxy_connect_backend disabling worker for (bitbucket2) for 60s
[Tue Apr 09 11:12:29.297469 2019] [proxy_http:error] [pid 18610] [client 10.50.2.31:1409] AH01114: HTTP: failed to make connection to backend: bitbucket2, referer: https://10.50.1.92/

 Not sure whats going on here

Suggest an answer

Log in or Sign up to answer
TAGS
AUG Leaders

Atlassian Community Events