8 / 8
May 2024

Dear Support!

We have a really bad issue with the latest update (23.1.20240430). After login the calendar throw an error:

/usr/share/egroupware/api/src/Accounts/LdapVIvSortRequestTrait.php (145)

All other modules like mail, address book are working properly.

Downgrade to 23.1.20240304-2 solve this.

Can you help with this? This is an urgent issue!

Thank you!

BR.,
Z

  • created

    May '24
  • last reply

    May '24
  • 7

    replies

  • 528

    views

  • 2

    users

  • 4

    likes

  • 7

    links

The error is caused by the following change:

Thought it’s not clear to my, why the LDAP query returns an error in the first place.

Please run /etc/egroupware-docker/egroupware-logs.sh while the error happens, and post the Log here.

Btw. what type of ActiveDirectory Controller do you have (Samba4 or Windows) and what version?

Ralf

Hi Ralf!

We have Samba4 AD. Version is 4.15.

I will check this log sh in test environment.

BR.,
Z

Ok, Samba 4, the customer I just talked with, also has a Samba4.

Still puzzled, why the error, which was previously silently ignored, happens i the first place …

Ralf

Ok, no need for your log, got it from an other customer.

Looking into it right now.

Please stay on the previous version. I let you know, once it’s fixed.

Ralf

If you need a test DC you can use this (filll IP address with your IP, administrator pwd: Member22%):

docker-compose.yml:

version: '3.7'

services:
  samba:
    build: .
    container_name: samba-dc01
    volumes:
      - /etc/localtime:/etc/localtime:ro
      - './samba-dc01/tls:/var/lib/samba/private/tls'
      - './samba-dc01/data:/var/lib/samba/'
      - './samba-dc01/log:/var/log/samba'
    environment:
      - TZ=Europe/Budapest
      - DOMAIN=DEV.TEST
      - DOMAIN_NETBIOS=DEV
      - DOMAIN_PASS=Member22%
      - HOSTIP=X.X.X.X
      - HOSTNAME=dc
      - JOIN=false
#      - JOIN_SITE=Site0
      - NTPSERVERLIST=0.pool.ntp.org 1.pool.ntp.org 2.pool.ntp.org
      - FEATURE_RECYCLEBIN=true
      - FEATURE_KERBEROS_TGT=true
      - DISABLE_MD5=true
      - DISABLE_PWCOMPLEXITY=true
      - ENABLE_CUPS=false
      - ENABLE_DNSFORWARDER=8.8.8.8
      - ENABLE_DYNAMIC_PORTRANGE=49152-49170
      - ENABLE_INSECURELDAP=true
      - ENABLE_LAPS_SCHEMA=true
      - ENABLE_LOGS=true
      - ENABLE_MSCHAPV2=true
      - ENABLE_RFC2307=true
      - TLS_ENABLE=false
      - DEBUG_ENABLE=true
      - DEBUGLEVEL=1
      - BIND_INTERFACES_ENABLE=false
      - BIND_INTERFACES=eth1
    ports:
      - 53:53
      - 53:53/udp
      - 88:88
      - 88:88/udp
      - 123:123
      - 135:135
      - 137-138:137-138/udp
      - 139:139
      - 389:389
      - 389:389/udp
#      - 445:445
      - 464:464
      - 464:464/udp
      - 636:636
      - 3268-3269:3268-3269
      - 49152-49170:49152-49170
    dns_search:
      - DEV.TEST
    dns:
      - 127.0.0.1
    extra_hosts:
      - dc dc.dev.test:x.x.x.x
    hostname: dc
    domainname: DEV.TEST
#    cap_add:
#      - NET_ADMIN
#      - SYS_NICE
#      - SYS_RESOURCE
#      - SYS_TIME
#    devices:
#      - /dev/net/tun
    privileged: true

Command: docker compose up -d
If you work with windows, you can manage AD users with this free tool: https://sourceforge.net/projects/ldapadmin/

On linux (or console in container): https://www.tecmint.com/manage-samba4-active-directory-linux-command-line/

BR.,
Z

Ok, the problem ist fixed now:

It only happens if your own account was not returned in the first query, as the 2nd query (only querying your own account) contained a syntax error / one missing bracket:

You can apply the above commit to your container, or wait until I’ve build a patch container with the fix.

Ralf

Ok, there is now a patched container with tags “23.1.20240430-2” and rolling tags “23.1” and “latest”.

So you can switch your tag back to “23.1”, docker-compose pull && docker compose up -d

Ralf