Basket: Can't connect to LDAP


Status Graveyard
Server Operations
8 years ago
3 years ago


(Reporter: abuchanan, Assigned: oremj)





8 years ago
I'm getting error emails from Basket,

Error: {'desc': "Can't contact LDAP server"}

Aravind said this is probably due to a moved LDAP slave that was moved.

Comment 1

8 years ago
Do you get more detail that than?  Is it transient?

Comment 2

8 years ago
These errors come and go sometimes, usually I ignore them and they go away quickly.  These have been going for 12+ hours now.

Seems like they started about the time that jabba pulled a minor Basket update.  That update only touched one line afaik, and it wasn't related to LDAP.

Sorry, I can't think of any more detail.  Maybe check that is pointing at the correct LDAP slave?

Comment 3

8 years ago
I emailed and thought I filed a bug on making the new LDAP slaves permanent. is pointing to the now-decommissioned LDAP slave.  

LDAP = {
    'host': 'ldap://',

That should be or

Comment 4

8 years ago
I should also say, I was told there wasn't anything in svn that had to be changed and that my local edit was just fine.

Comment 5

8 years ago
I manually edited that file (again).  Who has to fix this in svn or whatever so it doesn't break on the next update?
Let's not put configs in revision control.  use -dist or something to avoid conflicts or we can use a script to generate config files -- whatever we can do to avoid getting a conflict in a config.

Comment 7

8 years ago
Changes to shouldn't be getting reverted.  How did that happen?
(In reply to comment #6)
> Let's not put configs in revision control.
I mean we should, but not in a way that causes conflicts.  :)

Comment 9

8 years ago
I don't know but I'm punting to oremj.
Assignee: server-ops → jeremy.orem+bugs
Let's find out what caused the issue:
- rcs conflict on update
- git lock
- the code change
- another cause

Comment 11

8 years ago
Matthew, will you give me the full path to the file you edited?

Comment 13

8 years ago
The deploy script wasn't run. .
Last Resolved: 8 years ago
Resolution: --- → FIXED
Product: → Graveyard
You need to log in before you can comment on or make changes to this bug.