Chef Infra Server
Troubleshooting for and configuration of Chef Infra Server on all platforms, topologies and architectures
General Chef Server (incl. OpsWorks, AWS Marketplace, Azure Marketplace)
- Chef Infra Server Compatibility with Reporting
- postgresql database export password hashes vs. plain-text passwords on standalone or frontends
- Upgrades to Chef Infra Server 14.x from Earlier Versions
- Error Syncing Cookbooks (Connection timed out - connect(2))
- Change Chef Infra Server IP Address
- Erchef beam.smp processes consume 100% CPU, services won't start after reboot / patching
Chef-Backend Cluster (Tiered and HA Topologies)
- Chef-Backend Cluster (Tiered and HA Topologies) management during maintenance/service (patching, upgrading, failover-testing, VM snapshot creation)
- Chef-Backend Cluster: Chef Server Frontend/Backend Tuning
- 503 Errors from Chef frontend servers after migration to new backend servers
- My Chef Backend HA cluster system is returning 500s at the UI
- Chef-Backend Cluster failover (long duration/frequency of GC young/tenured processes)
- Chef Backend Cluster degraded after network disruption/outage (Knife / Client 500, 502, 504 / ERROR: cannot execute UPDATE in a read-only transaction)