Winbind fails to start due to permissions issue on socket directory

Solution Verified - Updated -

Issue

  • Winbind is not starting
  • winbindd dead but pid file exists
  • After securing system, winbind is no longer starting

Environment

  • Red Hat Enterprise Linux 6

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content