Tests can't connect to service

[greg nicol]

I've got a pipeline unit test script that uses 2 services, postgresql and samba. I'm accessing them by 127.0.0.1 as suggested, not localhost. I've got a sleep 15 infront of the tests and an nmap shows ports open and services up. Tests can connect to the database service just fine, but can not connect to the samba service.

+ nmap -v -sT 127.0.0.1
Starting Nmap 7.70 ( https://nmap.org ) at 2018-08-21 14:02 UTC
Initiating Connect Scan at 14:02
Scanning localhost (127.0.0.1) [1000 ports]
Discovered open port 22/tcp on 127.0.0.1
Discovered open port 445/tcp on 127.0.0.1
Discovered open port 139/tcp on 127.0.0.1
Discovered open port 135/tcp on 127.0.0.1
Discovered open port 3268/tcp on 127.0.0.1
Discovered open port 49153/tcp on 127.0.0.1
Discovered open port 5432/tcp on 127.0.0.1
Discovered open port 389/tcp on 127.0.0.1
Discovered open port 49154/tcp on 127.0.0.1
Discovered open port 3269/tcp on 127.0.0.1
Discovered open port 464/tcp on 127.0.0.1
Discovered open port 636/tcp on 127.0.0.1
Discovered open port 88/tcp on 127.0.0.1
Discovered open port 49152/tcp on 127.0.0.1
Completed Connect Scan at 14:02, 0.04s elapsed (1000 total ports)
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00013s latency).
Not shown: 986 closed ports
PORT      STATE SERVICE
22/tcp    open  ssh
88/tcp    open  kerberos-sec
135/tcp   open  msrpc
139/tcp   open  netbios-ssn
389/tcp   open  ldap
445/tcp   open  microsoft-ds
464/tcp   open  kpasswd5
636/tcp   open  ldapssl
3268/tcp  open  globalcatLDAP
3269/tcp  open  globalcatLDAPssl
5432/tcp  open  postgresql
49152/tcp open  unknown
49153/tcp open  unknown
49154/tcp open  unknown

RAN: /usr/bin/ldapadd -c -x -H ldap://127.0.0.1 -D CN=Administrator,CN=Users,DC=padnag,DC=dev -w Password1 -f /root/ad_users.add.ldif
  STDOUT:
  STDERR:
ldap_result: Can't contact LDAP server (-1)

I've run out of ideas how to debug / resolve this.

[Philip Hodder]

Hi Greg,

Is there anything of interest in the logs of your Samba service container?

Do you need to specify any specific ports when running ldapadd, or do the defaults match with what samba is using?

I can't see any reference to samba in the output of 'nmap'. Is that expected, or should it be there?

Thanks,

Phil

[greg nicol]

Thanks. It's Samba AD active directory on the default port 389. It's all works under docker-compose. I'll try bump the verbosity on the logs and see if something shows up.

[greg nicol]

Bingo! found this in the logs which I've seen before.

set_nt_acl_no_snum: fset_nt_acl returned NT_STATUS_ACCESS_DENIED.

With docker-compose I had to pass --privileged to docker run. Is there a pipelines equivalent available?