All systems are operational.
This page shows an overview of our system status.
Please keep in mind that all helpers do this voluntarily in their free time.
If you have any questions or specific problems, feel free to open a ticket in our helpdesk.
Last updated 2025-08-22 00:52:06
Last updated 2025-08-22 10:03:58
House A, CJD
Last updated 2025-08-22 11:07:30
House B, C, D, E, H, I, K, L, N, P, Q and FeM-Office
Last updated 2025-09-11 22:19:35
FeM AdminDB and network services (DHCP, DNS...)
Last updated 2025-09-01 18:43:59
Last updated 2025-09-01 18:44:00
Mail servers, inboxes & list systems
Last updated 2025-09-01 18:43:58
Last updated 2025-08-22 00:52:02
Last updated 2025-09-01 18:43:59
Storage systems for servers (e.g. Ceph, ha-storage)
Last updated 2025-07-13 21:19:41
Federated social network
View DetailsLast updated 2025-05-15 16:21:07
A Service to Sell Tickets and Manage Events
View DetailsLast updated 2019-08-19 18:39:41
A Mirror for some selected Linux Distributions
View DetailsLast updated 2025-07-13 21:19:42
A Browser based Video-Conferencing Software
View DetailsLast updated 2025-02-16 10:03:47
XMPP / Jabber Instant Messaging
View DetailsLast updated 2019-12-11 11:52:44
FeM Content Infrastructure
View DetailsLast updated 2025-07-14 07:06:00
Our homepage
View DetailsLast updated 2024-10-17 12:36:00
Federated Instant Messaging
View DetailsDuring updates of lower campus VM host cluster, the experimental Kea DHCP nodes, which are currently providing DHCP for house N in a field test went down.
Normally, the HA mechanism should have prevented this, as one node was kept alive at all times. However, the first node didn't start again due to a software bug killing the DHCP server if it was unable to connect to the local database and the system not having automatic restarts on failure enabled.
As soon as the problem was noticed, it could be fixed by simply restarting the nodes, as they now were able to connect to their database servers.