-
Notifications
You must be signed in to change notification settings - Fork 36
Troubleshooting
Alexander Smirnov edited this page Mar 29, 2020
·
12 revisions
ADVICE: Join our Discord group and check pinned messages in #general channel. You can also ask your questions there and we will answer them if possible.
- If there's an error in the console log, search for the detailed error message in the log file and post it with your report. The name of the log file can be identified by the text in the square brackets on the console message. Example:
12:49:34 [ Module] [ Notification]: Inititalizing Notifications module...
whereNotification
is the name of the log file.Logs
folder is located in the app directory but if you use Docker under Linux then it will be located in the boundData
folder instead. - If there's a problem related to EVE Notifications feed then find original notification message in
notifications_lg.log
log file and attach it to your report. - If your problem is related to the module configuration, make sure you attach corresponding config section from
settings.json
file to your report. You can omit sensitive data such as IDs but the general config layout will be helpful.
As a temp solution you can:
- Assign an automated job (using Cron in Linux) to restart bot container
- Specify
docker run --restart always
flag when running container - Use
Restarter
app provided up from the v1.4.9 release.
Set "RunAsServiceCompatibility": true
in config file. This will disable all implemented console interactions and should lessen the CPU load.
Contact me on Discord or create new issue on GitHub and we will get it sorted out and fixed!
Docker runs inside its own container so to access MySQL you will have to allow remote connections to the database and then connect to it via public ip instead of localhost. When you use localhost on Docker it tries to look for a MySQL inside the Docker container.