Closed tdudgeon closed 5 years ago
mh, can you run it as postgres user?
Create the output folder as root and give the galaxy user write permissions. Then pg_dumpall
should work.
sorry, yes I had missed the su postgres
command, but that still didn't work as postgres
user can't write to /export/postgresql
. If you create a new dir and owned by postgres
then you can do the dump to there as the postgres
user.
2 other problems I found:
for f in *; do echo $f; diff $f ../../galaxy-data-old/galaxy-central/config/$f; read; done
didn't wok for me. It just hung and did nothing. postgres user can't write to /export/postgresql
On my instance /export/postgresql is owned by postgres user, it's not the case for you? Which version are you upgrading from? Is /export mounted from a local path?
the for f in *; do echo $f; diff $f ../../galaxy-data-old/galaxy-central/config/$f; read; done didn't wok for me. It just hung and did nothing.
Strange, are there the expected xml files in ./
and ../../galaxy-data-old/galaxy-central/config/
?
OK, so I can write to the /export/postgresql
dir when doing the dump now (using the upgraded environment) so I'm not sure what was wrong. I was upgrading from 19.01.
And yes, there are the expected files in the galaxy-central/config
dir.
Th instructions for upgrading postgres in 19.05 don't work.
1) The command
docker exec galaxy bash
needs to bedocker exec -it galaxy bash
2) The command
pg_dumpall --clean > /export/postgresql/9.3dump.sql
fails with:I also tried as galaxy user but that fails with permission denied error