Occasionally you'll see this fellow on your visit to our site. Whenever this happens we've made a mistake. This page is here to help you understand what went wrong and (hopefully) give you a sense that we're constantly improving. If you find any problems using the site please report a bug here
We hope you won't have to refer to this page too often. :)
NotABug.org was completey unreachable for most of the 31st of August and the 1st of September. The frontend was not reachable, git pulls and pushes were not possible.
Due to a bad DIMM and non-ECC RAM in the server the filesystem of the main gogs repository got corrupted. This had to be restored from backup. No data was lost, however
NotABug.org was completey unreachable for most of the 31st of January and the 1st of February. The frontend was not reachable, git pulls and pushes were not possible.
Due to a drive failure in the array the filesystem housing the Git repositories went in read-only mode. During recovery of the situation a admin-error accidentally deleted the root filesystems of both the hypervisor and the NotABug.org VM. Due to this error the SSH key of the server was changed. The new fingerprints are:
NotABug.org web front-end was throwing 500 errors for most of the day. It seems git pushes also did not work.
Someone has flooded the Gogs install with thousands of new user registrations. We were effectively suffering a denial of service attack.
NotABug.org web front-end was down between 19:00 and 19:30 CEST. It was impossible to view any of the NotABug.org web content. Git pulls and pushes were unaffected.
The Gogs software crashed and the monitoring software responsible for restarting it automatically was still faulty. We now know that the problem was that the gogs daemon expects to be able to read the current userid from the $USER environment variable. This only works if the init script is started with the shell runing in bash mode. The init script was called with /bin/sh when running non-interactively (during startup and during the monitor cron job).
NotABug.org web front-end was down between 17:00 and 19:00 CEST. It was impossible to view any of the NotABug.org web content. Git pulls and pushes were unaffected.
The Gogs software crashed and the monitoring software responsible for restarting it automatically was faulty causing a restart loop.
NotABug.org web front-end was down between 17:00 and 18:00 CEST. It was impossible to view any of the NotABug.org web content. Git pulls and pushes were unaffected.
We currently believe that a bad merge of one of Gogs' dependencies caused a problem with the application. At the time the only person who could fix the problem was off at a party. There was no monitoring. Additionally the error page offered no recourse making it seem like we had just gone away.