System operational

Past Incidents

30th April 2017

No incidents reported

29th April 2017

No incidents reported

28th April 2017

No incidents reported

27th April 2017

No incidents reported

26th April 2017

No incidents reported

25th April 2017

Other Servers Outage of one web-cluster server
  • 2017-04-25 05:07: One web-cluster server (DE) went Offline.
  • 2017-04-25 09:00: Server did not recover as in previous incidents.
  • 2017-04-25 09:47: Outage reported as Ticket 339470-527516-78 to VPS provider (Webtropia).
  • 2017-04-25 12:22: Restart of VPS via web front-end seems not successful.
  • 2017-04-25 13:50: Feedback from VPS provider (http://webtropia-status.de/de/919/) about the outage
  • 2017-04-25 15:18: VPS seems running but inaccessible. Investigation shows corrupt/missing/empty configuration files.
  • 2017-04-26 11:40: No feedback from VPS provider about the damaged vServer.
  • 2017-04-26 17:15: Feedback vom VPS provider: There was a data loss and I should just reinstall my vServer. Seems acceptable for Webtropia.
  • 2017-04-26 17:23: At this point, the Server was taken off the web-cluster as of its unknown state. A first check revealed a lot of missing files from configuration files as well as binary files of the operating system. Additionally the support of Webtropia disabled the firewall and exposed services to public access (see Ticket 339470-527896-30 ). As of this, this vServer is considered insecure and unusable at the current state. Reinstallation is needed before the server can be returned to the web-cluster.
  • 2017-05-06 : Removed the server from cluster and triggered reinstallation of the OS to avoid any further problems with the corrupt data on the server.

24th April 2017

Virtualisation Host Scheduled restart of Virtualisation infrastructure

Due to a change in the data center, a shutdown is required to move the visualization server to another Rack. This shutdown will cause all VM's to be off-line during the time of the data center work.

  • Scheduled date: 2017-04-24
  • Scheduled start time: approx. 16:00
  • Expected duration: approx. 2-4 hours

To follow the progress of the scheduled maintenance, visit https://status.cm.tinned-software.net/.

2017-04-24 19:00: Most services restored. VM with full-disk-encryption are not yet up and running.

2017-04-24 20:50: All systems operational again. VM's requiring a disc-encryption password are booted.