mailcow-dockerized-docs/docs/debug.md

17 Zeilen
1,4 KiB
Markdown

2017-05-06 19:10:37 +02:00
When a problem occurs, then always for a reason! What you want to do in such a case is:
2017-05-06 18:24:40 +02:00
1. Read your logs; follow them to see what the reason for your problem is.
2017-06-30 00:24:34 +02:00
<<<<<<< HEAD
2017-05-06 18:24:40 +02:00
2. Follow the leads given to you in your logfiles and start investigating.
3. Restarting the troubled service or the whole stack to see if the problem persists.
4. Read the documentation of the troubled service and search it's bugtracker for your problem.
5. Search our [issues](https://github.com/mailcow/mailcow-dockerized/issues) for your problem.
2017-06-30 00:24:34 +02:00
=======
2017-05-09 17:54:50 +02:00
2. Follow the leads given to you in your log files and start investigating.
2017-05-09 17:23:05 +02:00
3. Restart the troubled service or the whole stack to see if the problem persists.
2017-05-09 17:54:50 +02:00
4. Read the documentation of the troubled service and search it's bug tracker for your problem.
2017-06-30 00:24:34 +02:00
5. Search our [issues](https://github.com/mailcow/mailcow-dockerized/issues) <!-- and [forum](https://forum.mailcow.email/) --> for topics related to your problem.
>>>>>>> 2ef7ae0f89cf3f9e8c7a73c99449cc50215450d7
2017-05-06 18:24:40 +02:00
6. [Create an issue](https://github.com/mailcow/mailcow-dockerized/issues) over at our GitHub repository if you think your problem might be a bug or a missing feature you badly need. But please make sure, that you include **all the logs** and a full description to your problem.
2017-05-06 18:40:18 +02:00
8. Connect to IRC ([chat.freenode.net](https://webchat.freenode.net/)) and join our IRC channel [#mailcow](irc://chat.freenode.net:6667/mailcow).