Bug 54665 - AD Connector module shows always connector not running
AD Connector module shows always connector not running
Status: NEW
Product: UCS
Classification: Unclassified
Component: AD Connector
UCS 4.4
Other Linux
: P5 normal (vote)
: ---
Assigned To: Samba maintainers
Samba maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2022-04-12 16:04 CEST by Dirk Schnick
Modified: 2022-04-12 16:36 CEST (History)
1 user (show)

See Also:
What kind of report is it?: Bug Report
What type of bug is this?: 1: Cosmetic issue or missing function but workaround exists
Who will be affected by this bug?: 1: Will affect a very few installed domains
How will those affected feel about the bug?: 1: Nuisance – not a big deal but noticeable
User Pain: 0.006
Enterprise Customer affected?: Yes
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number: 2022030721000231
Bug group (optional): bitesize
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dirk Schnick univentionstaff 2022-04-12 16:04:37 CEST
A really easy to solve bug. In
/usr/lib/python2.7/dist-packages/univention/management/console/modules/adconnector/__init__.py
we search in row 364 if ad-connector is running:
self.status_running = self.__is_process_running('*python*univention/connector/ad/main.py*')

The process looks like that in the system:
root@dc1:~ # ps fax | grep connector                                                                                                                                                                               
 8157 pts/4    S+     0:00  |                   \_ grep connector
 1759 ?        S      0:12 /usr/bin/python2.7 -W ignore -m univention.connector.ad.main

We need to correct the line to:

self.status_running = self.__is_process_running('*python*univention.connector.ad.main*')

This is already patched in UCS5.