Project

General

Profile

Actions

Bug #2192

closed

FAILED: LdapError: No such address or other socket error

Added by Gustavo Varela about 11 years ago. Updated about 11 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Authentication
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

I just upgraded from version 1.0 to 1.1 and my auth vs Active Directory does not work. It was working before the upgrade.

This is the error on the log,

Started POST "/users/login" for 10.127.245.72 at Sat Feb 09 14:57:29 -0600 2013
Processing by UsersController#login as HTML
Parameters: {"login"=>{"login"=>"sg0214163", "password"=>"[FILTERED]"}, "authenticity_token"=>"KoCSAg0tibaXKwZIVSNw2d+It5JR79aUoABQmeVt9Po=", "utf8"=>"✓", "commit"=>"Login »"}
Operation FAILED: LdapError: No such address or other socket error.
Rendered home/_topbar.rhtml (4.3ms)
Rendered common/500.rhtml within layouts/application (15.8ms)
Completed 500 Internal Server Error in 40050ms (Views: 16.8ms | ActiveRecord: 1.6ms)

I tried creating a new LDAP source but no luck.

Actions #1

Updated by Ohad Levy about 11 years ago

  • Priority changed from Immediate to Normal

the error indicate some low level error, like DNS, etc/hosts etc?

can you please provide more details (e.g. complete logs with debug)?

Actions #2

Updated by Gustavo Varela about 11 years ago

It was a problem with my DNS, sorry for the inconvenience.

Actions #3

Updated by Gustavo Varela about 11 years ago

This can be closed.

Actions #4

Updated by Dominic Cleal about 11 years ago

  • Category set to Authentication
  • Status changed from New to Closed

Thanks for updating us!

Actions

Also available in: Atom PDF