aw man, downtime again :(

something's fucky with cawfee club and I can't tell what ;;;__;;;
unable to load the site or even ssh to the server
last time (a few weeks ago) I just waited it out but it's making me nervous

cute
2019-02-14-133038_860x297_scrot…

so basically… how can I debug why Pleroma isn’t starting?

Feb 13 18:31:31 cawfee.club systemd[1]: pleroma.service: main process exited, code=exited, status=1/FAILURE Feb 13 18:31:31 cawfee.club systemd[1]: Unit pleroma.service entered failed state. Feb 13 18:31:31 cawfee.club systemd[1]: pleroma.service failed. Feb 13 18:31:31 cawfee.club systemd[1]: pleroma.service holdoff time over, scheduling restart. Feb 13 18:31:31 cawfee.club systemd[1]: Stopped Pleroma social network. Feb 13 18:31:31 cawfee.club systemd[1]: Started Pleroma social network. Feb 13 18:31:33 cawfee.club systemd[1]: pleroma.service: main process exited, code=exited, status=1/FAILURE Feb 13 18:31:33 cawfee.club systemd[1]: Unit pleroma.service entered failed state. Feb 13 18:31:33 cawfee.club systemd[1]: pleroma.service failed. Feb 13 18:31:33 cawfee.club systemd[1]: pleroma.service holdoff time over, scheduling restart. Feb 13 18:31:33 cawfee.club systemd[1]: Stopped Pleroma social network. Feb 13 18:31:33 cawfee.club systemd[1]: start request repeated too quickly for pleroma.service Feb 13 18:31:33 cawfee.club systemd[1]: Failed to start Pleroma social network. Feb 13 18:31:33 cawfee.club systemd[1]: Unit pleroma.service entered failed state. Feb 13 18:31:33 cawfee.club systemd[1]: pleroma.service failed.

the biggest mistake was assuming I can keep things from falling apart

cawfee.club is kill ;_;
I tried updating the instance (git pull + mix ecto.migrate) and now pleroma fails to start
and I can't even connect to IRC to ask why because my current IP is banned (an open proxy record half a year ago)

real failure hours, good night

so... do I retire this account right away?

I'm so happy everything works  
now, onto the UX part