Outage: Jupyter-Cloud

The restart of the service Jupyter-Cloud resolved problems with regard to launching of
notebook servers. Tests showed that server can be launched again.
The restart was necessary in order to clear faulty session information for a large number
of users that appeared after the outage this morning.

Pending support tickets will be answered in short while.

For a number of users starting notebook servers currently fails with an error 503.
In order to rectify the issue the service unfortunately needs to be restarted between
2.10-2.25pm. Running notebooks will be terminated in the process.
This is necessary to delete invalid session information in order to allow affected users
to start their notebook servers again.

The service Jupyter-Cloud suffered an outage over night till 10.15 am because the file
system for user data was used up completely.
As a result no notebook servers could be launched although login on the service was
successful.
The file system has now been grown and the service is fully available again.

Usually resource usage of the service is monitored and resources are increased with rising
demand. Why this went unnoticed in this case is still under investigation.

The service Jupyter-Cloud currently suffers an outage because the file system for user
data has been used up completely. An increase will be made as soon as possible.