FeM e.V. Infrastructure and System Status
This page shows an overview of the status of infrastructure, services and systems of FeM e.V.
Please keep in mind that all helpers do this voluntarily in their free time. Therefore, there are no guarantees for any given timelines or time estimations.
If you have any questions or specific problems, feel free to send us a ticket via our helpdesk: https://helpdesk.fem.tu-ilmenau.de.
Some systems are experiencing issues.
-
-
Internet Uplink
OperationalLast updated 2026-08-23 21:59:06 -
Wireless (Aruba system)
House B, C, D, E, H, I, K, L, N, P, Q, CJD and FeM-Office
OperationalLast updated 2026-07-28 17:49:29 -
Wired
Ethernet sockets
OperationalLast updated 2026-01-19 23:58:28 -
Network Management
FeM AdminDB and network services (DHCP, DNS...)
OperationalLast updated 2026-04-23 21:48:54
-
-
-
Helpdesk
OperationalLast updated 2026-01-30 15:05:44 -
Storage systems
Storage systems for servers (e.g. Ceph, ha-storage)
OperationalLast updated 2026-01-17 14:09:13 -
Monitoring
All monitoring systems, e.g. Icinga, Grafana, ...
OperationalLast updated 2025-11-04 14:15:17 -
Databases
OperationalLast updated 2026-08-23 19:28:39 -
VM-Hosts
OperationalLast updated 2026-08-23 19:28:40 -
Mailserver
Mail servers, inboxes & list systems
OperationalLast updated 2026-01-30 15:05:22 -
Webcluster
OperationalLast updated 2026-08-23 19:28:38
-
-
-
Mastodon
Federated social network
Last updated 2026-05-10 14:39:06 -
Mattermost
Internal Messenger
OperationalLast updated 2026-08-23 19:28:41 -
Pretix
A Service to Sell Tickets and Manage Events
OperationalLast updated 2026-08-23 19:28:42 -
Dist-Mirror
A Mirror for some selected Linux Distributions
OperationalLast updated 2025-10-31 12:35:48 -
XMPP
XMPP / Jabber Instant Messaging
OperationalLast updated 2026-05-05 23:21:05 -
FeMCI
FeM Content Infrastructure
OperationalLast updated 2026-08-23 19:28:43 -
Homepage
Our homepage
OperationalLast updated 2026-05-22 15:00:39 -
Matrix
Federated Instant Messaging
OperationalLast updated 2026-08-23 19:28:44
-
Past incidents
Kea DHCP field test in house N
We are planning to migrate to Kea as our new DHCP server software. Previous tests in more isolated networks have shown that the DHCP server should behave as expected. The next step is a field test where we set up Kea as the DHCP server for house N.
While we are migrating the network to Kea DHCP, users must expect outages of up to 30 minutes, while the configurations on the switches are updated and DHCP relaying for Kea is set up.
No incidents reported.
No incidents reported.
No incidents reported.
Fixed
Our Mailserver is unable to receive emails from other mailservers or forward emails submitted from users. We are investigating the situation. The current assumption is that the database behind the mailserver might be broken or unreachable.
Update 16:39
We have successfully tested other components which are using the database cluster in question. It is unlikely that the database is the source of the problems.
Update 18:00
We have identified a misconfiguration in the mailserver system. The mailing list software tried to connect to the database using a target IP address, which was not the high-availability IP. Thus, during maintenance on the database cluster, the mailing list software was now unable to connect to the database when that one node with the right IP address went offline.
Resolution
The mailserver config has been adjusted so that the highly available IP address will be used in the future. This should prevent an outage like this in the future.
No incidents reported.
No incidents reported.