This repository has been archived by the owner on Dec 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 69
Troubleshooting
Seth Art edited this page Sep 3, 2018
·
2 revisions
If things are not acting like you think they should, there are two log files you can look at.
log/celeryWorker.log is the Celery debug log. I print things to this log that will help you understand what is going on. Also, this is where I look for any python syntax issues that occur in asynchronous jobs. If you see any uncaught exceptions in here, please let me know!
log/cmdExecutionAutdit.log is a tab delimited log file that records the following columns for each executed command: Start Time, End Time, Duration, Command Name, Command
The following commands will show you what is in the celerystalk database:
./celerystalk db hosts
./celerystalk db services
./celerystalk db paths
If you want to access the database itself, try using sqlitebrowser:
# sqlitebrowser csdb.sqlite3 &
The reset script in the setup directory will:
- Remove all .pyc files
- Wipe the celerystalk database
- Remove any jobs still in the Redis queue
- Restart celery.
# cd setup
# ./reset.sh
# cd ..
# ./celerystalk ...