[Solved] Univention not reachable after package update

UCS - Univention Corporate Server
1

Hi, after Performing a package update to 4.3-2 errata344 yesterday we encountered some weired Problems today.

The server is doing DNS and DHCP in our Network. This morning some users encountered that their PCs did not receive an IP address from the DHCP Service from the univention server. So I restarted the whole System. Now DHCP adresses are assigned again to the clients but they can not get into the Internet. So I tried to login to the univention Server using putty by IP but due to some reason I can not get a connection using the IP of the server. Ping doesn’t work as well.

The only way connecting to the server is by using the FQDN.

What I recognized is when I send a reboot to the server suddenly for a short period a ping is possible to the server by using the IP address. But I do not know which service is stopped in this moment.

EDIT:
This is the output of /var/log/syslog when shutting down. One of these shutdown steps makes the server reachable again.


Dec  1 18:32:13 mail UMC: Das System wird nun neu gestartet
Dec  1 18:32:13 mail systemd[1]: Stopping pNFS block layout mapping daemon...
Dec  1 18:32:13 mail blkmapd[512]: exit on signal(15)
Dec  1 18:32:13 mail systemd[1]: Stopped target Remote File Systems (Pre).
Dec  1 18:32:13 mail systemd[1]: Stopping NFS server and services...
Dec  1 18:32:13 mail systemd-memcached-wrapper[1828]: Signal handled: Terminated.
Dec  1 18:32:13 mail systemd-memcached-wrapper[2470]: Signal handled: Terminated.
Dec  1 18:32:13 mail systemd[1]: Stopped target Graphical Interface.
Dec  1 18:32:13 mail systemd[1]: Stopped target Multi-User System.
Dec  1 18:32:13 mail systemd[1]: Stopping memcached daemon...
Dec  1 18:32:13 mail systemd[1]: Stopping Make remote CUPS printers available locally...
Dec  1 18:32:13 mail systemd[1]: Stopping memcached univention_saml daemon...
Dec  1 18:32:13 mail systemd[1]: Stopping LSB: saslauthd startup script...
Dec  1 18:32:13 mail systemd[1]: Stopping LSB: Kopano Webmeetings server...
Dec  1 18:32:13 mail systemd[1]: Stopping LSB: Samba Winbind daemon...
Dec  1 18:32:13 mail systemd[1]: Stopped Postfix Mail Transport Agent.
Dec  1 18:32:13 mail systemd[1]: Stopping Postfix Mail Transport Agent (instance -)...
Dec  1 18:32:13 mail systemd[1]: Stopping Clam AntiVirus userspace daemon...
Dec  1 18:32:13 mail systemd[1]: Stopping Login Service...
Dec  1 18:32:13 mail systemd[1]: Stopping The Apache HTTP Server...
Dec  1 18:32:13 mail systemd[1]: Stopping Internet superserver...
Dec  1 18:32:13 mail systemd[1]: Stopping OpenBSD Secure Shell server...
Dec  1 18:32:13 mail systemd[1]: Stopping Kopano Core Storage Server...
Dec  1 18:32:13 mail systemd[1]: Stopping LSB: Univention S4 Connector...
Dec  1 18:32:13 mail systemd[1]: Stopping LSB: Univention Directory Policy...
Dec  1 18:32:13 mail systemd[1]: Stopping LSB: nagios host/service/network monitoring and management system...
Dec  1 18:32:14 mail kernel: [25908.984489] nfsd: last server has exited, flushing export cache
Dec  1 18:32:14 mail systemd[1]: Stopping Suspend/Resume Running libvirt Guests...

Would be good to have some ideas to figure out what happend.

Thanks!

Andy

2

I recently ran a system diagnosis and it shows me the following:

KDC Critical
Die folgenden KDCs waren nicht erreichbar: tcp <fqdn>:88, udp <fqdn>:88 samba/interfaces enthält weder lo noch 127.0.0.1 noch 0.0.0.0.

Gateway critical
Das gateway '192.168.178.1' konnte nicht erreicht werden. Bitte durch Benutzung des [Modul "Netzwerk-Einstellungen"](javascript:void(0)) sicherstellen, dass Gateway- und zusammengehörige Netzwerkeinstellungen korrekt konfiguriert sind. Wenn diese Einstellungen richtig sind liegt das Problem im Gateway selbst: Stellen Sie sicher, dass die Hardware des Gateway-Geräts korrekt funktioniert. PING 192.168.178.1 (192.168.178.1) 56(84) bytes of data. --- 192.168.178.1 ping statistics --- 4 packets transmitted, 0 received, 100% packet loss, time 3053ms

Th funny thing is, that I am connected through the gateway to the server.


Samba replication state
Traceback (most recent call last): File "/usr/lib/pymodules/python2.7/univention/management/console/modules/diagnostic/__init__.py", line 270, 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 148, in run drs = DRSUAPI() File "/usr/lib/pymodules/python2.7/univention/management/console/modules/diagnostic/plugins/41_samba_tool_showrepl.py", line 61, 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 mail.360x.media failed: (-1073741258, 'The transport-connection attempt was refused by the remote system.')


Warning nameserver
1 der konfigurierten Nameserver anworten nicht auf DNS-Anfragen. Bitte sicherstellen, dass die DNS-Einstellungen in [Modul "Netzwerk-Einstellungen"](javascript:void(0)) korrekt konfiguriert sind. Falls das Problem bestehen bleibt stellen Sie sicher, dass der Nameserver mit dem Netzwerk verbunden ist und die DNS-Forwarder das Internet erreichen können (www.univention.de). Der Nameserver 192.168.178.1 (UCR Variable 'dns/forwarder1') ist nicht ansprechbar: Eine Zeitüberschreitung trat beim Erreichen des Nameservers auf (ist er online?).

So in the end it tells me what I am already knowing, that some module is blocking outgoing and incoming traffic by IP address. But how can I find out which one it is?

Andy