Downtime on 2026-03-14
So uh.. I unfortunately opened up an old, compressed logfile of 1 GB size compressed, and typed Shift + g, to scroll to the end of the file. Unfortunately it was about 20 GB in size uncompressed. So the server behind FP kept on churning through the file, and as it hit it's RAM limit it started swapping to disk (using swap ram) while simultaneously decompressing the log file in chunks... My connection aborted and FP came to a stand still. Unexpectedly FP did not recover from this within 10 hours so our Owner swammy had to restart the hardware behind the server by hand. Which resolved the issue.
Thanks swammy.
I shall not try to scroll through a compressed logfile again, with no limitations set through c-group settings (with limits for cpu cycles or ram usage). Instead I should download such files in-before.
I apologize.
So uh.. I unfortunately opened up an old, compressed logfile of 1 GB size compressed, and typed Shift + g, to scroll to the end of the file. Unfortunately it was about 20 GB in size uncompressed. So the server behind FP kept on churning through the file, and as it hit it's RAM limit it started swapping to disk (using swap ram) while simultaneously decompressing the log file in chunks... My connection aborted and FP came to a stand still. Unexpectedly FP did not recover from this within 10 hours so our Owner swammy had to restart the hardware behind the server by hand. Which resolved the issue.
Thanks swammy.
I shall not try to scroll through a compressed logfile again, with no limitations set through c-group settings (with limits for cpu cycles or ram usage). Instead I should download such files in-before.
I apologize.