Pixelated-server is not started on boot
varac opened this issue · comments
When (re)booting a server, the pixelated-server service is not started.
Pixelated-server is not starting on deploy because of a bug on Soledad-server. This bug is being carried out on https://leap.se/code/issues/8647.
@varac and the royal @ayoyoness stated that we don't know yet if the pixelated-server isn't starting strictly because of the soledad-server bug. So we should debug this more extensively.
I rebooted dev.pix, and after reboot the pixelated-server service is not running.
--- ~ » pixssh dev.pixelated-project.org
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Nov 23 12:49:09 2016 from 213.61.36.58
root@dev1:~# w
12:53:37 up 0 min, 1 user, load average: 1.43, 0.42, 0.15
USER TTY FROM LOGIN@ IDLE JCPU PCPU WHAT
root pts/0 213.61.36.58 12:53 1.00s 0.06s 0.00s w
root@dev1:~# systemctl status pixelated-server.service
● pixelated-server.service - Pixelated
Loaded: loaded (/lib/systemd/system/pixelated-server.service; static)
Active: inactive (dead)
root@dev1:~# run_tests
PASS: Network > Can connect to internet?
PASS: Network > Is stunnel running?
PASS: Network > Is shorewall running?
PASS: Network > Are server certificates valid?
PASS: CouchDB > Are daemons running?
PASS: CouchDB > Is CouchDB running?
PASS: CouchDB > Do ACL users exist?
PASS: CouchDB > Do required databases exist?
PASS: CouchDB > Can records be created?
PASS: Webapp > Can contact couchdb?
PASS: Webapp > Can contact couchdb via haproxy?
PASS: Webapp > Are daemons running?
PASS: Webapp > Can access webapp?
PASS: Webapp > Can create and authenticate and delete user via API?
PASS: Webapp > Can sync Soledad?
PASS: Mx > Can contact couchdb?
PASS: Mx > Can contact couchdb via haproxy?
PASS: Mx > Can query identities db?
PASS: Mx > Are MX daemons running?
PASS: Mx > Can deliver email?
PASS: Mx > Can postfix query leapmx?
FAIL: Pixelated > Are daemons running? [pixelated.rb:11]:
No running process for /usr/bin/pixelated-user-agent
Tests halted on failure (because of --no-continue).
So it's still not solved.
@varac Did you look at the UA logs?
btw, soledad-server is runing so it's not related to soledad:
root@dev1:~# systemctl status soledad-server.service
● soledad-server.service - LSB: Start soledad daemon at boot time
Loaded: loaded (/etc/init.d/soledad-server)
Active: active (running) since Wed 2016-11-23 12:53:10 UTC; 11min ago
Process: 755 ExecStart=/etc/init.d/soledad-server start (code=exited, status=0/SUCCESS)
CGroup: /system.slice/soledad-server.service
├─1765 /usr/bin/python /usr/bin/twistd --uid=soledad --gid=soledad --pidfile=/var/run/soledad.pid --logfile=/var/log/soledad.log web --wsgi=leap.soledad.server.application --po...
├─5936 sudo -u soledad-admin /usr/bin/create-user-db user-f568c59df06e4d4ec28147577a1f1d57
└─5937 /usr/bin/python /usr/bin/create-user-db user-f568c59df06e4d4ec28147577a1f1d57
Did you look at the UA logs?
No I didn't because I'm not planning to fix it now.
Follow-up issue is at https://leap.se/code/issues/8671
To QA: Deploy to dev, upgrade to latest version of pixelated-server, reboot and see if pixelated-server is started.
It works! 🎉
It's working awesomely!! 🎉 ❤️