All logs generated by the Chef server can be found in /var/log/opscode. Each service enabled on the system also has a sub-directory in which service-specific logs are located, typically found in /var/log/opscode/service_name.
The Chef server has built-in support for easily tailing the logs that are generated. To view all the logs being generated on the Chef server, enter the following command:
> chef-server-ctl tail
To view logs for a specific service:
> chef-server-ctl tail SERVICENAME
where SERVICENAME should be replaced Read more click here
Reference:- This article was originally posted on scmGalaxy.com
Thanks for sharing this practical explanation of logging in Chef — it’s great to see the basics laid out clearly because understanding where and how Chef logs information is essential for troubleshooting and maintaining your infrastructure automation. The article does a nice job of pointing out that Chef Server logs are stored under the /var/log/opscode directory and that you can use commands like chef-server-ctl tail to live-tail logs for all services or specific ones, which can be incredibly helpful when investigating issues in real time. It’s also useful to know about how supervisor logs are automatically rotated and kept with timestamped filenames, making it easier to track historical events without cluttering your system. For Chef Client runs, the point about the default log_location being STDOUT, but configurable in client.rb, is especially handy for tailoring where your logs end up on disk. Overall, having visibility into both server-side and client-side logs is key to diagnosing failures or performance issues when automating infrastructure with Chef — thanks for breaking down these core concepts in a way that’s easy to follow, especially for those newer to Chef or DevOps.
ReplyDelete