Samba registry values

UCS - Univention Corporate Server
#1

Hey,
After migrating UCS 4.2 to 4.3, I noticed in the registry that these values remain old.

samba

Best Regards,
Michael Voigt

#2

Hey,

what’s the output of the following commands:

univention-app info
univention-ldapsearch -b cn=samba4,cn=apps,cn=univention,$(ucr get ldap/base) dn univentionAppID univentionAppVersion
dpkg -l | grep '^ii.*samba'

Kind regards,
mosu

#3

Hey,

follows below:

root@servidor:~# univention-app info
UCS: 4.3-0 errata0
Installed: cups=2.2.1 dhcp-server=12.0 kde=5.8 nagios=4.3 pkgdb=11.0 printquota=10.0 samba4=4.7 self-service=3.0
Upgradable:
___________________________________________________________________________________
root@servidor:~# univention-ldapsearch -b cn=samba4,cn=apps,cn=univention,$(ucr                                                                                         get ldap/base) dn univentionAppID univentionAppVersion
# extended LDIF
#
# LDAPv3
# base <cn=samba4,cn=apps,cn=univention,dc=goes,dc=lan> with scope subtree
# filter: (objectclass=*)
# requesting: dn univentionAppID univentionAppVersion
#

# samba4, apps, univention, goes.lan
dn: cn=samba4,cn=apps,cn=univention,dc=goes,dc=lan

# samba4_4.6, samba4, apps, univention, goes.lan
dn: univentionAppID=samba4_4.6,cn=samba4,cn=apps,cn=univention,dc=goes,dc=lan
univentionAppID: samba4_4.6
univentionAppVersion: 4.6

# search result
search: 3
result: 0 Success

# numResponses: 3
# numEntries: 2
___________________________________________________________________________________
root@servidor:~# dpkg -l | grep '^ii.*samba'
ii  python-samba                                        2:4.7.5-1A~4.3.0.201803140017                    amd64        Python bindings for Samba
ii  samba                                               2:4.7.5-1A~4.3.0.201803140017                    amd64        SMB/CIFS file, print, and login server for Unix
ii  samba-common                                        2:4.7.5-1A~4.3.0.201803140017                    all          common files used by both the Samba server and client
ii  samba-common-bin                                    2:4.7.5-1A~4.3.0.201803140017                    amd64        Samba common files used by both the server and the client
ii  samba-dsdb-modules                                  2:4.7.5-1A~4.3.0.201803140017                    amd64        Samba Directory Services Database
ii  samba-libs:amd64                                    2:4.7.5-1A~4.3.0.201803140017                    amd64        Samba core libraries
ii  samba-vfs-modules                                   2:4.7.5-1A~4.3.0.201803140017                    amd64        Samba Virtual FileSystem plugins
ii  univention-nagios-samba                             3.0.0-1A~4.3.0.201712120054                      amd64        nagios plugin for UCS samba
ii  univention-newsid                                   9.0.0-1A~4.3.0.201712120245                      amd64        UCS - generate a new samba sid
ii  univention-samba-local-config                       12.0.1-1A~4.3.0.201802271540                     all          UCS - UCR Extensions for configuration of local shares
ii  univention-samba4                                   7.0.2-6A~4.3.0.201803011601                      amd64        UCS - Samba4 integration package
ii  univention-samba4-sysvol-sync                       7.0.2-6A~4.3.0.201803011601                      all          UCS - Samba4 sysvol synchronization
#4

Hey,

thanks. Please try running univentoin-app register samba4 and univention-run-join-scripts Then look at the UCR variables and the output of that LDAP search command again and see if the numbers are updated.

Kind regards,
mosu

#5

Mosu,

I did what you said.
Now he’s set the record. Maybe this is not happening automatically when upgrading from 4.2 to 4.3

Best Regards,
Michael

#6

The app registration is not done automatically when updating to UCS 4.3, that is a known issue. It will be fixed with an errata update.

#7

Wonderful

Best regards,
Michael Voigt

Mastodon