-7
Something gone bad
(no.lastname.nz)
Oh well good by:
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 19 Feb 2024
-7 points (31.6% liked)
Selfhosted
39677 readers
548 users here now
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
founded 1 year ago
MODERATORS
Weird. netin was busy, yet the bottom of the screen implies more outbound traffic (I guess it's connected the other way around?)
And the log looks like a SMB/CIFS issue... maybe not the interweb?
But, it definitely looks like something got stuck in a loop and triggered a memory leak.
Whatever VM / CT was using CPUs 7 & 10 at the time was the problem... find that and you'll find the next step down the rabbit hole...
It looks like it was a Plex scan that tied it's self up in knots and locked up the SMB share and it just happened that it was the QBT container that I noticed it on first.
Some of the logs did mention Plex was soft locked as well.