diaspora-installer package results in unstartable service
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.
Active: active (exited) since Mon 2016-07-25 09:25:27 EDT; 1min 54s ago
Docs: man:systemd-
Process: 11714 ExecStop=
Process: 11724 ExecStart=
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/
Jul 25 09:25:27 bug-test sudo[11736]: pam_unix(
Jul 25 09:25:28 bug-test sudo[11736]: pam_unix(
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-
upstream domain11 {
server 127.0.0.1:3000;
}
Connections to the new pod result in a 404 (see attached screenshot):
root@bug-
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://
2016/07/25 09:30:53 [error] 11671#11671: *3 open() "/usr/share/
The root cause appears to be a failure of the application server to start:
root@bug-
WARNING: You are in detached HEAD state!
Starting Diaspora in production mode with 1 Sidekiq worker(s).
D, [2016-07-
/usr/share/
from /usr/share/
from /usr/share/
from /usr/share/
from /usr/share/
from /usr/share/
from /usr/share/
from /usr/share/
from /usr/share/
from /usr/share/
description: | updated |
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).