Traceback in s4 connector

UCS - Univention Corporate Server
#1

Hi all,

I have a fully patched DC Master (4.4-4-528) that throws an error in the diagnostics of S4 Connector Rejects. Calling univention-s4connector-list-rejected shows the same message:

root@dcm:~# univention-s4connector-list-rejected 
Traceback (most recent call last):
  File "/usr/sbin/univention-s4connector-list-rejected", line 162, in <module>
    main()
  File "/usr/sbin/univention-s4connector-list-rejected", line 114, in main
    mapping.s4_mapping,
AttributeError: 'module' object has no attribute 's4_mapping'

Some packages, maybe relevant:

python-univention-connector-s4                      13.0.2-66A~4.4.0.202003122223
univention-nagios-s4-connector                      4.0.1-2A~4.4.0.201905212123
univention-s4-connector                             13.0.2-66A~4.4.0.202003122223

What is missing here?

#2

If somebody cares to know the solution: something in a cron.daily job (06:25) has regenerated the mapping.py file, but the corresponding .pyc did not follow:

root@dcm:/etc/univention/connector/s4# ls -la
insgesamt 148
drwxr-xr-x 2 root root  4096 Apr 12 06:25 .
drwxr-xr-x 3 root root  4096 Apr 12 05:41 ..
-rw-r--r-- 1 root root 67537 Mär 12 22:05 mapping
-rw-r--r-- 1 root root 67337 Apr 12 06:25 mapping.py
-rw-r--r-- 1 root root   126 Apr 12 06:25 mapping.pyc

Removing the (nearly empty) .pyc file and restarting the connector cured the problem.

1 Like
Mastodon