FeM e.V. Infrastructure and System Status

Some systems are experiencing issues.

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.

If you have any questions or specific problems, feel free to send us a ticket via our helpdesk: https://helpdesk.fem.tu-ilmenau.de.

  • Internet Uplink

    Last updated 2026-03-19 19:44:57
  • Wireless (Freescale system)

    House A, CJD

    Last updated 2025-11-03 20:55:28
  • Wireless (Aruba system)

    House B, C, D, E, H, I, K, L, N, P, Q and FeM-Office

    Last updated 2026-05-21 22:38:41
  • Wired

    Ethernet sockets

    Last updated 2026-01-19 23:58:28
  • Network Management

    FeM AdminDB and network services (DHCP, DNS...)

    Last updated 2026-04-23 21:48:54
  • Mastodon

    Federated social network

    Operational
    Last updated 2026-05-10 14:39:06
  • Mattermost

    Internal Messenger

    Last updated 2025-10-31 12:35:48
  • Pretix

    A Service to Sell Tickets and Manage Events

    Last updated 2025-10-31 12:35:48
  • Dist-Mirror

    A Mirror for some selected Linux Distributions

    Operational
    Last updated 2025-10-31 12:35:48
  • Jitsi

    A Browser based Video-Conferencing Software

    Last updated 2026-06-07 00:01:18
  • XMPP

    XMPP / Jabber Instant Messaging

    Operational
    Last updated 2026-05-05 23:21:05
  • FeMCI

    FeM Content Infrastructure

    Last updated 2025-12-12 09:58:46
  • Homepage

    Our homepage

    Last updated 2026-05-22 15:00:39
  • Matrix

    Federated Instant Messaging

    Last updated 2026-02-22 09:15:18

Past Incidents

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

No incidents reported.

3 years ago ยท
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.