Troubleshooting Chatwoot Installation Restart Issue

TLDR mh2753 experienced issues with restarting the Chatwoot installation. v_shnu provided a diagnostic process, but the problem was due to lack of disk space. v_shnu shared where to find logs in the future.

Photo of mh2753
mh2753
Mon, 12 Sep 2022 11:23:13 UTC

Hi 👋. My chatwoot installation has suddenly refused to restart. running "sudo systemctl restart chatwoot.target" does not bring up the server. I do see a " ruby bin/rails server -p 3000 -e production" running but no puma application. Since I have no experience with ruby on rails, can someone please guide me where to find the logs or where to start looking. Thanks

Photo of v_shnu
v_shnu
Mon, 12 Sep 2022 11:39:43 UTC

What is the output of `systemctl restart`?

Photo of v_shnu
v_shnu
Mon, 12 Sep 2022 11:41:09 UTC

Could you try killing the process manually and try again? ``` ps -aux | grep chatwoot kill #get pids from the output of above command systemctl start chatwoot.target ```

Photo of mh2753
mh2753
Mon, 12 Sep 2022 11:50:09 UTC

Thanks for the response. It turns out there was no space left on device. After clearing some logs, it has now worked.

Photo of mh2753
mh2753
Mon, 12 Sep 2022 11:50:27 UTC

But in the future, is there a way for me to look at some logs? I coudnt find any server/process logs anywhere

Photo of v_shnu
v_shnu
Mon, 12 Sep 2022 11:59:53 UTC

https://www.chatwoot.com/docs/self-hosted/deployment/chatwoot-ctl#viewing-logs

Photo of v_shnu
v_shnu
Mon, 12 Sep 2022 12:05:52 UTC

Chatwoot being wrapped as a systemd service uses the journald logging. You can use journactl to view the logs. `cwctl --logs ` is a wrapper around these.