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)
- 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
- Infra Server space usage unexpected /var
- Chef Infra Server 13.0.17 - 13.2.0 rapid performance degradation (status=500, {error,{case_clause,{error,sel_conn_closed}}})
- Chef Infra Server data ( /var disk full 100%, '500 smell something burning' )
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
- 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)
- Backend failover and subsequent performance degradation, Postgres leader Unknown (VMware DRS, failover, rebalancing)