Loomio not working after installation
Hello,
I am trying to install loomio on dedicated vps machine running ubuntu and docker. I followed all steps described in loomio-deploy section on github. The containers gave started up and i managed to open sign_in and sign_up pages. After creating the account the dashboard page is blank.
Errors logged by ngix_1 container attached in err-docker.txt file, errors reported by browser attached in err-browser.txt file.
I tried to follow the hints described here: https://www.loomio.org/d/oYVb6WIs/blank-dashboard-after-install-with-docker, but did not succeed much.
Would you have any hints or suggestions?
Hi @robertguthrie
Thank you for swift reply. Please advise what should be my next step to use your fix? Should I make a fresh installation or there is some way to enforce docker to update files?
Ok, I managed to download the updated files by
docker-compose pull
I am now facing some problems with communication with my smtp server, but it seems to be authentication issue here.
Thanks for identifying a problem for us. Good luck with the SMTP issues.
Hello there, I am hijacking this thread, as it is fresh and I feel my issue is on topic.
I have followed the loomio-deploy README.md some four or five times, with clean installs on debian jessie virtual machines. Everything seemed OK but the application was really sluggish, and I was getting a timeout when creating a group. I was blaming it on being short of RAM and horsepower.
But today I started from scratch on a rather cool laptop running a current opensuse tumbleweed, with 4Gb RAM and SSD harddisk and, while the sluggishness is gone, the timeout is still there.
Steps to reproduce (this works for me every time):
* Install a clean instance from scratch
* Access the app on the browser and create a new user
* Launch the "Start a group" wizard, fill a name and a description, push "Start group" blue button
At this point the webapp shows the "Loading" notification in the lower-left corner for a while, and then it stays forever in the "Start a group" wizard.
When I close the "Start a group" wizard I can see the group has been created, but I am not a member and, while I can request membership, I don't get any email, and I don't see any smtp-related error on the logs.
I am copying two fragments of the logfiles here, inline, and I am attaching the full logfile to this post.
I get a timeout in the 'docker-compose logs' output for 'loomio_1':
------ 8< ------------------------------------
Started POST "/api/v1/groups" for 172.17.0.7 at 2017-02-15 14:48:14 +0000
Processing by API::GroupsController#create as JSON
Parameters: {"group"=>{"parent_id"=>nil, "name"=>"Group Name", "group_privacy"=>"closed", "discussion_privacy_options"=>"private_only", "members_can_add_members"=>true, "members_can_edit_discussions"=>true, "members_can_edit_comments"=>true, "motions_can_be_edited"=>false, "description"=>"Description", "membership_granted_upon"=>"approval", "members_can_raise_motions"=>true, "members_can_vote"=>true, "members_can_start_discussions"=>true, "members_can_create_subgroups"=>false}}
[ActiveJob] Enqueued SendBulkEmailJob (Job ID: f10aa9dd-d5f9-4489-853f-5e58f17eed83) to DelayedJob(default) at 2017-02-15 14:48:14 UTC with arguments: 1
Completed 500 Internal Server Error in 60605ms (ActiveRecord: 53.4ms)Net::OpenTimeout (execution expired):
app/services/message_channel_service.rb:16:inpublish'block (2 levels) in '
config/initializers/event_bus.rb:86:in
app/extras/event_bus.rb:8:inblock in broadcast'broadcast'
app/extras/event_bus.rb:8:in
app/models/events/new_discussion.rb:4:inblock in publish!'tap'
app/models/events/new_discussion.rb:4:in
app/models/events/new_discussion.rb:4:inpublish!'block in add_to_group!'
app/extras/example_content.rb:6:in
app/extras/example_content.rb:5:intap'add_to_group!'
app/extras/example_content.rb:5:in
app/services/group_service.rb:12:increate'create_action'
app/controllers/api/restful_controller.rb:12:in
app/controllers/api/groups_controller.rb:17:in `create'
------ 8< ------------------------------------
And then I get this from time to time, in 'nginx_1'
------ 8< ------------------------------------
2017/02/15 14:49:14 [warn] 52#52: *35 upstream server temporarily disabled while reading response header from upstream, client: 10.10.10.40, server: loomio.test.example.com, request: "POST /api/v1/groups HTTP/1.1", upstream: "http://172.17.0.5:3000/api/v1/groups", host: "loomio.test.example.com", referrer: "https://loomio.test.example.com/explore"
------ 8< ------------------------------------
Thanks for your help 👍
Looking at your log, it says execution timeout on publish which means it's trying to send a message to the FAYE instance but failing.
I don't know why this is, but if you take the FAYE_URL out of the ENV file, it won't try to send a message in the first place.
Hi @radekpaliszkiewicz,
Thanks for letting us know about the issue.
It seems like the client assets are not being built, so you're getting 404's.
I've updated the Dockerfile to install
yarnwhich is now required by the client build system.Hopefully this fixes the issue.