After update to 12.0.3, and reboot, postgreSQL goes back to 10.x and

Support Installation & Updates

After update to 12.0.3, and reboot, postgreSQL goes back to 10.x and ERR_CONNECTION_REFUSED

Added by Piotr F almost 4 years ago

Hi,

I am not too familiar with LAMP, but here is what happened just an hour ago:

did the regular update from 12.0.2 to 12.0.3,

all fine, admin center output correct: 12.0.3, postgresql 13.5

then VPS, Ubuntu 20.04 LTS, demanded reboot.

Did it.

And bang, the website with OP does not work at all: ERR_CONNECTION_REFUSED

So I did this:

sudo cat /etc/openproject/installer.dat | grep postgres/autoinstall

and got:
postgres/autoinstall skip

But this output is very strange then:

pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
10 main 5432 online postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
13 main 5432 down postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log

Why aye? Why aye man?!

Anybody could help?

I realize I have to turn off v.10, and turn on v.13, but how to do it?

Will be very grateful for any clues and hints.

Cheers,

Piotr

Replies (4)

RE: After update to 12.0.3, and reboot, postgreSQL goes back to 10.x and ERR_CONNECTION_REFUSED - Added by Piotr F almost 4 years ago

Would be happy if I could do some typing changes in any of conf files, instead of going through all reconfigure stuff.

RE: After update to 12.0.3, and reboot, postgreSQL goes back to 10.x and ERR_CONNECTION_REFUSED - Added by Piotr F almost 4 years ago

I stopped postgresql 10, ran 13, still nothing, same result as above.

Here we go:

pg_lsclusters
Ver Cluster Port Status Owner Data directory Log file
10 main 5432 down postgres /var/lib/postgresql/10/main /var/log/postgresql/postgresql-10-main.log
13 main 5432 online postgres /var/lib/postgresql/13/main /var/log/postgresql/postgresql-13-main.log

sudo openproject config
ADMIN_EMAIL=xx
APP_GROUP=xx
APP_HOME=xx
APP_NAME=xx
APP_RUNNER_CLI=systemctl
APP_RUNNER_TYPE=systemd
APP_SAFE_NAME=xx
APP_USER=xx
APP_WIZARDS=legacy-installer,openproject-edition,postgres,apache2,repositories,smtp,memcached,openproject
ATTACHMENTS_STORAGE_PATH=/var/db/openproject/files
DATABASE_URL=postgres://xx:xx@127.0.0.1:**5432**/xx
EMAIL_DELIVERY_METHOD=smtp
EXECJS_RUNTIME=Node
GEM_PATH=/opt/openproject/vendor/bundle/ruby/2.7.0:
GIT_REPOSITORIES=
HOME=/home/openproject
HOST=127.0.0.1
LANG=en_US.UTF-8
MALLOC_ARENA_MAX=2
MEMORY_AVAILABLE=14336
NODE_ENV=production
NODE_HOME=/opt/openproject/.heroku/node
OLDPWD=/
OPENPROJECT_INSTALLATION__TYPE=packager
OPENPROJECT_RAILS__FORCE__SSL=true
ORIGINAL_PWD=/root
PATH=bin:/opt/openproject/vendor/bundle/bin:/opt/openproject/vendor/bundle/ruby/2.7.0/bin:/opt/openproject/.heroku/node/bin:/opt/openproject/.heroku/yarn/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/sbin:/opt/openproject/bin:/opt/openproject/node_modules/.bin
PORT=6000
PWD=/opt/openproject
RACK_ENV=production
RAILS_CACHE_STORE=file_store
RAILS_ENV=production
RAILS_LOG_TO_STDOUT=enabled
RAILS_RELATIVE_URL_ROOT=/xx
RAILS_SERVE_STATIC_FILES=enabled
RECOMPILE_RAILS_ASSETS=
ROOT_PATH=/
SECRET_KEY_BASE=xx
SECRET_TOKEN=xx
SERVER_GROUP=www-data
SERVER_HOSTNAME=xx
SERVER_PATH_PREFIX=/xx
SERVER_PATH_PREFIX_PREVIOUS=/xx
SERVER_PROTOCOL=https
SERVER_USER=www-data
SHLVL=0
SMTP_AUTHENTICATION=xx
SMTP_DOMAIN=xx
SMTP_HOST=xx
SMTP_PASSWORD=xx
SMTP_PORT=xx
SMTP_URL=xx
SMTP_USERNAME=xx
SVN_REPOSITORIES=
SYS_API_KEY=xx
WEB_CONCURRENCY=28
WEB_MEMORY=512
WEB_TIMEOUT=300

Looks like openproject listens to port 5432, and postgreSQL 13 uses it.

Despite, I used the commands from here to set postgresql 13 to port 45432.

Does anyone have clue how to solve it?

Cheers,

Piotr

RE: After update to 12.0.3, and reboot, postgreSQL goes back to 10.x and ERR_CONNECTION_REFUSED - Added by Piotr F almost 4 years ago

Solved.

Had to re-run reconfigure, along with Apache2 settings again.

Looks like so far so good.

RE: After update to 12.0.3, and reboot, postgreSQL goes back to 10.x and ERR_CONNECTION_REFUSED - Added by Piotr F almost 4 years ago

Unfortunately, similar problem:

after the update to 12.0.5, unsuccessful, PostgreSQL showed, AGAIN, 10.19.

Side Menu

Content