After update from 4.3.2 to 4.3.3 I can't reach the server any more

UCS - Univention Corporate Server
1

Hello
After updating to 4.3.3. I can’t reach the server anymore… The address and interfaces are correct, pinging works, but I have the following errors in the system diagnostics ;

Problem : Samba Replikations Status
Traceback (most recent call last):
  File "/usr/lib/pymodules/python2.7/univention/management/console/modules/diagnostic/__init__.py", line 275, in execute
    result = execute(umc_module, **kwargs)
  File "/usr/lib/pymodules/python2.7/univention/management/console/modules/diagnostic/plugins/41_samba_tool_showrepl.py", line 149, in run
    drs = DRSUAPI()
  File "/usr/lib/pymodules/python2.7/univention/management/console/modules/diagnostic/plugins/41_samba_tool_showrepl.py", line 62, in __init__
    drs_tuple = drs_utils.drsuapi_connect(self.server, self.load_param, self.credentials)
  File "/usr/lib/python2.7/dist-packages/samba/drs_utils.py", line 56, in drsuapi_connect
    raise drsException("DRS connection to %s failed: %s" % (server, e))
drsException: drsException: DRS connection to ucsmaster1.turpelschank.intranet failed: (-1073741258, 'The transport-connection attempt was refused by the remote system.')

I really would appreciate help

2

Moin,

we prefer English for our international users, so please switch the language (you might use some translator tools…).

You say “I can not reach the server, except ping”. How is you infrastructure configured?
Do you have a single server?
On which of these servers did you get the above messages?
Looks like your samba on ucsmaster1.turpelschrank.intranet did not start properly. Could you do so manually on this host (connect ie through putty):
/etc/init.d/samba restart

Any output? What do you see in /var/log/samba/log.samba?

/CV

3

Thanks for the reply
Samba is running an listening on port 88.

4

Hi,

IF Samba is really listening on port 88 you have configured your system in a very, very strange way!

To allow us to help you should give us the information we request, not any other possibly misleading information we have not asked for.

/CV

5

Hi,
I’m now near the machine…
Here /var/log/samba/log.samba after rerstart

[2018/12/20 10:26:14.636631,  0, pid=2045] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
[2018/12/20 10:26:14.636644,  0, pid=2937] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
[2018/12/20 10:26:14.636641,  0, pid=2047] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2045 on SIGTERM
  Exiting pid 2937 on SIGTERM
  Exiting pid 2047 on SIGTERM
[2018/12/20 10:26:14.636693,  0, pid=2044] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
[2018/12/20 10:26:14.636692,  0, pid=2040] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2044 on SIGTERM
  Exiting pid 2040 on SIGTERM
[2018/12/20 10:26:14.636960,  0, pid=2039] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2039 on SIGTERM
[2018/12/20 10:26:14.640802,  0, pid=2037] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2037 on SIGTERM
[2018/12/20 10:26:14.641301,  0, pid=2036] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2036 on SIGTERM
[2018/12/20 10:26:14.641424,  0, pid=2035] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2035 on SIGTERM
[2018/12/20 10:26:14.641557,  0, pid=2033] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2033 on SIGTERM
[2018/12/20 10:26:14.641645,  0, pid=2031] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2031 on SIGTERM
[2018/12/20 10:26:14.641930,  0, pid=2029] ../source4/smbd/process_standard.c:86(sigterm_signal_handler)
  Exiting pid 2029 on SIGTERM
[2018/12/20 10:26:18.340730,  0, pid=16584] ../source4/smbd/server.c:448(binary_smbd_main)
  samba version 4.7.8-Debian started.
  Copyright Andrew Tridgell and the Samba Team 1992-2017
[2018/12/20 10:26:18.540076,  0, pid=16585] ../source4/smbd/server.c:620(binary_smbd_main)
  samba: using 'standard' process model
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
[2018/12/20 10:26:18.564800,  0, pid=16585] ../lib/util/become_daemon.c:124(daemon_ready)
  STATUS=daemon 'samba' finished starting up and ready to serve connections
samba: setproctitle not initialized, please either call setproctitle_init() or link against libbsd-ctor.
[2018/12/20 10:26:33.591356,  1, pid=16615] ../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on DC=ForestDnsZones,DC=turpelschank,DC=intranet and looking for deleted objects
[2018/12/20 10:26:33.593120,  1, pid=16615] ../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on DC=DomainDnsZones,DC=turpelschank,DC=intranet and looking for deleted objects
[2018/12/20 10:26:33.596027,  1, pid=16615] ../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on CN=Configuration,DC=turpelschank,DC=intranet and looking for deleted objects
[2018/12/20 10:26:33.633076,  1, pid=16615] ../source4/dsdb/kcc/garbage_collect_tombstones.c:68(garbage_collect_tombstones_part)
  Doing a full scan on DC=turpelschank,DC=intranet and looking for deleted objects
[2018/12/20 10:26:38.596562,  0, pid=16617] ../source4/dsdb/dns/dns_update.c:290(dnsupdate_nameupdate_done)
  ../source4/dsdb/dns/dns_update.c:290: Failed DNS update - with error code 110
6

I am still missing important information I have asked for…

Error Code means: 110 = ETIMEDOUT (Connection timed out)

Is this the end of the logfile? Looks like there are some following lines missing.

/CV

7

Hello
This is the end of the logfile, a small time after restarting Samba. /etc/init.d/samba restart gives no error message.
For this afternoon I have no more access to the server,but I will have tomorrow morning a look to see if there are other messages.
thx

8

You can also check for “red” services in systemctl .