Loomio
Thu 21 Nov 2019 4:56PM

Loomio not running after update

MM Michael McKinsey Public Seen by 46

Hi,

I have been running a loomio install for quite some time (years). It has been a long time since I did an update.

I ran the following:

cd loomio-deploy/

docker-compose down

docker-compose pull

docker-compose run app rake db:migrate

ERROR: No such service: app

I upgraded docker, and did a general update on my system, which is Ubuntu 14.04. I had to do a kernel update to get docker running after the update, but that seems to be working fine.

When I use:

docker-compose up -d

I end up with a:

502 Bad Gateway


nginx/1.17.5

When looking at:

docker-compose logs -f

I am getting a massive amount of scrolling text, it is difficult to pull out what might be important, it just keeps cycling through and shooting out massive lists of text.

I will include some snipits from the log in the hopes it may help. Any advice as to how to proceed would be great.

Thanks!

RG

Robert Guthrie Thu 21 Nov 2019 4:59PM

Hi @Michael McKinsey. try a git pull origin master to begin with.

MM

Michael McKinsey Thu 21 Nov 2019 5:07PM

@Rob Guthrie Thanks for the quick response - that seemed to get me further along. Now the update command exists and it runs, however seems to fail ending with:

docker-compose run app rake db:migrate

7f6f03435000-7f6f03436000 rw-p 00003000 00:3d 77 /usr/local/lib/ruby/2.6.0/x86_64-linux/enc/encdb.so

7f6f03436000-7f6f03461000 r--p 00000000 00:3d 50 /usr/local/lib/libruby.so.2.6.5

7f6f03461000-7f6f03695000 r-xp 0002b000 00:3d 50 /usr/local/lib/libruby.so.2.6.5

7f6f03695000-7f6f0377b000 r--p 0025f000 00:3d 50 /usr/local/lib/libruby.so.2.6.5

7f6f0377b000-7f6f03781000 r--p 00344000 00:3d 50 /usr/local/lib/libruby.so.2.6.5

7f6f03781000-7f6f03784000 rw-p 0034a000 00:3d 50 /usr/local/lib/libruby.so.2.6.5

7f6f03784000-7f6f03797000 rw-p 00000000 00:00 0

7f6f03797000-7f6f03798000 r--p 00000000 00:3d 40 /lib/x86_64-linux-gnu/ld-2.28.so

7f6f03798000-7f6f037b6000 r-xp 00001000 00:3d 40 /lib/x86_64-linux-gnu/ld-2.28.so

7f6f037b6000-7f6f037be000 r--p 0001f000 00:3d 40 /lib/x86_64-linux-gnu/ld-2.28.so

7f6f037be000-7f6f037bf000 r--p 00026000 00:3d 40 /lib/x86_64-linux-gnu/ld-2.28.so

7f6f037bf000-7f6f037c0000 rw-p 00027000 00:3d 40 /lib/x86_64-linux-gnu/ld-2.28.so

7f6f037c0000-7f6f037c1000 rw-p 00000000 00:00 0

7ffd31c1e000-7ffd3241d000 rw-p 00000000 00:00 0 [stack]

7ffd32559000-7ffd3255c000 r--p 00000000 00:00 0 [vvar]

7ffd3255c000-7ffd3255e000 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

RG

Robert Guthrie Thu 21 Nov 2019 5:09PM

You may want to backup your env file then run the generate config stuff from the readme again. I think that will change your default Docker images

MM

Michael McKinsey Thu 21 Nov 2019 5:17PM

@Rob Guthrie

./scripts/create_env loomio.fr33.me [email protected]

Changed my SMTP settings back to the way they are in my backed up env

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

WARNING: Found orphan containers (loomiodeployloomio1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

Creating loomio-redis

Creating loomio-db

/usr/local/bundle/gems/ffi-1.11.1/lib/ffi/library.rb:112: [BUG] Illegal instruction at 0x00007f8d467197a2

ruby 2.6.5p114 (2019-10-01 revision 67812) [x86_64-linux]

-- Control frame information -----------------------------------------------

c:0084 p:---- s:0462 e:000461 CFUNC :open

c:0083 p:0022 s:0456 e:000455 BLOCK /usr/local/bundle/gems/ffi-1.11.1/lib/ffi/library.rb:112 [FINISH]

c:0082 p:---- s:0447 e:000446 CFUNC :each

c:0081 p:0113 s:0443 e:000442 BLOCK /usr/local/bundle/gems/ffi-1.11.1/lib/ffi/library.rb:109 [FINISH]

c:0080 p:---- s:0436 e:000435 CFUNC :map

c:0079 p:0069 s:0432 e:000431 METHOD /usr/local/bundle/gems/ffi-1.11.1/lib/ffi/library.rb:99

c:0078 p:0079 s:0425 e:000424 CLASS /usr/local/bundle/gems/sassc-2.2.1/lib/sassc/native.rb:11

c:0077 p:0007 s:0421 e:000420 CLASS /usr/local/bundle/gems/sassc-2.2.1/lib/sassc/native.rb:6

c:0076 p:0014 s:0418 e:000417 TOP /usr/local/bundle/gems/sassc-2.2.1/lib/sassc/native.rb:5 [FINISH]

c:0075 p:---- s:0415 e:000414 CFUNC

...

7ffd2172e000-7ffd21731000 r--p 00000000 00:00 0 [vvar]

7ffd21731000-7ffd21733000 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

MM

Michael McKinsey Thu 21 Nov 2019 5:49PM

@Rob Guthrie I have backups of the database and info etc. If I need to wipe this server and install on a newer distro or something and I can import the databases that would be fine. I realize 14.04 is getting pretty old. I really hope I will not lose the loomio groups on this server, as they are active, but I wanted to upgrade to get the newer features.

RG

Robert Guthrie Thu 21 Nov 2019 6:45PM

Illegal instruction may mean that is required. If you can run this command (which I took from the backup script)

docker exec loomio-db su - postgres -c 'pg_dump -O -Fc loomio_production -f /pgdumps/loomio_production.dump'


and keep a copy of that loomio_production.dump and your uploads folder then we can run the migrations over the database from a fresh install.

MM

Michael McKinsey Thu 21 Nov 2019 8:09PM

okay I am up to try that getting this error:

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

RG

Robert Guthrie Thu 21 Nov 2019 8:11PM

can you run this first

docker-compose up db -d 

that might help it run, mapping that directory it cannot access

MM

Michael McKinsey Thu 21 Nov 2019 8:13PM

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

WARNING: Found orphan containers (loomiodeployloomio1) for this project. If you removed or renamed this service in your compose file, you can run this command with the --remove-orphans flag to clean it up.

ERROR: No such service: -d

RG

Robert Guthrie Thu 21 Nov 2019 8:14PM

try shuffling the param around. maybe docker-compose up -d db

Load More