[Pkg-samba-maint] Bug#918432: Bug#918432: samba: net ads join to armel arch Samba DC failed

[Mathieu Parent]

Control: forwarded -1 https://bugzilla.samba.org/show_bug.cgi?id=13755

Hi Tomasz,

Please keep the bug CC-ed.

Le mer. 9 janv. 2019 à 21:03, Tomasz Jeliński <tjelinski at gmail.com> a écrit :
>
>
> W dniu 09.01.2019 o 04:56, Mathieu Parent pisze:
> > Le dim. 6 janv. 2019 à 01:12, Tomasz Jelinski <tjelinski at gmail.com> a écrit :
> >> Package: samba
> >> Version: 2:4.5.12+dfsg-2+deb9u4
> >> Severity: normal
> >>
> >> Dear Maintainer,
> > Hi,
> Hi,
> >> I can't connect workstation to samba DC configured on Orion platform
> >> (armel arch) with installed  Debian Stretch (packages are fully updated to newest avaliable versions).
> > Are you able to reproduce this from Debian testing (4.9.4)?
> >
> Today I upgraded samba to testing on device which trying to acts as
> samba AD DC (QNAP TS-209 armel arch). I cleaned samba databases
> (ldb,tdb) and performed DC provision from scratch. I acknowledge that
> problem still exists and I can reproduce this on samba packages from
> Debian testing repository (attachment - netadsjoin.log)

OK.

> System Information  from QNAP TS-209 samba AD-DC:
>
> Package: samba
> Version: 3:4.9.4+dfsg-1
>
> Debian Release: 10.6
>   APT prefers testing
>   APT policy: (561, 'testing'), (550, 'stable'), (510,
> 'stable-updates'), (500, 'stable')
> Architecture: armel (armv6tel)
>
> Kernel: Linux 4.9.0-8-marvell
> Locale: LANG=pl_PL.UTF-8, LC_CTYPE=pl_PL.UTF-8 (charmap=UTF-8),
> LANGUAGE=pl_PL.UTF-8 (charmap=UTF-8)
> Shell: /bin/sh linked to /bin/dash
> Init: systemd (via /run/systemd/system)
>
> Versions of packages samba depends on:
> ii  adduser           3.115
> ii  dpkg              1.18.25
> ii  libbsd0           0.8.3-1
> ii  libc6             2.28-2
> ii  libldb1           2:1.5.1+really1.4.3-1
> ii  libpam-modules    1.1.8-3.6
> ii  libpam-runtime    1.1.8-3.6
> ii  libpopt0          1.16-10+b2
> ii  libpython2.7      2.7.13-2+deb9u3
> ii  libtalloc2        2.1.8-1
> ii  libtdb1           1.3.16-2+b1
> ii  libtevent0        0.9.37-1
> ii  lsb-base          9.20161125
> ii  procps            2:3.3.12-3+deb9u1
> ii  python            2.7.13-2
> ii  python-dnspython  1.15.0-1
> ii  python-samba      2:4.9.4+dfsg-1
> ii  python2.7         2.7.13-2+deb9u3
> ii  samba-common      2:4.9.4+dfsg-1
> ii  samba-common-bin  2:4.9.4+dfsg-1
> ii  samba-libs        2:4.9.4+dfsg-1
> ii  tdb-tools         1.3.11-2
>
> Versions of packages samba recommends:
> ii  attr                1:2.4.47-2+b2
> ii  logrotate           3.11.0-0.1
> ii  samba-dsdb-modules  2:4.9.4+dfsg-1
> ii  samba-vfs-modules   2:4.9.4+dfsg-1
>
> Versions of packages samba suggests:
> pn  bind9          <none>
> pn  bind9utils     <none>
> pn  ctdb           <none>
> ii  ldb-tools      2:1.1.27-1+b1
> ii  ntp            1:4.2.8p10+dfsg-3+deb9u2
> pn  smbldap-tools  <none>
> ii  ufw            0.35-4
> ii  winbind        2:4.9.4+dfsg-1
>
> -- no debconf information
>
> Workstation has a samba stable version - 2:4.5.12+dfsg-2+deb9u4. I
> suppose that problem is related to armel architecture because I can
> perform 'net ads join' from my workstation to samba DC stable version
> 2:4.5.12+dfsg-2+deb9u4 , configured in the same way on amd64 arch
> (tested on Debian Stretch VM in Virtualbox)

So, you have upgraded the server, but not the workstation. What if you
test with a testing/sid armel?

Regards

-- 
Mathieu Parent