Project

General

Profile

Bug #8885

authentic2 traceback when an LDAP is unreachable for synchronization

Added by Benjamin Dauvergne over 5 years ago. Updated about 3 years ago.

Status:
Fermé
Priority:
Haut
Category:
-
Target version:
Start date:
05 Nov 2015
Due date:
% Done:

100%

Estimated time:
Patch proposed:
Yes
Planning:

Description

It should log a warning instead.


Files

Associated revisions

Revision c0aa1fb8 (diff)
Added by Benjamin Dauvergne over 5 years ago

ldap_backend: do not traceback on synchronization (fixes #8885)

If we cannot connect to the LDAP servers during a synchronization, we log a
warning.

History

#1

Updated by Benjamin Dauvergne over 5 years ago

It prevents seeing this in cron mails:

Traceback (most recent call last):
  File "/usr/lib/authentic2/manage.py", line 21, in <module>
    execute_from_command_line(sys.argv[:1] + argv)
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 385, in execute_from_command_line
    utility.execute()
  File "/usr/lib/python2.7/dist-packages/django/core/management/__init__.py", line 377, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/usr/lib/python2.7/dist-packages/hobo/multitenant/management/commands/tenant_command.py", line 47, in run_from_argv
    klass.run_from_argv(args)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 288, in run_from_argv
    self.execute(*args, **options.__dict__)
  File "/usr/lib/python2.7/dist-packages/django/core/management/base.py", line 338, in execute
    output = self.handle(*args, **options)
  File "/usr/lib/python2.7/dist-packages/authentic2/management/commands/sync-ldap-users.py", line 14, in handle
    for user in LDAPBackend.get_users():
  File "/usr/lib/python2.7/dist-packages/authentic2/backends/ldap_backend.py", line 930, in get_users
    users = conn.search_s(user_basedn, ldap.SCOPE_SUBTREE, user_filter, [])
AttributeError: 'NoneType' object has no attribute 'search_s'
run-parts: /etc/cron.hourly/authentic2-multitenant exited with return code 1

#2

Updated by Benjamin Dauvergne over 5 years ago

  • Priority changed from Normal to Haut
#3

Updated by Frédéric Péters over 5 years ago

fine by me.

#4

Updated by Benjamin Dauvergne over 5 years ago

  • Status changed from En cours to Résolu (à déployer)
  • % Done changed from 0 to 100
#5

Updated by Benjamin Dauvergne about 5 years ago

  • Status changed from Résolu (à déployer) to Solution déployée
#6

Updated by Benjamin Dauvergne about 3 years ago

  • Status changed from Solution déployée to Fermé

Also available in: Atom PDF