Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Improve logging format #53

Closed
aiida-bot opened this issue Jun 26, 2013 · 2 comments
Closed

Improve logging format #53

aiida-bot opened this issue Jun 26, 2013 · 2 comments
Labels
good first issue Issues that should be relatively easy to fix also for beginning contributors

Comments

@aiida-bot
Copy link

Originally reported by: Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi)

Use same format for global logger used by celery, and our logger (defined in the settings.py file).
Possibly, split the logs in different files for different tasks.
@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):

The problem was due to 'print' statements hidden in the code, plus non-configured celery and paramiko loggers.

Removed print statements, configured loggers in the settings.py, reduced the default logging level to WARNING, added also a new DbLogger handler to log to DB messages pertaining to a calculation.

@aiida-bot
Copy link
Author

Original comment by Giovanni Pizzi (Bitbucket: pizzi, GitHub: giovannipizzi):

Solved mainly in 619c824

@aiida-bot aiida-bot added good first issue Issues that should be relatively easy to fix also for beginning contributors enhancement labels Dec 23, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
good first issue Issues that should be relatively easy to fix also for beginning contributors
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@aiida-bot