Univention Bugzilla – Bug 33858
Only write pickle files on systems running s4-connector
Last modified: 2014-05-07 15:26:05 CEST
Ticket#: 2014010721001213 The /var/lib/univention-connector/s4/* pickle files are written on every system that has "univention-s4-connector" installed. In larger environments this may lead to a couple of million files, exceeding the inode limit of filesystems.
Happens again: Ticket #2014040721001333
As discussed with Arvid, we will set an UCR variable on the backup that the files should not be written. Of course only if there is already a running connector in the domain.
The UCR variable connector/s4/listener/disabled has been added. If it is set to true the listener does not write any changes. The variable is not set by default during this upgrade. Code: r49488 + r49490 YAML: r49489 + r49491
Verified: * After update I have connector/s4/listener/disabled is neither set on a DC Backup nor on the DC Master. * After running univention-join again on the DC Backup I have connector/s4/listener/disabled set to true on that system. * Advisory: Ok Just one detail question, probably this is not important?: * The joinscript calls "univention-directory-listener-ctrl resync s4-connector" on the S4 Connector host, which starts the listener even in case it didn't run. * On other systems is uses a "univention-directory-listener crestart", which only restarts the listener only in case it was running.
(In reply to Arvid Requate from comment #4) > Just one detail question, probably this is not important?: > > * The joinscript calls "univention-directory-listener-ctrl resync > s4-connector" on the S4 Connector host, which starts the listener even in > case it didn't run. Yes, that's for the case backup2master. In this case we have to re-sync all changes from OpenLDAP to S4. > * On other systems is uses a "univention-directory-listener crestart", which > only restarts the listener only in case it was running. Ah, you mean the difference between restart and crestart? I think in the backup2master case you defiantly want to restart the listener. But you are right, in most cases we should use restart in the join script for the listener. But I think it is currently not so important.
Ok. I just tried one other thing: On my updated DC Backup I had quite a lot of pickle files below /var/lib/univention-connector/s4 . The I set the variable manually and out of couriosity I manually called "univention-directory-listener-ctrl resync s4-connector". This had the nice effect of cleaning up that directory. So maybe we could do the resync also in the joinscript instead of the crestart? Anyway, just a suggestion.
http://errata.univention.de/ucs/3.2/107.html