Problem: univention-s4connector-list-rejected shows a traceback

s4-connector
problem
reject
ucs4

#1

Problem: univention-s4connector-list-rejected shows a traceback

You are getting a traceback and an error message when starting univention-s4connector-list-rejected:

root@backup:~# univention-s4connector-list-rejected 
Traceback (most recent call last):
  File "/usr/sbin/univention-s4connector-list-rejected", line 73, in <module>
    import mapping
ImportError: No module named mapping

Environment

Rejects can only listed on the UCS server where the s4connector is active. You could verify if it is active on your current server:

root@master:~# systemctl status univention-s4-connector
● univention-s4-connector.service - LSB: Univention S4 Connector
   Loaded: loaded (/etc/init.d/univention-s4-connector; generated; vendor preset: enabled)
   Active: active (running) since Tue 2019-01-29 13:05:39 CET; 4h 35min ago

In case it is not running you will get the following output:

root@backup:~# systemctl status univention-s4-connector
● univention-s4-connector.service
   Loaded: masked (/dev/null; bad)
   Active: inactive (dead)

Note: The S4-connector should only be active on one server within the domain! Do not attempt to start it while it is running on an other server!

Solution

Execute the failing command on a server where the S4-connector is running (see above).


closed #2