On Sat, Oct 1, 2016 at 3:08 AM, Doug Forster <[email protected]> wrote:
> Everyone, > > I need a little help I have two instances of foreman that I have > installed. I am planning on upgrading an instance that is behind a F5 so I > have done the following on the system that worked. > > 1. Installed current version on a fresh rhel 7 host. > 2. Cloned the production database to a new mysql server for testing. > 3. upgraded from 1.10 to 1.11. > 4. upgraded to 1.12. > > Everything seemed to work fine. > > Added a new host and pointed it at the same database and installed foreman > 1.12. I cannot auth via LDAP on the new host. > > This is the error: > *LdapFluff::Generic::UnauthenticatedException* > *Could not bind to ActiveDirectory user !LDAPForeman* > [snip] > Foreman Debug output from system that worked: > HOSTNAME: working.net > OS: redhat > RELEASE: Red Hat Enterprise Linux Server release 7.2 (Maipo) > FOREMAN: 1.12.3 > RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux] > PUPPET: 3.8.6 > DENIALS: 0 > > Foreman debug output from system that didn't work: > HOSTNAME: broken.net > OS: redhat > RELEASE: Red Hat Enterprise Linux Server release 7.2 (Maipo) > FOREMAN: 1.12.3 > RUBY: ruby 2.0.0p598 (2014-11-13) [x86_64-linux] > PUPPET: 3.8.6 > DENIALS: 0 > > Each is running under passenger with the tfm-ruby --version > ruby 2.2.2p95 (2015-04-13 revision 50295) [x86_64-linux] > > If you need any other info please let me know. > Were you able to manually bind on the new host using ldapsearch with same credentials as foreman? Also, see if passenger is able to make ldap requests (# getsebool -a | grep passenger_can_connect_ldap) Anurag -- You received this message because you are subscribed to the Google Groups "Foreman users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/foreman-users. For more options, visit https://groups.google.com/d/optout.
