Ticket #6856 (closed defect: worksforme)

Opened 9 years ago

Last modified 9 years ago

RDP auth "forgets" about LDAP server over time

Reported by: mooninite Owned by:
Component: RDP Version: VirtualBox 3.2.0
Keywords: Cc:
Guest type: other Host type: Linux


Host: Fedora 12 x86_64 8 core machine

All VirtualBox guests are running in headless mode. I have RDP auth for all guests set to External. There is a LDAP server on another machine on the same network. It appears that over time the Headless instance forgets how to communicate to the LDAP server. The time it takes seems to be about 3 or 4 days. This has been a recurring problem for some time now, which I thought was attributed to network changes or package updates, but I know now that those cases are not true. I can perform "getent passwd" on LDAP users at all times with no error, so I know there is no connectivity problem at the host level.

If I immediately stop and then start a single broken guest (while others continue to run) that guest can now authenticate against LDAP. The other guests are still broken.

I have tried changing my /etc/ldap.conf values for a broken guest, but this does not help. The only known workaround is to stop and start the broken guest.

Default values in /etc/ldap.conf
uri  ldap://server.local/
ssl start_tls
pam_password md5

Jun 1 10:19:21 localhost VBoxHeadless: pam_ldap: ldap_starttls_s: Can't contact LDAP server

Other values in /etc/ldap.conf
uri  ldaps://server.local/
#ssl start_tls
pam_password md5

Jun 1 10:23:24 localhost VBoxHeadless: pam_ldap: ldap_simple_bind Can't contact LDAP server
Jun 1 10:23:24 localhost VBoxHeadless: pam_ldap: reconnecting to LDAP server...

Change History

comment:1 Changed 9 years ago by mooninite

It has been one month since some of my VMs have been started and RDP is still functional. I will blame this on OS updates after all. Please close this bug.

comment:2 Changed 9 years ago by sandervl73

  • Status changed from new to closed
  • Resolution set to worksforme

Thanks for the feedback.

Note: See TracTickets for help on using tickets.
ContactPrivacy policyTerms of Use