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.
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
What is the output of `systemctl restart`?
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
Thanks for the response. It turns out there was no space left on device. After clearing some logs, it has now worked.
But in the future, is there a way for me to look at some logs? I coudnt find any server/process logs anywhere
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.
Indexed 2258 threads
Chatwoot | Knowledge Base powered by Struct.AI