diaspora-installer package results in unstartable service

Bug #1606251 reported by Sean O'Connell
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
diaspora
New
Undecided
Unassigned

Bug Description

Installation of the diaspora-installer package on a clean, up-to-date 16.04.1 LTS server results in an app server that will not start and throws a Ruby exception. This renders the newly installed diaspora* server unaccessible.

The package installs correctly if the system has enough memory (at least 1GB). On a server with 512M memory and no swap gem compilation exhausted the system memory and the package installation failed without a clear error message as to why.

Following installation of the package, the diaspora service is started:

root@bug-test:~# systemctl status diaspora
● diaspora.service - LSB: Diaspora application server
   Loaded: loaded (/etc/init.d/diaspora; bad; vendor preset: enabled)
   Active: active (exited) since Mon 2016-07-25 09:25:27 EDT; 1min 54s ago
     Docs: man:systemd-sysv-generator(8)
  Process: 11714 ExecStop=/etc/init.d/diaspora stop (code=exited, status=0/SUCCESS)
  Process: 11724 ExecStart=/etc/init.d/diaspora start (code=exited, status=0/SUCCESS)

Jul 25 09:25:27 bug-test systemd[1]: Stopped LSB: Diaspora application server.
Jul 25 09:25:27 bug-test systemd[1]: Starting LSB: Diaspora application server...
Jul 25 09:25:27 bug-test diaspora[11724]: * Starting diaspora server...
Jul 25 09:25:27 bug-test systemd[1]: Started LSB: Diaspora application server.
Jul 25 09:25:27 bug-test sudo[11736]: root : TTY=unknown ; PWD=/usr/share/diaspora ; USER=diaspora ; COMMAND=./script/server
Jul 25 09:25:27 bug-test sudo[11736]: pam_unix(sudo:session): session opened for user diaspora by (uid=0)
Jul 25 09:25:28 bug-test sudo[11736]: pam_unix(sudo:session): session closed for user diaspora

However, the application server is not launched on localhost TCP port 3000:

root@bug-test:~# netstat -an | more
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State
tcp 0 0 127.0.0.1:6379 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:5432 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN
tcp 0 0 0.0.0.0:443 0.0.0.0:* LISTEN
tcp 0 0 192.168.122.185:22 192.168.122.1:36410 ESTABLISHED
tcp6 0 0 :::80 :::* LISTEN
tcp6 0 0 :::22 :::* LISTEN
tcp6 0 0 ::1:5432 :::* LISTEN
tcp6 0 0 ::1:25 :::* LISTEN
udp 0 0 0.0.0.0:68 0.0.0.0:*
udp6 0 0 ::1:44959 ::1:44959 ESTABLISHED

Which is configured as the nginx proxy target:

root@bug-test:/etc/nginx/sites-enabled# cat pod.bugtest.lan
upstream domain11 {
        server 127.0.0.1:3000;
}

Connections to the new pod result in a 404 (see attached screenshot):

root@bug-test:/var/log/diaspora# cat error.log
2016/07/25 09:30:53 [error] 11671#11671: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.122.1, server: pod.bugtest.lan, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "pod.bugtest.lan"
2016/07/25 09:30:53 [error] 11671#11671: *3 open() "/usr/share/diaspora/50x.html" failed (2: No such file or directory), client: 192.168.122.1, server: pod.bugtest.lan, request: "GET / HTTP/1.1", upstream: "http://127.0.0.1:3000/", host: "pod.bugtest.lan"

The root cause appears to be a failure of the application server to start:

root@bug-test:/usr/share/diaspora/log# cat startscript.log
WARNING: You are in detached HEAD state!
Starting Diaspora in production mode with 1 Sidekiq worker(s).

D, [2016-07-25T09:22:40.150407 #11554] DEBUG -- : Terminating 5 actors...
/usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/lib/eye/sigar.rb:1:in `require': /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sigar-0.7.3/lib/sigar.so: undefined symbol: sigar_skip_token - /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/sigar-0.7.3/lib/sigar.so (LoadError)
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/lib/eye/sigar.rb:1:in `<top (required)>'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/lib/eye/controller.rb:13:in `require'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/lib/eye/controller.rb:13:in `<top (required)>'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/lib/eye/control.rb:2:in `require'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/lib/eye/control.rb:2:in `<top (required)>'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/bin/loader_eye:53:in `require'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/gems/eye-0.7/bin/loader_eye:53:in `<top (required)>'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/bin/loader_eye:23:in `load'
        from /usr/share/diaspora/vendor/bundle/ruby/2.3.0/bin/loader_eye:23:in `<main>'

Tags: diaspora ruby
Revision history for this message
Sean O'Connell (sdoconnell) wrote :
description: updated
Revision history for this message
Jason Robinson (jaywink) wrote :

Hi Sean,

This team where you logged the bug was for packaging Diaspora but has not been active in ages. The people who have packaged Diaspora for Debian are not in this group, so you should really log this bug in the Debian bug tracker.

I'll notify the packager of this bug and if he wants to take ownership of this team here, I'll give it to him, otherwise I'll close this team here (if able to).

Revision history for this message
Sean O'Connell (sdoconnell) wrote :

Okay, thank you Jason.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.