and remove your orphans. that's safe

root@loomio:~/loomio-deploy# docker-compose up -d db

Creating loomio-db

root@loomio:~/loomio-deploy# docker exec loomio-db su - postgres -c 'pgdump -O -Fc loomioproduction -f /pgdumps/loomio_production.dump'

pgdump: [custom archiver] could not open output file "/pgdumps/loomioproduction.dump": Permission denied

root@loomio:~/loomio-deploy#

docker exec -ti loomio-db su - postgres -c 'pg_dump loomio_production' > loomio_production.sql

How about that one? do you know anything about pg_dump and what flag to use?

@Rob Guthrie Looks like that worked:

root@loomio:~/loomio-deploy# ls -lah|grep -i loom

-rw-r--r-- 1 root root 14M Nov 21 12:28 loomio_production.sql

so I need my uploads folder and that file to bring to a new install - I will grab that and spin up another VM on the same IP - how far should I go with the install before checking back in how to get this database imported?

I would also take a copy of your pgdata folder, you may not need to import the sql if that comes along too. the sql just means you can easily move the data between postgresql versions if the pgdata dir is incompatible with it's new host

@Rob Guthrie I am getting the same error on an 18.04 fresh install. Not sure what is causing this, but I have not copied anything over from the other machine. Following the install instructions at https://github.com/loomio/loomio-deploy - the only thing I did differently is I installed docker directly following instructions at https://docs.docker.com/install/linux/docker-ce/ubuntu/ because I was getting some errors about not finding the docker binary using the snap install. This is all fresh and clean install.

root@loomio:~/loomio-deploy# docker-compose run app rake db:setup

..... lots of scrolling text ...

7f586c967000-7f586c968000 rw-p 00000000 00:00 0

7fff70f43000-7fff71742000 rw-p 00000000 00:00 0 [stack]

7fff717e1000-7fff717e4000 r--p 00000000 00:00 0 [vvar]

7fff717e4000-7fff717e6000 r-xp 00000000 00:00 0 [vdso]

ffffffffff600000-ffffffffff601000 r-xp 00000000 00:00 0 [vsyscall]

[NOTE]

You may have encountered a bug in the Ruby interpreter or extension libraries.

Bug reports are welcome.

For details: https://www.ruby-lang.org/bugreport.html

SEGV received in ILL handler

what cpu architecture is your server? I wonder if this is 32bit or 64bit issue

root@loomio:~/loomio-deploy# uname -a

Linux loomio 4.15.0-70-generic #79-Ubuntu SMP Tue Nov 12 10:36:11 UTC 2019 x8664 x8664 x86_64 GNU/Linux

Sorry, I'm stumped right now. I'll keep thinking. Your .env file uses "latest" for the loomio image tag right? These images are running well on my boxes with the sameish uname results.

 4.18.0-25-generic #26-Ubuntu SMP Mon Jun 24 09:32:08 UTC 2019 x8664 x8664 x86_64 GNU/Linux

Nothing in the env file says anything about image tag or "latest".