Problem with systemd-journal after upgrade to ucs 4.3-4 from 4.3-3

UCS - Univention Corporate Server
1

hi, I just updated ucs from 4.3-3 to 4.3-4 when the following problems appeared:

  1. systemd-journal hog my memory & cpu
  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     TIME+ COMMAND
29261 root      20   0 8433384 1.393g 1.388g S   5.9 36.1  11:26.21 systemd-journal
  1. lots of : systemd[25295]: Failed to open directory /dev/null/.config/systemd/user/run-user-7002.mount.wants: Not a directory

is there a different workaround to change the home directory of computer accounts?

ps: if I try to modify a computer account:

udm computers/computer modify --dn cn=testwin,cn=computers,dc=test,dc=lab --set unixhome=/var/tmp/computer

WARNING: No attribute with name ‘unixhome’ in this module, value not set.
Modify computers/computer not allowed

2

Hey,

yeah, I’ve used ldapmodify for changing the accounts on our systems. First iterate over all computer objects with home directory /dev/null and create the appropriate LDIF file:

univention-ldapsearch -o ldif-wrap=no objectClass=univentionWindows dn | \
  grep '^dn:' | {
  while read DN ; do
    cat <<EOF
$DN
changetype: modify
replace: homeDirectory
homeDirectory: /var/empty

EOF
  done
} > home_dir_changes.ldif

Next take a look at home_dir_changes.ldif. If those look OK, apply the changes:

ldapmodify -D cn=admin,$(ucr get ldap/base) -y /etc/ldap.secret -f home_dir_changes.ldif

I suggest you don’t use anything beneath /tmp or /var/tmp in any permanent manner as those directories might be cleaned/cleared. Just create an empty directory in a more permanent place, e.g. /var/empty

1 Like
3

I just noticed that there’s a nice article by Christian about filtering a lot of those unimportant messages caused by computer logins:

That filtering can be used instead of or in addition to changing the home directory. Obviously it filters a lot more messages than just the “Not a directory” ones.

4

hi, I disabled systemd log altogether, but I don’t understand what has changed since release 4.3-2 where all these problems were not there. :thinking: